- Created by Mark Scrimshire, last modified on May 02, 2023
The MedMorph/FluSurv-NET/Health Care Surveys(HCS) Connectathon track aims to test the FluSurv-NET and HCS Content Implementation Guides (IGs) leveraging the MedMorph Reference Architecture.
Currently the FluSurv-NET content implementation guide is not developed, however the plan is to use the Electronic Case Reporting (eCR) FHIR IG since the eCR FHIR IG has all the needed data elements for FluSurv-NET.
For HCS, the following HL7.FHIR.US.HEALTH-CARE-SURVEYS-REPORTING\Health Care Surveys Content IG Home - FHIR v4.0.1 IG would be used.
FluSurv-NET and HCS intend to test established and developing FHIR components created by Centers for Disease Control (CDC) / Public Health, and similarly the FHIR components used by clinical partners for public health reporting using MedMorph.
The track also intends to raise awareness of the infrastructure being developed both by the clinical organizations and the CDC / Public Health for public health surveillance.
The track focus will be on the use of identified content in the FluSurv-NET and HCS IGs for automated transmission and submission of Data from Electronic Health Records (EHRs) to Public Health Agencies (PHAs), CDC Data Repositories using the MedMorph Reference Architecture.
The Track organizers will provide the first participants who volunteer to perform testing with access to a simulated environment consisting of a FHIR server populated with fictitious data and a “Backend Submitter Application” configured to the same target “Public Health Data Receiver platform”.
A few objectives of this track are:
Test Implementation Guides.
|Other Public Health tracks / Helios Accelerator|
Call for participants
Providers/EHR vendors and Health Information Exchanges (HIEs) who are interested in creating/submitting bundles conforming to either the HCS or FluSurv-NET IGs.
The CDC is planning to participate as the receiving endpoint.
The ability to send bundles conforming to either specified IG, or the ability to provide synthetic data that can be used to construct bundles that conform to the specified IGs.
The Track Leads will be providing a very limited number of simulated Health Data Exchange App (HDEA - backend services app) environments for use during the Connectathon - of course we are also encouraging participants who have the capacity to implement their own test environments to do so and particpate in the track. At a minimum those participants who are preparing their own simulated environments should have the ability to send bundles conforming to either specified IG. You will be provided with the Appropriate API Key for machine to machine connectivity.
Nagesh (Dragon) Bashyam, Aaron Seib. Backup: Mark Scrimshire
Track Lead Email(s)
firstname.lastname@example.org, email@example.com (backup: firstname.lastname@example.org)
HealthCare Survey Content IG 0.1.0 STU1 Ballot
Electronic Case Reporting (eCR) FHIR IG
Making Electronic Data More available for Research and Public Health (MedMorph) 1.0.0 STU1 / Continuous Integration Build
2022-01 MedMorph Track ( Sub-tracks: Health Care Surveys Reporting, Central Cancer Registry Reporting, Research Data Exchange)
Track Kick off Call
Thursday April 27th at 1pm-2pm ET
Recording of Track Kick-off Call:https://us02web.zoom.us/rec/share/YHAnHZiyQHeVZrjk13vbuCw8zd0Jt2xbwyN1FsrqrByuxZUIJ1dlj5Ugdd5oh4ic.3VW28fQn0gMYFhLe
Track Kick-off Deck: CAT33 Track Kick Off Call MedMorph.pptx
Pre-Connectathon Office Hours session:
Wednesday, May 3rd. 12:00 - 1:00pm ET
Optional meeting for Testing participants. We will keep the call open for 15 minutes. Please dial in early if you have questions (or let us know in advance when you are able to join the call).
Aaron Seib has reached out to volunteer testers individually already. This is an opportunity to address any last-minute questions as we complete preparations for the weekend’s testing event.
Zoom Link: https://us02web.zoom.us/j/87418298907
Data Submitter: providers, EHR systems and HIEs that can post FHIR bundles.
Data Receiver: a CDC system that can receive and validate FHIR bundles.
NOTE: CDC Representatives will be operating a common Data Receiver platform at the connectathon and hope to have all participants submitting to it.
Health Care Surveys Reporting
The following are example scenarios enabled by the implementation guide:
Knowledge Artifact Repository (KAR), Health Data Exchange App (HDEA - backend services app) using eCR Now project, EHR, Public Health Agency (PHA)/CDC
Base Scenario: Data Submission Workflow (HDEA, PHA/CDC)
An HDEA (or proxy) submits data to PHA/CDC directly using the $process-message operation.
Bonus Scenario 1: Export data from CDC FHIR Server to a Data Lake
The target CDC Data Lake will not be available in time for the Connectathon. However, a temporary Data Lake will be established that enables the export of data from the CDC FHIR Server to be demonstrated.
Bonus Scenario 2: Demonstrate a visualization of data from a Data Lake using data collected via the CDC FHIR Server
The temporary Data Lake will be used to support a visualization of extracted FHIR data using PowerBI. This should demonstrate the potential capability to gain insights from data received via the CDC FHIR Server.
HDEA Workflow Testing Scenario
Note: all these workflows have been tested at previous HL7 Connectathons
Creation and Publishing of Knowledge Artifact (FluSurv-NET and HCS Programs)
Notification Workflow (EHR, HDEA)
Pre-Conditions: Providers entering data into the EHR
HDEA gets notified of changes to patient record and queries the EHR for patient data
NOTE: EHRs who want to natively implement the Knowledge Artifact processing can do so and skip this scenario.
NOTE: HDEA can be used along with the EHR to successfully process a Knowledge Artifact and be ready for notifications. If an EHR cannot notify via POSTMAN or some other client tool it can notify the HDEA as a proxy for the connectathon.
Data Collection Workflow (EHR, HDEA)
HDEA queries the data necessary to create the package for submission from the EHR.
HDEA or Proxy creates subscriptions in the EHR
NOTE: Dependent upon support for FHIR R4B subscriptions.
HDEA or Proxy processes Knowledge Artifacts and creates subscriptions in the EHR.
SMART on FHIR Backend Services is required for EHR participants and other participants to interact with each other.
For testing communication with the CDC Target FHIR Server machine tokens will be provisioned manually to enable secure data exchange.
Testing the Tokens will be conducted BEFORE the event. Either at the Track Kick-off or as a subsequent Security testing event.