DAF-Research Profile List and Mappings from FHIR to PCORnet CDM and OMOP CDM

The next few sections identify the profiles used by DAF-Research and capability statements specific to DAF-Research along with resource/data element mappings between FHIR and PCORnet CDM and between FHIR and OMOP CDM.

DAF-Research defined profiles and operations

The following is a list of DAF-Research defined profiles and operations that are used for implementing PCORnet actors and capabilities along with their workflow requirements.

DAF-Research Profiles and Operations	Usage
DAF-Task	The profile is used to satisfy PCORnet workflow requirements for data extraction, data mart loading, submitting queries and returning results.
DAF-Provenance	The profile is used to keep track of provenance data for data mart loading, submitting queries and getting results back.
DAF-OperationDefinition	The profile is used to publish what data models and what query formats are supported for each DAF-Research operation.
DAF-CapabilityStatement	The profile is used to publish what operations are supported by each DAF-Research actor.
DAF-QueryResults	The profile is used to provide aggregate results to the Researcher who submits queries.
daf-extract-operation	The profile is used to extract data for all or a subset of patients from data sources using FHIR APIs.
daf-load-operation	The profile is used to load data extracted from data sources in data marts.
daf-execute-query	The operation is used to execute a DAF-Research query and create query results.

Profiles and FHIR Resources used by DAF-Research for Data Extraction and Data Mapping

This paragraph identifies a list of profiles from US-Core that are reused by DAF-Research, along with ones explicitly defined by DAF-Research. In addition a few of the FHIR Resources are used without profiling currently. These resources may be profiled in the future depending on feedback obtained from DAF-Research pilots.

US-Core profiles used by DAF-Research

DAF-Research specific profiles of US-Core

We are not profiling any of the US-Core profiles but may add if needed based on pilot feedback.

Base FHIR Resources used without profiling by DAF-Research

Mappings from FHIR to PCORnet CDM

NOTE: Mappings from one data model to another such as FHIR to PCORnet CDM or FHIR to OMOP etc, always have a potential for data loss. In these cases where there is not an exact mapping between codes the extraction process is encouraged to include the actual raw values if permitted by the data model. For example in FHIR the Coding element can be used to accommodate all the local values which were used to translate to standardized codes.

PCORnet CDM Table Name	Recommended Profile/Resource for Data Extraction
DIAGNOSIS, CONDITION	Condition
LAB_RESULT_CM	DiagnosticReport-Results,Observation
ENCOUNTER	Encounter
PRESCRIBING	MedicationOrder
DISPENSING	MedicationDispense
VITALS	Observation-Vitalsigns
DEMOGRAPHIC	Patient
PROCEDURES	Procedure
PRO CM	Questionaire,Observation
ENROLLMENT	ResearchSubject
PCORNET_TRIAL	ResearchStudy
DEATH	Patient
DEATH_CAUSE	Patient
HARVEST	DAF-CapabilityStatement

A detailed data element level mapping can be accessed here:

FHIR to PCORnet CDM mapping

Mappings between FHIR and OMOP CDM

OMOP Table Name	Recommended Profile/Resource for Data Extraction
Concept,Vocabulary,Domain,Concept_Synonym,Concept_Ancestor	ValueSet
Concept_Class	Concept
Concept_Relationship, Relationship	ConceptMap
Cohort_Definition, Attribute_Definition	Group
Specimen	Specimen
Drug_Strength	Medication
Procedure_Occurence	Procedure
Drug_Exposure	MedicationOrder,MedicationStatement,Immunization
Device_Exposure	Procedure,Device
Measurement,Note,Observation	Observation
Person	Patient
Observation_Period, Visit_Occurence	Encounter
Condition_Occurence	Condition

A detailed data element level mapping can be accessed here:

OMOP to FHIR mapping