IHE Devices Technical Framework Supplement Published for Public Comment

Hello IHE Canada Community Members,

The IHE Devices Technical Committee has published the following updated Technical Framework Supplement for public comment in the period from April 11 through May 11, 2024:

• Point-of-Care Identity Management (PCIM) - Rev. 2.0

PCIM Rev. 2.0 Highlights:
The latest PCIM supplement for public comment incorporates working group efforts that resulted in simplification of the design to better align with existing system architectures to minimize roll-out time. Additional details have been added throughout and error codes were introduced. New and noteworthy changes include:

• The PCIM supplement is now an HTML publication authored in AsciiDoc and maintained on the IHE / DEV.PCIM GitHub repository.
• PCD-17 (assert association) and PCD-18 (assert disassociation) transactions were combined into a DEV-51 (communicate association state) transaction.
• A DEV-52 (report association state) transaction was added to reflect the manager to consumer reporting of real-time association status events. A separate transaction between the manager and consumer actors and reporter and manager actors is consistent with IHE assignments and it allows for different message content and constraints.
• The DEV-19 (query associations subscription) transaction is now optional and no longer includes a “snapshot” in the response. Instead, a DEV-52 sequence for all selected associations are sent from the manager to the specified consumer.
• The PCD-20 transaction and DREG Actor are eliminated from this specification. References to MEM DMC capabilities to address registration and reporting of device association availability have been added.

The document is available at profiles.ihe.net/DEV/index.html#1.2 . Comments submitted by May 11, 2024 will be considered by the IHE Devices Technical Committee in developing the trial implementation version of the supplement. Comments can be submitted via traditional methods at Devices Public Comments or by submitting a GitHub Issue .

Best regards,
Helen