Skip to end of metadata
Go to start of metadata

Publication Request

Publication Request

1. Published Name of the Standard for which request is being made

2. Standards Material/Document


3. Date of Request

Mar 05, 2020

4. Use Period

5. Reason for extension, timeline, and actions

6. Original Publication Date

7. End date of the current STU period

8. Length of the requested extension

9. Review Process

10. HL7 Work Group making this request and date

Public Health

10a. Requesting WG Date

Mar 05, 2020

11. URL of approval minutes

12. HL7 Product Management Group


12a. Management Group Date of Approval

Mar 06, 2020

13. URL of approval minutes

14. Is the artifact ready for final publication?


15. If not ready, please describe remaining steps.

16. Tool name used to produce the machine processable artifacts in the IG


17. The name of the “IG artifact” within the context of the above mentioned tool.

18. Balloted Name of the standard for which request is being made

HL7 Version 2.6 Implementation Guide: Early Hearing Detection and Intervention (EHDI) Results, Release 1

19. Requested name for published standard

HL7 Version 2.6 Implementation Guide: Early Hearing Detection and Intervention (EHDI) Results, Release 1

20. If CMET, list IDs balloted

21. Project Insight Number


22. Document Realm


23. Ballot cycle in which the document was successfully balloted


24. Results of that ballot (following reconciliation activities):

24. Results of that ballot (following reconciliation activities):

(not needed for errata, STU extension, or unballoted STU update)

25. Affirmative


26. Negative


27. Abstentions


28. Not Returned


29. Total in ballot pool


30. Date on which final document/standards material was supplied to HQ

Mar 06, 2020

31. URL of publication material/ SVN repository

32. Publishing Facilitator

Craig Newman

33. Special Publication Instructions

34. URL of ballot reconciliation document

35. Has the Work Group posted its consideration of all comments received in its reconciliation document on the ballot desktop?


36. Substantive Changes Since Last Ballot?


37. Product Brief Reviewed By

Public Health

38. Date Product Brief Reviewed

Mar 05, 2020

39. Has the Product Brief changed?

Product Brief

Product Brief

40. Family


41. Section

Implementation Guides

42. Topic

Public Health

43. Please Describe the Topic

44. Product Type

Implementation Guide

45. Parent standard


46. Parent Standard Status

47. Update/replace standard

Replaces existing STU version

48. Common name/search keyword

Hearing Screening, EHDI, Newborn Screening

49. Description

Early Hearing Detection and Intervention (EHDI) programs exist world-wide to help identify children with hearing loss. Because newborn hearing loss is a neuro-developmental emergency, children with hearing loss need to be identified shortly after birth to help them achieve better communication outcomes. This implementation guide focuses on the transmission of the hearing screening data elements from the hearing screening device to a recipient of data, which may be an electronic health record (EHR) or a Public Health Information System.



These are categories of potential users, implementers, or other interested parties such as those that are indicated on the Project Scope Statement under “Stakeholders/Vendors/Providers”. Select those that are applicable, or suggest others:

50. Stakeholders

Other (specify in text box below)

51. Vendors

EHR, PHR, Health Care IT, Other (please specify)

52. Providers

Local and State Departments of Health Healthcare Institutions (hospitals, long term care, home care, mental health)

53. Benefits

Enables newborn hearing screening information to be transmitted from a point of care screening device to an interested consumer such as public health or an EHR in a standard format

54. Implementations/Case Studies

Michigan Department of Health and Human Services/Altarum
OZ Systems
Utah Department of Health
Minnesota Department of Health

55. Development Background

Primary Authors:
Lura Daussat (Public Health Informatics Institute)
Craig Newman (Altarum)