This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "DAF FHIR Profile Proposal"

From HL7Wiki
Jump to navigation Jump to search
 
(14 intermediate revisions by one other user not shown)
Line 3: Line 3:
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<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:Approved  FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
 
</div>
 
</div>
 
</div>
 
</div>
 
[[Category:FHIR Resource Proposal]]
 
[[Category:FHIR Resource Proposal]]
 
[[Category:FHIR Profile Proposal]]
 
[[Category:FHIR Profile Proposal]]
−
[[Category:Pending FHIR Profile Proposal]]
+
[[Category:Approved FHIR Profile Proposal]]
  
  
Line 54: Line 54:
 
* [http://www.hl7.org/implement/standards/fhir/medicationdispense.html MedicationDispense]
 
* [http://www.hl7.org/implement/standards/fhir/medicationdispense.html MedicationDispense]
 
* [http://www.hl7.org/implement/standards/fhir/allergyintolerance.html AllergyIntolerance]
 
* [http://www.hl7.org/implement/standards/fhir/allergyintolerance.html AllergyIntolerance]
−
* [http://www.hl7.org/implement/standards/fhir/order.html Order]
+
* [http://www.hl7.org/implement/standards/fhir/diagnosticorder.html DiagnosticOrder]
 +
* [http://www.hl7.org/implement/standards/fhir/diagnosticreport.html DiagnosticReport]
 
* [http://www.hl7.org/implement/standards/fhir/procedure.html Procedure]
 
* [http://www.hl7.org/implement/standards/fhir/procedure.html Procedure]
 
* [http://www.hl7.org/implement/standards/fhir/immunization.html Immunization]
 
* [http://www.hl7.org/implement/standards/fhir/immunization.html Immunization]
 
* [http://www.hl7.org/implement/standards/fhir/familyhistory.html FamilyHistory]
 
* [http://www.hl7.org/implement/standards/fhir/familyhistory.html FamilyHistory]
 +
* [http://www.hl7.org/implement/standards/fhir/practitioner.html Practitioner]
 +
* [http://www.hl7.org/implement/standards/fhir/list.html List]
  
 
====Constraints to be Applied====
 
====Constraints to be Applied====
−
 
+
The following constraints will be applied to the FHIR resources as necessary.
 
<!--Describe how the current resource will be constrained.-->
 
<!--Describe how the current resource will be constrained.-->
−
* Constraint 1
+
* Constrain the cardinality of the data elements within the resource.
−
* Constraint 2
+
* Constrain the mustSupport attribute of the data elements within the resource.
 +
* Define searchParameters as necessary for the resource.
 +
* Constrain vocabularies to Meaningful Use Stage 2 specific vocabularies for the resources as applicable.
  
 
====Extensions to be Applied====
 
====Extensions to be Applied====
−
 
+
The following extensions may be applied to resources as appropriate.
 
<!--Describe how the current resource will be extended.-->
 
<!--Describe how the current resource will be extended.-->
−
* Extension 1
+
* US Realm specific extensions for the various FHIR resources.
−
* Extension 2
 
  
 
===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.) -->
 +
* Query Examples for each resource
 +
* Query Result Examples for each resource
  
 
===Scope of coverage===
 
===Scope of coverage===
Line 87: Line 93:
 
As a rule, Profiles should encompass all of these aspects.
 
As a rule, Profiles should encompass all of these aspects.
 
-->
 
-->
 +
 +
* Subject: Patient
 +
* Disciplines: Patient Care, Clinical Research, Public Health
 +
* Delivery Environment: Inpatient, Ambulatory, Community, Emergency etc.
 +
* Locale: United States
  
 
==Ownership==
 
==Ownership==
Line 92: Line 103:
  
 
<!-- 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. -->
−
[[YourCommitteeName]]
+
[[Infrastructure and Messaging]]
  
 
===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) -->
−
* Work Group Name
+
* Structured Documents
−
* or link
+
* Orders and Observations
−
* or "None"
+
* Templates
 +
* Conformance Guidance for Implementation and Testing
 +
* Patient Administration
 +
* Patient Care
 +
* Pharmacy
 +
* Public Health Emergency Response
  
 
===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. -->
 +
* ONC S&I Framework DAF Pilots
 +
* ONC Standards Implementation and Testing Environment
  
 
===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 (a.k.a Dragon)
 +
* Brett Marquard
  
 
===FHIR Profile Development Project Insight ID===
 
===FHIR Profile Development Project Insight ID===
  
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
 +
* Pending
  
 
==Plans==
 
==Plans==
Line 118: Line 138:
  
 
<!-- 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 -->
−
*TargetDateForInternalReview
+
* October 2014
  
 
===Balloting Requirements===
 
===Balloting Requirements===
Line 124: Line 144:
 
<!-- Indicate the intended method of balloting by choosing one of the options below, or propose alternative.  If Realm Specific or No Ballot indicate the amount of informal review required by the FHIR community.-->
 
<!-- Indicate the intended method of balloting by choosing one of the options below, or propose alternative.  If Realm Specific or No Ballot indicate the amount of informal review required by the FHIR community.-->
  
−
Choose one:
+
* Ballot independently as DSTU
−
*Ballot with next FHIR DSTU or Normative Edition
+
* US Realm Specific Ballot as appropriate
−
*or Ballot independently as DSTU
 
−
*or Realm specific ballot
 
−
*or No Ballot
 
  
 
<!-- Indicate the desired ballot date.-->
 
<!-- Indicate the desired ballot date.-->
 
Desired Ballot Date
 
Desired Ballot Date
−
*PutDesiredBallotDateHere
+
* Submit Draft for Comment - December 2014
 +
* Submit for DSTU - March 2015
 +
* Ballot Reconcilation - May 2015
 +
* DSTU Period - June 2015

Latest revision as of 20:05, 5 December 2014

OpenHotTopic.GIF

This page documents a Pending FHIR Resource Proposal



Data Access Framework (DAF) FHIR Profile Proposal

This project aims to create Fast Healthcare Interoperability Resources (FHIR) Profiles for access to discrete meaningful-use information as FHIR resource instances. In some cases, the profiles will extend beyond meaningful use data requirements based on stakeholder feedback. This project will not create a profile for document access since this is covered by the Integrating Healthcare Enterprise Mobile access to Health Documents (IHE MHDv2).

The Artifacts to be produced as part of this project include:

  • Define profiles on selected FHIR resources that define additional search criteria for retrieving those resources.
  • Define a conformance resource instance that defines expectant system behavior on server side, client side for DAF conformant systems. Project expects one for client, and one for servers.
  • Create profiles on selected FHIR resources identifying minimum data and corresponding constraints and value sets for query response.This activity may overlap with C-CDA on FHIR activities to some extent. See notes below on coordination with C-CDA on FHIR project.
  • Define a DAF implementation guide that organizes and provides context for the above artifacts.


Coordination with CCDA on FHIR project: This project will coordinate with the C-CDA on FHIR project to minimize duplicate profiles on common resources. An additional profile will only be created if the C-CDA profile doesn’t already exist for the resource, or the C-CDA profile doesn’t include required data elements in a current resource to support DAF. Coordination with the C-CDA on FHIR will be done by engagement with the work groups responsible for FHIR resources. Where multiple profiles are required on the same resource, common data elements will be kept in alignment; Where different profiles require different scope in near term, additional work will be done in future to bring back into alignment.The DAF Profile(s) will build from the existing work of the Standards & Interoperability (S&I) Data Access Framework (DAF) Initiative.


Profile Details

The following FHIR resources will be profiled.

Constraints to be Applied

The following constraints will be applied to the FHIR resources as necessary.

  • Constrain the cardinality of the data elements within the resource.
  • Constrain the mustSupport attribute of the data elements within the resource.
  • Define searchParameters as necessary for the resource.
  • Constrain vocabularies to Meaningful Use Stage 2 specific vocabularies for the resources as applicable.

Extensions to be Applied

The following extensions may be applied to resources as appropriate.

  • US Realm specific extensions for the various FHIR resources.

Example Scenarios

  • Query Examples for each resource
  • Query Result Examples for each resource

Scope of coverage

  • Subject: Patient
  • Disciplines: Patient Care, Clinical Research, Public Health
  • Delivery Environment: Inpatient, Ambulatory, Community, Emergency etc.
  • Locale: United States

Ownership

Owning committee name

Infrastructure and Messaging

Contributing or Reviewing Work Groups

  • Structured Documents
  • Orders and Observations
  • Templates
  • Conformance Guidance for Implementation and Testing
  • Patient Administration
  • Patient Care
  • Pharmacy
  • Public Health Emergency Response

Expected implementations

  • ONC S&I Framework DAF Pilots
  • ONC Standards Implementation and Testing Environment

gForge Users

  • Nagesh Bashyam (a.k.a Dragon)
  • Brett Marquard

FHIR Profile Development Project Insight ID

  • Pending

Plans

Timelines

  • October 2014

Balloting Requirements

  • Ballot independently as DSTU
  • US Realm Specific Ballot as appropriate

Desired Ballot Date

  • Submit Draft for Comment - December 2014
  • Submit for DSTU - March 2015
  • Ballot Reconcilation - May 2015
  • DSTU Period - June 2015
Retrieved from "https://wiki.hl7.org/w/index.php?title=DAF_FHIR_Profile_Proposal&oldid=93821"