Closed ohr closed 8 years ago
I find this idea very opportune and will be happy to contribute starting from mid-November.
Sounds great - I'll see if I have some time too
Sorry, occasionally committed a fix for #89 here.
Created a "fhir" branch for ipf and ipf-oht-atna.
Initial scope is to provide generic FHIR capabilities (component, endpoint) based on DSTU2 and the HAPI FHIR library, as well as an ITI-83 (Mobile PIX Query) component and translators between ITI-83 and ITI-9. All other IHE FHIR transactions are still based on DSTU1 but they are planned to be updated soon.
verify implementation against IHE ballot #32 (PIXm/PDQm in DSTU2)
additional issues will be opened for improvements of FHIR support
After FHIR DSTU2 has released and a couple of IHE profile offer FHIR equivalents to legacy transactions, we should start thinking about providing some support, and how...
Most of the stuff in http://jamesagnew.github.io/hapi-fhir/ look pretty useful. FHIR interfaces can be exposed as Camel consumers and producers, although there is not much obvious overlap with existing Camel ReST functionality. Resource Handlers are identified pretty statically by using annotations. At least we could offer the usual ATNA auditing, logging etc. stuff.
I would also propose to take PIXm (ITI-83) as an "easy" IHE transaction for nailing down how this can be done using general IPF mechanisms.
Whatever we do should happen an on branch
Comments welcome!