|Submitted By: Craig Newman / Altarum
|Data Element Information
|Use Case Description(s)
|Use Case Description
|An expectant mother’s pregnancy attributes are crucial for providing the best possible pre-natal care. As well, after delivery, Public Health needs to capture this data as part of birth certification, fetal death reporting and birth defect reporting. In particular, birth certification forms the basis of the patient census required by a large number of other Public Health programs including newborn screening, birth defect reporting and immunization registries making it critical that birth certification is as automated, timely and accurate as possible.
|Estimate the breadth of applicability of the use case(s) for this data element
|Consumption of this data is widespread. Every jurisdiction in the country captures birth certification information and immunization adminstration. Most also capture birth defects and fetal deaths. Healthcare systems which provide care for expectant mothers should be collecting this data.
|Maturity of Use and Technical Specifications for Data Element
|LOINC codes exist for each of the proposed data elements:
8665-2 - Last menstrual period start date
11778-8 - Delivery date Estimated
56077-1 - Body weight --pre current pregnancy
|Vital Records Common Profiles Library FHIR IG - http://build.fhir.org/ig/HL7/fhir-vr-common-ig/branches/master/index.html
Birth Defect Reporting FHIR IG - https://build.fhir.org/ig/HL7/fhir-birthdefectsreporting-ig/index.html
Vital Records Birth and Fetal Death Reporting - https://build.fhir.org/ig/HL7/fhir-bfdr/index.html
|This data element has been used at scale between multiple different production environments to support the majority of anticipated stakeholders
This data is exchanged routinely as part of birth certification, fetal death reporting and birth defect reporting, however these workflow typically are executed on paper or via flat files rather than through electronic interoperability.
|Extent of exchange
|Restrictions on Standardization (e.g. proprietary code)
|Restrictions on Use (e.g. licensing, user fees)
|Privacy and Security Concerns
|No concerns over and above the typically privacy and security considerations associated with any health related data.
|Estimate of Overall Burden
|These data elements are straightforward in nature and should not present a large burden to implement provided the EHR system is capturing the data as part of caring for the woman.
Estimated Date of Delivery
The expected date of delivery (i.e. the due date).