Chair and Scribe: Floyd Eisenberg 

Minutes from last call: OMOP Quality Measurement 23 March 2022

Recording of this call (access requires passcode):

The FHIR-OMOP WG- subgroups are as follows:

    • Data Model Harmonization 
    • Data Quality Measurements 
    • Terminologies 
    • Oncology 

Zoom Meeting:

Agenda TopicDiscussion Notes
New Discussion Topics/Updates:

Overview - Presentation from OMOP All-Hands Meeting March 28, 2022: FHIR_OMOP_All Hands_28March2022_dQM.pptxFloyd reviewed the slides from the OMOP All-Hands call.  Paul Denning noted the second use case, OMOP to FHIR cohort with unknown patient population, might also have a FHIR to OMOP direction. Others confirm the asynchronous unknown patient cohort use case may be bidirectional.

Update discussion regarding Jack Brewster's (IQVIA) presentation for automatically importing VSAC value sets into OMOP. 

Davera noted that Hopkins automated the front end of the process - pull VSAC value sets into the NCC enclave, they do it in bulk using the NLM API. That process and the one presented by Jack Brewster last meeting may help develop a common approach. There is still work to be done. It was done for NCC and is not FHIR-involved.  There is a call to the NLM FHIR API. It is something this group might take on. There is no current activity taking an OMOP value set and converting to a VSAC value set - VSAC doesn't have OMOP vocabulary currently. And, there is no business arrangement between OHDSI and NLM that would need to be established to make this work.  Globally, Darwin EU is creating momentum for a repository for value sets - doesn't have the same infrastructure as VSAC but has a similar inventory.  The machinery is not currently optimized but it can be explored and evaluated as a demonstration. Sebastiaan is working on the European use case - this discussion has been very US focused. The European community is aligned with the ICHOM outcomes work: ICHOM IG

Discussion of OMOP-Atlas to FHIR-CQL conversion - what are next steps?

Discussion about creating content for a track in the Digital Quality Summit. Davera asked if there might be an ability to present in the CMS Connectathon in July. CMS 2022 - 07 FHIR Connectathon 3

Discussion about potential synthetic patient set in (a) FHIR, (b) OMOP

No new discussion.

Follow up next steps from last call  - validate actions needed: Reminder from last call regarding COVID Criteria for cohort:; Describe requirements for the various components of the architecture - Seeking input from WG members:


  • Infrastructure:
    • VSAC value sets and FHIR API
    • Programmatic methodology for extracting VSAC value sets and mapping terms to OMOP terminology (current manual upload)
    • Recommendations for handling concepts missing from OMOP (such as examples Qi experienced for HSLOC and CDC Race and Ethnicity Codes)
    • Subscription or periodic requery when VSAC updates the terminology
  • Participants:
    • TBD

Further detail would be use-case specific. Content requirements include characteristics to match the use case. Do we specify the use case and then build the data? If we assume the demonstration is the COVID and matched control cohorts - we would need ICD-10 on the terminology server (reference terminology in synthetic data) and assure the synthetic data meet the phenotype expression.

Content Requirements for COVID Use case: 

     Reference terminologies on servers: ICD10CM, SNOMED CT, LOINC, CVX

      Synthetic cohort data matching N3C phenotype:

                    COVID positive test results

                     Comorbid conditions

                      Possible:  Vaccine admin records


  • Infrastructure:
    • Atlas - SQL capability exists - need Atlas SQL instance for pilot testing
    • FHIR - CQL capability exists - need FHIR CQL instance for pilot testing
    • Expression conversion (what infrastructure is required here):
      • Atlas phenotype to FHIR cohort conversion
      • FHIR cohort expression with CQL to Atlas phenotype conversion
  • Participants:
    • TBD
Use-case specific

Data Query and Response:

  • Infrastructure:
    • Atlas data store for synthetic patients
    • FHIR data store for synthetic patients
    • Query capability for Atlas patients and retrieve of OMOP cohort(s)
    • Query capability for FHIR patients and retrieve of FHIR synthetic cohort(s)
    • Structure to compare OMOP cohort with FHIR cohort, identify concordance and challenges
  • Participants:
    • TBD

Next Steps from March 9:

  • Continue to build on Project Scope Statement PSS-1981 such that it can be progressed.
  • Further discussions with Vulcan to understand potential Accelerator support.
  • At this point, if folks want to move forward with the project and/or Connectathon piloting, we definitely need people to step up to do the work to define the elements, to create the prototypes, and to pilot them.

New Next Steps:

Davera and Kristin will fill in the infrastructure requirements for the last 3 row for discussion in future calls.

The next call, April 20 will be 30 minutes for OMOP-dQM and the remaining 30 minutes will address May FHIR Connectathon planning.  The May 4 meeting will be cancelled as it is during the May HL7 FHIR Connectathon. The next call after April 20 will be May 18, 2022.

AdjournmentAdjourned at 10:52 AM ET


AttendeeAttendee's OrganizationAttendee's emailPresent
1Abdullah RafiqiESAC




Ben Hamlin


5Bryan Laraway 



8Johns Hopkinsdgabrie4@jh.eduyes
9Dipti Gandhi

10Dorothy LeeNCQA

11Edward Smith

12Esther Ndemo 

13Evan Patrick Minty


Floyd Eisenberg

iParsimony, LLC


16Jack BrewsterIQVIA

17James Brash 

18Jamie Smith


20John David Evans


22Julia Dawson


24Justin McKelvy

25Kristin Kostka

26Latasha Estrada

27Luis Alaniz 



30Ming Dunajick







37Raju Hemadri

38Raquel Belarmino


40@Sandra Siami

41Sebastian van SandijkOdysseus
42Shaun Shakib



44MedStar Health

45Vickie Reyes (GC) 

46Yan Heras 


48Zhen Lin

  • No labels