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
| Line 32: | Line 32: | ||
--> | --> | ||
| − | == | + | ==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 | 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 | * Submit content for ballot - September 2016 | ||
| Line 38: | Line 38: | ||
* Submit publication Request - December 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)=== | ||
<!--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.--> | ||
| − | * [[ | + | * [[http://hl7-fhir.github.io/task.html|Task]] |
====Constraints to be Applied==== | ====Constraints to be Applied==== | ||
| Line 75: | Line 86: | ||
===Realm=== | ===Realm=== | ||
| − | + | It is a US Realm IG | |
==Ownership== | ==Ownership== | ||
| Line 81: | Line 92: | ||
<!-- 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 107: | Line 120: | ||
<!-- 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 114: | Line 127: | ||
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 |
Revision as of 21:21, 22 May 2016
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)
- [[1]]
Constraints to be Applied
- Constraint 1
- Constraint 2
Extensions to be Applied
- Extension 1
- Extension 2
Example Scenarios
Scope of coverage
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
