Updated Releases: PCC Occupational Data for Health (ODH) 1.0.0 Query for Existing Data for Mobile (QEDm) 3.0.0 ITI  normative Technical Framework - updated with approved CPs Add RESTful ATNA (Query and Feed) - updated with approved CPs Mobile Care Services Discovery (mCSD) - updated with approved CPs Scheduling (formerly published by Argonaut in STU3 flavor) - 1.0.0 Document Digital Signature JSON signature option Finance and Insurance Services Public Comment ITI Extensions to Document Metadata Subscription Formal Announcement PCC ITI first and second See all at https://profiles.ihe.net Some Explanations Most of these releases are incremental updates that don't require much comment. Either addressing the public-comment from last quarter or integrating formal Change Proposals (CPs) that were balloted and passed. If you need to understand these changes, there is traceability within the representative IHE GITHub repositories. All issues and CPs are indicated with individual github issues and pull-requests.  The biggest news is: Scheduling (formerly published by Argonaut in STU3 flavor) - 1.0.0 Finance and Insurance Services with an important mention of: Document Digital Signature JSON signature option Query for Existing Data for Mobile (QEDm) 3.0.0 QEDm This is mostly a conversion to IG publication of the QEDm profile that has before this been only published in PDF form. In PDF form, the supplement was nothing but narrative. There was some conformance resources but there was little assurance they were right. Now that QEDm is published in IG form there is a full set of conformance resources, and examples. There is a clear connection to MHD using mXDE.  The future of QEDm is still in play. We are intending to adjust QEDm to be a derivative of the HL7 IPA. In this way there will be little mismatch between the two.  This effort will need to address that IPA includes functionalities that IHE covers with PDQm and MHD. I expect this might be ready in Summer 2025, assistance is always welcome. DSG - JSON signature option This is an addition of an Option to the normative Document Digital Signature. Original Profile used XML-Signature, as that was the best solution at the time. However, there is more tooling support for JSON Digital Signatures now days, and less interest in XML-Signature. So IHE adjusted the DSG profile to have two options, the original XML-Signature (which is assumed if no option is declared), and the JSON Digital Signature. The use-cases supported have not changed, the DSG is about Document Digital Signature and has some variations for the various ways that Documents can be moved around using IHE Document Sharing. Finance and Insurance Services This supplement is a new domain for IHE. Although there is a robust community in the USA that is profiling the FHIR standard to support Finance and Insurance Services; there is a need outside the USA for similar profiling. This is the scope of this supplement, mostly "Not the USA". This does not mean it is conflicting with USA needs, but rather to indicate that the intended audience is everyone outside the USA. The current profiling is not all that much different than the use-case analysis found in the FHIR Core for the Finance profiles but does define some capabilities that have been identified by some open-source implementations. The initial deployment is expected to be by WHO. I would expect we will receive robust comments as this gets "Trial Implemented", which is an admission that this IG is rather immature and open for discussion. Scheduling This IHE profile is based on the Argonaut Scheduling Implementation Guide, originally published back in the FHIR STU3 days. Argonaut has agreed to hand over the FHIR R4 and future to IHE. Thus, this IG is mostly a conversion to FHIR R4, but includes significant improvements based on experience. The following are some of the major differences from the Argonaut IG:The IHE Profile is based on FHIR R4 The IHE Profile is intended for international use, and it does not have required bindings or any dependencies to national profiles The operations described are $find, $hold, and $book A separate transaction describes the use of FHIR Search for the Appointment resource The operation parameters use explicit data types, and support only POST transactions

View Entire Post