Ballot SubmissionTriage & Committee ResolutionBallot Comment Tracking
Comment NumberBallotChapterSectionPage #Line #Artifact IDResource(s)HTML Page name(s)URLVote and TypeSub-categoryTracker #Existing WordingProposed WordingBallot CommentSummaryIn person resolution requestedComment groupingScheduleTriage NotePubsDisposition WGDispositionDisposition Comment or Retract/Withdraw detailsDisposition/Retract/ Withdrawal DateMover / seconderFor AgainstAbstainRetracted / WithdrawnDisposition External OrganizationResponsible PersonChange AppliedSubstantive ChangeSubmitted ByOrganizationOn behalf ofCommenter EmailSubmitter Tracking IDReferred ToReceived FromNotes
1PH11.4.5NEGThe actual OID for the EHDI IG is 2.16.840.1.113883.9.801. This should be added to the section on profile IDs and updated in all the example messages (MSH-21)Block 1PHPersuasiveThe example messages will be updated to use the new OID.2020-02-13Craig Newman/Lura Daussat2100YesNoCraig NewmanAltarum
2PH11.4.5A-SAdd an explanation of how the EHDI OID may be used to manage artifacts like value sets and profile IDs.Block 1PHPersuasiveSection 1.4.5 will be updated to indicate that an OID has been assigned by the HL7 registry to the IG. The OID will be used to define the message profile ID in MSH-21 and future versions of the IG may use it to assign OIDs to value sets.2020-02-13Craig Newman/Lura Daussat2100YesNoCraig NewmanAltarum
3PH33.1.236A-SACK^VARIES^ACKACK^R01^ACKIn general, the MSH-9.2 trigger event ID for ACKs does vary, depending on the message type being acknoweldged. However, the only outbound message type defined in this IG is ORU^R01^ORU_R01, so the only ACK trigger event ID that could ever be returned is "R01" (which is explicitly specified by Conformance Statement MSH_CCHD02_5215675 on page 46). Therefore, I suggest re-labeling the ACK profile name for the Sec. 3.1.2 header (at the bottom of page 36 as well as the Table of Contents on page 4) to "ACK^R01^ACK" instead of "ACK^VARIES^ACK."ACK profile name / section headerBlock 1PHPersuasiveThe title of the ACK message profile will be updated to ACK^R01^ACK2020-02-13Craig Newman/Lura Daussat2100YesNoDanny WiseAllscripts
4PH33.1.237A-TACK^Varies^ACKERR (segment)In the ACK profile definition, the ERR segment has a Conditional Usage, so there is a Conditional Predicate defined below it. However, the "Location" for that condition is "ACK^Varies^ACK" -- shouldn't this more clearly indicate it's referring to the ERR segment specifically?Conditional Predicate LocationBlock 1PHPersuasiveThe current location value (ACK^Varies^ACK) indicates that the conformance statement is applied at the message level because it involves interactions between multiple segments. The Location will be updated to read "ERR"2020-02-13Craig Newman/Lura Daussat2100YesNoDanny WiseAllscripts
5PH117A-TThe goal of EHDI is to Early Hearing Detection and Intervention (EHDI) has evolved globally as a screening program where testing occurs at the point of care. The first goal of EHDI programs is to screen all newborns for hearing loss before 1 month of age. Any infants who screen positive, need to have a diagnostic evaluation before 3 months of age. The third goal of EHDI programs is to identify connect all infants identified with hearing loss to appropriate early intervention services before 6 months of age.Early Hearing Detection and Intervention (EHDI) has evolved globally as a screening program where testing occurs at the point of care. The first goal of EHDI programs is to screen all newborns for hearing loss before 1 month of age. Any infants who screen positive, need to have a diagnostic evaluation before 3 months of age. The SECOND(?) goal of EHDI programs is to CONNECT all infants identified with hearing loss to appropriate early intervention services before 6 months of age.The second paragraph in the Introduction includes several editorial mishaps: 1. The first sentence starts with extra text ("The goal of EHDI is to") that looks like it should be removed 2. The first and third goals are specifically identified, but not a second goal. Is the follow-up diagnostic evaluation for infants who screen positive prior to 1 month the second goal? Or is this part of the first goal, and the goal of connecting affected infacnts with intervention servies really the second goal? 3. I think the word "identify" before "connect" in the last sentence should be removed...?editorial mishaps in second paragraph of IntroductionBlock 1PHPersuasive with modThe text will be updated to read: Early Hearing Detection and Intervention (EHDI) has evolved globally as a screening program where testing occurs at the point of care. The first goal of EHDI programs is to screen all newborns for hearing loss before 1 month of age. Any infants who screen positive, need to have a diagnostic evaluation before 3 months of age. Another goal of EHDI programs is to connect all infants identified with hearing loss to appropriate early intervention services before 6 months of age.2020-02-13Craig Newman/Lura Daussat2100YesNoDanny WiseAllscripts
6PH1.4.515As new versions of this IG are published, the profile IDs will be updated to include a new version identifier (e.g. n1.0 will be updated to n1.1 if a new dot release is published). As new versions of this IG are published, the profile IDs will be updated to include a new profile version identifier (e.g. is version n1.0 would define profile version n1.0 and a new dot release (n1.1) would create the profile veriosn will be updated to n1.1 if a new dot release is published). Either make the ig version and the profile verison in a 1:1 relationship, i.e. each ig verison m.n would define a new profile version m.n, or if necessary, an ig version m.n could create profile versions m.n, m.n.1 m.n.2 ..., etc. In any event each specification document should clearly state which versions of the profile(s) are to used with the document. Block 1PHPersuasive with modThe existing text will be updated to read: As new versions of this IG are published, the profile IDs will be updated to include a new version identifier. This IG will use the version identifier "n1.0" to construct profile IDs. Future versions of the IG will use a different version identifier when constructing profiles. For example, if the next release is dot release 1.1, then the profiles defined in that IG will use the version identifier "n1.1" (e.g. CCHD-ORU_n1.1).2020-02-13Craig Newman/Lura Daussat2100YesNoJohn RobertsTennessee Dept. of HealthJohn Roberts john.a.roberts@tn.gov
7PH2.2.4.120A-SMSH|^~\&|EHDI Screening Device^2.16.840.1.113883.9.98^ISO|MSH|^~\&|EHDI Screening Device^2.16.840.1.113883.19.1^ISO| (an invalid OID) or MSH|^~\&|EHDI Screening Device^2.16.840.1.113883.19.1^ISO| (a valid OID, albeit not appropriate in context)In examples use the ISO values from the HL7 examples tree (…113883.19). The first OID in the message points to: Northwest Regional Council 2.16.840.1.113883.9.98. Ther are two benefits for using the examples tree: you can instantly see a message creator who does not know much about OIDs and you shield your production oids from traffic that is not in production.Block 1PHPersuasive with modExample OIDs (ie. those not part of MSH-21) will be updated to use 2.16.840.1.113883.19 (the HL7 example OID).2020-02-13Craig Newman/Lura Daussat2100YesNoJohn RobertsTennessee Dept. of Health
8PH2.2.4.426A-SMSA|CR|201907010022 - Message rejected before application processing ERR||MSH^1^12^1^1 1. The Ack indicates (MSA-1 CR) that the ACK message is a reject, discovered in the (Enhanced Mode Accept acknowledgement stage) but also contains an ERR segment, which points to an error in the message and not appropriate in a reject acknowledgement. Suggest making the example an error and create an ERR segment exmaple that is consistent.Example of "Error ACK" but it is a "Reject" ACK code. 1. The Ack indicates (MSA-1 CR) that the ACK message is a reject, discovered in the (Enhanced Mode Accept acknowledgement stage) but also contains an ERR segment, which points to an error in the message and is not appropriate in a reject acknowledgement. Suggest making the example an error, using the ack reponse code AA, identify a appropriate Table 0357 error condition code (from a version 2.6 or higher, that has improved comments language,) and create an ERR segment example that is consistent with the error conditon code.PHConsidered for future useWhen using enhanced acknowledgements, the Accept ACK can include errors on content such as MSH-12 version ID. Given that the scope of the IG includes Accept ACKs (but is silent on (but does not prohibit) the use of Application ACKs), the CR example pointing to MSH-12 seems appropriate. Adding requirements surrounding application level ACKs will be considered in furture versions.2020-02-13Craig Newman/Lura Daussat2100John RobertsTennessee Dept. of Health
9PH2.2.4.322A-SMSA|CR|201907010022 - Message rejected before application processing ERR||MSH^1^12^1^1 1. The Ack indicates (MSA-1 CR) that the ACK message is a reject, discovered in the (Enhanced Mode Accept acknowledgement stage) but also contains an ERR segment, which points to an error in the message and not appropriate in a reject acknowledgement. Suggest making the example an error and create an ERR segment exmaple that is consistent.Example of "Error ACK" but it is a "Reject" ACK code. 1. The Ack indicates (MSA-1 CR) that the ACK message is a reject, discovered in the (Enhanced Mode Accept acknowledgement stage) but also contains an ERR segment, which points to an error in the message and is not appropriate in a reject acknowledgement. Suggest making the example an error, using the ack reponse code AA, identify a appropriate Table 0357 error condition code (from a version 2.6 or higher, that has improved comments language,) and create an ERR segment example that is consistent with the error conditon code.PHConsidered - No action requiredDuplicate to comment #82020-02-13Craig Newman/Lura Daussat2100John RobertsTennessee Dept. of Health
10PH3.1.127A-AThe ORU message contains pre-adopted occupational data segments (OH2 and OH3) that allows trading partners to agree to exchange occupational data for the next of kin for the newborn subject if warranted by the implementation requirements. … Note that while v2.9 does allow occupational data to be exchanged for the subject of the message, because of the nature of the patients covered by this IG (i.e. newborns), we have chosen not to pre-adopt the OH* segments associated with the patient (PID) segment. no changeAlthough it may get some negative comment the implementaton of the OH* segments looks like a great compromise and the proejct team should get a gold star.The ORU message contains pre-adopted occupational data segments (OH2 and OH3) that allows trading partners to agree to exchange occupational data for the next of kin for the newborn subject if warranted by the implementation requirements. … Note that while v2.9 does allow occupational data to be exchanged for the subject of the message, because of the nature of the patients covered by this IG (i.e. newborns), we have chosen not to pre-adopt the OH* segments associated with the patient (PID) segment. Block 1PHConsidered - No action required2020-02-13Craig Newman/Lura Daussat2100John RobertsTennessee Dept. of Health
11PH3.1.1.125NEGConformance Statements ID MSH_EHDD01-15 Description MSH-15 SHALL contain the constant value 'AL' drawn from the code system 'HL70155'. Conformance Statements ID MSH_EHDD01-15 Description MSH-15 SHALL contain the constant value 'ER' drawn from the code system 'HL70155'. The Accept Acknowlegement (-15) codes are required meaning all errors and rejects detected up to but not including the actual receiving application result status ARE required but the Applicaton Acknowledgement (-16) is NOT required? This is at least inconsistent and perhaps should be reversed: application ack status (-16) is AL Always Required but Accept Ack Types is not (NE) or errors only (ER) required. Accept acknowledgement (all types) [are AL/are not] NE required; Application Acknowledgement (all types) are ER Errors/Rejects only are required.PHConsidered for future useThe scope of the document is to include the exchange of accept (communication level) ACKs (thus MSH-15 is constrained to AL). The guide is silent on the use of application level ACKs (MSH-16 is required to be populated but can be any value agred up by trading partners). We feel that this guarantees ensured transmission of the data but doesn't place any processing requirements on the receiving system. Adding requirements surrounding application level ACKs will be considered in furture versions.2020-02-13Craig Newman/Lura Daussat2100John RobertsTennessee Dept. of Health
12PH3.1.125NEGValue Set Bindings Location MSH_EHDI01-15 Single Code Value AL Location MSH_EHDI01-16 Value Set ID 0155 Value Set Name Accept/Application … Single Code Value AL Value Set Bindings Location MSH_EHDI01-15 Single Code Value ER Location MSH_EHDI01-16 Value Set ID 0155 Value Set Name Accept/Application … Single Code Value AL (see the comment for the other comment number for the same section 3.1.1)Accept acknowledgement (all types) [are AL/are not] NE required; Application Acknowledgement (all types) are ER Errors/Rejects only are required.PHConsidered for future useThe scope of the document is to include the exchange of accept (communication level) ACKs (thus MSH-15 is constrained to AL). The guide is silent on the use of application level ACKs (MSH-16 is required to be populated but can be any value agreed up by trading partners). We feel that this guarantees ensured transmission of the data but doesn't place any processing requirements on the receiving system. Adding requirements surrounding application level ACKs will be considered in furture versions.2020-02-13Craig Newman/Lura Daussat2100John RobertsTennessee Dept. of Health
13PHNEG“Sending and receiving of serial number of pulse oximetry device”; for OBX-18 Equipment Instance Identifier – the serial number is used. Instead this should identify the device by the UDI for the device– the UDI is an instance identifier. Note: Audiometer devices are class II devices and should all have a UDIYesPHPersuasiveThe description of OBX-18 will be updated to indicate that the UDI should be placed in OBX-18.1 (with a reference to the base standard for guidance on how to populate the OID in OBX-18.3). The data type for OBX-18 will be an EI flavor that will require EI.1, EI.3 and EI.4 to supporting sending a UDI. It will also require support for EI.2 so that a model and manufacturer can be send if a UDI is not available.2020-02-13Craig Newman/Lura Daussat2100Behnaz MinaeiFood and Drug AdministrationMarti Velezis
14PH1.Introduction77A-TThe goal of EHDI is to Early Hearing Detection and Intervention (EHDI) has evolved globally as a screening program where testing occurs at the point of care.Delete the sentence. So the paragraph starts as : The first goal of EHDI programs is to …obvious error in existing wording, also the same wording appears in 1.2 Other related standards. Suggest remove the entire sentence completely so the paragraph starts as : The first goal of EHDI programs is to Block 1PHPersuasive with modSee Comment #5. The existing text will be updated to read: As new versions of this IG are published, the profile IDs will be updated to include a new version identifier. This IG will use the version identifier "n1.0" to construct profile IDs. Future versions of the IG will use a different version identifier when constructing profiles. For example, if the next release is dot release 1.1, then the profiles defined in that IG will use the version identifier "n1.1" (e.g. CCHD-ORU_n1.1).2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention
15PH1. Introduction1.3.18A-SEHDI program level protocols involve multiple screening results in each ear.Newborn hearing screening protocols often involve multiple screenings in each ear.suggest rewordingBlock 1PHPersuasiveText will be updated as suggested2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention
16PH1.3.27A-TBatch messaging is not be supported by this IG.Batch messaging is not to be supported by this IG.typoBlock 1PHPersuasiveText will be updated as suggested2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention
17PH2. Use Cases2.116Table 5A-SMessaging goals for hearing screening device "Supply comprehensive, individual hearing screening results to …"Supply comprehensive observations about the hearing screeningsuggest rewording to be consistent with other actorsBlock 1PHPersuasiveText will be updated as suggested2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention
18PH3.Message Infrastructure3.1.1.428PV1-3A-SThis field contains the patient's initial location or where the patient is being movedThis field contains the patient's location during the the hearing screeningoriginal wording "initial location" was confusingBlock 1PHPersuasiveText will be updated as suggested2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention
19PH3.1.1.428PV1-7A-CThis field contains the attending physician informationJust want to clarify that this refers to infant's doctor assigned at hospital, or the primary care provider (if known), not the person who performed the hearing screening.Block 1PHPersuasive with modThe text associated with PV1-7 will be updated to indicate that the attending physcian is typically not the person who performs the screen. New text will be associated with OBR-10 to indicate that OBR-10 will identify the person, department or facility that performed the hearing screening, the hearing screener.2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention
20PH3.1.1.528A-SIn the reporting of hearing screening data there are three possible observation request (OBR) segments that are used to capture information about the hearing screening panel performed. The first OBR will report the newborn hearing loss panel. This SHALL be followed by an OBR for the newborn hearing loss panel of the right ear and an OBR for the newborn hear panel of the left ear. In the reporting of hearing screening data, one OBR is used to report the newborn hearing screening panel. This contains observations relevant to the hearing screening and it may be followed by supporting OBX segments that include details on any comments or discussion and/or the hearing loss risk indicators (risk factors). This OBR serves as the report header for the newborn hearing screening panel. There are two additional OBRs that support the Newborn Hearing Screen Panel; Newborn Hearing Screen Panel of Ear - RIght and Newborn Hearing Screen Panel of Ear - Left. The OBR for newborn hearing screening panel - right ear and the OBR for newborn hearing screening panel- left ear SHALL be supported by at least one OBX segment that indicates the result of the hearing screening. If a screening is not performed, a reason SHALL be recorded in the OBX segment. Other data elements relevant to hearing screening recorded in the OBX segment include details on the hearing screening technique, equipment, and screener. Note that the three OBRs have similar structure and use the same OBR segment flavor. The information in OBR-4 identifies whether it is the OBR for the Newborn Hearing Screen panel, the Newborn Hearing Screen panel of Ear - Right or the Newborn Hearing Screen panel of Ear - left.In the reporting of hearing screening data there are three possible observation request (OBR) segments that are used to capture information about the hearing screening performed. The first OBR will report the newborn hearing screening panel. This contains observations relevant to the hearing screening and it may be followed by supporting OBX segments that include details on any comments or discussion and/or the hearing loss risk indicators (risk factors). This OBR serves as the report header for the newborn hearing screening panel. This first OBR SHALL be followed by an OBR for the newborn hearing screening panel of the right ear and an OBR for the newborn hearing screening panel of the left ear. The OBR for newborn hearing screening panel - right ear and the OBR for newborn hearing screening panel- left ear SHALL each be supported by at least one OBX segment that indicates the result of the hearing screening. If a screening is not performed, a reason SHALL be recorded in the OBX segment. Other data elements relevant to hearing screening recorded in the OBX segment include details on the hearing screening technique, equipment, and screener. Note that the three OBRs have similar structure and use the same OBR segment flavor. The information in OBR-4 identifies whether it is the OBR for the newborn hearing screening panel, the newborn hearing screening panel - right ear or the newborn hearing screen ear - left ear.This whole session was a bit mixed-up. What is the panel name? is it newborn hearing screening panel, or newborn hearing screen panel, or newborn hearing loss panel? The way it was originally written made it seem like there are 6 OBRs instead of 3.Block 1PHPersuasiveText will be updated as suggested2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention
21PH3.1.1.529Segment Definition Table, Value Set column, and Value Set Bindings tableA-TUSI-EDHI01 0123-EDHI01USI-EHDI01 0123-EHDI01typoBlock 1PHPersuasiveText will be updated as suggested2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention
22PH3.1.1.631Segment definition table, value set columnA-TOS-EDHI01OS-EHDI01typoBlock 1PHPersuasiveText will be updated as suggested2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention
23PH3.1.1.63258232-0, OBX-5A-TRI_EDHI01RI_EHDI01typoBlock 1PHPersuasiveText will be updated as suggested2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention
24PH34Value set bining tableA-TOS_EDHI01OS_EHDI01typoBlock 1PHPersuasiveText will be updated as suggested2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention
25PH3.1.237Conformance profile definition tableA-TMSA_EDHDI01MSA_EHDI01typoBlock 1PHPersuasiveText will be updated as suggested2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention
26PH3.1.2.238section titleA-TMSA_EDHDI01MSA_EHDI01typoBlock 1PHPersuasiveText will be updated as suggested2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention
27PH39Value set bining tableA-TMSA_EDHDI01MSA_EHDI01typoBlock 1PHPersuasiveText will be updated as suggested2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention
28PH3.1.1.428PV1-7A-TIt is recommended to use a NPI to identify the Attending DoctorIt is recommended to use an NPI to identify the Attending DoctortypoBlock 1PHPersuasiveText will be updated as suggested2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention
29PH3.1.1.636OBX-18A-TIn hearing screening the relevant fields to report on a piece of equipment are: Brand, model, version, instance data, serial number, local name.In hearing screening, the relevant fields to report on a piece of equipment are: Brand, model, version, instance data, serial number, local name.typoBlock 1PHPersuasiveText will be updated as suggested2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention
30PH35Reason Screen not DoneA-TThe reason the screen was not done OBX Segment is required when OBX-5 of the newborn hearing screen right OBX and/or Newborn Hearing Screen Left OBX is Not Performed; 262008008 SNOMED-CTThe reason the screen was not done OBX Segment is required when OBX-5 of the newborn hearing screen right OBX and/or Newborn Hearing Screen Left OBX is Not Performed; Extra/unfinished words at the end of the sentence.Block 1PHPersuasiveText will be updated as suggested2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention
31PH35 Reason Screen not DoneA-SExample segmentsPerhaps a more useful example for “Reason Screen Not Done” might be where screening was only successful in one ear.Block 1PHNot persuasiveThe suggested reason is not part of the value set for Result Not Performed Reason. 2020-02-13Craig Newman/Lura Daussat2100Xidong DengCenters for Disease Control and Prevention