1

DAF Phase 3 ObjectiveDAF Phase 3 Objective

Enable researchers to access data from multiple organizations and data sources within a Learning Health System (LHS) infrastructure

2

PCORI/PCORnet PCORI/PCORnet Abstract Abstract ModelModel

Researcher Interface

23CDRN 1Data

Mart

Data Source 2

Patient Generated Data

1

CDRN 2Data Mart

PPRNData Mart

Data Source 1

5

Step 1: Creation of Data Marts within CDRN’s and PPRN’s1.Export Transform Loads are written to extract data from one or more data sources and loaded into a data mart to be queried by researchersStep 2-5: Researcher submitting a query and examining the query results2.Researcher composes a query to be submitted to various data marts (permissions and access controls determine who can query what data, at what time, and for what purpose)3.Queries are distributed to various sites depending on access controls, frequency, date, time, orchestration pattern, etc.4.Queries are executed and results computed on the data marts, optionally reviewed manually5.Query results are released by the networks to the researcher along with data disclosure policies

4

3

Step 1Step 1

CDRN 1Data Mart

Data Source 2

Patient Generated Data

1

CDRN 2Data Mart

PPRNData Mart

Data Source 1

• Proprietary Extract Transform Loads (ETLs) are used to extract data from data sources and populate the PCORNet CDM.

• ETLs are created by the CDRNs working with the vendors for each data source onboarded onto the CDRN/PPRN.In DAF Phase 3 these would be replaced by1. Data Source implementing a FHIR Extraction layer using DAF FHIR profiles.2. DAF FHIR profiles to PCORNet CDM mapping to enable data mart population3. Pilot would pilot capability (C1): Standardize data extraction mechanism from clinical data sourcesPotential Pilot• Cerner with GPC CDRN• LA CDRN• pSCANNER

4

Steps 2Steps 2

PopMedNet’s Implementation of Query Composition Portal, Data Mart Management View and Query Results View In DAF Phase 3:• Data Mart Management View would be standardized using FHIR resources in capability C2: Standardize metadata about data marts, data sources and networks •Query Composition portal would be standardized using FHIR queries in capability C6: Standardize Query Structure•Query Results View would be standardized using FHIR resources in capability C4: Standardize Query Results for aggregate data and C5: Standardize Query Results for de-identified and patient level dataPotential Pilot•PopMedNet

Researcher Interface

2CDRN 1Data Mart

CDRN 2Data Mart

PPRNData Mart

5

Steps 3-5Steps 3-5

PopMedNet’s implementation of Query Distribution mechanism and Query Results View CreatorIn DAF Phase 3:• Query Distribution mechanism would be standardized using FHIR resources in capability C3: Standardize Query Distribution mechanism•Query Results View Creator would be standardized using FHIR resources in capability C4: Standardize Query Results for aggregate data and C5: Standardize Query Results for de-identified and patient level dataPotential Pilot•PopMedNet

Researcher Interface

3CDRN 1Data Mart

CDRN 2Data Mart

PPRNData Mart

5

PopMedNet’s implementation of Query Responder Agent, Query Result Creator, Query Execution AgentIn DAF Phase 3:•Query Responder Agent would be standardized using FHIR resources in capability C3: Standardize Query Distribution mechanism•Query Results Creator would be standardized to use FHIR resources in capability C4: Standardize Query Results for aggregate data and C5: Standardize Query Results for de-identified and patient level data•Query Execution Agent would be standardized using FHIR queries in capability C6: Standardize Query StructurePotential Pilots•PopMedNet

4

6

Proposed Technical Proposed Technical CapabilitiesCapabilities

Capability BenefitsAbstract Model

ReferencePilot Deliverable

C1: Standardize data extraction mechanism from clinical data sources

Reduces the onboarding time for data sources within each network

Step 1 • DAF Extract Transform Load (ETL) Technical Specification written by DAF support team based on pilot feedback

• Reuses all the work completed in DAF Phases 1 & 2

C2: Standardize metadata about data marts, data sources and networks

Provides researchers ability to determine which networks have the right data for their activities

Happens out of band

currently

• Proposal and content submitted to HL7 for new FHIR resources capturing the data mart metadata

C3: Standardize Query Distribution mechanism

LHS Data infrastructure not tied to a particular vendor or productAlso helps bridge multiple networks

Step 3 • Proposal and content submitted to HL7 for new FHIR resources to submit queries

7

Capability Benefits Abstract Model Reference

Deliverables

C4: Standardize Query Results for aggregate data

LHS Data infrastructure not tied to a particular vendor or productCan be used for other use cases such as surveillance, quality reporting

Step 5 • Proposal and content submitted to HL7 for new FHIR resources capturing the query results data

• Includes View Create and View Results

• Proposal covers C4

C5: Standardize Query Results for de-identified and patient level data

LHS Data infrastructure not tied to a particular vendor or productCan be used for other use cases such as surveillance, quality reporting

Step 5 • Proposal and content submitted to HL7 for new FHIR resources capturing the query results data

• Proposal covers C5

C6: Standardize Query Structure

LHS Data infrastructure not tied to a particular vendor or product

Step 2 • DAF Support team Draft a “DAF Query Composition Technical Specification” based on pilot feedback

• Reuses existing FHIR Search capability

• Includes Composition Portal and Query Execution Agent

• Technical Specification Covers C6

Proposed Technical Proposed Technical Capabilities Capabilities CONTINUEDCONTINUED