This wiki has undergone a migration to Confluence found Here

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

From HL7Wiki
Jump to navigation Jump to search
Line 36: Line 36:
 
==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. 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).  
  
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==
  
<!-- What is the path within the HL7 github repository (i.e. https://github.com/HL7/xxx) or what is the Simplifier project name? -->
+
http://build.fhir.org/ig/HL7/davinci-alerts/branches/master/index.html
  
  
 
==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==
Line 74: Line 68:
 
==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.
 
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 
  
 
==Example Scenarios==
 
==Example Scenarios==
Line 93: Line 85:
 
==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==

Revision as of 11:20, 3 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

Long Description

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

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