This wiki has undergone a migration to Confluence found Here

Difference between revisions of "201901 International Patient Summary"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}")
 
Line 2: Line 2:
 
[[Category:201901_FHIR_Connectathon_Track_Proposals|Jan2019 Proposals]]
 
[[Category:201901_FHIR_Connectathon_Track_Proposals|Jan2019 Proposals]]
 
__NOTOC__
 
__NOTOC__
=Track Name=
+
=International Patient Summary=
 +
 
 +
This track will test the creation and exchange of FHIR International Patient Summary (IPS) documents (using a document Bundle resource containing a Composition and other supporting resources).  We anticipate working closely with the FHIR Documents track.
  
 
==Submitting WG/Project/Implementer Group==
 
==Submitting WG/Project/Implementer Group==
 
<!-- Who is asking for this track? -->
 
<!-- Who is asking for this track? -->
 +
* Structured Documents WG
 +
* FHIR Product Director
 +
* IPS Project
  
 
==Justification==
 
==Justification==
 
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. -->
 
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. -->
 
+
The updated FHIR R4 version of the International Patient Summary (IPS) is being balloted in the September cycle (http://hl7.org/fhir/uv/ips/index.html) plus there is existing work in STU3 in the Trillium II project (and otherwise). The primary use case envisioned for the IPS specification is the cross-border, unscheduled care of a patient, and additional use cases may be tested.  The Connectathon in Baltimore provides an opportunity for implementation and testing of this specification.  We intend to build on the initial efforts which were made with the STU3 version of the IPS specification during the May Connectathon in Cologne, and we hope to further integrate and coordinate with the FHIR Documents track and work further on current and planned future alignment with the Argonaut specification.
  
 
==Clinical input requested==
 
==Clinical input requested==
Line 20: Line 25:
 
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon -->
 
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon -->
 
See [[Connectathon_Track_Lead_Responsibilities]]
 
See [[Connectathon_Track_Lead_Responsibilities]]
 +
* [mailto:rrhausam@gmail.com Rob Hausam]
 +
* [mailto:giorgio.cangioli@gmail.com  Giorgio Cangioli]
 +
* [mailto:chronaki@gmail.com  Catherine Chronaki]
  
 
==Expected participants==
 
==Expected participants==
 
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
 
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
 +
* Rob Hausam
 +
* Giorgio Cangioli
 +
* Catherine Chronaki
 +
* Remote participants (e.g. from Europe)
 +
* Others TBD
  
 
==Roles==
 
==Roles==
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
+
===IPS Document Creator===
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
+
<!-- Provide a description of the capabilities this role will have within the connectathon -->
===Role 1 Name===
+
Creates a FHIR IPS document (Bundle containing a Composition and supporting resources) from source data.  The source data likely will be existing data on a FHIR server, but this can be done using whatever means are appropriate, including manual creation, assembling documents from other resources, transforming from a CDA IPS document, etc.  Submits that document to a FHIR server. Optionally a document creator may digitally sign the document (but this is not expected at this time).
 +
 
 +
===IPS Document Consumer===
 
<!-- Provide a description of the capabilities this role will have within the connectathon -->
 
<!-- Provide a description of the capabilities this role will have within the connectathon -->
 +
Retrieves a FHIR IPS document created by the Document Creator from the FHIR server and does one or more of the following: a) validates the document against the IPS Clinical Document profile, b) displays the document 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.
  
 
==Scenarios==
 
==Scenarios==
 
<!-- What will be the actions performed by participants? -->
 
<!-- What will be the actions performed by participants? -->
 +
For all scenarios below, participants are expected to provide their own content for the documents (obviously nothing with PHI should be used at a public Connectathon). If participants don't have readily available content, they are encouraged to create documents that mimic the content in IPS or other patient summary sample files.
 +
 +
1. Create an IPS document
 +
:Action: User creates a FHIR IPS document consisting of a Composition resource with narrative sections, bundled with Patient (Composition.subject) and Practitioner (Composition.author) and the additional supporting resources containing the summary clinical data. User then POSTs the document to a FHIR server.
 +
:Precondition: none, but existing resources may be used.
 +
:Success Criteria: Bundle is successfully submitted to a FHIR server. Consumer in Scenario 4 can display the document and render all attested content.
 +
 +
Basic script:
 +
* Step 1: Create a Composition resource
 +
* Step 2: Ensure the subject, author, and custodian references point to valid Patient, Practitioner, and additional clinical resources .
 +
* Step 3: POST the Composition to a FHIR server
 +
* Step 4: Check the operation outcome to ensure it was successful
 +
* Step 5: Call $document on the Composition (if supported by the server) to get a full document Bundle back, or create the Bundle through other means (custom code, etc.)
  
===Scenario Step 1 Name===
+
2. Display an IPS document
:Action: <!--Who does what?  (Use the role names listed above when referring to the participants -->
+
:Action: User retrieves an IPS document from the FHIR server and displays it in a web browser (or by other means).
:Precondition: <!-- What setup is required prior to executing this step? -->
+
:Precondition: An IPS document exists on the target FHIR server.
:Success Criteria: <!-- How will the participants know if the test was successful? -->
+
:Success Criteria: Document is successfully displayed.
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
 
  
<!-- Provide a description of each task -->
+
3.  Translate the narrative and coded data into different language(s) for display or to other code systems appropriate for different jurisdictions (as in IPS Document Consumer c, d above).
  
 
==TestScript(s)==
 
==TestScript(s)==

Revision as of 07:41, 6 November 2018


International Patient Summary

This track will test the creation and exchange of FHIR International Patient Summary (IPS) documents (using a document Bundle resource containing a Composition and other supporting resources). We anticipate working closely with the FHIR Documents track.

Submitting WG/Project/Implementer Group

  • Structured Documents WG
  • FHIR Product Director
  • IPS Project

Justification

The updated FHIR R4 version of the International Patient Summary (IPS) is being balloted in the September cycle (http://hl7.org/fhir/uv/ips/index.html) plus there is existing work in STU3 in the Trillium II project (and otherwise). The primary use case envisioned for the IPS specification is the cross-border, unscheduled care of a patient, and additional use cases may be tested. The Connectathon in Baltimore provides an opportunity for implementation and testing of this specification. We intend to build on the initial efforts which were made with the STU3 version of the IPS specification during the May Connectathon in Cologne, and we hope to further integrate and coordinate with the FHIR Documents track and work further on current and planned future alignment with the Argonaut specification.

Clinical input requested

Related tracks

Proposed Track Lead

See Connectathon_Track_Lead_Responsibilities

Expected participants

  • Rob Hausam
  • Giorgio Cangioli
  • Catherine Chronaki
  • Remote participants (e.g. from Europe)
  • Others TBD

Roles

IPS Document Creator

Creates a FHIR IPS document (Bundle containing a Composition and supporting resources) from source data. The source data likely will be existing data on a FHIR server, but this can be done using whatever means are appropriate, including manual creation, assembling documents from other resources, transforming from a CDA IPS document, etc. Submits that document to a FHIR server. Optionally a document creator may digitally sign the document (but this is not expected at this time).

IPS Document Consumer

Retrieves a FHIR IPS document created by the Document Creator from the FHIR server and does one or more of the following: a) validates the document against the IPS Clinical Document profile, b) displays the document 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.

Scenarios

For all scenarios below, participants are expected to provide their own content for the documents (obviously nothing with PHI should be used at a public Connectathon). If participants don't have readily available content, they are encouraged to create documents that mimic the content in IPS or other patient summary sample files.

1. Create an IPS document

Action: User creates a FHIR IPS document consisting of a Composition resource with narrative sections, bundled with Patient (Composition.subject) and Practitioner (Composition.author) and the additional supporting resources containing the summary clinical data. User then POSTs the document to a FHIR server.
Precondition: none, but existing resources may be used.
Success Criteria: Bundle is successfully submitted to a FHIR server. Consumer in Scenario 4 can display the document and render all attested content.

Basic script:

  • Step 1: Create a Composition resource
  • Step 2: Ensure the subject, author, and custodian references point to valid Patient, Practitioner, and additional clinical resources .
  • Step 3: POST the Composition to a FHIR server
  • Step 4: Check the operation outcome to ensure it was successful
  • Step 5: Call $document on the Composition (if supported by the server) to get a full document Bundle back, or create the Bundle through other means (custom code, etc.)

2. Display an IPS document

Action: User retrieves an IPS document from the FHIR server and displays it in a web browser (or by other means).
Precondition: An IPS document exists on the target FHIR server.
Success Criteria: Document is successfully displayed.

3. Translate the narrative and coded data into different language(s) for display or to other code systems appropriate for different jurisdictions (as in IPS Document Consumer c, d above).

TestScript(s)

Security and Privacy Considerations