Highlighted IHE Profiles

IHE Profiles Highlighted for the 2022 Joint IHE Connectathon®

 

A number of IHE Profiles have been selected for special focus at the Joint IHE Connectathon 12-16 September. They have been chosen because of their particular importance at this time and with the ability to perform peer to peer testing simultaneously in the USA and in Europe.

 

As such there is an opportunity for increased intercontinental interoperability - “Building the Bridge” - to be undertaken enabling these key IHE Profiles to have a wider pool of vendor testing at this Joint Connectathon.

 

DICOMWeb

 

can impact the imaging environment taking advantage of the HTTP REST protocol and the XML/JSON format via a number of IHE Profiles:

  • Web-based Image Access (WIA) Profile introduces how to query for series, studies and instances, and how to retrieve them, using QIDO-RS and WADO-RS;
  • Web-based Image Capture (WICProfile is dedicated to storage of images, using STOW-RS;
  • AI Results (AIR) Profile specifies how Artificial Intelligence applied to imaging analysis results can be reliably stored, retrieved and displayed; it reuses parts of the above two IHE Profiles.

These IHE Profiles will be of great importance regardless of whether a vendor/institution is developing a PACS, VNA, Image Display or even an imaging-enabled client application running on a smartphone. The Radiology Domain is looking to harmonise the way implementers use the DICOMWeb standard to address the immediate and expected image sharing need using both mobile and non-mobile applications.


 
Document and Image Sharing

 

using IHE Profiles XDM, XDS, XDS-I, XCA, XCA-I XCDR and DSUB has been long established with hundreds of communities, regions, nations and cross-border installations deployed worldwide. The availability of health records throughout the EU and across many international borders is now common place. However new and evolving systems are required to integrate with established eHealth infrastructures and hence there remains a strong demand for interoperability testing at the IHE Connectathon, with specific reference to the following IHE Profiles:

  • Cross-Enterprise Document Interchange (XDMProfile when point to point secure email is deployed for targeted communication between health professionals and between professionals and patients;
  • Document Subscription (DSUBProfile enhances workflows around existing XDS deployments to issue notifications of document publication to intended recipients;
  • Cross-Enterprise Sharing of imaging Information (XDS-I) Profile and cross-community (XCA-I) under deployment in a large number of national, regional or cross-border (X-Health in Europe) image sharing deployments;
  • With ever increasing Cross-Enterprise Document Sharing (XDS) communities and in some cases, their Cross-Community Access federation (XCA), together with Cross-Community Document Reliable publication (XCDR) the interoperability robustness product features gain is frequently retested at the IHE Connectathon, a prerequisite to IHE Conformity Assessment.

The IHE Connectathon is open to both final, market-ready products and prototype implementations and if your organisation is considering membership of the IHE SHARAZONE then it will also be able to benefit from continuous, 24/7 virtual testing capability opportunities with fellow IHE SHARAZONE members. Further information can be found on the IHE SHARAZONE webpage.


Imaging Object Change Management

 

 

The IHE Imaging Object Change Management IOCM Profile allows synchronisation of downstream systems having a copy of the same images whenever a structural change to the images occurs in the system that is considered the master of these images.

Structural changes include moving images from one study to another study of the same patient or different patient because of operator error, deleting images for quality reasons or obsolescence.

The IOCM Profile makes use of the DICOM Key Object Selection SOP class to communicate the list of images to be rejected to the downstream systems and provide the rejection reason.

The support of the IOCM Profile is a MUST for PACS, VNA and workstation systems. It often occurs that after the PACS has archived images to the VNA or routed images to workstations, some structural changes are performed on the PACS. Thanks to the IOCM Profile, these changes can be communicated by the PACS (acting as a Change Requester actor) to the downstream VNA or workstation (acting as Image manager of Image display actor). Thus, the VNA or workstations can apply the changes and remain fully synchronised with the PACS at all times.

The IOCM Profile can also be utilised to implement in a modality (as change Requester), especially for modalities sending images on the fly to the PACS. It facilitates the rejection of poor quality images for example.

Does your product already support the IOCM Profile? Or are you looking to test it out? Join us in September for the Joint IHE Connectathon 2022. You will have the unique opportunity to meet other implementers and test the interoperability of your solution against other IHE implementations. Coming to an IHE Connectathon is also the chance to share your experience with the IHE specifications and be sure to be involved in their continuous improvement process. 

You will certainly find some bugs but you will also be able to rely on your peers to seek guidance in fixing them, under the watchful eye of the experienced IHE Monitors.

The IHE Connectathon is open to both final, market-ready products and prototype implementations. You will have a full week to complete your work with standards experts and other implementers to guide you through the process.

 

 

Patient Administration Management, Scheduled Workflow and Encounter Based Image Work

 

The well-known IHE Scheduled Workflow.b (SWF.b) Profile describes order-based imaging workflows (such as found in CT, MRI or Mammography procedures). This is handled by the use of order-driven worklists.

However, medical imaging is increasingly undertaken outside the context of an ordered procedure. It is enounter-driven (e.g., during a dermatology consultaiton, the physician decides to capture pictures of a mole for future comparison.)

The IHE Encounter Based Imaging Workflow (EBIW) Profile addresses this need. The primary goal of the EBIW Profile is to ensure that images acquired in the context of a patient encounter are combined with the corresponding metadata about the patient, the encounter, and the performed imaging procedure. This facilitates managing the imaging data, linking it into the patient medical record, and accessing it later. This IHE Profile introduces these capabilities for encounter-based imaging procedures in ways that are analogous to those of order-based imaging procedures as coordinated by the SWF.b Profile. This Encounter-Based Imaging Workflow Profile specifies how to capture appropriate context, populate relevant indexing fields, link to related data, and ensure the images are accessible and incorporated into the medical record.

Typical systems that can be part of the EBIW Profile include an EMR acting as “Encounter Manager” to provide patient metadata, encounter metadata (visit…), procedure metadata (Study IUID, Accession # …) to the modality. The modality then sends the DICOM images with appropriate metadata to the PACS. The PACS can then notify the EMR acting as “Result Aggregator” of the availability of the images.

The EBIW Profile makes use of DICOM (Modality Worklist and storage services) or DICOMweb (UPS-RS and STOW-RS) and HL7 standard (ORU-R01).

The IHE Patient Administration Management (PAM) Profile can also be supported by the EMR system in the context of the EBIW Profile:

For example, the EMR “Encounter Manager” actor could group with a “Patient Demographics Consumer” actor in the (PAM) Profile to receive a feed of patient demographics for all patients in the facility. The Encounter Manager could alternatively group with a “Patient Encounter Consumer” actor in the (PAM) Profile since the Patient Encounter Management transaction also contains patient demographics.

Does your product already support the one of those IHE Profiles? Or are you looking to test it out? Join us in September for the Joint IHE Connectathon 2022. You will have the unique opportunity to meet other implementers and test the interoperability of your solution against other IHE implementations. Coming to an IHE Connectathon is also the chance to share your experience with the IHE specifications and be sure to be involved in their continuous improvement process.

You will certainly find some bugs but you will also be able to rely on your peers to seek guidance in fixing them, under the watchful eye of the experienced IHE Monitors.

 

The IHE Connectathon is open to both final, market-ready products and prototype implementations. You will have a full week to complete your work with standards experts and other implementers to guide you through the process.

 

 

Want to know more about how IHE-Europe Connectathon can help your eHealth programme or project?

Please contact IHE-Europe by email