This wiki has undergone a migration to Confluence found Here
Difference between revisions of "DAF Phase3 FHIR IG Proposal"
Jump to navigation
Jump to search
(Created page with "{{subst::Template:FHIR Profile Proposal}}") |
(migrate to Confluence) |
||
| (10 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
<div class="messagebox cleanup metadata"> | <div class="messagebox cleanup metadata"> | ||
| − | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | + | Current version: https://confluence.hl7.org/display/FHIR/DAF+Phase3+FHIR+IG+Proposal<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> |
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] | This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] | ||
| Line 14: | Line 14: | ||
| − | = | + | =DAF Research Data Access IG= |
| + | |||
| + | This DAF implementation guide will specify the necessary conformance requirements, profiles, extensions and vocabularies necessary to enable researchers to access data from one or more data sources. This implementation guide will complement the existing DAF FHIR IG. While the existing DAF FHIR IG is expected to be used to enable use cases which deal with a single patient, the DAF Research Data Access IG will deal with extracting data for multiple patients from data sources such as EMRs, local databases. | ||
| + | |||
<!-- Profile names should meet the following characteristics: | <!-- Profile names should meet the following characteristics: | ||
| Line 28: | Line 31: | ||
* Incorporate the name of the Resource being profiled | * Incorporate the name of the Resource being profiled | ||
--> | --> | ||
| + | ==Implementation Guide balloting plans== | ||
| + | The balloting of the DAF Research Data Access IG will follow the FHIR STU3 timelines. The DAF milestones are listed below | ||
| − | + | *Submit content for ballot - September 2016 | |
| + | *Complete ballot Reconciliation - November 2016 | ||
| + | *Submit publication Request - December 2016 | ||
| + | ==Implementation Guide Details== | ||
| + | The DAF Initiative which is sponsored by the Office of the National Coordinator (ONC) is currently piloting with PCORNet (Patient Centered Outcome Research Network) sites to enable data access for researchers using FHIR constructs. As part of the initiative the following capabilities are being developed | ||
| − | + | *Capability to use FHIR resources and profiles to extract data from data sources for multiple patients | |
| + | *Capability to populate data marts from multiple data sources to make the data available to researchers | ||
| + | *Capability that defines metadata about data marts that will be useful for researchers to formulate hypothesis, trial concepts, define queries | ||
| + | *Capability that allows researchers to submit different types of queries (FHIR Search based queries, SASS queries, SQL queries, Other proprietary queries) | ||
| + | *Capability that allows data marts to send back aggregate data to researcher based on queries | ||
| + | *Capability that allows data marts to send back patient level data to researchers based on queries | ||
| + | *Capability to use FHIR Search/Query mechanisms to build cohorts | ||
| + | |||
| + | Each of these capabilities will be implemented using PCORNet sites and the implementation guide content will be based on the feedback obtained from these implementations. | ||
===Profiled Resource(s)=== | ===Profiled Resource(s)=== | ||
| + | |||
| + | The following are resources that are being considered for defining the data extraction, metadata representation, query packaging, query submission and retrieving query results. | ||
<!--Put a link to the resource/datatype (or group of resources) that will be profiled here.--> | <!--Put a link to the resource/datatype (or group of resources) that will be profiled here.--> | ||
| − | * | + | *Bundle: http://hl7-fhir.github.io/bundle.html |
| + | *Task : http://hl7-fhir.github.io/task.html | ||
| + | *Operation Definition: http://hl7-fhir.github.io/operationdefinition.html | ||
| + | *Conformance: http://hl7-fhir.github.io/conformance.html | ||
| + | *Consent: http://hl7-fhir.github.io/consent.html | ||
| + | *Parameters: http://hl7-fhir.github.io/parameters.html | ||
| + | *Observation: http://hl7-fhir.github.io/observation.html | ||
| + | *MeasureReport: http://hl7-fhir.github.io/measurereport.html | ||
====Constraints to be Applied==== | ====Constraints to be Applied==== | ||
<!--Describe how the current resource will be constrained.--> | <!--Describe how the current resource will be constrained.--> | ||
| − | * | + | *The IG will define how to instantiate a data extraction task for extracting bulk data for research purposes. |
| − | * | + | *The IG will define how to characterize a data mart that can be used by researchers to formulate queries. |
| + | *The IG will define how to use Task, Operation Definition and Parameters to submit queries. | ||
| + | *The IG will define how to use Observations or Measure Reports to retrieve aggregate data. | ||
| + | *The IG will define how to use the existing DAF IG patient level profiles. | ||
| + | *The IG will provide data mapping between FHIR and PCORNet CDM. | ||
====Extensions to be Applied==== | ====Extensions to be Applied==== | ||
<!--Describe how the current resource will be extended.--> | <!--Describe how the current resource will be extended.--> | ||
| − | * | + | *Extensions will be needed to characterize data mart meta data. |
| − | * | + | *Extensions may also be needed for the other resources, they will be based on the actual implementation needs. |
===Example Scenarios=== | ===Example Scenarios=== | ||
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this Profile. They should demonstrate the full scope of the Profile and allow exercising of the Profiles capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | <!-- Provide a listing of the types of scenarios to be represented in the examples produced for this Profile. They should demonstrate the full scope of the Profile and allow exercising of the Profiles capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | ||
| + | |||
| + | *A PCORNet site would like to extract data from multiple different data sources supported by different EMR vendors to populate a data mart that will be used for PCORNet research studies. | ||
| + | *A researcher would like to retrieve the characteristics of a data mart to determine the total number of patients represented in the data mart, the platforms that are supported for queries etc. | ||
| + | *A researcher would like to submit a query to determine the total number of patients with diabetes within the age group of 20 and 70 stratified by race, age groups, postal codes. | ||
===Scope of coverage=== | ===Scope of coverage=== | ||
| − | |||
<!-- Define the full scope of coverage for the Profile. The scope must be clearly delineated such that it does not overlap with any other existing or expected Profile. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | <!-- Define the full scope of coverage for the Profile. The scope must be clearly delineated such that it does not overlap with any other existing or expected Profile. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | ||
| Line 67: | Line 100: | ||
As a rule, Profiles should encompass all of these aspects. | As a rule, Profiles should encompass all of these aspects. | ||
--> | --> | ||
| + | The Scope of the IG is as defined in the previous sections. | ||
===Realm=== | ===Realm=== | ||
| − | + | It is a US Realm IG | |
==Ownership== | ==Ownership== | ||
| Line 75: | Line 109: | ||
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the Profiles. --> | <!-- The name of the committee that is proposed to have responsibility for developing and maintaining the Profiles. --> | ||
| − | [[ | + | [[FHIR Infrastructure WG]] |
===Contributing or Reviewing Work Groups=== | ===Contributing or Reviewing Work Groups=== | ||
<!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the Profile (optional) --> | <!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the Profile (optional) --> | ||
| − | * | + | *Infrastructure and Messaging |
| − | * | + | *RCRIM |
| − | |||
===Expected implementations=== | ===Expected implementations=== | ||
<!--Key Profiles are justified by CCDA, for Profiles not deemed "key", what interest is there by implementers in using this particular Profile. Provide named implementations if possible - ideally provide multiple independent implementations. --> | <!--Key Profiles are justified by CCDA, for Profiles not deemed "key", what interest is there by implementers in using this particular Profile. Provide named implementations if possible - ideally provide multiple independent implementations. --> | ||
| + | *PCORNet CDRN REACHNet | ||
| + | *PCORNet CDRN pSCANNER | ||
===gForge Users=== | ===gForge Users=== | ||
<!-- Identify the userids who will require commit access to gForge to maintain the Profile. (Ensure all users have registered for gForge.) --> | <!-- Identify the userids who will require commit access to gForge to maintain the Profile. (Ensure all users have registered for gForge.) --> | ||
| − | + | *Nagesh Bashyam | |
| + | *Brett Marquard | ||
===FHIR Profile Development Project Insight ID=== | ===FHIR Profile Development Project Insight ID=== | ||
| Line 101: | Line 137: | ||
<!-- Indicate the target date for having the Profile complete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the Profile complete from a committee perspective and ready for vetting and voting --> | ||
| − | * | + | *Will be following FHIR STU 3 timelines, along with meeting the timelines from FHIR Infrastructure WG. |
===Balloting Requirements=== | ===Balloting Requirements=== | ||
| Line 108: | Line 144: | ||
Choose one: | Choose one: | ||
| − | *Ballot with next FHIR | + | |
| − | + | *Ballot with next FHIR STU | |
| − | |||
| − | |||
<!-- Indicate the desired ballot date.--> | <!-- Indicate the desired ballot date.--> | ||
Desired Ballot Date | Desired Ballot Date | ||
| − | * | + | |
| + | *September 2016 | ||
Latest revision as of 16:06, 31 October 2019
Current version: https://confluence.hl7.org/display/FHIR/DAF+Phase3+FHIR+IG+Proposal
This page documents a Pending FHIR Resource Proposal
Contents
DAF Research Data Access IG
This DAF implementation guide will specify the necessary conformance requirements, profiles, extensions and vocabularies necessary to enable researchers to access data from one or more data sources. This implementation guide will complement the existing DAF FHIR IG. While the existing DAF FHIR IG is expected to be used to enable use cases which deal with a single patient, the DAF Research Data Access IG will deal with extracting data for multiple patients from data sources such as EMRs, local databases.
Implementation Guide balloting plans
The balloting of the DAF Research Data Access IG will follow the FHIR STU3 timelines. The DAF milestones are listed below
- Submit content for ballot - September 2016
- Complete ballot Reconciliation - November 2016
- Submit publication Request - December 2016
Implementation Guide Details
The DAF Initiative which is sponsored by the Office of the National Coordinator (ONC) is currently piloting with PCORNet (Patient Centered Outcome Research Network) sites to enable data access for researchers using FHIR constructs. As part of the initiative the following capabilities are being developed
- Capability to use FHIR resources and profiles to extract data from data sources for multiple patients
- Capability to populate data marts from multiple data sources to make the data available to researchers
- Capability that defines metadata about data marts that will be useful for researchers to formulate hypothesis, trial concepts, define queries
- Capability that allows researchers to submit different types of queries (FHIR Search based queries, SASS queries, SQL queries, Other proprietary queries)
- Capability that allows data marts to send back aggregate data to researcher based on queries
- Capability that allows data marts to send back patient level data to researchers based on queries
- Capability to use FHIR Search/Query mechanisms to build cohorts
Each of these capabilities will be implemented using PCORNet sites and the implementation guide content will be based on the feedback obtained from these implementations.
Profiled Resource(s)
The following are resources that are being considered for defining the data extraction, metadata representation, query packaging, query submission and retrieving query results.
- Bundle: http://hl7-fhir.github.io/bundle.html
- Task : http://hl7-fhir.github.io/task.html
- Operation Definition: http://hl7-fhir.github.io/operationdefinition.html
- Conformance: http://hl7-fhir.github.io/conformance.html
- Consent: http://hl7-fhir.github.io/consent.html
- Parameters: http://hl7-fhir.github.io/parameters.html
- Observation: http://hl7-fhir.github.io/observation.html
- MeasureReport: http://hl7-fhir.github.io/measurereport.html
Constraints to be Applied
- The IG will define how to instantiate a data extraction task for extracting bulk data for research purposes.
- The IG will define how to characterize a data mart that can be used by researchers to formulate queries.
- The IG will define how to use Task, Operation Definition and Parameters to submit queries.
- The IG will define how to use Observations or Measure Reports to retrieve aggregate data.
- The IG will define how to use the existing DAF IG patient level profiles.
- The IG will provide data mapping between FHIR and PCORNet CDM.
Extensions to be Applied
- Extensions will be needed to characterize data mart meta data.
- Extensions may also be needed for the other resources, they will be based on the actual implementation needs.
Example Scenarios
- A PCORNet site would like to extract data from multiple different data sources supported by different EMR vendors to populate a data mart that will be used for PCORNet research studies.
- A researcher would like to retrieve the characteristics of a data mart to determine the total number of patients represented in the data mart, the platforms that are supported for queries etc.
- A researcher would like to submit a query to determine the total number of patients with diabetes within the age group of 20 and 70 stratified by race, age groups, postal codes.
Scope of coverage
The Scope of the IG is as defined in the previous sections.
Realm
It is a US Realm IG
Ownership
Owning committee name
Contributing or Reviewing Work Groups
- Infrastructure and Messaging
- RCRIM
Expected implementations
- PCORNet CDRN REACHNet
- PCORNet CDRN pSCANNER
gForge Users
- Nagesh Bashyam
- Brett Marquard
FHIR Profile Development Project Insight ID
Plans
Timelines
- Will be following FHIR STU 3 timelines, along with meeting the timelines from FHIR Infrastructure WG.
Balloting Requirements
Choose one:
- Ballot with next FHIR STU
Desired Ballot Date
- September 2016
