Page tree
Skip to end of metadata
Go to start of metadata

Quick Start Guide

Connectathon Agenda

Official hours of Connectathon:

  • Wednesday, May 13, 2020: 4pm ET – 7pm EST; some will start earlier at 9am ET if others want to start any time before 4pm ET
  • Thursday, May 14, 2020: 9am ET – 7pm EST
  • Friday, May 15, 2020: 9am ET – 6pm ET with wrap-up from 6-630pm ET

Touchpoints

Touchpoints will be held on this line at the following times (All ET)

  • Wednesday, May 13th - 9:00a, 1:00p, 5:00p, 9:00p
  • Thursday, May 14th - 9:00a, 1:00p, 5:00p, 9:00p
  • Friday, May 15th - 9:00a, 1:00p, 5:00p

Virtual Tours

We are hosting a virtual tour of the HL7 Connectathon track where these resources are being tested in real-time with hospital IT systems from vendors like Epic, Cerner and GE Healthcare along with other interactive software solutions from Microsoft, AWS and ESRI.

These virtual tours will occur

  • Thursday 3-3:45 ET
  • Friday 11-11:45 ET

during the HL7 Connectathon activities, and will include opportunities to speak to participants who are implementing the specification, and others from MITRE and IHE USA who are validating the results. If you are interested in joining one of these sessions please email Katie Iser and Keith Boone at kiser@ainq.com and kboone@ainq.com


Submitting WG/Project/Implementer Group

This track is for testing of The Situation Awareness for Novel Epidemic Response (SANER) Implementation Guide, a project of the Patient Administration (PA) workgroup with support from Orders & Observations (OO) and Public Health (PH).

Justification and Objectives

The SANER IG enables transmission of high level situational awareness information from inpatient facilities to centralized data repositories to support the treatment of COVID-19.

Objectives for this HL7 FHIR Connectathon:

  • Testing
    • A Measure Source creates a MeasureReport resource
    • A Measure Consumer consumes a MeasureReport resource
    • A Measure Source pushes a MeasureReport resource to a Measure Consumer
    • A Measure Consumer pulls a MeasureReport from a Measure Source
  • Identify gaps in the IG

What’s the purpose of hosting this connectathon track? What do you hope to achieve?

This track will use what version of FHIR

The SANER draft implementation guide is based on FHIR version R4 

Clinical input requested (if any)

None.  The use cases are based on metrics requested by CDC and FEMA, and interpretation of clinical meaning is based on their descriptions and answers.     

Related tracks

2020-05 FHIR Shorthand Track - The content for the SANER implementation guide is defined using FHIR Shorthand. 

Proposed Track Leads

Expected participants

Track Orientation

A webinar was hosted at 2020-04-22T16:00Z to share further participation information about this track.  

A recording of the webinar is available on youtube.

Slides from the call are available via Google Docs.

System Roles

Measure Source

The Measure Source reports results for a single facility, results for a collection of facilities, or aggregated data for a region.

Preparation
  • Be able to produce a MeasureReport resource for the CDC Measure.
  • Load realistic sample data into your system to populate the MeasureReport.
    • These data should be sufficiently distinctive that you can recognize them in a MeasureReport or in someone else's system.  
  • If you're doing the publication scenario, have a client that can do a MeasureReport create.
  • If you're doing the retrieval scenario, have a server that can respond to a MeasureReport search. 
Measure Consumer

The Measure Consumer provides access to aggregated or fine-grained data gathered from one or more Measure Sources.

Preparation
  • Be able to parse a MeasureReport resource for the CDC Measure and store it in your system. 
  • If you're doing the publication scenario, have a server that can accept a MeasureReport create.
  • If you're doing the retrieval scenario, have a client that can initiate a MeasureReport search. 
Measure Intermediary

The Measure Intermediary is a grouping of a Measure Source with a Measure Consumer.

TODO: Observe to inform for future Connectathons  

Scenarios

Generate and Consume a MeasureReport

Action: A Measure Source generates a MeasureReport for the CDC Measure resource (available as part of a ZIP with multiple example resources) using realistic sample data from its system.  Participants manually transmit this MeasureReport by whatever means are expedient.  A Measure Consumer consumes the MeasureReport and stores the measure data. 

Precondition: The Measure Source system is preloaded with whatever data it needs to populate the MeasureReport.

Success Criteria: The Measure Consumer has the Measure Source's data stored in its system.

Produce Measure 

Action: The Measure Source POSTs a MeasureReport to a Measure Consumer using the Produce Measure Transaction

Preconditions:

  • The Measure Source system is preloaded with whatever data it needs to populate the MeasureReport.
  • The Measure Consumer's server exposes an endpoint for the MeasureReport create interaction.

Success Criteria: The Measure Consumer has the Measure Source's data stored in its system.

Bonus Point: The Measure Consumer performs the Communicate Results transaction: "This can be demonstrated by generation of a report, summary, or other artifact, or by transmission of resource availability data or some computation over it to another system."

Query Measure

Action: The Measure Consumer searches for MeasureReport resources on the Measure Source's system using the Query Measure Transaction.

Preconditions:

  • The Measure Source system is preloaded with whatever data it needs to populate the MeasureReport.
  • The Measure Source and Measure Consumer agree
  • The Measure Consumer's server exposes an endpoint for the MeasureReport create interaction.

Success Criteria: The Measure Source returns the correct results.

Bonus Point: The Measure Consumer performs the Communicate Results transaction: "This can be demonstrated by generation of a report, summary, or other artifact, or by transmission of resource availability data or some computation over it to another system."

TestScript(s)

  • TODO: Postman examples

Security and Privacy Considerations

Security and privacy will be essential in implementation of SANER but are out of scope for this HL7 FHIR Connectathon track.  

  • No labels