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
 
(12 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: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 15: Line 15:
 
=PutProposedIGNameHere=
 
=PutProposedIGNameHere=
  
<!-- Resource names should meet the following characteristics:
+
Da Vinci Alerts/Notification
* 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==
 
==Owning work group name==
Line 31: Line 22:
  
 
==Committee Approval Date:==
 
==Committee Approval Date:==
<i>Please enter the date that the committee approved this IGproposal</i>
+
CDS approved on:
  
 
==Publishing Lead==
 
==Publishing Lead==
Line 39: Line 30:
 
==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) -->
+
Financial Management
* Work Group Name
+
 
* or link
+
Attachments
* or "None"
+
 
 +
O&O
  
 
==FHIR Development Project Insight ID==
 
==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 -->
+
1516
  
 
==Scope of coverage==
 
==Scope of coverage==
  
<!-- Define the full scope of coverage for the IG.  **(NOT the project - Do NOT copy from the PSS)**  The scope must be clearly delineated such that it does not overlap with any other existing or expected HL7 Int'l-maintained IG. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%". Essentially, set the boundaries that would determine whether new content brought to HL7 should fall within the scope of your IG or somewhere else.  This should be 1 paragraph max.
+
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).  
  
Scope should consider numerous aspects of breadth of scope, including:
 
* Subject: Human vs. non-human vs. non-patient (e.g. lab bench medicine)
 
* Disciplines: Environmental Health, Palliative, Respiratory, Psychology, Maternity, Clinical Research
 
* Delivery environment (Community, Geriatric, Home care, Emergency, Inpatient, Intensive, Neonatal, Pediatric, Primary)
 
* Locale: Country, region
 
-->
 
  
 
==Content location==
 
==Content location==
 
+
http://build.fhir.org/ig/HL7/davinci-alerts/branches/master/index.html
<!-- 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==
 
==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 -->
+
US/DaVinci-Alerts
  
 
==Maintenance Plan==
 
==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.  I.e. Who will be maintaining this IG content 5 years after it's published? -->
+
Da Vinci project intends to provide ongoing support of this implementation guide
  
 
==Short Description==
 
==Short Description==
  
<!-- 1-2 sentences describing the purpose/scope of the IG for inclusion in the registry- this is the sentence that will be used here: http://www.fhir.org/guides/registry.  This must describe the IG from the perspective of an implementer scanning a registry, it should not talk about the project and should NOT be copied from the PSS. -->
+
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.
  
==Long Description==
 
  
<!-- 1-2 paragraphs describing the purpose/scope of the IG in more detail for inclusion in the version history - this is content that will be used in your IG's equivalent of this: http://www.hl7.org/fhir/us/core/history.cfml.  Again, this must describe the IG from the perspective of an implementer scanning a registry, it should not talk about the project and should NOT be copied from the PSS. -->
+
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==
  
<!-- 1 paragraph describing who is sponsoring or involved in creating the IG **for inclusion in the version history**. Don't copy from the PSS - think about the specific language you want to appear in the registry. -->
+
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==
  
<!--Provide named implementations if possible - ideally provide multiple independent implementations. -->
+
Da Vinci members in response to the details in the CMS final rule
  
 
==Content sources==
 
==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
+
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:
  
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
+
1) Admissions
  
==Example Scenarios==
+
2) Discharges
 +
 
 +
3) New Treatments
 +
 
 +
4) Discontinuation of treatments
  
<!-- 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.) -->
+
5) Referrals
  
 
==IG Relationships==
 
==IG Relationships==
  
<!-- Are there any IGs this resource depends on or that depend on this IG? -->
+
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==
 
==Timelines==
  
<!-- Indicate the target date for having the IGcomplete from a committee perspective and ready for vetting and voting -->
+
Submit for STU Ballot for 2019 Sep Ballot cycle
  
 
==When IG Proposal Is Complete==
 
==When IG Proposal Is Complete==

Latest revision as of 15:41, 17 September 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. 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

FMG Notes