Difference between revisions of "Da Vinci Alerts Notification FHIR IG Proposal"
| (6 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: | + | 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: | + | [[Category:Approved FHIR IG Proposal]] |
| Line 42: | Line 42: | ||
==Scope of coverage== | ==Scope of coverage== | ||
| − | The scope is to define a HL7 FHIR R4 based exchange standard to communicate alerts and notifications from the initiating source to the members of a care team and other interested parties. | + | The scope is to define a HL7 FHIR R4 based exchange standard to communicate alerts and notifications from the initiating source to the members of a care team and other interested parties. Initially this will be focused on admission to or discharge from a care setting (ED, Hospital, office visit, SNF, etc.). In the future, it may also include other events such as changes in treatment (e.g. medications) or patient status (new diagnosis). |
| Line 58: | Line 58: | ||
==Short Description== | ==Short Description== | ||
| − | + | The goal of this IG is to support the real-time exchange of alerts and notifications that impact patient care and value based or risk based services. | |
| + | ==Long Description== | ||
| + | |||
| + | The project will focus on the use of FHIR R4 resources to exchange patient information relevant to a specific event (e.g. admission, discharge, change in treatment, new diagnosis) to another provider or the health plan to communicate the details of where care was delivered and help to ensure timely follow-up as needed. Health care stakeholders are increasingly responsible for knowing what chare their patients have received and what care they need, regardless of where the patient sought care. This information can be used to build an encounter record in the receiving system with appropriate provenance and make it available to CDS and other local services. This IG will define both subscription and push based transactions to support both solicited and unsolicited exchange of alerts. | ||
| + | Workflow will be defined to establish consistently adoptable and reproducible methods to exchange the alerts.This project will reference, where possible the 'standards' defined by the Health Record exchange (HRex) Library/Framework Implementation Guide which in turn will utilize prior work from US Core for FHIR R4 where appropriate. | ||
| − | |||
| − | + | This project consider the impact of the Argonaut work on Subscription for R5 and, where possible, take the approach into account as part of the considerations for the artifacts exchange in the R4 Alerts effort. | |
| Line 69: | Line 72: | ||
This implementation guide is being developed by U.S. payer, provider and vendor organizations as part of the Da Vinci project. | This implementation guide is being developed by U.S. payer, provider and vendor organizations as part of the Da Vinci project. | ||
| − | |||
==Expected implementations== | ==Expected implementations== | ||
| Line 81: | Line 83: | ||
==Example Scenarios== | ==Example Scenarios== | ||
| − | + | There are a large number of alerts and notifications that may be supported by the exchange standard defined in the IG. These include, but are not limited to, notification of: | |
| + | |||
| + | 1) Admissions | ||
| + | |||
| + | 2) Discharges | ||
| + | |||
| + | 3) New Treatments | ||
| + | |||
| + | 4) Discontinuation of treatments | ||
| + | |||
| + | 5) Referrals | ||
==IG Relationships== | ==IG Relationships== | ||
Latest revision as of 15:41, 17 September 2019
This page documents a Approved FHIR IG Proposal
Contents
- 1 PutProposedIGNameHere
- 1.1 Owning work group name
- 1.2 Committee Approval Date:
- 1.3 Publishing Lead
- 1.4 Contributing or Reviewing Work Groups
- 1.5 FHIR Development Project Insight ID
- 1.6 Scope of coverage
- 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 Alerts/Notification
Owning work group name
Clinical Decision Support
Committee Approval Date:
CDS approved on:
Publishing Lead
Contributing or Reviewing Work Groups
Financial Management
Attachments
O&O
FHIR Development Project Insight ID
1516
Scope of coverage
The scope is to define a HL7 FHIR R4 based exchange standard to communicate alerts and notifications from the initiating source to the members of a care team and other interested parties. Initially this will be focused on admission to or discharge from a care setting (ED, Hospital, office visit, SNF, etc.). In the future, it may also include other events such as changes in treatment (e.g. medications) or patient status (new diagnosis).
Content location
http://build.fhir.org/ig/HL7/davinci-alerts/branches/master/index.html
Proposed IG realm and code
US/DaVinci-Alerts
Maintenance Plan
Da Vinci project intends to provide ongoing support of this implementation guide
Short Description
The goal of this IG is to support the real-time exchange of alerts and notifications that impact patient care and value based or risk based services.
Long Description
The project will focus on the use of FHIR R4 resources to exchange patient information relevant to a specific event (e.g. admission, discharge, change in treatment, new diagnosis) to another provider or the health plan to communicate the details of where care was delivered and help to ensure timely follow-up as needed. Health care stakeholders are increasingly responsible for knowing what chare their patients have received and what care they need, regardless of where the patient sought care. This information can be used to build an encounter record in the receiving system with appropriate provenance and make it available to CDS and other local services. This IG will define both subscription and push based transactions to support both solicited and unsolicited exchange of alerts. Workflow will be defined to establish consistently adoptable and reproducible methods to exchange the alerts.This project will reference, where possible the 'standards' defined by the Health Record exchange (HRex) Library/Framework Implementation Guide which in turn will utilize prior work from US Core for FHIR R4 where appropriate.
This project consider the impact of the Argonaut work on Subscription for R5 and, where possible, take the approach into account as part of the considerations for the artifacts exchange in the R4 Alerts effort.
Involved parties
This implementation guide is being developed by U.S. payer, provider and vendor organizations as part of the Da Vinci project.
Expected implementations
Da Vinci members in response to the details in the CMS final rule
Content sources
Requirements are drawn from payer organizations as part of the Da Vinci initiative.
Example Scenarios
There are a large number of alerts and notifications that may be supported by the exchange standard defined in the IG. These include, but are not limited to, notification of:
1) Admissions
2) Discharges
3) New Treatments
4) Discontinuation of treatments
5) Referrals
IG Relationships
This project will reference, where possible the "standards" defined by the Health Record exchange (HRex) Framework Implementation Guide which in turn will utilize prior work from US Core and R4.
Timelines
Submit for STU Ballot for 2019 Sep Ballot cycle
When IG Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
