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

Difference between revisions of "Da Vinci Alerts Notification FHIR IG Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 64: Line 64:
 
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.
 
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.
 
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==
 
==Involved parties==

Revision as of 17:04, 10 July 2019



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. This may be as traditional as admission to or discharge from a care setting (ED, Hospital, etc.) but may also include 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

FMG Notes