Date: Sept 20, 2022

Quarter: Q3

Minutes Approved as Presented 

This is to approve minutes via general consent. "You have received the minutes. Are there any corrections to the minutes? (pause) Hearing none, if there are no objections, the minutes are approved as printed."


Set goals, objectives or some context for this meeting.

Discussion items

90 minNorth Start Jeremy (US Digital Service)
  • See slide deck and notes from Tuesday Q1 session
  • Working with Virginia, USDS has created a prototype pipeline for data transformations and analytics
  • Scope is reportable results (v2), immunizations (v2) and case reports (CDA) going to Virginia
    • Data is consolidated from different PH programs in Virginia
      • Authority to share and combine data is potential issue
    • Driven by need to identify COVID break through cases
  • Data is transformed/standardized to FHIR and stored to a FHIR server
    • Data that can't be converted to FHIR are stored as "invalid" 
    • They are looking at using  the NIST v2 validator for incoming v2 content
    • Includes names, phone numbers, addresses (and Geocoding (via a third-party vendor))
    • Patient linkage is being done after standardization
      • Linkages can be used in a de-identified way via a standardized hash value
    • Standardization at this point is for patients, but not other resources (but will with a goal to do so eventually)
    • The conversion service has been containerized to be cloud agnostic
  • That FHIR data is then extracted and tabularized for analytic tools to operate on
    • There is an interactive schema generator to convert from FHIR to a tabular format
      • The configuration file can be used by the tool so that FHIR calls can be made to extract the data for storing in a tabular format
      • Supports Parquet and .csv formats but they are looking at other formats
  • USDS also supports a re-conversion from the FHIR format back to a v2 message if necessary (currently for ORU messages but extensible)
    • ReportStream 
    • Will be released as open-source Java code
  • They are looking to start a Developer Community of Practice
  • In November there is planned to be a FHIR Building Block Hackathon
  • Investigating other jurisdictions to work with (including those with a lower level of technical expertise)
  • Possible wish list:
    • A way to extract data from the FHIR server for purposes other than tabularization (like reporting to other agencies)
    • Variable solutions for security as some programs have very different security requirements

Action items