Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Page properties


Short Description

This track will test the ability of authorized users (healthcare providers, payers, state programs, etc) to access immunization data help by immunization information systems (ISS). The track will apply the Group Level Export operation as defined by the Bulk Data Access FHIR IG to this problem.

Long Description

This track will test the Group Level Export operation as a means to access a payload of immunization data. It aims to educate possible implementers of the basic scope and standards related to the Helios FHIR Accelerator Bulk Data priority area and allow them to gain experience alongside other actors. It also aims to confirm the usability of existing standards for this priority area and identify gaps in the current standards.

Type

Test an Implementation Guide

Track Lead(s)

Craig Newman

Track Lead Email(s)

craig.newman@altarum.org

Specification Information

Bulk Data Access FHIR IG

Helios Bulk Data Priority Area

Call for participants

This track welcomes all participants who may play a role as either:

  • An authorized user who is looking to access data held by the Public Health Immunization program (IIS), this may include (but is not limited to):
    • EHR vendors
    • Healthcare organizations
    • Payor organizations
    • State programs (including Medicaid) programs
  • Public Health programs making immunization data available in bulk, this may include (but is not limited to):
    • State immunization programs
    • IIS vendors

Other organizations who support reference implementations of the Bulk Data Access IG are also encouraged to participate.

Zulip stream

https://chat.fhir.org/#narrow/stream/355139-Helios-Bulk-Data

Track Kick off Call

Wednesday December 14th at 12PM Eastern

Zoom link to come

Clinical Input Required?n/a
Related Tracks?n/a

Specification(s) this track uses

http://hl7.org/fhir/uv/bulkdata/

US Core (5.0.1) Patient and Immunization resource profiles

Testing Scenario:

  • Roles:
    • Querying System (AKA the Authorized User System)
      • Will execute the Group Level Export operation
        • URL: [base]/Group/[id]/$export
      • Will poll Responding system for status updates
      • Will retrieve response files when available
      • Will consume response files with basic validation of the data returned
      • Will consume multiple files for the same resource
    • Responding System (AKA the IIS)
      • Will generate Group resource containing an enumerated list of patients containing immunization data
      • Will expose endpoint to receive the Group Level Export operation
      • Will generate response files containing relevant resources conforming to the US Core (5.0.1) Patient and Immunization resource profiles
      • Will respond to status queries from the Querying System (both in process and complete)
      • Will make response files available to Querying System
  • Data Content Expectations:
    • Responses will contain both Patient and Immunization resources
    • (Optional) Associated supporting information (as either stand alone resources or as contained resources)
      • Provider (administering or ordering provider)
      • Organization (manufacturer)
      • Organization (location)
      • RelatedPerson (parent or guardian)
    • (Optional) Immunization forecast
      • Forecast for at least recommended vaccination
      • Forecast indicating the completion of a vaccination series
  •  Pre-conditions:
    • A Group resource containing an enumerated list of example patients exists with the IIS
      • Future Connectathons will explore how to exchange patient list data between authorized users and IIS in support of creating the patient list Group resource on the IIS
  • Out of Scope:
    • Any authentication (OAuth) steps unless implementers mutually agree to test it
  • Data Sets (Patient Groups):
    • Prior to the Connectathon, a standard data set of patients (to be organized in the form of unique Group resources containing variable numbers of patients) will be created and made available to groups playing the Responding System role. Two sets of patients will be create:
      • 10 patients constituting a diverse set of potential patient states including:
        • Patient (child) with no immunization history
        • Patient (child) with at least one immunization event documented
        • Patient (child) with at least one historical event documented
        • Patient (child) with multiple immunization events documented
        • Patient (child) with at least one refused immunization document (if refusals are in scope for the IIS)
        • Patient (adult) with at least one immunization event documented (if adult patients are in scope for the IIS)
        • Minimally populated patient with one historical immunization and one administered immunization. Only HL7 v2 R fields are valued, all others are empty.
        • Maximally populated patient with one historical immunization and one administered immunization. All HL7 v2 R and RE fields are populated.
        • Patient (child) with multiple historical events documented
        • Parent (child) with COVID immunization event documented
      • 100,000 patients  made up of 3 different "patterns":
        • Patient with no vaccines
        • Patient with 1 vaccine event each
        • Patient with 2 vaccine events each
    • Groups should be created of different sizes and be made available for query. Varying the size of the Groups will allow exercising of systems' capacity to work with variable sized data sets and allow for testing of status queries which return an "in process" status.
    • Patient Groups should be comprised of:
      • 10 patients making of the "diverse" group
      • 100 patients from the set of 100,000 patterned patients
      • 1,000 patients from the set of 100,000 patterned patients
      • 10,000 patients from the set of 100,000 patterned patients
      • 100,000 patients from the set of 100,000 patterned patients
    • Test patient/immunization event data will be available for loading in the form of HL7 v2 VXU messages
      • A flat file format can be provided upon request if needed
  • Success Criteria:
    • A set of response files, containing at least Patient and Immunization resources, are accessed by the querying system and consumed
  • Bonus Points:
    • Additional support resources (e.g. Provider, Location, Organization, RelatedPerson) are also made available in the response files
    • ImmunizationRecommendation (and potentially ImmunizationEvaluation) resources are included in the response files



...