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

Difference between revisions of "Da Vinci HRex FHIR IG Proposal"

From HL7Wiki
Jump to navigation Jump to search
 
(21 intermediate revisions by 3 users 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 IG Proposal|Pending]] [[:category:FHIR IG Proposal|FHIR IG Proposal]]
+
This page documents a [[:category:Approved FHIR IG Proposal|Approved]] [[:category:FHIR IG Proposal|FHIR IG Proposal]]
 
</div>
 
</div>
 
</div>
 
</div>
 
[[Category:FHIR IG Proposal]]
 
[[Category:FHIR IG Proposal]]
−
[[Category:Pending FHIR IG Proposal]]
+
[[Category:Approved FHIR IG Proposal]]
  
  
Line 25: Line 25:
 
* Be consistent with other similar IGs
 
* Be consistent with other similar IGs
 
  -->
 
  -->
 +
 +
HL7 FHIR® Implementation Guide: Health Record Exchange (HRex) Framework, Release 1 (HL7_FHIR_IG_HRex)
  
 
==Owning work group name==
 
==Owning work group name==
Line 32: Line 34:
  
 
==Committee Approval Date:==
 
==Committee Approval Date:==
−
<i>Please enter the date that the committee approved this IGproposal</i>
+
<i>Approved by CIC WG on Thursday, March 28, 2019</i>
  
 
==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 IG (optional) -->
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the IG (optional) -->
−
* Work Group Name
+
* FM
−
* or link
+
* Patient Care
−
* or "None"
 
  
 
==FHIR Development Project Insight ID==
 
==FHIR Development Project Insight ID==
Line 49: Line 50:
 
==Scope of coverage==
 
==Scope of coverage==
  
−
The Health Record exchange (HRex) Framework is part of the larger Da Vinci use case for Health Record exchange (HRex).
+
US-centric, payer related shared artifacts
  
−
The project scope statement (PSS) can be found here:
+
==IG Purpose==
  
−
https://confluence.hl7.org/display/CIC/PSS+for+Health+Record++Exchange+%28HRex%29+Framework
+
<!-- Why is this IG necessary? -->
−
 
 
−
After careful evaluation, the HRex project was decomposed into four independent efforts (and tied to 4 separate PSSs). The exchange of Quality Measures was included in the existing work on the Data Exchange for Quality Measures (DEQM) that is sponsored by the CQI workgroup. The exchange of Payer Data (PDex) is sponsored by Financial Management. The exchange of provider originated data or Clinical Data exchange (CDex) is sponsored by Patient Care. The overall HRex Framework described in the PSS is planned to be sponsored by CIC as a US Realm specific framework that defines common elements and interactions necessary for the other implementation guides.
 
−
 
 
−
The following depicts the relationship of the multiple Da Vinci use cases developed during 2018 and planned for 2019.  Many of these will use the HRex Framework as their basis for defining the use of specific FHIR artifacts.
 
−
 
 
−
https://confluence.hl7.org/download/attachments/40738385/image2019-1-29_5-44-7.png?version=1&modificationDate=1548762242388&api=v2
 
−
 
 
−
The scope of the HRex Framework project is to defined combinations of exchange methods (push, pull, subscribe, CDS Hooks, …), specific payloads (Documents, Bundles, and Individual Resources), search criteria, conformance, provenance, and other relevant requirements to support specific exchanges of clinical information between: 1) providers, 2) a provider and a payer, 3) a payer and providers, and/or a provider and any third party involved in value based care (e.g. a quality management organization). The goal is to identify, document and constrain very specific patterns of exchange so that providers and payers can reliably exchange information for patient care (including coordination of care), risk adjustment, quality reporting, identifying that requested services are necessary and appropriate (e.g. should be covered by the payer) and other uses that may be documented as part of this effort. The specific use case driven implementation guides will inherit the HRex Framework to avoid defining the same exchanges, profiles, constraints in multiple guides with slightly differed variations.
 
−
 
 
−
https://confluence.hl7.org/download/attachments/40738385/image2019-1-29_5-44-7.png?version=1&modificationDate=1548762242388&api=v2
 
−
https://confluence.hl7.org/download/attachments/40738385/image2019-1-29_5-43-27.png?version=1&modificationDate=1548762203104&api=v2
 
−
 
 
−
 
 
−
This project will reference, where possible, the prior work from Argonaut, US Core and QI Core effort for FHIR DSTU2, STU3, and R4. The following diagram depicts the anticipated scope of the eHRx Framework IG.
 
−
 
 
−
https://confluence.hl7.org/download/attachments/40738385/image2019-1-29_5-42-37.png?version=1&modificationDate=1548762152463&api=v2
 
  
 
The ultimate goal is to provide a framework from which specific implementation guides can be developed with reduces effort and potential conflicting definitions to support the exchange of provider and payer data on specific patients/members or groups of patients/members to reduce provider and payer burden, and improve patient care using technology that supports FHIR DSTU2, STU3, and R4 releases of the FHIR standard.
 
The ultimate goal is to provide a framework from which specific implementation guides can be developed with reduces effort and potential conflicting definitions to support the exchange of provider and payer data on specific patients/members or groups of patients/members to reduce provider and payer burden, and improve patient care using technology that supports FHIR DSTU2, STU3, and R4 releases of the FHIR standard.
Line 75: Line 60:
 
The project team plans to work with existing FHIR artifacts where possible. If changes are necessary, the project team will work with the responsible Work Group to review and implement (via tracker items or new PSS) any necessary enhancements to base FHIR resources, extensions, and/or profiles.
 
The project team plans to work with existing FHIR artifacts where possible. If changes are necessary, the project team will work with the responsible Work Group to review and implement (via tracker items or new PSS) any necessary enhancements to base FHIR resources, extensions, and/or profiles.
  
−
==IG Purpose==
+
==Content location==
 +
 
 +
<!-- What is the path within the HL7 github repository (i.e. https://github.com/HL7/xxx) or what is the Simplifier project name? -->
  
−
<!-- Why is this IG necessary? -->
+
The GitHub repository is here:
  
−
==Content location==
+
https://github.com/HL7/davinci-ehrx
  
−
<!-- What is the path within the HL7 github repository (i.e. https://github.com/HL7/xxx) or what is the Simplifier project name? -->
+
The IG is being edited using Trifolia on FHIR, and can be found here (after logging in and selecting the R4 HAPI server in settings):
  
 +
https://trifolia-fhir.lantanagroup.com/implementation-guide/davinci-hrex
  
 
==Proposed IG realm and code==
 
==Proposed IG realm and code==
  
 
<!-- What is the realm code (2-character country code or 'uv') and IG code to use for the path when the IG is published under http://hl7.org/fhir?  E.g. us/ccda -->
 
<!-- What is the realm code (2-character country code or 'uv') and IG code to use for the path when the IG is published under http://hl7.org/fhir?  E.g. us/ccda -->
 +
 +
us/davinci-hrex
  
 
==Maintenance Plan==
 
==Maintenance Plan==
Line 98: Line 88:
 
<!-- 1-2 sentences describing the purpose/scope of the IG for inclusion in the registry -->
 
<!-- 1-2 sentences describing the purpose/scope of the IG for inclusion in the registry -->
  
 +
A library of shared artifacts used by other Da Vinci and payer related implementation guides
  
 
==Long Description==
 
==Long Description==
Line 103: Line 94:
 
<!-- 1 paragraph describing the purpose/scope of the IG in more detail for inclusion in the version history -->
 
<!-- 1 paragraph describing the purpose/scope of the IG in more detail for inclusion in the version history -->
  
 +
A library of shared artifacts from which specific implementation guides can be developed to support the exchange of provider and payer data on specific patients/members or groups of patients/members to reduce provider and payer burden, and improve patient care using technology that supports FHIR DSTU2, STU3, and R4 releases of the FHIR standard. This guide references, where appropriate, the prior work from Argonaut, US Core and QI Core effort for FHIR DSTU2, STU3, and R4.
  
 
==Involved parties==
 
==Involved parties==
Line 108: Line 100:
 
<!-- 1 paragraph describing who is sponsoring or involved in creating the IG for inclusion in the version history -->
 
<!-- 1 paragraph describing who is sponsoring or involved in creating the IG for inclusion in the version history -->
  
 +
Da Vinci project members, CIC work group members, and various other HL7 volunteers and members of the FHIR community.
  
 
==Expected implementations==
 
==Expected implementations==
  
 
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. -->
 
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. -->
 +
 +
Initially Da Vinci project members, expanding to more payers, providers, and vendors over time.
  
 
==Content sources==
 
==Content sources==
Line 118: Line 113:
  
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 +
 +
See those listed under dependencies.
  
 
==Example Scenarios==
 
==Example Scenarios==
  
 
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this IG.  They should demonstrate the full scope of the IG and allow exercising of the IG's capabilities (all profiles, different types of applications, etc.) -->
 
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this IG.  They should demonstrate the full scope of the IG and allow exercising of the IG's capabilities (all profiles, different types of applications, etc.) -->
 +
 +
This IG will contain shared profiles, operations, and other materials for the CDex and PDex IGs, thus will not be directly implemented itself.
  
 
==IG Relationships==
 
==IG Relationships==
  
 
<!-- Are there any IGs this resource depends on or that depend on this IG? -->
 
<!-- Are there any IGs this resource depends on or that depend on this IG? -->
 +
 +
This IG depends on US Core (STU3 and R4), C-CDA on FHIR, and Argonaut profiles, and also leverages CDS-Hooks.
 +
 +
The CDex and PDex IGs depend on this IG.
  
 
==Timelines==
 
==Timelines==
  
−
<!-- Indicate the target date for having the IGcomplete from a committee perspective and ready for vetting and voting -->
+
<!-- Indicate the target date for having the IG complete from a committee perspective and ready for vetting and voting -->
 +
 
 +
The plan is to have a STU1 ready for the September ballot cycle (as an early ballot in July), so the Da Vinci group plans to meet all official dates required to meet HL7 deadlines.
  
 
==When IG Proposal Is Complete==
 
==When IG Proposal Is Complete==

Latest revision as of 19:55, 17 April 2019

OpenHotTopic.GIF

This page documents a Approved FHIR IG Proposal



PutProposedIGNameHere

HL7 FHIR® Implementation Guide: Health Record Exchange (HRex) Framework, Release 1 (HL7_FHIR_IG_HRex)

Owning work group name

Clinical Interoperability Council

Committee Approval Date:

Approved by CIC WG on Thursday, March 28, 2019

Contributing or Reviewing Work Groups

  • FM
  • Patient Care

FHIR Development Project Insight ID

1494

Scope of coverage

US-centric, payer related shared artifacts

IG Purpose

The ultimate goal is to provide a framework from which specific implementation guides can be developed with reduces effort and potential conflicting definitions to support the exchange of provider and payer data on specific patients/members or groups of patients/members to reduce provider and payer burden, and improve patient care using technology that supports FHIR DSTU2, STU3, and R4 releases of the FHIR standard.

The project team plans to work with existing FHIR artifacts where possible. If changes are necessary, the project team will work with the responsible Work Group to review and implement (via tracker items or new PSS) any necessary enhancements to base FHIR resources, extensions, and/or profiles.

Content location

The GitHub repository is here:

https://github.com/HL7/davinci-ehrx

The IG is being edited using Trifolia on FHIR, and can be found here (after logging in and selecting the R4 HAPI server in settings):

https://trifolia-fhir.lantanagroup.com/implementation-guide/davinci-hrex

Proposed IG realm and code

us/davinci-hrex

Maintenance Plan

The Da Vinci project intends to provide ongoing support of this implementation guide.

Short Description

A library of shared artifacts used by other Da Vinci and payer related implementation guides

Long Description

A library of shared artifacts from which specific implementation guides can be developed to support the exchange of provider and payer data on specific patients/members or groups of patients/members to reduce provider and payer burden, and improve patient care using technology that supports FHIR DSTU2, STU3, and R4 releases of the FHIR standard. This guide references, where appropriate, the prior work from Argonaut, US Core and QI Core effort for FHIR DSTU2, STU3, and R4.

Involved parties

Da Vinci project members, CIC work group members, and various other HL7 volunteers and members of the FHIR community.

Expected implementations

Initially Da Vinci project members, expanding to more payers, providers, and vendors over time.

Content sources

See those listed under dependencies.

Example Scenarios

This IG will contain shared profiles, operations, and other materials for the CDex and PDex IGs, thus will not be directly implemented itself.

IG Relationships

This IG depends on US Core (STU3 and R4), C-CDA on FHIR, and Argonaut profiles, and also leverages CDS-Hooks.

The CDex and PDex IGs depend on this IG.

Timelines

The plan is to have a STU1 ready for the September ballot cycle (as an early ballot in July), so the Da Vinci group plans to meet all official dates required to meet HL7 deadlines.

When IG Proposal Is Complete

When you have completed your proposal, please send an email to FMGcontact@HL7.org

FMG Notes

Retrieved from "https://wiki.hl7.org/w/index.php?title=Da_Vinci_HRex_FHIR_IG_Proposal&oldid=165576"