Difference between revisions of "Da Vinci CDex FHIR IG Proposal"
Lisa Nelson (talk | contribs) |
Lisa Nelson (talk | contribs) |
||
Line 87: | Line 87: | ||
<!-- 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 --> | ||
− | This IG provides detailed guidance that helps implementers reuse and and refine FHIR-based interactions and resources relevant to scenarios associated with Provider exchange of clinical information with Payers and other Providers. The IG covers six specific use cases that demonstrate | + | This IG provides detailed guidance that helps implementers reuse and and refine FHIR-based interactions and resources relevant to scenarios associated with Provider exchange of clinical information with Payers and other Providers. The IG covers six specific use cases that demonstrate how to exchange clinical data generated by Providers with Payers and other Providers to improve care coordination, support risk adjustment, ease quality management, facilitate claims auditing and confirm medical necessity, improve member experience, and support orders and referrals. |
+ | |||
+ | For these six use cases, the IG describes how to share needed data as individual FHIR resources, data extracted together as a meaningful collection of information, or data shared in the form of a clinical document such as an encounter summary or patient summary. An encounter summary document includes a predefined collection of data that tells the story of an encounter where services were provided to a patient. A patient summary document includes a predefined collection of data that provides and overview of the provision of care services provided to a patient over a range of time. The IG clarifies exchange requirements for metadata that establishes the context (provenance) for documents, collections of resources, and individual informational resources as well. | ||
==Involved parties== | ==Involved parties== |
Revision as of 16:13, 10 February 2019
Contents
- 1 PutProposedIGNameHere
- 1.1 Owning work group name (Sponsor)
- 1.2 Committee Approval Date:
- 1.3 Contributing or Reviewing Work Groups
- 1.4 FHIR Development Project Insight ID
- 1.5 Scope of coverage
- 1.6 IG Purpose
- 1.7 Content location
- 1.8 Proposed IG realm and code
- 1.9 Maintenance Plan
- 1.10 Short Description
- 1.11 Long Description
- 1.12 Involved parties
- 1.13 Expected implementations
- 1.14 Content sources
- 1.15 Example Scenarios
- 1.16 IG Relationships
- 1.17 Timelines
- 1.18 When IG Proposal Is Complete
- 1.19 FMG Notes
PutProposedIGNameHere
Da Vinci Clinical Data Exchange
Owning work group name (Sponsor)
Patient Care Work Group
Committee Approval Date:
Please enter the date that the committee approved this IGproposal
Contributing or Reviewing Work Groups
Structured Documents
FHIR Development Project Insight ID
Scope of coverage
This Implementation Guide (IG) will define how to utilize exchange methods (push, pull, triggers, subscription) and other interoperability "standards" (e.g. CDS Hooks and SMART on FHIR) to effectively exchange clinical information captured by care providers in electronic health record (EHR) systems with payers responsible for the health plan used by a specific patient or a set of patients or with other providers where a patient has been referred for additional services. The IG defines specific use of FHIR resources to represent the information being exchanged, including the provenance of the data.
IG Purpose
To transform and accelerate the shift in care delivery models toward a focus on health outcomes and value, provider and payer systems need standard ways to bi-directionally share electronic clinical, payer, and quality measure information.
The goal of this project is to rapidly improve available computer processing methods that can be used between payers, providers, and service supplier systems. The project will accelerate the shift toward value-based care and support value-based reimbursement models. More efficient and effective exchange of health record information will improve coordinated care and network performance, increase operational efficiencies, improve delivery of patient care and care outcomes, and reduce the burden of quality reporting.
Content location
https://github.com/HL7/davinci-ecdx
Proposed IG realm and code
US/Davinci-CDex
Maintenance Plan
The Da Vinci project intends to provide ongoing support of this implementation guide.
Short Description
Provider data exchange with Payers and other Providers to improve care coordination, support risk adjustment, ease quality management, facilitate claims auditing and confirm medical necessity, improve member experience, and support orders and referrals.
Long Description
This IG provides detailed guidance that helps implementers reuse and and refine FHIR-based interactions and resources relevant to scenarios associated with Provider exchange of clinical information with Payers and other Providers. The IG covers six specific use cases that demonstrate how to exchange clinical data generated by Providers with Payers and other Providers to improve care coordination, support risk adjustment, ease quality management, facilitate claims auditing and confirm medical necessity, improve member experience, and support orders and referrals.
For these six use cases, the IG describes how to share needed data as individual FHIR resources, data extracted together as a meaningful collection of information, or data shared in the form of a clinical document such as an encounter summary or patient summary. An encounter summary document includes a predefined collection of data that tells the story of an encounter where services were provided to a patient. A patient summary document includes a predefined collection of data that provides and overview of the provision of care services provided to a patient over a range of time. The IG clarifies exchange requirements for metadata that establishes the context (provenance) for documents, collections of resources, and individual informational resources as well.
Involved parties
Expected implementations
Content sources
Example Scenarios
IG Relationships
Timelines
When IG Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org