So far, the FHIR component is bound to DSTU2, including the IHE profiles MHD, PIXm, PDQm, and Restful ATNA query. These profiles have been migrated to FHIR STU3 (see http://wiki.ihe.net/index.php/ITI_TI_Supp_Updates_to_FHIR_STU3 for the details) and approved with Ballot 42 (ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2017/Ballot_42/)
At the same time, a few inconsistencies and imprecise specification language have been fixed.
Unlike other IHE components, I'd like to factor out FHIR-version independent parts, keep the current state as-is (and deprecate it), and add STU3 versions of the Camel components and translators in a separate module. There will be more FHIR versions in future anyway.
ohr
commented
7 years ago
So far, the FHIR component is bound to DSTU2, including the IHE profiles MHD, PIXm, PDQm, and Restful ATNA query. These profiles have been migrated to FHIR STU3 (see http://wiki.ihe.net/index.php/ITI_TI_Supp_Updates_to_FHIR_STU3 for the details) and approved with Ballot 42 (ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2017/Ballot_42/) At the same time, a few inconsistencies and imprecise specification language have been fixed.
Unlike other IHE components, I'd like to factor out FHIR-version independent parts, keep the current state as-is (and deprecate it), and add STU3 versions of the Camel components and translators in a separate module. There will be more FHIR versions in future anyway.