Difference between revisions of "Newborn Admission Notification Information"

Latest revision as of 18:28, 4 November 2019

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.

Part of the Early Hearing Detection and Intervention - Family of Profiles.

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

The NANI Profile describes the content needed to notify another system of a newborn admission and discharge event. The newborn admission and discharge event notifications are used by the receiving system as workflow triggering events.

NANI includes a new transaction similar to the Patient Identity Management [ITI-30] transaction between an Information Source and an Information Recipient. Content is created by an Information Source and is ultimately consumed by an Information Recipient.

Systems Affected

Birthing Facility EHRs might expect to function as an Information Source as could a third party intermediary system (HIE) or public health.

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 can be used to track specimen receipt by the LIMS in Public Health or by the Birthing Facility.

Actors & Transactions:

Specification

Profile Status: Trial Implementation

Documents:

IHE QRPH Supplement NANI

Underlying Standards:

This page is based on the Profile Overview Template

@@ Line 1: / Line 1: @@
+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.
+Part of the [[Early Hearing Detection and Intervention - Family of Profiles]].
 __TOC__
 ==Summary==
-''<Describe the profile in about a paragraph using user-oriented language.  Focus 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 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.
-''<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.  .>''
-''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
+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==
-''<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 profile.  If the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>''
-==Details==
+*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.
-''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
+*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.
-''<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.>''
+*NANI automation will result in more effective and timelier delivery of services through accurate information
-''<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.>''
+*NANI will facilitate both evaluation of the quality of care delivered and the capacity for improving care
-==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.>''
-* ''PACS systems may store, manage, and/or display Evidence Documents.''
+*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.
-* ''Display systems may query, retrieve and display Evidence Documents.''
-* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
-'''Actors & Transactions:'''
+==Details==
-''<Insert an actor-transaction diagram, and or list of Content Definitions>''
+The NANI Profile describes the content needed to notify another system of a newborn admission and discharge event. The newborn admission and discharge event notifications are used by the receiving system as workflow triggering events.
-==Specification==
+NANI includes a new transaction similar to the Patient Identity Management [ITI-30] transaction between an Information Source and an Information Recipient.  Content is created by an Information Source and is ultimately consumed by an Information Recipient.
-'''Profile Status:''' [[Comments| Final Text]]
+==Systems Affected==
-''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
+Birthing Facility EHRs might expect to function as an Information Source as could a third party intermediary system (HIE) or public health.
-'''Documents:'''
+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 can be used to track specimen receipt by the LIMS in Public Health or by the Birthing Facility.
-''<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.>''
+'''Actors & Transactions:'''
-[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
+<center>[[Image:NANI Transaction.PNG]]</center>
-:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
-:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
-:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
-'''Underlying Standards:'''
-''<list all the standards on which the profile is based; if possible with links to sources>''
+<center>[[Image:NANI Transaction Actor II.png]]</center>
-:* [http://dicom.nema.org DICOM]
-:* [http://www.hl7.org HL7]
-:* ...
-==See Also==
+==Specification==
-''<The following sections can be left out if there is nothing to point to.  This is just to show where such information can go.>''
+Profile Status:  Trial Implementation
+'''Documents:'''
-'''Related Profiles'''
+:* [http://www.ihe.net/Technical_Framework/upload/IHE_QRPH_Suppl_NANI.pdf IHE QRPH Supplement NANI]
-''<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.>''
-* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
+'''Underlying Standards:'''
-* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
-* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
-* ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
-* ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''
+:* [http://www.ihe.net/technical_framework/upload/ihe_iti_suppl_pix_pdq_hl7v3_rev2-1_ti_2010-08-10.pdf - IHE ITI Supplement PIX PDQ]
+:* [http://www.interfaceware.com/hl7-standard/hl7-message-ADTA01.html - HL7 message]
-'''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>''
+This page is based on the [[Profile Overview Template]]
-'''Implementer Information'''
+[[Category:Profiles]]
+[[Category:QRPH Profile]]
-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>''
+[[Category:HL7v2]]
+[[Category:Hearing]]
-'''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]]