2023 - 05 International Patient Summary

Short Description

This track will test the creation, exchange and visualization of patient summary data across jurisdictions and usage contexts using the FHIR International Patient Summary (IPS) Implementation Guide specification. It will use and collect feedback on the most recent publication of the IPS (STU 1.1) and help prepare for the next IPS ballot. In addition it will include testing of SMART Health Links for Patient Mediated IPS exchange.

Long Description

This track will test the creation, exchange and visualization of patient summary data across jurisdictions and usage contexts using the FHIR International Patient Summary (IPS) Implementation Guide specification.  The track will focus on the primary theme of cross-border IPS document bundle data exchange. This will support initiatives by the Joint Initiative Council (JIC) on IPS (See http://jointinitiativecouncil.org/projects/ips.asp) and also nations participating through the Global Digital Health Partnership (See https://gdhp.health/). Any organization within any country is invited to participate.  

This track will test the creation, exchange and visualization of patient summary data across jurisdictions and usage contexts using the FHIR International Patient Summary (IPS) Implementation Guide specification.  The track will focus on the primary theme of cross-border IPS document bundle data exchange. This will support initiatives by the Joint Initiative Council (JIC) on IPS (See http://jointinitiativecouncil.org/projects/ips.asp) and also nations participating through the Global Digital Health Partnership (See https://gdhp.health/). Any organization within any country is invited to participate.  

Several themes will be advanced as part of the track including: 

• Pilot implementations of multiple jurisdictions (e.g., GDHP) for cross-border IPS document bundle data exchange
• A particular focus will be on the usage of SMART Health Links (see https://docs.smarthealthit.org/smart-health-links/design) for the patient mediated exchange of IPS document
• Parties who have expressed interest may include Washington state and Commons Project (attendees TBD)
• Test implementation of proposed Patient resource $summary operation (See https://hl7.org/fhir/uv/ips/OperationDefinition-summary.html)
• Can generate an IPS instance for a patient based on existing data and a set of rules
• Rules can be server-defined (default) or specified by parameter
• Need to answer the “relevant” question for what data to include
• Need to refine what narrative text is included in IPS and how that text is linked to machine-readable resources
• Enhanced IPS instance testing leveraging available testing suites
• The Inferno testing tool (ONC/MITRE) https://inferno.healthit.gov/
• Use of the HL7/ONC developed reference implementation server: https://ips.health/
• The Gazelle testing tool suite https://gazelle.ihe.net/content/tools
• One or more FHIR server(s) for demonstrating and testing IPS data exchange
• Examine the relationship between IPA (International Patient Access) and IPS

General track goals include:

• Promote the sharing of experiences
• Identify tools and resources for IPS examples and validation
• Identify gaps and pitfalls in the IPS adoption

An open approach will be followed, expecting attendees to actively participate in the selection and definition of the tests to be performed and topics to be discussed, beyond those suggested by the track leaders.

Type

Test an Implementation Guide

Related Tracks?

International Patient Access

Call for participants

• Personal Health Record (PHR) and Electronic Health Record (EHR) vendors
• Implementers and consultants involved in regional adaptation of IPS (e.g. PS-CA in Canada, NZIPS in New Zealand, etc.) 
• Health information exchanges

Track Prerequisites

No advance preparation is specifically required, although the following may be helpful

• Previous IPS samples from multiple nations (https://github.com/jddamore/IPSviewer/tree/main/samples)
• If you intend to work with SMART Health Links, please review videos here https://docs.smarthealthit.org/smart-health-links/
• HAPI documentation on IPS: https://hapifhir.io/hapi-fhir/docs/server_jpa/ips.html 

Track Lead(s)

Track Lead Email(s)

johnd@moreinformatics.com rob@hausamconsulting.com 

Specification Information

• https://hl7.org/fhir/uv/ips/index.html
• https://docs.smarthealthit.org/smart-health-links/

Zulip stream

https://chat.fhir.org/#narrow/stream/207835-IPS

Agenda & Track Kick off Call

Testing Scenario:

System roles:

• Generator of IPS documents (such as personal health records, health information exchanges or electronic health records)
• Patient mediators of IPS document exchange, particularly mobile devices with QR code wallets
• Consumer of IPS Documents: Retrieves a FHIR IPS document and/or individual component resource instances created by the Document Creator from the FHIR server and does
  one or more of the following:
  • a) validates the document and/or component resource instances against the IPS Clinical Document profile,
  • b) displays the document and/or discrete data components in a browser (or by other means),
  • c) translates the coded and/or narrative data to a different language for display, or
  • d) translates the coded data to different code system(s) used in a jurisdiction that is different from the source.

Action:

• Create an IPS bundle from a FHIR server using the $summary operation (http://build.fhir.org/ig/HL7/fhir-ips/OperationDefinition-summary.html)
• View an IPS bundle using tools provided 
• Encode and decode a SMART Health Link QR Code
• Demonstrate IPS terminology utilization (and translations)

Precondition: Success Criteria: 

• Usage of tools to validate IPS conformance
• Usage of tools to visualize IPS content 
• Effective sharing of IPS documents across devices

Success Criteria:  

• Conformant IPS documents that validate without errors
• Successful visualization of IPS documents
• Successful storage of SMART Health Links on mobile devices
• Advancement and feedback on the implementation guidance

TestScript(s): No test scripts at this time. 

Security and Privacy Considerations:

No plans to test security at this time, although prototype framework for limiting access (e.g. auth access for SMART Health Links) may be piloted. Privacy and confidentiality are within scope for discussion.