Narrative patient data relevant to the context identified by note types.

  •  
  • Usage note: Clinical Notes data elements are content exchange standard agnostic. They should not be interpreted or associated with the structured document templates that may share the same name. 

Data Element
Clinical Notes for Newborn
Submitted By: Adam Bazer, MPD / Integrating the Healthcare Enterprise USA (IHE USA)
Data Element Information
Data Element Description Clinical notes information for a newborn may include the Labor and delivery summary
record under–Infant data, and maternal progress note. Example information will include breastfeeding information at time of discharge.
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.
Estimate the breadth of applicability of the use case(s) for this data element 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
Healthcare Aims
  • Improving patient experience of care (quality and/or satisfaction)
  • Improving the health of populations
  • Improving provider experience of care
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

https://loinc.org/?s=73756-9
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 test environments only
Supporting Artifacts "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"


https://www.healthit.gov/isa/reporting-birth-and-fetal-death-public-health-agencies
https://www.epic.com/software#PatientEngagement
https://www.cdc.gov/nchs/data/dvs/facility-worksheet-2016-508.pdf
Extent of exchange 4
Supporting Artifacts 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)

https://www.healthit.gov/isa/reporting-birth-and-fetal-death-public-health-agencies
https://www.epic.com/software#PatientEngagement
https://www.cdc.gov/nchs/data/dvs/facility-worksheet-2016-508.pdf
Potential Challenges
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.


Comment

Submitted by CDC_DSMH_WG on

CDC's comment on behalf of NACCHO for USCDI v5

Hospital systems are not collecting this consistently or reporting it using standard terminology. This should first become a requirement of the EHR Certification standard (if not already), then work must be done with health systems to have this information be collected in a standard format before including it in USCDI.Hospital systems are not collecting this consistently or reporting it using standard terminology. This should first become a requirement of the EHR Certification standard (if not already), then work must be done with health systems to have this information be collected in a standard format before including it in USCDI.Hospital systems are not collecting this consistently or reporting it using standard terminology. This should first become a requirement of the EHR Certification standard (if not already), then work must be done with health systems to have this information be collected in a standard format before including it in USCDI.

Log in or register to post comments

FormGuide

Help

1. Optional: Background Text / Cover Letter

The "Optional Background Text / Cover Letter" field provides space for additional context or introductory information related to your comment.

If you wish to provide context, explanation, or an introduction to your comment, enter this information in the field labeled "Optional Background Text / Cover Letter." This is entirely optional and is most useful when submitting multiple related comments or when additional background would help reviewers understand your feedback.

If you are only commenting on a single data class or element, you may leave this field blank.

2. Select the Data Class

To specify which data class your comment addresses:

  1. In the "Data Class" drop-down menu, select the appropriate data class you want to comment on.
  2. If you are providing a general comment that is not specific to a data element, select "General" from the options. Comments with this designation will be displayed on the USCDI landing page.
  3. Note that the Data Class field will automatically populate based on your current location in the platform:
    1. If you are on a data class page, the field will be set to that specific data class
    2. If you are on a data element page, the corresponding data class will be pre-selected
       

3. Select the Data Element

To specify which data element your comment addresses:

  1. In the "Data Element" drop-down menu, select the specific data element you want to comment on.
  2. The drop-down menu will display only the elements available under the data class you selected in the previous step.
  3. You can use the search function within the drop-down to quickly locate a specific data element.
  4. If you are commenting on the data class itself rather than a specific element, you may leave this field blank.

Note: Comments on a specific data element will appear on the respective data element page, while comments on a data class (without a specific element selected) will appear on the landing page for that data class.
 

Data Class and Data Element

Fig 1 The "Data Class" and "Data Element" dropdown menus allow users to specify the exact content they wish to comment on.

4. Optional: Propose New Data Class or Element

If you cannot find the appropriate data class or element for your comment:

  1. Instead of clicking the "Comment On An Existing Data Class Or Element" button, click the adjacent button labeled "Propose a New Data Class or Data Element."
  2. This will redirect you to the ONDEC (ONC New Data Element and Class) Submission System.
  3. In the ONDEC system, follow the provided instructions to submit your proposal for a new data class or element.
  4. Once your proposal is submitted through ONDEC, it will be reviewed separately from the commenting process.
Propose New Data Class or Element

Fig 2 The "Propose a New Data Class or Data Element" button redirects users to the ONDEC Submission System for proposing new data elements not currently available in the system.

5. Complete the Comment Form

Fill out the required fields in the comment form:

Subject: Enter a brief, descriptive title that summarizes your comment. This helps reviewers quickly understand the nature of your feedback.

Comment: In this field, provide the full details of your comment or feedback. Be as clear and specific as possible about your suggestions, concerns, or observations. Include any relevant details that support your position.

6. Optional: Add Additional Comments

If you need to comment on multiple data classes or elements:

  1. After completing your first comment, click the link labeled "Comment on another data element" at the bottom of the form.
  2. A new comment section will appear, allowing you to enter details for your additional comment.
  3. For each additional comment, you must select the appropriate data class and data element from the drop-down menus.
  4. Complete the Subject and Comment fields for your additional comment.
  5. Repeat this process for each additional comment you wish to submit.

Fig 3 The "Comment on another data element" link enables users to create multiple comments addressing different elements within a single submission.

7. Optional: Upload Supporting Files

The platform allows you to upload supporting documentation to enhance your comment:

  • Locate the "File Upload" section at the bottom of the comment form.
  • Click to upload any files (such as PDFs or documents) that provide additional context, evidence, or clarification for your comment.

Important: If you have already entered your comments using the form fields, there is no need to upload duplicate content in PDF format. The file upload feature is intended for supplementary materials only. Please avoid uploading files that contain the same information already provided in your comment text.

Upload Supporting Files

Fig 4 The "File Upload" section permits users to attach supporting documentation that supplements their written comments.

8. Optional: Save and Exit

If you need to pause your work and return to complete your comment later:

  1. Click the "Save and Exit" button at the bottom of the form.
  2. Your comment will be saved as a draft that you can access and complete later.
  3. When you return to the platform, you will see a red triangle with an exclamation mark next to the “Return to saved Comment” button, indicating that you have saved comments in draft status.
  4. Click this button to continue working on your draft.
  5. You will be taken to a review page where you can:
    1. Select "Submit Comment" to officially submit your feedback.
    2. Click "Edit" to return to the comment form and make changes
    3. Select "Discard Draft" to delete the saved draft and start fresh

Fig 5 A red triangle with exclamation mark indicator appears next to the “Return to saved Comment” button when draft comments are saved in the system.

9. Review and Submit

Once you have completed your comment:

  1. Click the "Review and Submit" button at the bottom of the form.
  2. This will take you to a review screen displaying your comment(s) in full.
  3. Review all information for accuracy and completeness.
  4. On this review screen, you have three options: 
    1. Click "Submit Comment" to officially submit your feedback
    2. Click "Edit" to return to the comment form and make changes
    3. Click "Discard Draft" to delete the comment and start fresh
  5. The review screen also includes a "Print" button that allows you to create a printed copy of your comments for your records. 
  6. If you choose to submit, your comment will be recorded in the system and made available for review by the appropriate stakeholders.
Review and Submit

Fig 6 The review screen allows users to verify comment content and make any necessary modifications before final submission.

USCDI Comments

Close

Add a New Comment

Review comment and Submit

Edit
Comment #1
PDF, Doc, Docx
Max Size : 10 MB