IG for Accessibility to IPS

[JohnMoehrke]

Given that IPS is a specification from HL7 that is a FHIR-Document, and that ITI has Document Sharing that is able to communicate the IPS, Then IHE needs an Implementation Guide that explains simply how to utilize Document Sharing with the HL7 defined IPS.

This is proposed as an ITI project, as we have more of engagement at this time, and the project will not be making any clinical decisions. The IPS will be specified in general. This mention should support other derivatives from the HL7 IPS such that this IG is reusable infrastructure.

I expect a very small IG that simply hooks HL7 IPS to IHE Document Sharing (XDS, XCA, XDR, XDM, MHD, MHDS), using existing PCC Content Creator / Content Consumer actors that already support this binding. Note there is a CP that has updated the PCC Technical Framework to show mapping of FHIR-Document to Document Sharing Metadata, but this CP has not yet been integrated into the PCC Technical Framework (PDF).

Given that it is possible we are addressing a new audience than our historic IHE audience: We could express in a bit more detail the above use-cases than we tend to do for a basic Content Profile.

Additional mentions

It is possible that this IG could/should mention the:

• On-Demand document concept, especially given IPS is a summary
• IPS $summary operation, mostly to explain how this mechanism might be hooked to Document Sharing On-Demand document entries
• IPA $docref operation.
• MHD Simplified Publish
• MHD Generate Metadata
• MHD ITI-65 FHIR documents Publish
• HE-DSG for document digital siganture

I don't know that mentioning these is useful or necessary as they already exist in the HL7 / IHE specifications.

Also PCC CPs

Note that there is at least one CP that added FHIR-Document to the PCC Volume 2: 4.1 on how to map document content to document sharing metadata. This added support for FHIR-Document in addition to the CDA mapping that exists. This is very important in addition to something specific about IPS as a FHIR-Document.

It might be best to bring into this IG the content from PCC TF-2 sections 3 and 4. This would be useful as we could modernize it, make it html linkable (vs PDF), and better represent advancements ITI has made (e.g. metadata handbook). Bringing it within this IG would also make it more accessible to the target reader.

Prototype

I have started a prototype of this IG as part of a discussion with the broader organizations driving IPS projects.

https://github.com/IHE/ITI.aIPS

[JohnMoehrke]

Alternative names are encouraged:

• IPS Sharing (IPSS)

[stl-steve-moore]

IPS Document Exchange (IPS-DX) IPS Sharing: IPS-S to set a pattern for other document sharing and make the -S the known text for sharing IPS Metadata (IPS-M): This is similar to Document Exchange but is more subtle. -M is probably a bad choice because that is to close to "m" for Mobile. IPS Metadata (IPS Meta): So you can post your IPS on Facebook.

…

________________________________ From: John Moehrke ***@***.***> Sent: Monday, March 20, 2023 11:01 AM To: IHE/IT-Infrastructure ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [IHE/IT-Infrastructure] IG for Accessibility to IPS (Issue #197) * External Email - Caution * Alternative names are encouraged: * IPS Sharing (IPSS) — Reply to this email directly, view it on GitHub<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIHE%2FIT-Infrastructure%2Fissues%2F197%23issuecomment-1476507910&data=05%7C01%7Cmoore.stephen.m%40wustl.edu%7C8ad9e0b6e4334fd5f2f208db295c5cf7%7C4ccca3b571cd4e6d974b4d9beb96c6d6%7C0%7C0%7C638149248892883690%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=F%2BMoXPZ03%2FXQDfUTZD%2Fj%2B18Hkd6TN87D4w7omH6%2BBpM%3D&reserved=0>, or unsubscribe<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAGZIOKZ4K5HHVACSMOYR4TW5B5MBANCNFSM6AAAAAAWA65JMU&data=05%7C01%7Cmoore.stephen.m%40wustl.edu%7C8ad9e0b6e4334fd5f2f208db295c5cf7%7C4ccca3b571cd4e6d974b4d9beb96c6d6%7C0%7C0%7C638149248892883690%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KbTdQsakT%2BAeGXCaPKR%2FlCkPviy7M4%2B%2FAi9QqVlT4ZQ%3D&reserved=0>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

________________________________ The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.

[mhnusbaum]

VERY supportive of this. Let's find another name besides an IG, as HL7 has IPS IG's as well. This will confuse the marketplace.
Let's also include a profile update to the newest HL7 IPS FHIR IG, which was recently published. There's also been an update to the SNOMED terminology set for IPS.

[mhnusbaum]

As requested by JohnM: there are 5 SDO's contributing standards artifacts to the IPS ecosystem at present:

• IHE IPS Profile (FHIR & CDA)
• HL7 IG's (FHIR and CDA) - FHIR IG revised Nov22
• SNOMED Terminology Set, specific for IPS (free set) - revised 2022
• ISO/CEN 27269 - IPS Specification and Data Model - being revised now
• CEN also has EU-specific specifications and IG's based on the ISO specs