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
1PHERNEGIn and of itself, this statement: Note: The C-CDA R2.1 US Realm Header (V3) was considered for use here as a base template but was considered unsuitable due to differences betwen it and this top-level template in value sets for addresses, gender, maritalStatus, and race and ethnicity. reflects a disregard for existing national standards implemented by EHR vendors providing products used by mor e than 90% of hospitals and 65% of EHR providers. Such disregard cannot be ignored. Please ensure that this guide can be used and is consistent with such existing national standards. Do NOT include V2 value sets for coding things such as administrativeGender when there is an already accepted value set, already used in C-CDA today that can be mapped to the desired value domain. Such disregard for national standards increases the the costs of providers using existing HIT solutions to deploy further CDA based solutions, as it requires them to provide for the impedance match to the much smaller number of public health systems they must connect to.**website comment**Block vote 20190214Not persuasiveThe value sets have been developed to meet the specific reporting requirements for the national standard for death and birht reporting as denoted in all the 2003 certificates (death, birth, fetal death). Especially with Race and Ethnicity codes where there is a lot of "second-step" automatic coding after the data has been sent, it is important that these codes are from the correct value set. This IG is aligned with the V2 IG which also uses these value sets as well as the CDA IG for Vital Records Death Reporting.2019-02-14Sarah Gaunt/Dave deRoode704Keith Boone MBIAudacious Inquirykboone@ainq.com
2PHERVol 21.1.5.235A-SMother Participant and Father Participant are in the informationRecipient section but should be independent sibling sections. This same issue occurs in other places in the document (eg section 1.1.7.4)DispositionedWeds Q? - Affirmative/PersuasivePersuasiveThis is a Trifolia tooling issue and will be fixed before publicationSarah Gaunt/Mead Walker1200Craig NewmanAltarum
3PHERVol 21.1.20110A-QIn all documents other than the Provider Supplied Mother's Live Birth document, the patient includes sdtc:multipleBirthInd. Is there a reason why this document doesn't include this information? It does appear to be on the workstheet form but the Patient's Worksheet for the Report of Fetal Death doesn't seem to include it either yet it's part of that document.Block vote 20190221PersuasiveWill update so that sdtc:multipleBirthInd only appears in the correct documents (where it appears on the corresponding form). Sarah/Craig701Craig NewmanAltarum
4PHERVol 21.1.21.1112A-QWhy is the Provider Supplied Mother's Live Birth document the only one that supplies on guidance on what to do if a name has not been choosen yet? Can the other documents only be used once a name has been selected?Email to HettyPresumably. Ask jrusdictioanl offices and national statics agency SME to confirmCraig NewmanAltarum
5PHERVol 22.4147A-SIf possible, could the order of tables 37 (Ethnicity Detail) and 38 (Ethnicity Group) be reversed so that they match the order they are used in the template?Block vote 20190214Not persuasiveThis can't be changed as the export from Trifolia is automatied and the order of the tables can't be changed.2019-02-14Sarah Gaunt/Dave deRoode704Craig NewmanAltarum
6PHERVol 22.5148A-QNote, if there is a multiple delivery, there will be a separate report for each delivered fetus.Assuming that "report" in the existing wording refers to Fetal Delivery Section, how can multiple reports be included when the templates containing the Fetal Delivery Section only have a cardinality of 1..1?DispositionedWeds Q? - Affirmative/Considered - Question AnsweredConsidered - Question AnsweredThe report actually refers to a full document, not just the section. There can be only one fetus/newborn in each document.Sarah Gaunt/Mead Walker1200Craig NewmanAltarum
7PHERVol 22.6151A-SThis section contains the infections present at the time of the pregnancy diagnosis or a confirmed diagnosis during the pregnancy with or without documentation of treatment.This section contains the confirmed diagnoses of infections present at the time of the pregnancy diagnosis or during the pregnancy with or without documentation of treatment.There is an implication in the existing wording that infections diagnoses at the time of "pregnancy diagonis" (I assume this means when the pregnancy is first confirmed) don't have to be "confirmed diagnoses". Is this the intent? If not, I suggest rewording to indicate that infections both at the time of pregnancy diagnosis and during the pregnancy must be "confirmed". The same comment applies to section 2.7 It looks like this wording is very similar to that of the Infection Present- Fetal Death template (section 3.30) which is a published template. It can't be changed there, but I still think it's a little ambiguous.Block vote 20190221 - PULLPersuasive with modWill update as suggested to: "This section contains the confirmed diagnoses of infections present at the time of the pregnancy diagnosis or during the pregnancy with or without documentation of treatment." Will also add: "Documentation of treatment during this pregnancy is adequate if a definitive diagnosis is not present in the avaliable record." THIS SHOULD BE: "Infections present at the time of the pregnancy diagnosis or a confirmed diagnosis during the pregnancy with or without documentation of treatment Documentation of treatment during this pregnancy is adequate if a definitive diagnosis is not present in the available record"Craig NewmanAltarum
8PHERVol 22.6153A-SThere may be multiple infections recorded. At least one observation will be present in the case that none are present.Please clarify the second sentence. When it says "none are present", what is "not present"? The template, an infection?. It's not clear what this means.The same comment applies to section 2.7Block vote 20190221PersuasiveWill update wording to: 'There may be multiple infections recorded. When there are no infections, one observation entry shall be present and observation/value shall be set to "none"'.Sarah/Craig701Craig NewmanAltarumFixed in Trifolia (both Live Birth and Fetal Death)
9PHERVol 22.8157A-QOnset of labor information is collected for a live birth certificate, but not for a fetal death report.How does a developer know if the Onset of Labor template is required (SHALL) for a live birth certificate? Can "is" be replaced with one of "may be" (not required) or "shall be" (required)?Block vote 20190214PersuasiveWill update working to say "Onset of labor information SHALL be collected for a live birth certificate, and SHALL NOT be collected for a fetal death report.2019-02-14Sarah Gaunt/Dave deRoode704Craig NewmanAltarumUpdated in Trifolia
10PHERVol 22.12168A-QNote, if there is a multiple delivery, there will be a separate report for each birth.Assuming that "report" in the existing wording refers to Newborn Delivery Section, how can multiple reports be included when the templates containing the Newborn Delivery Section only have a cardinality of 1..1?DispositionedWeds Q? - Affirmative/Considered - Question AnsweredConsidered - Question AnsweredThe report actually refers to a full document, not just the section. There can be only one fetus/newborn in each document.Sarah Gaunt/Mead Walker1200Craig NewmanAltarum
11PHERVol 22.12170A-QThere may be multiple congenital anomalies recorded. At least one observation will be present in the case that none are present.Please clarify the second sentence. When it says "none are present", what is "not present"? The template, an anomaly? It's not clear what this means.Block vote 20190221PersuasiveWill update wording to 'There may be multiple congenital anomilies recorded. When there are no congenital anomolies, one observation entry shall be present and observation/value shall be set to "none"'.Sarah/Craig701Craig NewmanAltarumUpdated in Trifolia
12PHERVol 23.12215A-SThis template represents the date of the patient's last live birth. If this was a multiple delivery, include all live born infants who preceded the live born infant in this delivery. If first born, do not include this infant. If second born, include the first born.It's not clear to me what value should be sent for a mother's first birth. When is says "If first born, do not include this infant." does that apply only to a multiple birth or the overal first born. If the latter, what does it mean to not include "this infant"? What value should be sent instead? Please clarify the requirement.Block vote 20190214PersuasiveWill update wording to "if this birth was the first born in this pregnancy, do not include this infant"2019-02-14Sarah Gaunt/Dave deRoode704Craig NewmanAltarumUpdated in Trifolia
13PHERVol 23.26252A-SNote: Was an autopsy performed?Note: Was a histological placental examination performed?This is the Histological Placental Examination template but the note references an autopsy being performed. This should be updated to reference the histological examination. Personally, I prefer the style of Note seen on page 333 where it says how to populate the element rather than ask a question like this one does.DispositionedWeds Q? - Affirmative/Persuasive with modPersuasive with modWill update as suggested. The note style is dependent on the exact wording on the certificate - that is the question that is being asked on the certificated.Sarah Gaunt/Mead Walker1200Craig NewmanAltarumUpdated in Trifolia
14PHERVol 23.32265A-SIt looks like the Pregnancy Risk Factor template (section 3.60 of the IG) isn't linked correctly in this template. It should be hyperlinked appropriately.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update linkSarah Gaunt/Mead Walker1200Craig NewmanAltarumHow to hyperlink?
15PHER2, Volume 12.222A-TJuridiction Live Birth Reporting- The use case addresses the need for information concerning a live birth and the issuance of a Birth Certificate to be recorded and communicated to NCHS. The data requirements for jurisdictional reporting of live births are based on the Birth Edit Specifications for the 2003 Proposed Revision of the U.S. Standard Certificate of Birth. Jurisdiction Live Birth Reporting- The use case addresses the need for information concerning a live birth and the issuance of a Birth Certificate to be recorded and communicated to NCHS. The data requirements for jurisdictional reporting of live births are based on the Birth Edit Specifications for the 2003 Proposed Revision of the U.S. Standard Certificate of Birth. Correct the spelling of the word jurisdiction (an "s" is missing)DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Craig NewmanAltarumRachelle May-GentileFixed in Vol 1
16PHER2, Volume 12.222A-TVoid Certificate Reporting— The use case addresses the need for information concerning the voiding of an Birth Certificate or Fetal Death Report to be recorded and communicated to NCHS. Void Certificate Reporting— The use case addresses the need for information concerning the voiding of a Birth Certificate or Fetal Death Report to be recorded and communicated to NCHS. Use of "a" versus "an"DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Craig NewmanAltarumRachelle May-GentileFixed in Vol 1
17PHER1, Volume 21.121A-TNote: The C-CDA R2.1 US Realm Header (V3) was considered for use here as a base template but was considered unsuitable due to differences betwen it and this top-level template in value sets for addresses, gender, maritalStatus, and race and ethnicity. Note: The C-CDA R2.1 US Realm Header (V3) was considered for use here as a base template but was considered unsuitable due to differences between it and this top-level template in value sets for addresses, gender, maritalStatus, and race and ethnicity. Correct the spelling of between (missing an "e")DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Craig NewmanAltarumRachelle May-GentileFixed in Trifolia
18PHERVol 2190A-Tsome timesometimeSpelling error correctionDispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Craig NewmanAltarumThanh Cheng
19PHERVol 2238, 320A-Tan otheranotherSpelling error correctionDispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Craig NewmanAltarumThanh ChengFixed in Trifolia
20PHERVol 2285A-TInfant’sInfantsSpelling error correctionDispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Craig NewmanAltarumThanh ChengFixed in Trifolia
21PHERVol 2331A-TCesarianCaesarianSpelling error correctionDispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Craig NewmanAltarumThanh ChengFixed in Trifolia
22PHERVol 2344A-TintensionallyintentionallySpelling error correction - or is meant to mean "value set defined by rules" as opposed to explicitly listing values (extensional definition)?DispositionedWeds Q? - Affirmative/Not persuasiveNot persuasiveThis is the correct spelling and it is meant to be a "value set defined by rules"Sarah Gaunt/Mead Walker1200Craig NewmanAltarumThanh Cheng
23PHERVol 2454A-TpregancypregnancySpelling error correctionDispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Craig NewmanAltarumThanh Cheng? Misspelling contained in a table underneath 'old' (has been replaced with pregnancy section (v2) no misspellings)
24PHERVol 2186A-Q3.2 Apgar Score Organizer Apgar Score at 5 Minutes (required) Apgar Score at 10 Minutes (optional). Is there any reason why Apgar score at 1 Min is NOT collected for Birth & Fetal Death Report?Block vote 20190214Considered - Question AnsweredIt is not on the certificates and is not data that is required to be collected.2019-02-14Sarah Gaunt/Dave deRoode704Craig NewmanAltarumThanh Cheng
25PHERVol 2366A-Q3.69.1 Birthweight - Vital Signs Observation template and code has been further constrained to 8339-4 | Birthweight Measured.What is the reason that other vital signs such as birth height, and head circumference are NOT collected for newborn for Birth & Fetal Death Reporting?Block vote 20190214Considered - Question AnsweredIt is not on the certificates and is not data that is required to be collected.2019-02-14Sarah Gaunt/Dave deRoode704Craig NewmanAltarumThanh Cheng
26PHERVol 2265A-SPregnancy Risk Factor (identifier: urn:oid:2.16.840.1.113883.10.20.26.44urn:oid:2.16.840.1.113883.10.20.26.44 should be a hyperlink but is not. Please create a hyperlink for this.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update linkSarah Gaunt/Mead Walker1200Craig NewmanAltarumThanh ChengHow to fix hyperlink?
27PHERVol. 2, Ch. 11.1.1.123, 25A-QThis patient SHOULD contain zero or one [0..1] administrativeGenderCode, which SHALL be selected from ValueSet Sex (MFU) urn:oid:2.16.840.1.114222.4.11.1038 DYNAMIC (CONF:4394-266180).Why not use the HL7 V3 ValueSet for Administrative Gender (urn:oid:2.16.840.1.113883.1.11.1)? The difference is that the V3 ValueSet includes "UN" ("Undifferentiated") instead of "U" ("Unknown") -- per http://www.hl7.org/documentcenter/public_temp_A970E49A-1C23-BA17-0CBB112FFC349E28/standards/vocabulary/vocabulary_tables/infrastructure/vocabulary/AdministrativeGender.html, "Undifferentiated" is defined as "The gender of a person could not be uniquely defined as male or female, such as hermaphrodite.," which seems to carry a little more clinical relevance than "Unknown."administrativeGenderCode "U" vs. "UN"Email to HettyJoyce Martin/David Johnson: Looked into this more closely and the death has "U=unknown" and the birth has "N=not yet determined" So the death edit specification uses Male, Female and Unknown and the birth edit specification uses Male, Female and Not yet determined. V2 specification also uses MFU and doesn't account for Not yet determined (if this is changed we need to make a comment to also change the V2 IG) Danny WiseAllscripts
28PHER1.11.1 Birth and Fetal Death Reporting DocumentA-SSHALL contain exactly one [1..1] templateId (CONF:4394-266131) such that it a. SHALL contain exactly one [1..1] @root="2.16.840.1.113883.10.20.26.1.1.109" (CONF:4394-266163). b. SHALL contain exactly one [1..1] @extension="2018-12-01" (CONF:4394-266164). If this document also conformed to base CCDA 2.1 then a lot of the duplicate definition here could probably be avoided.Block vote 20190214Considered - No action requiredAgreed, but there are valid reasons we can't use the US Realm Header as it was unsuitable due to differences in value sets for addresses, gender, maritalStatus, and race and ethnicity.2019-02-14Sarah Gaunt/Dave deRoode704Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
29PHERNEGThis id MAY contain zero or one [0..1] @nullFlavor="NA" (CodeSystem: HL7NullFlavor urn:oid:2.16.840.1.113883.5.1008) (CONF:4394-267005). This is confusing. All documents should have an ID, otherwise how would you ever reference them? “I need you to review document NA.” How would you submit to an HIE? How would you retrieve from an HIE? All documents shall have a unique Id value, so the 1st creator that creates one wins and all subsequent documents are invalid “duplicates”? Oddly enough Figure one, which is an example of a Fetal Death document shows a populated <id> element.DispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveWill remove this constraintSarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comRemoved NullFlavor constraint in Trifolia
30PHER1.1.4Coded Race and Ethnicity Document (BFDR)NEGSHALL contain exactly one [1..1] Mother's Coded Race and Ethnicity Section (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.2.103:2018-12-01) (CONF:4394-265790). The Coded Race and Ethnicity Document. However, the sample in Figure 2 does not include this section. Instead it includes a 2.16.840.1.113883.10.20.26.1.2.2 section.DispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveWill update sample so that the correct sections are present. Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comUpdated xml sample with correct OID
31PHER1.1.6Jurisdiction Fetal Death Reporting DocumentNEGThis code SHALL contain exactly one [1..1] @code="TEMP_LOINC_JURISDICTION_FETAL_DEATH" Jurisdiction Fetal Death Reporting Document (CONF:4394-265767). Code needs to be finalized.DispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveA LOINC code request has been submitted and all temporary codes will be replaced with standard codes before publication.Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
32PHERNEGThis patient MAY contain zero or one [0..1] sdtc:multipleBirthOrderNumber (CONF:4394-266596). Note: Records the order in which the newborn or fetus was delivered in the pregnancy. All live births and fetal losses resulting from the pregnancy should be included. Where should All live births and fetal losses be included? This document is about 1 fetal death. Any live births would not be reported in a fetal death document. Nor would multiple fetuses be included in a single document. Perhaps all births regardless of outcome shall be reported to the jurisdiction, but this is a confusing place to state that.Block vote 20190221PersuasiveWill update wording to: 'This item is to be completed only in the case of multiple gestation pregnancies. It captures the order of the birth or fetal death delivered in a multiple gestation pregnancy. (Note that both live births and fetal deaths delivered in the multiple-gestation pregnancy should be counted.) For example, if completing a birth certificate for the second born of a pregnancy which included 2 live births and one fetal death, , the order would be "2"' Sarah/Craig701Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
33PHERA-S7. SHALL contain at least one [1..*] informationRecipient (CONF:4394-265782). 8. SHALL contain exactly one [1..1] Mother Participant (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.4.1:2018-12-01) (CONF:4394-266301). Note: Mother I think there needs to be another header between these two items as the Mother Participant is not a child of the “1.1.7.4 informationRecipient”.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveThis is a Trifolia tooling issue and will be fixed before publicationSarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
34PHERA-SThis structuredBody SHALL contain exactly one [1..1] component (CONF:4394-265759) such that it 1. SHALL contain exactly one [1..1] Fetal Delivery Section (V2) (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.4:2018-12-01) (CONF:4394-265760). This structuredBody SHALL contain exactly one [1..1] component (CONF:4394-267129) such that it 1. SHALL contain exactly one [1..1] Pregnancy Risk Factors Section (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.2.108:2018-12-01) (CONF:4394-267130). Figure 3, the sample doesn’t have these sections.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update sample so that the correct sections are present. Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comFetal Delivery Section (V2) is in sample Added Pregnancy Risk Factors Section sample in Trifolia??<section classCode="DOCSECT" moodCode="EVN">
35PHERNEG7. SHALL contain at least one [1..*] informationRecipient (CONF:4394-265742). 8. SHALL contain exactly one [1..1] Mother Participant (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.4.1:2018-12-01) (CONF:4394-266299). Note: Mother I think there needs to be another header between these two items as the Mother Participant is not a child of the “1.1.7.4 informationRecipient”.DispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveThis is a Trifolia tooling issue and will be fixed before publicationSarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
36PHER1.1.8Jurisdiction Live Birth Reporting DocumentNEGThis code SHALL contain exactly one [1..1] @code="TEMP_LOINC_JURISDICTION_LIVE_BIRTH" Jurisdiction live birth report document (CONF:4394-265727). Code needs to be finalized.DispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveA LOINC code request has been submitted and all temporary codes will be replaced with standard codes before publication.Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
37PHERA-SThis structuredBody SHALL contain exactly one [1..1] component (CONF:4394-267131) such that it 1. SHALL contain exactly one [1..1] Pregnancy Risk Factors Section (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.2.108:2018-12-01) (CONF:4394-267132). However, Figure 4, the sample, doesn’t include this section.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update sample so that the correct sections are present. Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comAdded Pregnancy Risk Factors Section to xml sample (Fig 4) in Trifolia
38PHER1.1.10Provider Supplied Facility Fetal Death Reporting DocumentNEGThis patient MAY contain zero or one [0..1] sdtc:multipleBirthOrderNumber (CONF:4394-266924). Note: Records the order in which the newborn or fetus was delivered in the pregnancy. All live births and fetal losses resulting from the pregnancy should be included. Where should All live births and fetal losses be included? This document is about 1 fetal death. Any live births would not be reported in a fetal death document. Nor would multiple fetuses be included in a single document. Perhaps all births regardless of outcome shall be reported to the jurisdiction, but this is a confusing place to state that.Block vote 20190221PersuasiveWill update wording to: 'This item is to be completed only in the case of multiple gestation pregnancies. It captures the order of the birth or fetal death delivered in a multiple gestation pregnancy. (Note that both live births and fetal deaths delivered in the multiple-gestation pregnancy should be counted.) For example, if completing a birth certificate for the second born of a pregnancy which included 2 live births and one fetal death, , the order would be "2"' Sarah/Craig701Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
39PHER1.1.11.4A-S7. SHALL contain at least one [1..*] informationRecipient (CONF:4394-266927). Note: Jurisdiction of registration 8. SHALL contain exactly one [1..1] Mother Participant (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.4.1:2018-12-01) (CONF:4394-266912). Note: Mother I think there needs to be another header between these two items as the Mother Participant is not a child of the “1.1.7.4 informationRecipient”.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveThis is a Trifolia tooling issue and will be fixed before publicationSarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
40PHERA-SThis structuredBody SHALL contain exactly one [1..1] component (CONF:4394-266906) such that it 1. MAY contain zero or one [0..1] History of Infection - Fetal Death Section (V2) (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.48:2018-12-01) (CONF:4394-266907). MAY and SHALL are swapped. You MAY have a component that SHALL have a section.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveUpdate as suggestedSarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comFixed in Trifolia (CONF:266907 to SHALL 1..1 and 266906 to MAY 0..1)
41PHERNEGThis structuredBody SHALL contain exactly one [1..1] component (CONF:4394-267133) such that it 1. SHALL contain exactly one [1..1] Pregnancy Risk Factors Section (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.2.108:2018-12-01) (CONF:4394-267134). However, Figure 5, the sample, doesn’t include this section.DispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveWill update sample so that the correct sections are present. Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comAdded Pregnancy Risk Factors sample into xml (Fig 5) in Trifolia
42PHER1.1.12Provider Supplied Facility Live Birth Reporting DocumentNEGThis patient MAY contain zero or one [0..1] sdtc:multipleBirthOrderNumber (CONF:4394-266847). Note: Records the order in which the newborn or fetus was delivered in the pregnancy. All live births and fetal losses resulting from the pregnancy should be included. Where should All live births and fetal losses be included? This document is about 1 fetal death. Any live births would not be reported in a fetal death document. Nor would multiple fetuses be included in a single document. Perhaps all births regardless of outcome shall be reported to the jurisdiction, but this is a confusing place to state that.Block vote 20190221PersuasiveWill update wording to: 'This item is to be completed only in the case of multiple gestation pregnancies. It captures the order of the birth or fetal death delivered in a multiple gestation pregnancy. (Note that both live births and fetal deaths delivered in the multiple-gestation pregnancy should be counted.) For example, if completing a birth certificate for the second born of a pregnancy which included 2 live births and one fetal death, , the order would be "2"' Sarah/Craig701Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comUpdated in Trifolia
43PHERA-S7. SHALL contain at least one [1..*] informationRecipient (CONF:4394-266849). Note: Jurisdiction of registration 8. SHALL contain exactly one [1..1] Mother Participant (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.4.1:2018-12-01) (CONF:4394-266834). Note: Mother I think there needs to be another header between these two items as the Mother Participant is not a child of the “1.1.7.4 informationRecipient”.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveThis is a Trifolia tooling issue and will be fixed before publicationSarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
44PHERNEGThis structuredBody SHALL contain exactly one [1..1] component (CONF:4394-267135) such that it 1. SHALL contain exactly one [1..1] Pregnancy Risk Factors Section (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.2.108:2018-12-01) (CONF:4394-267136). However, Figure 6, the sample, does not include this section.DispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveWill update sample so that the correct sections are present. Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comAdded Pregnancy Risk Factors Section in xml sample in Trifolia
45PHERNEGThis structuredBody SHALL contain exactly one [1..1] component (CONF:4394-267135) such that it 1. SHALL contain exactly one [1..1] Pregnancy Risk Factors Section (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.2.108:2018-12-01) (CONF:4394-267136). AgainDispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveWill update sample so that the correct sections are present. Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comAdded Pregnancy Risk Factors Section in xml sample in Trifolia
46PHER1.1.14Provider Supplied Fetal Death Reporting Document (V2)NEG7. SHALL contain at least one [1..*] informationRecipient (CONF:4394-266305). Note: Jurisdiction of registration 8. SHALL contain exactly one [1..1] Mother Participant (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.4.1:2018-12-01) (CONF:4394-266303). Note: Mother I think there needs to be another header between these two items as the Mother Participant is not a child of the “1.1.7.4 informationRecipient”.DispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveThis is a Trifolia tooling issue and will be fixed before publicationSarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
47PHERNEGThis structuredBody SHALL contain exactly one [1..1] component (CONF:4394-26577) such that it 1. MAY contain zero or one [0..1] History of Infection - Fetal Death Section (V2) (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.48:2018-12-01) (CONF:4394-26578). MAY and SHALL are swappedDispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveWill update as suggested Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comFixed in Trifolia
48PHERNEGThis structuredBody SHALL contain exactly one [1..1] component (CONF:4394-267137) such that it 1. SHALL contain exactly one [1..1] Pregnancy Risk Factors Section (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.2.108:2018-12-01) (CONF:4394-267138). However, Figure 7, the sample, does not include this section.DispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveWill update sample so that the correct sections are present. Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comAdded Pregnancy Risk Factors xml sample in Trifolia
49PHER1.1.16Provider Supplied Live Birth Reporting Document (V2)NEG7. SHALL contain at least one [1..*] informationRecipient (CONF:4394-266306). Note: Jurisdiction of registration 8. SHALL contain exactly one [1..1] Mother Participant (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.4.1:2018-12-01) (CONF:4394-266297). Note: Mother I think there needs to be another header between these two items as the Mother Participant is not a child of the “1.1.7.4 informationRecipient”.DispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveA LOINC code request has been submitted and all temporary codes will be replaced with standard codes before publication.Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
50PHERNEGThis patient MAY contain zero or one [0..1] sdtc:multipleBirthOrderNumber (CONF:4394-266589). Note: Records the order in which the newborn or fetus was delivered in the pregnancy. All live births and fetal losses resulting from the pregnancy should be included. AgainBlock vote 20190221PersuasiveWill update wording to: 'This item is to be completed only in the case of multiple gestation pregnancies. It captures the order of the birth or fetal death delivered in a multiple gestation pregnancy. (Note that both live births and fetal deaths delivered in the multiple-gestation pregnancy should be counted.) For example, if completing a birth certificate for the second born of a pregnancy which included 2 live births and one fetal death, the order would be "2"' Sarah/Craig701Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comFixed in Trifolia - Updated CONF:4394-266589 Note: to proposed wording in disposition
51PHERNEGThis structuredBody SHALL contain exactly one [1..1] component (CONF:4394-267139) such that it 1. SHALL contain exactly one [1..1] Pregnancy Risk Factors Section (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.2.108:2018-12-01) (CONF:4394-267140). However, Figure 8, the sample, does not include this section.DispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveWill update sample so that the correct sections are present. Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comAdded Pregnancy Risk Factors Section to xml sample in Trifolia
52PHER1.1.18Provider Supplied Mother's Fetal Death Reporting DocumentNEGThis patient MAY contain zero or one [0..1] sdtc:multipleBirthOrderNumber (CONF:4394-266886). Note: Records the order in which the newborn or fetus was delivered in the pregnancy. All live births and fetal losses resulting from the pregnancy should be included. AgainBlock vote 20190221PersuasiveWill update wording to: 'This item is to be completed only in the case of multiple gestation pregnancies. It captures the order of the birth or fetal death delivered in a multiple gestation pregnancy. (Note that both live births and fetal deaths delivered in the multiple-gestation pregnancy should be counted.) For example, if completing a birth certificate for the second born of a pregnancy which included 2 live births and one fetal death, , the order would be "2"' Sarah/Craig701Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comFixed in Trifolia - Updated CONF:4394-266589 Note: to proposed wording in disposition
53PHER1.1.20Provider Supplied Mother's Live Birth Reporting DocumentNEG7. SHALL contain at least one [1..*] informationRecipient (CONF:4394-266884). Note: Jurisdiction of registration 8. SHALL contain exactly one [1..1] Mother Participant (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.4.1:2018-12-01) (CONF:4394-266873). Note: Mother Again 1.1.19.4 8. SHALL contain at least one [1..*] informationRecipient (CONF:4394-266806). Note: Jurisdiction of registration 9. SHALL contain exactly one [1..1] Mother Participant (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.4.1:2018-12-01) (CONF:4394-266795). Note: Mother Again 1.1.21.5DispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveThis is a Trifolia tooling issue and will be fixed before publicationSarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
54PHERNEGThis structuredBody SHALL contain exactly one [1..1] component (CONF:4394-267141) such that it 1. SHALL contain exactly one [1..1] Pregnancy Risk Factors Section (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.2.108:2018-12-01) (CONF:4394-267142). However, Figure 10, the sample, does not include this section.DispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveWill update sample so that the correct sections are present. Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comAdd Pregnancy Risk Factors Section to xml in Trifolia
55PHERNEGTable 25 - PHC1499 PHIN VS (CDC Local Coding System) urn:oid:2.16.840.1.114222.4.5. 274 Other (with write in text)If I wanted to use the “write in text”, where in CDA would that go? Perhaps the usage of a more complete value set, like personal and legal relationship, would be a better choice for this concept.DispositionedWeds Q? - have emailed Daniel/EmmaPersuasive with modPersonal and legal relationship has no concept for "father of baby" and this is the value set used in the certificates. Will add explanation/example on how to do the write in text using originalText.Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
56PHER2.2Edit Flags SectionNEGThis code SHALL contain exactly one [1..1] @code="TEMP_LOINC_EDIT_FLAGS_SECTION" Edit flags section (CONF:4394- 266337). Code needs to be finalizedDispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveA LOINC code request has been submitted and all temporary codes will be replaced with standard codes before publication.Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
57PHER2.4Father's Information SectionNEGThis code SHALL contain exactly one [1..1] @code="TEMP_LOINC_FATHER_INFO" Father's information section (CONF:4394-266504). Code needs to be finalizedDispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveA LOINC code request has been submitted and all temporary codes will be replaced with standard codes before publication.Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
58PHERNEGThe subject, if present, SHOULD contain zero or one [0..1] sdtc:raceCode, which SHALL be selected from ValueSet Race (NCHS) urn:oid:2.16.840.1.114222.4.11.7373 DYNAMIC (CONF:4394-266499) such that it Note: Father's race AND the following statement The subject, if present, MAY contain zero or more [0..*] sdtc:raceCode, which SHALL be selected from ValueSet Race (NCHS) urn:oid:2.16.840.1.114222.4.11.7373 DYNAMIC (CONF:4394-266500) such that it Note: Father's race Collapse down to 1 conformance statement “SHOULD contain [0..*]”Block vote 20190214Persuasive with modThe first constraint should actually be SHOULD 0..1 raceCode (not sdtc:raceCode). The CDA only allows 1 raceCode that's why the second sdtc:raceCode is there. Will udpate this to be raceCode not sdtc:raceCode2019-02-14Sarah Gaunt/Dave deRoode704Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comHow to remove sdtc:?
59PHER2.10Mother's Information SectionNEGThe subject, if present, SHALL contain exactly one [1..1] sdtc:raceCode, which SHALL be selected from ValueSet Race (NCHS) urn:oid:2.16.840.1.114222.4.11.7373 DYNAMIC (CONF:4394-266478) such that it Note: Mother's race AND the following statement The subject, if present, MAY contain zero or more [0..*] sdtc:raceCode, which SHALL be selected from ValueSet Race (NCHS) urn:oid:2.16.840.1.114222.4.11.7373 DYNAMIC (CONF:4394-266479) such that it Note: Mother's race Collapse down to 1 conformance statement “SHALL contain [1..*]”Block vote 20190214Persuasive with modThe 1st sdtc:raceCode should actually be 1..1 race (not sdtc:race). The 2nd sdtc:race is correct - it needs to be there because the base CDA constrains raceCode to allow only 1. 2019-02-14Sarah Gaunt/Dave deRoode704Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
60PHER2.12Newborn Delivery Section (V2)A-QSection “Newborn Delivery” 2.12 “The section contains information on the newborn baby. Note, if there is a multiple delivery, there will be a separate report for each birth. The content is drawn from labor and delivery records, newborn's medical records, mother's medical records.” Shouldn’t this say “…there will be a separate report document for each…”?DispositionedWeds Q? - Affirmative/PersuasivePersuasiveThis is correct, we will updated wording as suggested.Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comFixed in Trifolia
61PHER2.14Pregnancy Risk Factors SectionNEGThis code SHALL contain exactly one [1..1] @code="TEMP_LOINC_PREGNANCY_RISK_FACTORS" Pregnancy risk factors section (CONF:4394-267118). Finalize code value.DispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveA LOINC code request has been submitted and all temporary codes will be replaced with standard codes before publication.Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
62PHER2.17 Procedure Section (V2)NEG2.17 Procedure Section (V2)This is the 1st time the BFDR procedure section has been define is it not? Then why is it V2?DispositionedWeds Q? - have emailed Daniel/EmmaNot persuasiveNo, this is the second version of this template (see 9.30 - in the changes from previous version appendix)Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
63PHER3.2Apgar Score OrganizerA-QFigure 14: Apgar Score Organizer Why does the Organizer example show an apgar 10 min observation template?DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update example to the correct (organizer) example.Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.comFixed in Trifolia - updated Apgar Organizer sample to 'Apgar Score at 5 Minutes' (from 10 minutes)
64PHER3.9Coded Initiating Cause/Condition of Fetal DeathNEGThis code SHALL contain exactly one [1..1] @code="TEMP_LOINC_CODED_INIT_CAUSE_DEATH" Coded Initiating cause of death or condition Fetus (CONF:4394-266057) Finalize codeDispositionedWeds Q? - have emailed Daniel/EmmaPersuasiveA LOINC code request has been submitted and all temporary codes will be replaced with standard codes before publication.Sarah Gaunt/Mead Walker1200Emma JonesAllscriptsDaniel VentonDaniel.Venton@allscripts.com
65PHERVolume 1A-TSDWG Co-chair list needs to be updatedDispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update list in the disposition commentsSarah Gaunt/Mead Walker1200Gay DolinIntelligent Medical ObjectsUpdated in Vol 1
66PHERCoded Cause of Fetal Death section and Coded Cause of Fetal Death DocumentNEGThis code SHALL contain exactly one [1..1] @code="86804-2" Cause of death classification and related information Document (CONF:4394-265810). This code SHALL contain exactly one [1..1] @code="86804-2" Cause of death classification and related information Document (CONF:4394-265829).Why is the same code used here for both the document and section. This seems as if it would be problematic in document and section queries and document mgt systemsYesWaiting on commenterEmailed SwapnaGay DolinIntelligent Medical Objects
67PHERCoded Initiating Cause/Condition of Fetal Death (required) and Coded Other Significant Cause/Condition of Fetal Death (optional)NEGThis code SHALL contain exactly one [1..1] @code="TEMP_LOINC_CODED_OTHER_CAUSE" Coded death cause other significant conditions Fetus (CONF:4394-266066). And This code SHALL contain exactly one [1..1] @code="TEMP_LOINC_CODED_INIT_CAUSE_DEATH" Coded Initiating cause of death or condition Fetus (CONF:4394-266057).Has LOINC agreed to create these 2 codes with the exact LOINC long common name/meaning requested? I realize that timing is likely an issue here, but without knowing that this is true and without seeing the codes LOINC ultimatley creates, these 2 codes/meanings are the only differentiators between these two templates given they use the exact same observation/value value set. If codes are not supplied as hoped - either only 1 template is needed or a different design is needed.YesWaiting on commenterEmailed SwapnaNot persuasiveLOINC will create these codes - have confirmed with Swapna at RegenstriefGay DolinIntelligent Medical Objects
68PHERGeneral (Volumne 1 and 2/Overall ProjectNEGWRT the Reducing Clinician Burden Initiative (https://www.healthit.gov/topic/usability-and-provider-burden/strategy-reducing-burden-relating-use-health-it-and-ehrs) how does the perpetuation of the requirements for sending 3-5 (?) separate documents for each infant birth or death support this federal initiative??I realize this comment may considered beyond the scope of the standards development - however, we (HL7/Vendors etc) have certainly been accused making things worse by perpetuating the paper world in our HIT initiatives. We need to be innovative and create new technologies to harvest and collect data that is needed by the government, rather than regurgitate the paper world that, at best, does not eliminate burden and at worst adds implmentation costs, adds burden and adds no value. - but I request formal follow-up with input from HHS/CMS and/or the sponsor.. YesSG - working onJM: Not sure what is meant by sending 3-5 separate documents. What does this refer to? ASK Sarah how to answer this use of multiple worksheets SG - will craft response and run it by GayGay DolinIntelligent Medical Objects
69PHERVolume 1A-TFootNote 13: Federal Register 62FR58782. 1997. Available from: https://obamawhitehouse.archives.gov/omb/fedreg_1997standards.Inactive site: "Sorry, the page you're looking for can't be found."DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update footnoteSarah Gaunt/Mead Walker1200Gay DolinIntelligent Medical ObjectsFootnote updated in Vol 1
70PHERContained By: Provider Supplied Live Birth Reporting Document (V2) (required) Provider Supplied Fetal Death Reporting Document (V2) (required) Jurisdiction Live Birth Reporting Document (required) Jurisdiction Fetal Death Reporting Document (required) Coded Race and Ethnicity Document (BFDR) (required) Provider Supplied Mother's Live Birth Reporting Document (required) Provider Supplied Facility Live Birth Reporting Document (required) Provider Supplied Mother's Fetal Death Reporting Document (required) Provider Supplied Facility Fetal Death Reporting Document (required)NEG1.1.17.4 informationRecipient In the Provider Supplied Live Birth Reporting Document, the main informationRecipient is the jurisdictional vital records office. 7. SHALL contain at least one [1..*] informationRecipient (CONF:4394-266306). Note: Jurisdiction of registration 8. SHALL contain exactly one [1..1] Mother Participant (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.4.1:2018-12-01) (CONF:4394-266297). Note: Mother 9. MAY contain zero or one [0..1] Father Participant (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.4.2:2018-12-01) (CONF:4394-266298). Note: FatherIf the main recipient is the jursidictonal records office, why is their no discrete data elements describing this recipient? The InformationRecipient represents a recipient who should receive a copy of the document. Are the parents the recipients of these CDA documents? If so, given that the jursidiction is the main InformationRecipient, then aren't they secondary information recipients? (TRC (secondary recipient)) as opposed to PRCP?) Also, From the standard: NOTE: The information recipient is an entity to whom a copy of a document is directed, at the time of document authorship. It is not the same as the cumulative set of persons to whom the document has subsequently been disclosed, over the life-time of the patient. Such a disclosure list would not be contained within the document, and it outside the scope of CDA. Also, I see in the xml snippet you have listed "Participant - Mother" as a participant, not as an information recipient and yet I do not see a "Participant - Mother? template. Generally, I am confused about the intended use case for this InformationRecipient designYesBlock vote 20190221Persuasive with modWill update recipient as suggested. Parents are not recipients of the CDA Documents. There is a tooling issue which makes it look as though the mother and father are informationRecipients (Trifolia is not respecting the "header" checkbox for the Mother and Father participant - this will be fixed before publication). Will update the xml to say "Mother Participant" which is the proper name of the template. There is both a Father Participant and a Mother Participant in the Participation and Other Templates section.Sarah/Craig701Gay DolinIntelligent Medical ObjectsTODO: Fix tooling issue. Xml samples appear to have correct informationRecipient, Mother and Father participant
71PHER3.18 Father's Bridged Race A-CThis template represents a single race code assigned to the person. In cases where multiple races are recorded for a person an algorithm (NCHS defined) is used to select a single race from the "bridged race" codes. The goal is to provide race statistics that are comparable with those used historically to facilitate time series analysis.Please add references, such as "https://www.cdc.gov/nchs/nvss/bridged_race.htm" and perhaps and example of a few algorithms. For example, how is a "Bridged Black" or a "Bridged White" determined?The IG requires clarifying text regurgitating https://www.cdc.gov/nchs/data/series/sr_02/sr02_135.pdf into some high level, explanatory text, but with more detail than is currently presentYesDavid JohnsonJM: 2018 is the last year NCHS will publish/use bridged race data. Does this matter? David Johnson to give guidanceGay DolinIntelligent Medical Objects
72PHERValue Set: Bridged Race (NCHS) urn:oid:2.16.840.1.114222.4.11.7377NEGThe set of race codes used by NCHS for Vital Statistics reporting enhanced by “bridged race” codes. These codes are assigned to persons who assert multiple races using an algorithm defined by NCHS. The goal is to provide race statistics that are comparable with those used historically in order to facilitate time series analysis."The first 15 codes in this value set are from the CDC Race and Ethnicity codes system. Why are these members in this value set? If algorithms are used to determine a set of races that = what "White" means within this context (i.e when a person has selected more than one race), what does the code mean received out of the context.? How does, for example, "PHC1411 Bridged American Indian/Alaskan Native" differ from "1002-5 American Indian or Alaska Native" within this value set, and how does "1002-5 American Indian or Alaska Native" within this value set differ from "1002-5 American Indian or Alaska Native" not in this value set? Or more simply (or naively) asked, why does this value set have more than these 4 concepts (based on the stated goal): PHC1409 Bridged White PHC1410 Bridged Black PHC1411 Bridged American Indian/Alaskan Native PHC1412 Asian & Pacific IslanderYesDavid JohnsonGay DolinIntelligent Medical Objects
73PHERVol 1Appendix B44A-QFigure 16 Birth/Fetal Death Reporting Process1. Information Sourcing (Provider Supplied Fetal Live Birth & Death Reporting) is over simplified, it seems to represent the delivirey and / .EHR entity. 2. IF that is the case then by the diagram it seems that the entity is responsible for specific inforamtion but not the generation of the CDA reporting documents, these are in fact generated by the Jurisdictional Vital Records Office. 3. From an implementation perspective this is confusing - for a provider/EHR can we assume that this is not the case? Is it more accurate that the CDA Reporting documents are generated and the recipient is the Jurisdictional Vital Records Office? 4. At which point the Jurisdictional Vital Records Office decomposes the documents and generates specific documents or reports to the National Stasitical Agency? This needed clarification may help answer a following question on edit events in Vol. 2. SGEmail GeorgeGeorge Dixon
74PHERVol 1Appendix C46A-QExtensions to CDA R2 / raceCode and ethnicGroupCodeIs the intent to support additional / multiple top level race and ethnicity entries and this does not represent the MU2015 related structure where Race and Ethnicity entries are refined with multiple related selections? If this assumption is correct then EHR systems are likely not set up to capture this data since they were restructured to capture the MU2015 requirement. The additional or change in information requirement will add additional burden to the recorder to support both data collection workflows. Email to HettyDavid JohnsonGeorge Dixon
75PHERVol 21.1.1.426A-Qinformation RecipientInformation Recipient is found in more locations in the document, this question is more general. The interpretation of the 1.1.1.4 is that the document must have an information recipient and must have an intendedrecipient but the informationrecipient maybe UNK/NI. This becomes important from an implementation perspective and relates back the Figure 16 information/document flow. Providers want the generation of CDA documents to be as automated as possible and there may be no human involved in the sending. If the information recipient is a consistent entity its not an issue if it is not then depending on the workflow the intended recipient may not be known depending on the trigger for creation of document. Block vote 20190221Information recipient should never be UNK/NI (maybe we need to add a constraint saying this??)Considered - question answeredThere will always be a known informationRecipient. They are very specific and are outlined in the use cases - they are: jurisdictional vital records office and NCHSSarah/Craig701George Dixon
76PHERVol 23.8205NEGCigarette Smoking Before and During PregnancyEHRs already have requirements to collect smoking and or Tobacco Use data. Collecting this information will be seen as redundant and the values (entries) are very unlikely to be accurate. Use of existing collected data needs to be considered to reduce charting burden. Block vote 20190221Not persuasiveMaternal tobacco use is in the format shown is a required item on the US Standard Certificate of Live Birth and US Standard Report of Fetal Death. This information comes from the mother; not the EHR. Sarah/Craig701George Dixon
77PHERVol 22.1134NEGEdit Flags: Birthweight Edit Flag (required) Plurality Edit Flag (required) Number of Previous Cesareans Edit Flag (required) Number of Prenatal Care Visits Edit Flag (required) Mother’s Pre-Pregnancy Weight Edit Flag (required) Mother’s Height Edit Flag (required) Mother’s Education Edit Flag (required) Mother's At Delivery Weight Edit Flag (required) Mother’s Date of Birth Edit Flag (required) Estimate of Gestation Edit Flag (required) Father’s Education Edit Flag (required) Father’s Date of Birth Edit Flag (required) section contains the edit flags that specify whether the originally provided data passed validation checks. These validation checks are done at the jurisdiction prior to sending to the National Statistical Agency Please explain further the source of information. The Original Source of data is the EHR, is it the responsibilty of the EHR to implement and pass edit audit information (more accurate) or is the EHR only passing the data and the Jurisdiction entity tracking existing data and passing the flag? If its the jurisdiction then there is potentially a large loss of edit data. SG - email George - cc Hetty, David JusticeEmail George to find out what he exactly means Might need David Justice input Not responsibiltiy of EHR (should be built into state's edr system). George DixonMother's smoking status during pregnancy SHALL be mapped from existing records (i.e. Social History), if known?
78PHERVol 23.25248NEGFinal Route and Method of Delivery"This template represents the final route and method of delivery." Contains Trial of Labor Attempted which is defined as "This template represents, whether, in the case of a cesarean delivery, a trial of labor was attempted." The section title is miss leading and needs to reflect the actual information being collected to not confuse implementation. Block vote 20190214Not persuasiveThis is how this is set up and worded on the certificate. The name of the template only deals with the information collected in that actual template. The contained template has it's own title. This is the usual representation of data in CDA Igs (see C-CDA for examples)2019-02-14Sarah Gaunt/Dave deRoode704George Dixon
79PHERVol 2276NEGTable 160 Maternal MorbiditiesThis table of values is insufficient and needs expanding. Example - Eclampsia (Severe Acute Hypetenstion) represents morbidity to mother and infant. DispositionedWeds Q3 - GeorgeNot persuasiveThese values are the exact and only values from the Birth and Fetal Death Certificates and are the only values allowedSarah Gaunt/George Cole1300George Dixon
80PHERVol 23.38282NEGMother Married at Conception, Birth or BetweenPaternity Acknowledgement SignedSection title - "Mother Married at Conception, Birth or Between"defined as - This template represents whether the mother was married at conception, at the time of birth, or at any time between conception and giving birth. and contains "Paternity Acknowledgement Signed" defined as This template represents whether or not a paternity acknowledgement was signed by the father if the mother was not married at conception, at the time of birth, or at any time between conception and giving birth. The section title and discription does not well represent the actual purpose and information collected. Also Marriage is not indicative of paternity. This should be corrected to decrease implementation confusion and more accurately represent the information corrected DispositionedWeds Q3 - GeorgeNot persuasive with modThis is how it is set up and worded on the birth certificate. The information is only required if the mother was not married. Will include the forms and worksheets when the IG is published.Sarah Gaunt/George Cole1300George Dixon
81PHERVol 122A-TJuridictionJurisdiction DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200George DixonFixed in Vol 1
82PHERIntroduction1.1 Purpose8A-Tjurisdictional vital records officesjurisdictional Vital Records OfficesThe PHER WG had decided on standard language for the vital records information flows. Change to be consistent with that language here and throughout the document. DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Hetty KhanNCHShdk1@cdc.govFixed in Trifolia in following template: Coded Cause of Fetal Death(2.16.840.1.113883.10.20.26.1.1.107:2018-12-01)/informationRecipient Coded Crace and Ethnicity Document (2.16.840.1.113883.10.20.26.1.1.106:2018-12-01)/informationRecipient Juridictional Fetal Death Reporting (2.16.840.1.113883.10.20.26.1.1.104:2018-12-01)/author note: Juridictional Live Birth Reporting (2.16.840.1.113883.10.20.26.1.1.103:2018-12-01)/author note: PSFFDR (2.16.840.1.113883.10.20.26.1.1.113:2018-12-01)/informationRecipient PSFLBR (2.16.840.1.113883.10.20.26.1.1.111:2018-12-01) description and /informationRecipient PSFDR (2.16.840.1.113883.10.20.26.1.1.102:2018-12-01)/informationRecipient PSLBR (2.16.840.1.113883.10.20.26.1.1.101:2018-12-01)/informationRecipient PSMFDR (2.16.840.1.113883.10.20.26.1.1.112:2018-12-01)/informationRecipient and description PSMLBR (2.16.840.1.113883.10.20.26.1.1.110:2018-12-01)/informationRecipient Void Fetal Death Certificate (2.16.840.1.113883.10.20.26.1.1.108:2018-10-31)/author Void Live Birth Certificate (2.16.840.1.113883.10.20.26.1.1.105:2018-12-01)/author Volume 1 Purpose
83PHERIntroduction1.1 Purpose9A-TThey exchange information between the jurisdictional Vital Records Office and the CDC/NCHSThey exchange information between the jurisdictional Vital Records Offices and the CDC/NCHSAdd "s" to OfficeDispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Hetty KhanNCHShdk1@cdc.govFixed in Vol 1
84PHERIntroduction1.1 Purpose9A-SThis document is created to support the seven use cases for the expansion of the flow of information to CDC/NCHS in the cases of birth and fetal death, return coded cause of fetal death, and race and ethnicity information back to the states.This document is created to support the seven use cases for the expansion of the flow of information to CDC/NCHS in the cases of birth and fetal death, and the return of coded cause of fetal death, and race and ethnicity information back to the states.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Hetty KhanNCHShdk1@cdc.govFixed in Vol 1
85PHERIntroduction1.1 Scope9A-Sto support the expansion of the flow of information to CDC/NCHS and to return coded cause of death and race and ethnicity information back to the states.to support the expansion of the flow of information to CDC/NCHS and to return coded cause of death, fetal death, and race and ethnicity information back to the states.include fetal death also since we have already developed the return of featl death in the V2.6 BFDR.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Hetty KhanNCHSAlaina Elliotthdk1@cdc.govFixed in Vol 1
86PHERIntroduction1.3 Relationship to another Standard10A-SWe plan to expandWe are expandingsuggestion to state this in present tenseDispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Hetty KhanNCHShdk1@cdc.govFixed in Vol 1
87PHERIntroduction1.5 Approach14A-TFetal Death Edit Specification for the 2003 Revision of the U.S. Standard Report of Fetal of DeathFetal Death Edit Specification for the 2003 Revision of the U.S. Standard Report of Fetal DeathRemove the "of" at the second to last word.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Hetty KhanNCHShdk1@cdc.govFixed in Vol 1
88PHERVolume 12.2 Project Background21A-SThis CDA will be updated to support the following use cases:This CDA has been updated to support the following use cases:suggestion to state this in present tenseDispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Hetty KhanNCHShdk1@cdc.govFixed in Vol 1
89PHERVolume 12.2 Project Background21A-SProvider Supplied Live Birth Reporting: ...The data requirements for provider supplied live birth information are based on the Edit Specifications for the 2003 Revision of the U.S. Standard Certificate of Birth, the US Standard Facility Worksheet for the Live Birth Certificate, the US Standard Attachment to the Facility Worksheet for the Live Birth Certificate for Multiple Births, and the US Standard Mothers Worksheet for Child's Birth Certificate.Provider Supplied Live Birth Reporting: ...The data requirements for provider supplied live birth information are based on the Edit Specifications for the 2003 Revision of the U.S. Standard Certificate of Birth, the 2016 US Standard Facility Worksheet for the Live Birth Certificate, the 2016 US Standard Attachment to the Facility Worksheet for the Live Birth Certificate for Multiple Births, and the 2016 US Standard Mothers Worksheet for Child's Birth Certificate.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Hetty KhanNCHShdk1@cdc.govFixed in Vol 1
90PHERVolume 12.2 Project Background21A-TProvider Supplied Fetal Death Reporting: ...to the jurisdiction vitalProvider Supplied Fetal Death Reporting: ...to the jurisdictional vitalFor consistency DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Hetty KhanNCHShdk1@cdc.govFixed in Vol 1
91PHERVolume 12.2 Project Background22A-SProvider Supplied Fetal Death Reporting: ...The data requirements for provider supplied fetal death information are based on the U.S. Standard Report of Fetal Death, the US Standard Facility Worksheet for the Report of Fetal Death, and the US Standard Patient's Worksheet for the Report of Fetal Death.Provider Supplied Fetal Death Reporting: ...The data requirements for provider supplied fetal death information are based on the U.S. Standard Report of Fetal Death, the 2004 US Standard Facility Worksheet for the Report of Fetal Death, and the 2004 US Standard Patient's Worksheet for the Report of Fetal Death.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Hetty KhanNCHShdk1@cdc.govFixed in Vol 1
92PHERVolume 12.2 Project Background22A-SFetal Death Mother’s Information: ...The data requirements for fetal death mother's information are based on the US Standard Patient's Worksheet for the Report of Fetal Death.Fetal Death Mother’s Information: ...The data requirements for fetal death mother's information are based on the 2004 US Standard Patient's Worksheet for the Report of Fetal Death.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Hetty KhanNCHShdk1@cdc.govFixed in Vol 1
93PHERVolume 12.2 Project Background22A-SFetal Death Facility Information: ...The data requirements for fetal death mother's information are based on the US Standard Facility Worksheet for the Report of Fetal Death.Fetal Death Facility Information: ...The data requirements for fetal death mother's information are based on the 2004 US Standard Facility Worksheet for the Report of Fetal Death.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Hetty KhanNCHShdk1@cdc.govFixed in Vol 1
94PHERVolume 12.2 Project Background23A-SCoded Race/Ethnicity Reporting—Jurisdictional Vital Records OfficeCoded Race/Ethnicity Reporting—jurisdictional Vital Records OfficeChange "J" to "j" for consistency in standard language here and throughout documentDispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Hetty KhanNCHShdk1@cdc.govFixed in Vol 1
95PHERVolume 21.121A-TThe C-CDA R2.1 US Realm Header (V3) was considered for use here as a base template but was considered unsuitable due to differences betwen it and this top-level template in value sets for addresses, gender, maritalStatus, and race and ethnicity.The C-CDA R2.1 US Realm Header (V3) was considered for use here as a base template but was considered unsuitable due to differences between it and this top-level template in value sets for addresses, gender, maritalStatus, and race and ethnicity.Typo in Note at the end of this pageDispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Hetty KhanNCHShdk1@cdc.govFixed in Trifolia
96PHER44.1A-QFather Participant represents a personal relationship with the Maternal Mother. Would an implementer also use this template to represent a female partne or other mother? Would all the father designated templates apply here? Block vote 20190221Considered - question answeredThe only relationship is that they are the biological father of the child. Sarah/Craig701Kanwarpreet SethiLantana Consulting GroupZabrina Gonzagazabrina.gonzaga@lantanagroup.com
97PHER11.1.5.2A-SSHALL contain exactly one [1..1] Mother Participant (identifier: urn:hl7ii:2.16.840.1.113883.10.20.26.1.4.1:2018-12-01) (CONF:4394-266307). Note: MotherDoes this apply to maternal mother of the baby? Consider using "maternal" throughout IG or defining in Volume 1. Block vote 20190221Joyce - could you help out with descriptions (i.e. biological father?)Persuasive with modAlways want the information of the woman delivery the baby. Will add clarification throughout the IG and in Volume 1.Sarah/Craig701Kanwarpreet SethiLantana Consulting GroupZabrina Gonzagazabrina.gonzaga@lantanagroup.com
98PHER33.29A-TThis code SHALL contain exactly one [1..1] @code="88118-5" Tabulated Ethnicity^Father (CONF:4394-266767).Tabulated Ethnicity Father (CONF:4394-266767).Publication issue? Remove "^"DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update to "Father's Tabulated ethnicity [CDC]" Will also double check for any others containing "^" and update accordingly.Sarah Gaunt/Mead Walker1200Kanwarpreet SethiLantana Consulting GroupZabrina Gonzagazabrina.gonzaga@lantanagroup.com Updated to 'Tabulated Ethnicty of Father [CDC]' Updated (88118-5) Updated to 'Tabulated Mother's Ethnicity [CDC] (88117-7) Removed '^' from both Father and Mother Bridged Race codes
99PHER33.18 3.45A-QTable 115: Bridged Race (NCHS)How is this value set in PHINVADS different from what is in VSAC? https://vsac.nlm.nih.gov/valueset/2.16.840.1.113883.1.11.14914/expansion If equivalent, recommend updating the link to represent what is in VSAC.DispositionedWeds Q? - Affirmative/Considered - Question AnsweredConsidered - question answeredWe need to point to the phinvads value sets - this is a basic structural choice that was made for the birth and death reporting specifications.Sarah Gaunt/Mead Walker1200Kanwarpreet SethiLantana Consulting GroupZabrina Gonzagazabrina.gonzaga@lantanagroup.com
100PHER33.11A-QTable 96: Newborn Congenital Anomalies 260413007 None The value set is intended to include values that represent malformations of the newborn. Would they use a null flavor instead using "none"? nullFlavor=NI? The template allows a nullFlavor of UNK but does not specify the use of NI. Is the "none' in the table intended to represent "None of the specfied items in the value set"? This code appears to be a qualifier in SNOMED. Recommend clarifying the meaning of the value in the constraint(CONF:4394-154).Block vote 20190214Considered - question answeredNo, they would use the code for None as specified in the value set. There is no value in nullFlavor that means "none" and the recommendation from vocab is to use a code for this concept. This value set has been specifically created for the certificate. The value stated in PHINVADS is "None of the specified items in this value set (including concept codes: 89369001, 67531005, 12770006, 17190001, 18735004, 72951007, 67341007, 67341007, 80281008, 87979003, 70156005, 409709004, 416010008) for Newborn Congenital Anomalies"2019-02-14Sarah Gaunt/Dave deRoode704Kanwarpreet SethiLantana Consulting GroupZabrina Gonzagazabrina.gonzaga@lantanagroup.com
101PHER11.2.1.1A-TThis patientRole SHOULD contain exactly one [1..1] id (CONF:4394-265879This patientRole SHALL contain exactly one [1..1] id (CONF:4394-265879)Is this required? If so, recommend changing the "SHOULD" to "SHALL".Block vote 20190221VFDIPersuasive with modChange SHOULD to SHALL as suggested. Also update wording on the note above this constraint to be consistent with the other id constraint.Sarah/Craig701Kanwarpreet SethiLantana Consulting GroupZabrina Gonzagazabrina.gonzaga@lantanagroup.com
102PHERVolume 2A-TMissing the Certifier Name and Date Certified - need to add to the appropriate documentsMissing the Certifier Name and Date Certified - need to add to the appropriate documentsBlock vote 20190214PSLBI, PSLFBI, JLBI. Will add a <performer> in header. Maybe legalAuthenticatorPersuasiveWill add as suggested2019-02-14Sarah Gaunt/Dave deRoode704Kanwarpreet SethiLantana Consulting GroupSarah Gauntsarah.gaunt@lantanagroup.comHow is this different from the author of the document? Author SHALL contain a time. Add label to clarify?
103PHERVolume 2A-TMissing date received by registrar and date filed by registrar - need to add to the appropriate documentsMissing date received by registrar and date filed by registrar - need to add to the appropriate documentsDispositionedWeds Q? - Affirmative/PersuasivePersuasiveUpdate as suggestedSarah Gaunt/Mead Walker1200Kanwarpreet SethiLantana Consulting GroupSarah Gauntsarah.gaunt@lantanagroup.comIs JVRO=Registrar?
104PHERVolume 2A-TMissing "Place where birth occurred" (Hospital, freestanding birthing center, home birth, etc.) - need to add to the appropriate documentsMissing "Place where birth occurred" (Hospital, freestanding birthing center, home birth, etc.) - need to add to the appropriate documentsDispositionedWeds Q? - Affirmative/PersuasivePersuasiveUpdate as suggestedSarah Gaunt/Mead Walker1200Kanwarpreet SethiLantana Consulting GroupSarah Gauntsarah.gaunt@lantanagroup.comPresent in /L&D Section/ Labor & Delivery Process (V2)?
105PHERVolume 2A-TMother married - some confusion here about which use cases this is in - plus the difference between ever married and married between conception and birth - need to clarify and then update IG as neededMother married - some confusion here about which use cases this is in - plus the difference between ever married and married between conception and birth - need to clarify and then update IG as neededBlock vote 20190214Not in deathPersuasive with modConfirm 'ever married' is not contained in any all reports. Mother married at conception, birth, or between is contained in mother's information section with a note "This entry SHALL NOT be present in the fetal death document-types." We will add schematron validation to ensure this template shall not be in death reporting and shall be in birth reporting2019-02-14Sarah Gaunt/Dave deRoode704Kanwarpreet SethiLantana Consulting GroupSarah Gauntsarah.gaunt@lantanagroup.comNote added to entry template in TrifoliaTODO: schematron validation check
106PHERVolume 2A-TInside city limits - need to clarify which use cases this is included in and update IG as neededInside city limits - need to clarify which use cases this is included in and update IG as neededBlock vote 20190214PSLBI, PSMBLI, PSFDI, PSMFDI. Ask Hetty 'why not in V2'?May need to add notes which document types it should be in PersuasiveWill ensure that we add "inside city limits" to the correct use cases.2019-02-14Sarah Gaunt/Dave deRoode704Kanwarpreet SethiLantana Consulting GroupSarah Gauntsarah.gaunt@lantanagroup.comAdded to Note: that 'inside city limits' is required in these 4 use casesCleaner way?
107PHERVolume 2A-TPlanned home birth - need to clarify which use cases this is included in and update IG as needed.Planned home birth - need to clarify which use cases this is included in and update IG as needed.Block vote 20190214PSLBI, PSFLBI, PSFDI, FSFFDI, JLBI, JFDRConsidered - No action requiredChecked use cases and this template is contained in correct use cases2019-02-14Sarah Gaunt/Dave deRoode704Kanwarpreet SethiLantana Consulting GroupSarah Gauntsarah.gaunt@lantanagroup.com
108PHERVolume 2A-T CCOFDI - are the demographic data in the header correct? Need to clarify and update IG as needed CCOFDI - are the demographic data in the header correct? Need to clarify and update IG as neededSG emailAsk Meade: "4.4.9 PID_BR_ID - PATIENT IDENTIFICATION The Patient Identification Segment (PID) includes basic demographics. The birth reporting flavor highlights the fields within the segment that are relevant to the implementation guide. For void certificate reporting, and for reporting coded fetal cause of death and coded race and ethnicity reporting, a more specialized flavor has been created to identify the certificate that data is being conveyed about"Kanwarpreet SethiLantana Consulting GroupSarah Gauntsarah.gaunt@lantanagroup.com
109PHERVolume 2A-TCREI - are the demographic data in the header correct? Need to clarify and update IG as neededCREI - are the demographic data in the header correct? Need to clarify and update IG as neededBlock vote 20190214See CCOFDIPersuasiveWill ensure that the demographic data are correct2019-02-14Sarah Gaunt/Dave deRoode704Kanwarpreet SethiLantana Consulting GroupSarah Gauntsarah.gaunt@lantanagroup.com
110PHERVolume 2A-TNeed to check all use cases to ensure that the correct data elements, with the correct cardinalities are in each document type and update IG as needed.Need to check all use cases to ensure that the correct data elements, with the correct cardinalities are in each document type and update IG as needed.Block vote 20190214PersuasiveWill analyse use cases to ensure that the corrrect data elements, with the corretn cardinalities are in each document type and update IG as needed.2019-02-14Sarah Gaunt/Dave deRoode704Kanwarpreet SethiLantana Consulting GroupSarah Gauntsarah.gaunt@lantanagroup.com
111PHERVolume 22.2 Edit Flags SectionA-TThe section containsThis section containsUpdate wordingUpdate wordingDispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Kanwarpreet SethiLantana Consulting GroupSarah Gauntsarah.gaunt@lantanagroup.comFixed in Trifolia
112PHERVolume 2A-TUpdate temporary codes with standard codes - a LOINC request has been submitted.Update temporary codes with standard codes - a LOINC request has been submitted.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill ensure that all temporary codes are replaced by standard codes before publication.Sarah Gaunt/Mead Walker1200Kanwarpreet SethiLantana Consulting GroupSarah Gauntsarah.gaunt@lantanagroup.com
113PHERVolume 2A-TRemove "Prenatal Care (V2)" template and replace with Pregnancy IG template: "Date of First Prenatal Care Visit". Move the contained Pregnancy IG template "Total Number of Prenatal Care Visits for this Pregnancy" to "Prenatal Testing and Surveillance Section (V2)"Remove "Prenatal Care (V2)" template and replace with Pregnancy IG template: "Date of First Prenatal Care Visit". Move the contained Pregnancy IG template "Total Number of Prenatal Care Visits for this Pregnancy" to "Prenatal Testing and Surveillance Section (V2)"Block vote 20190214PersuasiveWill update as suggested2019-02-14Sarah Gaunt/Dave deRoode704Kanwarpreet SethiLantana Consulting GroupSarah Gauntsarah.gaunt@lantanagroup.com
114PHERVolume 2A-SAdd clarifying text to the Risk Factors template saying that for the PSMLBI use case, only a subset of the possible values will be used (list specific values)Add clarifying text to the Risk Factors template saying that for the PSMLBI use case, only a subset of the possible values will be used (list specific values)Block vote 20190214PersuasiveWill update as suggested2019-02-14Sarah Gaunt/Dave deRoode704Kanwarpreet SethiLantana Consulting GroupSarah Gauntsarah.gaunt@lantanagroup.com
115PHERV1A-SInclude a brief Vocabulary section and note that value sets for the IG can be downloaded from PHIN VADS.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill add vocab section as suggestedSarah Gaunt/Mead Walker1200Mead Walker
116PHERV2 TOCA-QWhy are there no record target references for the coded cause of fetal death and coded race/ethnicity documents, yet these are present for the other document types?Block vote 20190221Considered - question answeredThere is a recordTarget - it is detailed in the implied template - there are no changes from the implied template, so there are no further constraints for recordTarget needed in this document-type.Sarah/Craig701Mead Walker
117PHERV2 P21A-Srecord target contains information about the infant"infant or fetus"DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Mead WalkerFixed in Trifolia
118PHERV2 1.1.1.1A-SNote: Birth: Date of birth (infant) + time of birth; Death: Date of delivery (fetus)Note: Live Birth Reporting: Date of birth (infant) + time of birth; Fetal Death Reporting: Date of delivery (fetus)The note is unclear. At first reading, it seemed the reference was to date of delivery being recorded as the date of fetal death.Block vote 20190221PersuasiveWill update as suggestedSarah/Craig701Mead Walker
119PHERV2 1.1.1.2A-Sauthor can be the provider organization, NCHS or the jurisdiction"jurisdiction vital records office"note that the author is a particular body within the jurisdiction.Block vote 20190221PersuasiveWill update as suggestedSarah/Craig701Mead Walker
120PHERV2 1.1.1.3A-QCustodian ID should be a NPIWhat if the custodian is NCHS or the vital records office? (Is custodian equated to sender here?)Block vote 20190221PersuasiveIt is not a requirement to have an NPI here - it's only a SHOULD. So it's ok if this is not present. Will change to a MAY rather than a SHOULD.Sarah/Craig701Mead Walker
121PHERV2 1.1.1.4A-QWhy no id or name for the information recipient?Block vote 20190221PersuasiveWill add more detail to the information recipient as suggested.Sarah/Craig701Mead Walker
122PHERV2 P31A-S(the newborn) - within the record target comment(the fetus)Note, this comment applies to all the examples in which fetal death information is contained.DispositionedWeds Q? - Affirmative/PersuasivePersuasiveWill update as suggestedSarah Gaunt/Mead Walker1200Mead Walker
123PHERV2 1.1.7NEGOther document types note that medical record number may be recorded for a record target. In this case - Jurisdiction Fetal Death Reporting - it is important to instead note a place to capture the fetal death report identifier. Consideration should be given to capturing this as a document identifier instead. (Is consistency with the V2 IG a key consideration?) Note, this comment also applies to th e jurisdiction live birth report (birth certificate ID there), and to the coded cause of death for fetal death reporting and to the coded race and ethnicity reporting for both birth and fetal death. (I did not enter separate comments for those 3 other document types.)SGYes, consistency with the V2 IG is a key considerationMead Walker
124PHERV2 1.1.10NEGOptional Father ParticipationIt seems wrong to include this as an optional participation when no father information appears in the facility worksheet.Block vote 20190221PersuasiveWill remove father participation.Sarah/Craig701Mead Walker
125PHERV2 1.1.10A-QIs Mother's participation needed? The only item I saw on the work sheet was mother's weight which would be in the mother's vital signs section (I think)Block vote 20190221Not persuasive with modMother's participation is required as it's implied (i.e. for vitals). Also, when researching this noticed that we need to update the Mother's Vital Signs Section with the following wording in the description: "Note that the subject of this section - the mother - is different from the overall subject of the clinical document - which is the infant/fetus." and add a subject to that section (for the mother).Sarah/Craig701Mead Walker
126PHERV2 1.1.12A-QAs asked above, are mother and father participation needed?Block vote 20190221Persuasive with modWill remove father participation.Sarah/Craig701Mead Walker
127PHERV2 p87A-QWhy is "father" highlighted? Note, I see this on other pages as well.Block vote 20190221PersuasiveFather shouldn't be there - will removeSarah/Craig701Mead Walker
128PHERV2 1.2.1.1A-QWhy is the fetal death certificate file number included in the Void Certificate document? The same question for the birth certificate file number.SGTo specify which (recordTarget) birth/death certificate is to be voidedMead Walker
129PHERV2 1.3.1.1A-TDeath Certificate ID, Death Certificate File NumberI think the reference should be to birth here?Block vote 20190214PersuasiveWill udpate as suggested2019-02-14Sarah Gaunt/Dave deRoode704Mead Walker
130PHERV2 2.4A-QI see sdtc: race code twice, first as 0..1, second as 0..*. Why is the first instance prefaced with "sdtc"?Block vote 20190214PersuasiveThis is wrong, it should be just raceCode, not sdtc:raceCode. Will update.2019-02-14Sarah Gaunt/Dave deRoode704Mead Walker
131PHERV2 2.5A-QThe section includes an observation for fetal death cause or condition. In the worksheet, this is followed by information on other conditions contributing to death. Does that information belong here? (note, I found the entry further down.)Block vote 20190214Considered - Question AnsweredOther Significant Cause/Condition of Fetal Death is contained in Fetal Death Cause or Condition, which is contained in the Fetal Delivery Section. Templates are only shown in the table if they are directly contained by that template. Thus, even though this template is contained in the section is does not show up in it's containment table.2019-02-14Sarah Gaunt/Dave deRoode704Mead Walker
132PHERV2 2.13A-QIs Social Security Number requested reported to NCHS by the jurisdiction? If not, this section seems unneeded in the Jurisdiction Live Reporting Document. Should this template be required in any document?Block vote 20190221PersuasiveNo, it's not reported to NCHS by the jurisdiction. Will remove from Jurisdiction Live Reporting Document. Checked other document types and need to remove from Provider Supplied Live Birth Reporting Document. Where it is kept, will loosen SHALL to MAY.Sarah/Craig701Mead Walker
133PHERV2 3.5NEGState and city should be bound to value sets as well as countryBlock vote 20190221PersuasiveWill update as suggestedSarah/Craig701Mead Walker
134PHERV2 3.5NEGCounty should be included within address.Block vote 20190221PersuasiveWill update as suggestedSarah/Craig701Mead Walker
135PHERV2 3.22A-Tother significant does not need to be highlighted.SGI don't understand this. Email commenter.Mead Walker
136PHERV2. 3.45A-QSince it is possible to indicate the subject of a template, why are there separate bridged race, tabulated ethnicity and education level templates for mother and father?Block vote 20190214Considered - Question AnsweredBecause there are different codes for mother and father (e.g. 8700-0 "Father's education" and 57712-2 "mother's education".). Also, as discussed in comment 141, there are issues around validation if the templates were collapsed and you had to pick from 2 codes.2019-02-14Sarah Gaunt/Dave deRoode704Mead Walker
137PHERAllA-CThe document is very long.Block vote 20190214Considered - No action requiredThere are a lot of templates and a lot of different use cases to deal with.2019-02-14Sarah Gaunt/Dave deRoode704Mead Walker
138PHER42375NEGThis associatedEntity MAY contain zero or one [0..1] id (CONF:4394-266929). Note: Mother's Medical Record No.I don't see the point of including this id without further constraint when there is already another generic id element defined. The issue I can forsee here is that an implementer might not include the ids in the same order as defined here, which could cause some ids to be misinterpreted. I would think that adding guidance to the entry template that recommends the inclusion of the mother's medical record number in the ids would be better than adding the additional element constraint that really doesn't have a technical meaning. This also applies to the father template.Remove id specific to mother and father medical record number.DispositionedWeds - Q? - Michael (have emailed him to see if he can do either q Weds)Not persuasiveThis is a common pattern used in CDA IGs - repeating a constraint to add a note or mapping for the implementer. In this case we are stating that we are interested in the Mother's Medical Record Number and the Mother's US Social Security number. It really doesn't matter in what order these ids end up in the xml as the root oid is what determines what type of id is contained in an id elementSarah Gaunt/John Stamm1200Michael Clifton
139PHER42376NEGIf address is inside city limits, set addr/additionalLocator to "inside city limits". If address is outside city limits, set addr/additionalLocator to "outside city limits". If it is unknown whether or not the address is inside or outside city limits, set addr/additionalLocator/@nullFlavor to "UNK". vii. SHALL contain exactly one [1..1] additionalLocator (CONF:4394-266248). Note: Inside city limits? 1. This additionalLocator MAY contain zero or one [0..1] @nullFlavor="UNK" unknown (CodeSystem: HL7NullFlavor urn:oid:2.16.840.1.113883.5.1008) (CONF:4394-266262)Remove the nullFlavor constraint itself, but leave the guidance.The inclusion of the specific nullFlavor declaration is unnessary. The inclusion of the guidance is good, but there isn't a reason to define this as part of the template.Remove specific nullFlavor declaration in mother template.DispositionedWeds - Q? - Michael (have emailed him to see if he can do either q Weds)Not persuasiveThis is a common pattern used in CDA Igs. This disallows all nullFlavors other than UNK.Sarah Gaunt/John Stamm1200Michael Clifton
140PHER42376NEGIf address is inside city limits, set addr/additionalLocator to "inside city limits". If address is outside city limits, set addr/additionalLocator to "outside city limits". If it is unknown whether or not the address is inside or outside city limits, set addr/additionalLocator/@nullFlavor to "UNK". vii. SHALL contain exactly one [1..1] additionalLocator (CONF:4394-266248). Note: Inside city limits? 1. This additionalLocator MAY contain zero or one [0..1] @nullFlavor="UNK" unknown (CodeSystem: HL7NullFlavor urn:oid:2.16.840.1.113883.5.1008) (CONF:4394-266262)Remove this.This data really isn't necessary in the document itself as this can easily be calculated by the recipient instead of the sender. I would expect that the majority of the documents sent would just end up using the nullFlavor here, so this is probably better off being removed and moving the calculation to the recipient.Remove additionalLocator element from mother template.Block vote 20190214Not persuasiveThis data is required by the certificates. This aligns with the data captured in the CDA IG and also is the same as the modelling in the CDA Vital Records Death Reporting IG.2019-02-14Sarah Gaunt/Dave deRoode704Michael Clifton
141PHERNEGRepeated Mother/Father TemplatesCombine into single "parent" templates with value sets for mother/father specific data.Most of the sections that are labeled as "Mother…." and "Father…." are really just the same template with a code difference. It would seem more reasonable to me to define a more generic parent template that contains valuesets for mother and father specific codes so as to reduce the length and repetition of the document.Combine mother/father templates into "parent" templates.Block vote 20190214Not persuasiveMost of these are templates that are required in sections. If they were collapsed down to one template for both mother and father, then Schematron would not be automatically generated to ensure than each template is present in the section. You could use regular constraints to say that there SHALL be 2..2 of the templates, but then you would require confusing primitive statements (confusing for implementers) to say that you must have one of each type (code) and custom Schematron (error-prone) to validate that one of each was present. The same argument holds even for the ones that are optional - and in their own section. You always have to write custom Schematron and add primitive constraints to say that you actually only want, say, the mother, in this case.2019-02-14Sarah Gaunt/Dave deRoode704Michael Clifton
142PHER23A-QUnder "Coded Race Ethnicity Reporting" it says "This enables the construction of consistent time series information. "I don't understand how consistent time is even part of the race and ethnicity coding.For clarity, if it is important to people who will use this, perhaps explain more about consistent time in relation to race and ethnicity.Block vote 20190307Hetty - please assign to correct SME This comment is about the description for "Coded Race/Ethnicity Reporting" "The use case addresses the need to provide a single race code and a single ethnicity code for mother and father to the Jurisdictional Vital Records Office in those cases in which multiples of each were supplied. This enables the construction of consistent time series information. The data requirements for coded race & ethnicity information are based on the Office of Management and Budget - Revisions to the standards for the classification of federal data on race and ethnicity." The wording above was taken from the V2 spec (3.7 Coded Race & Ethnicity Reporting).PersuasiveWill add the following clarification: "The goal is to maintain consistency between data collected after the definitional change (allowing collection of multiple races and ethnicities) and that collected prior to that time. This intent is to maintain the integrity of time series (data collected from a range of time periods) reporting."Ruth BergeGE Healthcare
143PHER11.1.10, 1.1.14, 1.1.18NEGWhat is the difference between "Provider Supplied Facility Fetal Death Report", "Provider Suplied Fetal Death Report", and "Provider Supplied Mother's Fetal Death Report", and how are they different from the US standard report of fetal death? According to the text, the first two are based on the Facility Worksheet for the Report of Fetal Death, and the third on the Patient's Worksheet for the Report of Fetal Death. Does information from all three get combined to create the final US standard report? All three individual concepts have been assigned LOINC code="69045-3" displayName="US standard report of fetal death". If the three are truly different from each other as well as from the final US standard report of fetal death, they should use different LOINC codes, and the text should describe what they are more clearly.Block vote 20190221PersuasiveThe use cases are discussed in more detail in Volume 1. Mother's + Facility = Provider Supplied Will request new LOINC codes for the Mother's and Facility. Will update descriptions.Sarah/Craig701Sara Armson
144PHER11.1.12, 1.1.16, 1.1.20NEGWhat is the difference between "Provider Supplied Facility Live Birth Report", "Provider Suplied Live Birth Report", and "Provider Supplied Mother's Live Birth Report", and how are they different from the US standard certificate of live birth? According to the text, the first two are based on the US Standard Facility Worksheet for the Live Birth Certificate, and the third on the Mother's Worksheet for Child's Birth Certificate. Does information from all three get combined to create the final US standard birth certificate? All three individual concepts have been assigned LOINC code="68998-4" displayName="US standard certificate of live birth". If the three are truly different from each other as well as from the final US standard report of live birth, they should use different LOINC codes, and the text should describe what they are more clearly.Block vote 20190221PersuasiveThe use cases are discussed in more detail in Volume 1. Mother's + Facility = Provider Supplied Will request new LOINC codes for the Mother's and Facility. Will update descriptions.Sarah/Craig701Sara Armson
145PHER11.1.1059NEGProvider Supplied Facility Fetal Death ReportFacility Fetal Death ReportWhy is this "Provider Supplied Facility Fetal Death Report"? If it's based on the Facility Worksheet for the Report of Fetal Death, then shouldn't it just be the Facility Fetal Death Report?Block vote 20190214Not persuasiveThe names of the use cases /document-level templates are aligned with the names use in the V2 IG specification. These names have been standardized based on discussions in the Public Health work group.”2019-02-14Sarah Gaunt/Dave deRoode704Sara Armson
146PHER11.1.1066Figure 5A-TProvider Supplied Mother's Fetal Death ReportProvider Supplied Facility Fetal Death Report, or Facility Fetal Death Report (see comment above)This section is about the Provider Supplied Facility Fetal Death Report, not Mother's. The Provider Supplied Moter's Fetal Death Report is described in 1.1.18Block vote 20190214PersuasiveWill update as suggested2019-02-14Sarah Gaunt/Dave deRoode704Sara Armson
147PHER11.1.1269NEGProvider Supplied Facility Live Birth Reporting DocumentFacility Live Birth Reporting Document Why is this "Provider Supplied Facility Live Birth Reporting Document"? If there is a separate one for the Provider, then shouldn't this one just be the Facility Live Birth Reporting Document?Block vote 20190214Not persuasiveThe names of the use cases /document-level templates are aligned with the names use in the V2 IG specification. These names have been standardized based on discussions in the Public Health work group.”2019-02-14Sarah Gaunt/Dave deRoode704Sara Armson
148PHER11.1.1276Figure 6A-TProvider Supplied Live Birth Reporting DocumentProvider Supplied Facility Live Birth Reporting Document, or Facility Live Birth Reporting Document (see comment above)This section is about the Provider Supplied Facility Live Birth Report, not Provider Supplied Live Birth Reporting Document. The Provider Supplied Live Birth Reporting Document is described in 1.1.16Block vote 20190214PersuasiveWill update as suggested2019-02-14Sarah Gaunt/Dave deRoode704Sara Armson
149PHER11.1.18101NEGProvider Supplied Mother's Fetal Death Reporting DocumentParent's Fetal Death Reporting Document??If the information in this section is based on the Patient's Worksheet for the Report of Fetal Death, why is it called "Provider Supplied Mother's Fetal Death Report"? I don't understand "Provider Supplied", and if the Patient's Worksheet be filled out by the mother and/or father, then it shouldn't say "Mother's" either.Block vote 20190214Not persuasiveThe names of the use cases /document-level templates are aligned with the names use in the V2 IG specification. These names have been standardized based on discussions in the Public Health work group.”2019-02-14Sarah Gaunt/Dave deRoode704Sara Armson
150PHER22.4142A-STEMP_LOINC_FATHER_INFO80901-2LOINC 80901-2 Paternal information Narrative can be used for this sectionDispositionedWeds Q? - Affirmative/PersuasivePersuasiveDuplicate 150/162 Will update as suggestedSarah Gaunt/Mead Walker1200Sara Armson
151PHER22.10161A-STEMP_LOINC_MOTHER_INFO79192-1LOINC 79192-1 Maternal information section Narrative can be used for this sectionDispositionedWeds Q? - Affirmative/PersuasivePersuasiveDuplicate 151/163 Will update as suggestedSarah Gaunt/Mead Walker1200Sara Armson
152PHER22.13172A-STEMP_LOINC_NEWBORN_INFOWhy is a whole new section needed to carry one observation about whether an SSN has been requested (LOINC 87295-2 Social Security Number was requested)?Block vote 20190221Considered - question answeredBecause there is not another section that is suitable for this information. Would rather create a section with only one entry than try to fit the data somewhere it doesn't belong. Also the data it includes only belongs in one report (see comment 132), and rather than burden implmenters with a lot of if/then statements about when it should/shouldn't be present and writing custom Schematron, it works better to have it in this section.)Sarah/Craig701Sara Armson
153PHER3Edit flag sectionsFigures within the sectionA-TAll of the Edit Flag Figures give the LOINC OID and LOINC as the code system and code system name, respectively, for the various Edit Flag codes, but these are not LOINC codes. They all need to be updated to PHIN VSDispositionedWeds Q? - Affirmative/PersuasivePersuasiveDuplicate 153/165 Will update as suggstedSarah Gaunt/Mead Walker1200Sara Armson
154PHER3Edit flag sectionsEdit flag value setsA-QThis may not be relevant for this ballot, but I don't understand some of the Edit flags value set values. For example, for the Birth Weight Edit Flag value set (page 202, https://phinvads.cdc.gov/vads/ViewValueSet.action?oid=2.16.840.1.114222.4.11.7576), the possible values are "Off", "Queried data correct, out of range", and "Queried, failed birthweight/gestation edit". Why aren't there any values that indicate that the data passed the validation check, such as "Passed", "Queried data correct", or "Queried, birthweight edited"? Several of the Edit Flag value sets have this same issue.Block vote 20190221Considered - question answeredThese are the values for the edit flags contained in the Edit Specifications for birth and fetal death reporting. The edit flags are used for quality assurance by NCHS.Sarah/Craig701Sara Armson
155PHER11.1.10, 1.1.14, 1.1.18NEGWhat is the difference between "Provider Supplied Facility Fetal Death Report", "Provider Suplied Fetal Death Report", and "Provider Supplied Mother's Fetal Death Report", and how are they different from the US standard report of fetal death? According to the text, the first two are based on the Facility Worksheet for the Report of Fetal Death, and the third on the Patient's Worksheet for the Report of Fetal Death. Does information from all three get combined to create the final US standard report? All three individual concepts have been assigned LOINC code="69045-3" displayName="US standard report of fetal death". If the three are truly different from each other as well as from the final US standard report of fetal death, they should use different LOINC codes, and the text should describe what they are more clearly.Block vote 20190221PersuasiveThe use cases are discussed in more detail in Volume 1. Mother's + Facility = Provider Supplied Will request new LOINC codes for the Mother's and Facility. Will update descriptions.Sarah/Craig701Swapna Abhyankar
156PHER11.1.12, 1.1.16, 1.1.20NEGWhat is the difference between "Provider Supplied Facility Live Birth Report", "Provider Suplied Live Birth Report", and "Provider Supplied Mother's Live Birth Report", and how are they different from the US standard certificate of live birth? According to the text, the first two are based on the US Standard Facility Worksheet for the Live Birth Certificate, and the third on the Mother's Worksheet for Child's Birth Certificate. Does information from all three get combined to create the final US standard birth certificate? All three individual concepts have been assigned LOINC code="68998-4" displayName="US standard certificate of live birth". If the three are truly different from each other as well as from the final US standard report of live birth, they should use different LOINC codes, and the text should describe what they are more clearly.Dispositioned in block - add to next block (duplicate)This is a good point - discuss and maybe request other LOINC codes.Duplicate: 144/156Swapna Abhyankar
157PHER11.1.1059NEGProvider Supplied Facility Fetal Death ReportFacility Fetal Death ReportWhy is this "Provider Supplied Facility Fetal Death Report"? If it's based on the Facility Worksheet for the Report of Fetal Death, then shouldn't it just be the Facility Fetal Death Report?Block vote 20190214Not persuasiveThe names of the use cases /document-level templates are aligned with the names use in the V2 IG specification. These names have been standardized based on discussions in the Public Health work group.”2019-02-14Sarah Gaunt/Dave deRoode704Swapna Abhyankar
158PHER11.1.1066Figure 5A-TProvider Supplied Mother's Fetal Death ReportProvider Supplied Facility Fetal Death Report, or Facility Fetal Death Report (see comment above)This section is about the Provider Supplied Facility Fetal Death Report, not Mother's. The Provider Supplied Moter's Fetal Death Report is described in 1.1.18Block vote 20190214PersuasiveWill update as suggested2019-02-14Sarah Gaunt/Dave deRoode704Swapna Abhyankar
159PHER11.1.1269NEGProvider Supplied Facility Live Birth Reporting DocumentFacility Live Birth Reporting Document Why is this "Provider Supplied Facility Live Birth Reporting Document"? If there is a separate one for the Provider, then shouldn't this one just be the Facility Live Birth Reporting Document?Block vote 20190214Not persuasiveThe names of the use cases /document-level templates are aligned with the names use in the V2 IG specification. These names have been standardized based on discussions in the Public Health work group.”2019-02-14Sarah Gaunt/Dave deRoode704Swapna Abhyankar
160PHER11.1.1276Figure 6A-TProvider Supplied Live Birth Reporting DocumentProvider Supplied Facility Live Birth Reporting Document, or Facility Live Birth Reporting Document (see comment above)This section is about the Provider Supplied Facility Live Birth Report, not Provider Supplied Live Birth Reporting Document. The Provider Supplied Live Birth Reporting Document is described in 1.1.16Block vote 20190214PersuasiveWill update as suggested2019-02-14Sarah Gaunt/Dave deRoode704Swapna Abhyankar
161PHER11.1.18101NEGProvider Supplied Mother's Fetal Death Reporting DocumentParent's Fetal Death Reporting Document??If the information in this section is based on the Patient's Worksheet for the Report of Fetal Death, why is it called "Provider Supplied Mother's Fetal Death Report"? I don't understand "Provider Supplied", and if the Patient's Worksheet be filled out by the mother and/or father, then it shouldn't say "Mother's" either.Block vote 20190214Not persuasiveThe names of the use cases /document-level templates are aligned with the names use in the V2 IG specification. These names have been standardized based on discussions in the Public Health work group.”2019-02-14Sarah Gaunt/Dave deRoode704Swapna Abhyankar
162PHER22.4142A-STEMP_LOINC_FATHER_INFO80901-2LOINC 80901-2 Paternal information Narrative can be used for this sectionDispositionedWeds Q? - Affirmative/PersuasivePersuasiveDuplicate 150/162 Will update as suggestedSarah Gaunt/Mead Walker1200Swapna Abhyankar
163PHER22.10161A-STEMP_LOINC_MOTHER_INFO79192-1LOINC 79192-1 Maternal information section Narrative can be used for this sectionDispositionedWeds Q? - Affirmative/PersuasivePersuasiveDuplicate 151/163 Will update as suggestedSarah Gaunt/Mead Walker1200Swapna Abhyankar
164PHER22.13172A-STEMP_LOINC_NEWBORN_INFOWhy is a whole new section needed to carry one observation about whether an SSN has been requested (LOINC 87295-2 Social Security Number was requested)?Block vote 20190221Considered - question answeredBecause there is not another section that is suitable for this information. Would rather create a section with only one entry than try to fit the data somewhere it doesn't belong. Also the data it includes only belongs in one report (see comment 132), and rather than burden implmenters with a lot of if/then statements about when it should/shouldn't be present and writing custom Schematron, it works better to have it in this section.)Sarah/Craig701Swapna Abhyankar
165PHER3Edit flag sectionsFigures within the sectionA-TAll of the Edit Flag Figures give the LOINC OID and LOINC as the code system and code system name, respectively, for the various Edit Flag codes, but these are not LOINC codes. They all need to be updated to PHIN VSDispositionedWeds Q? - Affirmative/PersuasivePersuasiveDuplicate 153/165 Will update as suggstedSarah Gaunt/Mead Walker1200Swapna Abhyankar
166PHER3Edit flag sectionsEdit flag value setsA-QThis may not be relevant for this ballot, but I don't understand some of the Edit flags value set values. For example, for the Birth Weight Edit Flag value set (page 202, https://phinvads.cdc.gov/vads/ViewValueSet.action?oid=2.16.840.1.114222.4.11.7576), the possible values are "Off", "Queried data correct, out of range", and "Queried, failed birthweight/gestation edit". Why aren't there any values that indicate that the data passed the validation check, such as "Passed", "Queried data correct", or "Queried, birthweight edited"? Several of the Edit Flag value sets have this same issue.Block vote 20190221Considered - question answeredThese are the values for the edit flags contained in the Edit Specifications for birth and fetal death reporting. The edit flags are used for quality assurance by NCHS.Sarah/Craig701Swapna Abhyankar
167PHERA-SThis is a general comment that applies to all reporting from healthcare providers to public health entities. Reporting should always be bidirectional. Public health entities have information, acquired through reporting or from manipulation of reported data, that would be useful for a healthcare provider to know. In the specific case of reporting births and deaths, there are likely to be providers other than the reporting provider whou would benefit from knowing about these events. This standard should provide the capability for the reporter to identify other known providers who are engaged with caring for the patient(s), and who should receive a copy of the report from the public health agency. There may be other use cases for dissemination of these reports that should be supported by the standard.Block vote 20190221Considered - No action requiredPractices will vary by jurisdicaiton. Reporting of birth and fetal death is a legal event and subject to jurisdicational law. Sarah/Craig701Thomson KuhnACP
168PHERA-SThis is a general comment that applies to all reporting from healthcare providers to public health entities. Structured and coded data may not always capture all relevant information related to a healthcare event. Clinicians spend significant amounts of time crafting narrative notes that capture nuance that is not available in the structured data. Currently, public health entities may not have a way to extract this additional information from notes, but it is likely that they will have that capability in the near future. Relevant notes should be included in public health reporting now, so that public health entities can become accustomed to receiving, procesing, and examining them.Block vote 20190221Considered - question answeredThese are the values for the edit flags contained in the Edit Specifications for birth and fetal death reporting. The edit flags are used for quality assurance by NCHS.Sarah/Craig701Thomson KuhnACP