Difference between revisions of "Newborn Admission Notification Information"

From IHE Wiki
Jump to navigation Jump to search
Line 1: Line 1:
Newborn Admission Notification Information describes the content needed to communicate a timely newborn admission notification to public health to be used by Early Hearing Detection and Intervention (EHDI) screening programs.
+
Newborn Admission Notification Information describes the content needed to communicate a timely newborn admission notification electronically from a birthing facility to public health to be used by newborn screening programs.
  
 
__TOC__
 
__TOC__
  
 
==Summary==
 
==Summary==
''<Describe the profile in about a paragraph using user-oriented languageFocus on what it accomplishes for a user (i.e. the Use Cases)Don't get into how it works, leave that to the Details section.>''
+
A Newborn Admission Notification Information (NANI) profile transfers basic newborn demographic data electronically to public health programs from a birthing facility. By automating delivery of these basic required data elements, more effective and timelier services can be undertakenThe NANI profile provides accurate data on the number of newborn hospital admissions within a public health jurisdiction. These data can then be used as a denominator to evaluate the effectiveness of Public Health program interventions.   This helps birth facilities and state newborn screening programs by facilitating both the evaluation of the quality of care delivered and the capacity for improving care. In the case of EHDI this means determining the number of newborns accurately screened who received follow-up servicesNANI also eliminates aggregate reporting by birth facilities, replacing it with individual patient level data.
  
''<Insert a simple graphic that, at a glance, visually summarizes what the profile is about.  Do not use an actor/transaction diagram here.  Show your graphic to someone for 5 seconds (literally) and ask them what it's about.  If what they say hits the main points in your summary paragraph, you have succeeded.  E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them.  .>''
+
In the future, the Newborn Admission Notification Information Profile could be used for more than just newborn screening; to improve the quality and quantity of information by other child health programs.      
  
''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
+
==Benefits==
  
==Benefits==
+
•Newborn screening information communicated to public health is often incomplete and error prone NANI reduces patient errors from mistyped demographic information into public health systems through electronic transfer of patient demographics
''<If the profile can improve Cost, Safety, Quality or Efficiency then list the specific examples of that benefit (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler)Consider using a bullet list for readability. Such benefits help users and vendors make the business case for the profileIf the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>''
+
•Newborn screening reporting is often time-consuming for birthing facility staffNANI eliminates the staff time and costs associated with manually entering basic newborn demographic data for multiple uses.  
 +
•NANI automation will result in more effective and timelier delivery of services through accurate information
 +
•NANI will facilitate both evaluation of the quality of care delivered and the capacity for improving care
 +
•NANI provides accurate data on the number of newborn hospital admissions within a public health jurisdiction. These data are then used as the denominator to evaluate effectiveness of Public Health program interventionsIn the case of EHDI, this means determining the number of newborns accurately screened who received follow-up services.  
  
 
==Details==
 
==Details==
  
''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
+
This profile leverages IHI ITI transactions related to the Patient Identity Feed.  The two NANI transactions constrain and extend these two ITI transactions. There are three actors: the Newborn Admission Notification Manager, Admission Information Source and Newborn Admission Notification Subscriber. Content is created by an Admission Information Source and is ultimately consumed by a Newborn Admission Notification Subscriber. The Newborn Admission Notification Manager sends relevant Content to the Newborn Admission Notification Subscribers. An Admission Information Source delivers Content to a Manager using a transport mechanism. The Newborn Admission Notification Manager delivers the Content to the Newborn Admission Notification Subscriber also via unspecified transport. It is possible to use any of the transport mechanisms defined by the IHE ITI PIX profiles or by some other mechanism supported by the Actors.
 
 
''<If the user might be familiar with the mechanisms used by the profile, you can mention them here. E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>''
 
 
 
''<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short. E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>''
 
 
   
 
   
 
==Systems Affected==
 
==Systems Affected==
''<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>''
+
Birthing Facility EHRs might expect to function as a Newborn Admission Information Source and could function as the Newborn Admission Content Manager as could a third party intermediary system (HIE) or public health. The NANI Subscriber is expected to be a public health information system that requires basic demographic information on a newborn as part of its jurisdictional and programmatic requirements. An integrated newborn public health IS, an EHDI IS, a Newborn Bloodspot screening information system, and even an NBS Laboratory information management system (LIMS) could benefit from an accurate count of hospital births. A NANI message could be used to track specimen receipt by the LIMS in Public Health or by the Birthing Facility.
 
 
* ''PACS systems may store, manage, and/or display Evidence Documents.''
 
* ''Display systems may query, retrieve and display Evidence Documents.''
 
* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
 
  
 
'''Actors & Transactions:'''
 
'''Actors & Transactions:'''

Revision as of 12:37, 16 January 2014

Newborn Admission Notification Information describes the content needed to communicate a timely newborn admission notification electronically from a birthing facility to public health to be used by newborn screening programs.

Summary

A Newborn Admission Notification Information (NANI) profile transfers basic newborn demographic data electronically to public health programs from a birthing facility. By automating delivery of these basic required data elements, more effective and timelier services can be undertaken. The NANI profile provides accurate data on the number of newborn hospital admissions within a public health jurisdiction. These data can then be used as a denominator to evaluate the effectiveness of Public Health program interventions. This helps birth facilities and state newborn screening programs by facilitating both the evaluation of the quality of care delivered and the capacity for improving care. In the case of EHDI this means determining the number of newborns accurately screened who received follow-up services. NANI also eliminates aggregate reporting by birth facilities, replacing it with individual patient level data.

In the future, the Newborn Admission Notification Information Profile could be used for more than just newborn screening; to improve the quality and quantity of information by other child health programs.

Benefits

•Newborn screening information communicated to public health is often incomplete and error prone NANI reduces patient errors from mistyped demographic information into public health systems through electronic transfer of patient demographics. •Newborn screening reporting is often time-consuming for birthing facility staff. NANI eliminates the staff time and costs associated with manually entering basic newborn demographic data for multiple uses. •NANI automation will result in more effective and timelier delivery of services through accurate information •NANI will facilitate both evaluation of the quality of care delivered and the capacity for improving care •NANI provides accurate data on the number of newborn hospital admissions within a public health jurisdiction. These data are then used as the denominator to evaluate effectiveness of Public Health program interventions. In the case of EHDI, this means determining the number of newborns accurately screened who received follow-up services.

Details

This profile leverages IHI ITI transactions related to the Patient Identity Feed. The two NANI transactions constrain and extend these two ITI transactions. There are three actors: the Newborn Admission Notification Manager, Admission Information Source and Newborn Admission Notification Subscriber. Content is created by an Admission Information Source and is ultimately consumed by a Newborn Admission Notification Subscriber. The Newborn Admission Notification Manager sends relevant Content to the Newborn Admission Notification Subscribers. An Admission Information Source delivers Content to a Manager using a transport mechanism. The Newborn Admission Notification Manager delivers the Content to the Newborn Admission Notification Subscriber also via unspecified transport. It is possible to use any of the transport mechanisms defined by the IHE ITI PIX profiles or by some other mechanism supported by the Actors.

Systems Affected

Birthing Facility EHRs might expect to function as a Newborn Admission Information Source and could function as the Newborn Admission Content Manager as could a third party intermediary system (HIE) or public health. The NANI Subscriber is expected to be a public health information system that requires basic demographic information on a newborn as part of its jurisdictional and programmatic requirements. An integrated newborn public health IS, an EHDI IS, a Newborn Bloodspot screening information system, and even an NBS Laboratory information management system (LIMS) could benefit from an accurate count of hospital births. A NANI message could be used to track specimen receipt by the LIMS in Public Health or by the Birthing Facility.

Actors & Transactions:

<Insert an actor-transaction diagram, and or list of Content Definitions>

Specification

Profile Status: Final Text <Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>

Documents:

<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>

IHE Radiology Technical Framework:

  • Vol. 1 - Section 5 (SWF Profile)
  • Vol. 2 - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
  • Vol. 3 - Appendix E

Underlying Standards:

<list all the standards on which the profile is based; if possible with links to sources>

See Also

<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>


Related Profiles

<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>


Consumer Information

The Profile FAQ Template answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>

The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile. <Replace the link with a link to the actual Purchasing page for the Profile>

Implementer Information

The Profile Implementation Template provides additional information about implementing this Profile in software. <Replace the link with a link to the actual Implementation page for the Profile>

Reference Articles

<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis). Go ahead, Google: IHE <Profile Name> abstract or Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >


This page is based on the Profile Overview Template