|Submitted By: Nedra Garrett / Centers for Disease Control and Prevention|
|Data Element Information|
|Use Case Description(s)|
|Use Case Description||"Monitoring disease and making decisions about public health threats depends on accessible and accurate data. EHRs are a data source with potential to provide timely and relevant data beyond its use by health care providers. EHR data, if made more available for public health professionals and researchers, can lead to new innovations and can help rapid reporting for birth information reporting.
The details of a delivery found within clinical notes for a newborn are crucial for providing the best possible post-natal care to the mother and infant. As well, after delivery, public health needs to capture this data as part of birth certification and fetal death 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."
|Estimated number of stakeholders capturing, accessing using or exchanging||Every year there are approximately 3.7 million births in the United States. Consumption of this data is widespread. Every jurisdiction in the country captures birth certification information and immunization administration. Most also capture birth defects and fetal deaths. Healthcare systems which provide care for expectant mothers should be collecting this data.
|Link to use case project page||https://www.cdc.gov/nchs/nvss/births.htm|
|Maturity of Use and Technical Specifications for Data Element|
|Applicable Standard(s)||"LOINC codes exist for each of the proposed data elements
The clinical notes of an new born should capture information such as:
73756-9 | Infant is being breastfed at discharge"
|Additional Specifications||"Vital Records Common Profiles Library FHIR IG - http://build.fhir.org/ig/HL7/fhir-vr-common-ig/branches/master/index.html
Vital Records Birth and Fetal Death Reporting - https://build.fhir.org/ig/HL7/fhir-bfdr/index.html
HL7 Version 2.6 Implementation Guide: Vital Records Birth and Fetal Death Reporting, Release 1 STU Release 2 - US Realm https://www.hl7.org/implement/standards/product_brief.cfm?product_id=320
HL7 CDA® R2 Implementation Guide: Birth and Fetal Death Reporting, Release 1, STU Release 2 - US Realm -https://www.hl7.org/implement/standards/product_brief.cfm?product_id=387
IHE Quality, Research and Public Health Technical Framework Supplement – Birth and Fetal Death Reporting-Enhanced (BFDR-E) Revision 3.1 - https://www.ihe.net/uploadedFiles/Documents/QRPH/IHE_QRPH_Suppl_BFDR-E.pdf"
|Current Use||In limited use in production environments|
"Level 2 – at scale, or in more widespread production use (routinely collected already) on several different EHR/HIT systems.
EPIC FHIR APIs for patient, vitals, obstetric details (DSTU2, DSTU3, R4)
In production use:
EPIC stork module (obstetrics) for birth reporting
ONC Interoperability Standards Advisory - Sending Birth and Fetal Death Information to Public Health Agencies"
"Facility worksheet information:
EPIC stork module (obstetrics) for birth reporting: https://www.epic.com/software#PatientEngagement
EPIC FHIR APIs for patient, vitals, obstetric details:
BFDR-E in ISA:
|Number of organizations/individuals with which this data element has been electronically exchanged||4|
"Level 1 – exchanged between 2 or 3 different EHR/HIT systems
This data is exchanged routinely as part of birth certification, fetal death reporting and birth defect reporting, however these workflows typically are executed on paper or via flat files rather than through electronic interoperability.
IHE Connectathon integration profiles for BFDR-E (2013 - 2020)
HL7 FHIR Connectathon results (Sept 2020): birth and fetal death reporting results testing between electronic birth registration system vendors (FHIR)
NACCHO 360X Interoperability Demonstrations for Birth and Fetal Death reporting 2020 between NextGen and two state electronic birth registrations system vendors using FHIR.
HIMSS Interoperability showcase (2018 – 2019)"
"IHE Connectathon: Found in 'New Search', filter by 'Select an integration profile = Birth and Fetal Death Reporting-Enhanced' https://connectathon-results.ihe.net/view_result.php?rows=company&columns=actor&title=integration_profile
FHIR Connectathon: https://confluence.hl7.org/display/FHIR/2020-09+Public+Health+Track
BFDR-E in ISA:
|Restrictions on Standardization (e.g. proprietary code)||None
|Restrictions on Use (e.g. licensing, user fees)||None
|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.
|Other Implementation Challenges||When using FHIR there may be associated costs with development of tools needed to access specific data. Often these costs may be a limitation for states who need to develop tools to access certain data.
|ONC Evaluation Details
Each submitted Data Element has been evaluated based on the following 4 criteria. The overall Level classification is a composite of the maturity based on these individual criteria. This information can be used to identify areas that require additional work to raise the overall classification level and consideration for inclusion in future versions of USCDI
|Maturity – Standards/Technical Specifications||Level 1/2 - Must be represented by a vocabulary standard or an element of a published technical specification|
|Maturity - Current Use||Comment Level - Used in limited test environments or pilots|
|Maturity - Current Exchange||Level 1 - Demonstrates exchange between 2 or 3 organizations with different EHR/HIT systems|
|Breadth of Applicability - # Stakeholders Impacted||Level 2 - Used by a majority of patients, providers or events requiring its use|