View source for Da Vinci HRex FHIR IG Proposal


<div class="messagebox cleanup metadata">
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
<div style="background:#F0F0F0">
This page documents a [[:category:Pending FHIR IG Proposal|Pending]] [[:category:FHIR IG Proposal|FHIR IG Proposal]]
</div>
</div>
[[Category:FHIR IG Proposal]]
[[Category:Pending FHIR IG Proposal]]


<!-- For additional guidance on considerations for resource creation, refer to [[FHIR IG Considerations]] -->


=PutProposedIGNameHere=

<!-- Resource names should meet the following characteristics:
* Title Case
* U.S. English
* Domain-friendly
* Short
* Clear
* Unique
* Avoid non-universal abbreviations (e.g. URL would be ok)
* Be consistent with other similar IGs
 -->

==Owning work group name==

<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the IG. -->
Clinical Interoperability Council

==Committee Approval Date:==
<i>Please enter the date that the committee approved this IGproposal</i>

==Contributing or Reviewing Work Groups==

<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the IG (optional) -->
* Work Group Name
* or link
* or "None"

==FHIR Development Project Insight ID==

<!-- Please specify the id of your work group’s PSS for doing FHIR work that covers the development and maintenance of this IG.  (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 -->

1494

==Scope of coverage==

The Health Record exchange (HRex) Framework is part of the larger Da Vinci use case for Health Record exchange (HRex).

The project scope statement (PSS) can be found here:

https://confluence.hl7.org/display/CIC/PSS+for+Health+Record++Exchange+%28HRex%29+Framework

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.

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.

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.

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.

==IG Purpose==

<!-- Why is this IG necessary? -->

==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? -->


==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 -->

==Maintenance Plan==

<!-- What commitment does the WG have to maintaining this IG as the FHIR core specification continues to evolve - particularly if the initial project sponsors are no longer providing resources -->

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

==Short Description==

<!-- 1-2 sentences describing the purpose/scope of the IG for inclusion in the registry -->


==Long Description==

<!-- 1 paragraph describing the purpose/scope of the IG in more detail for inclusion in the version history -->


==Involved parties==

<!-- 1 paragraph describing who is sponsoring or involved in creating the IG for inclusion in the version history -->


==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. -->

==Content sources==

<!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult

Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->

==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.) -->

==IG Relationships==

<!-- Are there any IGs this resource depends on or that depend on this IG? -->

==Timelines==

<!-- Indicate the target date for having the IGcomplete from a committee perspective and ready for vetting and voting -->

==When IG Proposal Is Complete==
'''When you have completed your proposal, please send an email to [mailto:FMGcontact@HL7.org FMGcontact@HL7.org]'''

==FMG Notes==