Data Element
Gestational Age
Description

"The estimated gestational age (in weeks, or weeks and fraction of week) of the pregnancy at the time of the health care encounter (in contrast to the gestational age at birth), beginning from the time of fertilization. Needs to be correlated with the date the gestational age was documented. Gestational age (written with both weeks and days) is calculated using the best obstetrical estimated delivery date (EDD) based on the following formula: Gestational Age = (280 - (EDD - Reference Date))/ 7"
Submitted By: Nedra Garrett / Centers for Disease Control and Prevention
Data Element Information
Data Element Description "The estimated gestational age (in weeks, or weeks and fraction of week) of the pregnancy at the time of the health care encounter (in contrast to the gestational age at birth), beginning from the time of fertilization. Needs to be correlated with the date the gestational age was documented.
Gestational age (written with both weeks and days) is calculated using the best obstetrical estimated delivery date (EDD) based on the following formula: Gestational Age = (280 - (EDD - Reference Date))/ 7"
Use Case Description(s)
Use Case Description The data elements above are based on commonly used terms across the industry. Many of these data elements are captured in maternity EHRs, are defined and endorsed by the American College of Obstetricians and Gynecologists (ACOG)2, and are represented in LOINC with Class=”OB.US/clinical”.
Estimate the breadth of applicability of the use case(s) for this data element There are a large number of stakeholders, e.g., federal researchers and scientists, federal, state and local public health professionals, university-based researchers, clincians, health system administrators, private and public providers of health insurance, public and private-sector developers of new therapies and technologies.
Link to use case project page https://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1398
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) https://www.hl7.org/implement/standards/product_brief.cfm?product_id=494

https://www.hl7.org/implement/standards/product_brief.cfm?product_id=494
Additional Specifications https://www.hl7.org/implement/standards/product_brief.cfm?product_id=494
Current Use Extensively used in production environments
Supporting Artifacts https://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1399
CDAR2_IG_PREGNANCY_R1_DSTU_2019JAN.pdf
Extent of exchange N/A
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) We are not aware of restrictions.
Restrictions on Use (e.g. licensing, user fees) We are not aware of restrictions.
Privacy and Security Concerns Pregnancy-related data, particularly pregnancy outcome, is sensitive and private information. It will be important to safeguard identifying information of individuals using current HIPAA standards.
Estimate of Overall Burden N/A
Other Implementation Challenges N/A
ASTP Evaluation Details
Each submitted Data Element has been evaluated based on the following 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
Criterion #1
Maturity - Current Standards		 Level 2 - Data element is represented by a terminology standard or SDO-balloted technical specification or implementation guide.
Criterion #2
Maturity - Current Use 		Level 2 - Data element is captured, stored, or accessed in multiple production EHRs or other HIT modules from more than one developer.
Criterion #3
Maturity - Current Exchange		 Level 0 - Data element is electronically exchanged in limited environments, such as connectathons or pilots.
Criterion #4
Use Case(s) - Breadth of Applicability		 Level 0 - Use cases apply to a limited number of care settings or specialties, or data element represents a specialization of other, more general data elements.
Evaluation Comment This data element is a specialized use of the Level 2 Observation data elements in the Observations data class.

Comment

Submitted by minigrrl on

What is the justification…

What is the justification for the demotion of the following Case Reporting data elements in USCDI, specifically:

• Exposure/Contact Information: Exposure/Contact Agent
• Exposure/Contact Information: Exposure/Contact Date
• Exposure/Contact Information: Exposure/Contact Direction
• Exposure/Contact Information: Exposure/Contact Source/Target Participant
• Exposure/Contact Information: Exposure/Contact Type
• Health Insurance Information: Medicare Patient Identifier
• Immunizations: Vaccination Administration Date
• Laboratory: Specimen Collection Date/Time
• Patient Demographics/Information: Patient Birth Place
• Patient Demographics/Information: Tribal Enrollment
• Pregnancy Information: Estimated Date of Delivery
• Pregnancy Information: Gestational Age
• Pregnancy Information: Last Menstrual Period (LMP)
• Provenance: Unique Identifier
• Social Determinants of Health: Housing Instability and Homelessness
• Social History: Congregate Living
• Work Information: Employment Status
• Work Information: Job Employer Address
• Work Information: Job Employer Name
• Work Information: Usual Industry
• Work Information: Usual Occupation

Currently, 21 certified EHR products exchange these elements using electronic Case Reporting (eCR) specifications demonstrating real-world adoption that typically supports promotion, not demotion, within the USCDI maturity model.

Collectively, these elements provide clinical, demographic, occupational, social, and epidemiological context essential to disease investigation and outbreak response for nationally notifiable conditions.

We urge ONC to either reverse this decision or publish a detailed, evidence-based rationale.

Submitted by CDC_DSMH_WG on

CDC comments on Gestational Age

CDC requests this data element be considered for inclusion in USCDI V6.  A recent CDC/NACHC postpartum care services project documented the feasibility of collecting the data element in EHRs, and the importance for interoperability standards to support data exchange between health organizations to enhance quality improvement initiatives to improve perinatal outcomes.

Justification: The gestational age (in weeks, or weeks and fraction of week) of the pregnancy at time of pregnancy outcome. This data element is critical to inform obstetrical care and testing and evaluate preterm birth outcomes. Current elements do not capture this key outcome to inform infant health and maternal risk. The use case will be relevant for all maternal health patients and infants, all providers involved in maternal and infant health care, and all consumers of maternal and newborn health data used for research, public health and patient care and quality outcomes. The Centers for Disease Control and Prevention, in partnership with the National Association of Community Health Centers (NACHC), worked to build capacity of Federally Qualified Health Centers to improve the health informatics infrastructure for perinatal care measures and use perinatal care measures to identify and address gaps in postpartum care (https://liebertpub.com/doi/10.1089/jwh.2024.0364). Partner health center-controlled networks (Alliance Chicago, Health Choice Network, OCHIN, and Aliados Health) and nine Community Health Centers, implemented strategies to integrate evidence-based recommendations into the clinic workflow and use data-driven health information technology (HIT) systems to improve data standardization for quality improvement of postpartum care services. The respective EHRs were able electronically capture, access and exchange this data element through adequate testing in staging and development EHR environments. NACHC developed an implementation Guide (Improving Quality in Pregnancy and Postpartum Care) to provide practical strategies to leverage data from electronic clinical data systems for improved maternal health care (NACHC-WHPP-Implementation-Guide-2024_3.pdf). This data element is also captured as active in Logical Observation Identifiers Names and Codes (LOINC®) ontology as 18185-9 Gestational age.  It is also captured in ICD-10-CM diagnosis codes as Z3A and captured in the Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT) as 57036006: Fetal gestational age. 

Submitted by BLampkins_CSTE on

CSTE Comment - v6

CSTE supports inclusion of this data element in USCDI V6. Please see previously submitted CSTE comments for additional recommendations.

Submitted by RUy on

NACHC retains and supports previous comments

NACHC urges the inclusion of gestational age as it determines the trimester, and the week-appropriate diagnostic testing, evaluations, and overall obstetric management of pregnant patients.

Submitted by CDC_DSMH_WG on

CDC's Comment for draft USCDI v5

CDC supports the inclusion of this data element in USCDI v5 as it is an element that may be necessary for calculation of our digital quality metrics from FHIR data.

Submitted by RUy on

Reaffirming support for Women's Health data elements

The National Association of Community Health Centers (NACHC) remains steadfast in its commitment to advocating for and prioritizing Women's Health data elements. Recognizing the critical role that these factors play in shaping the clinical outcomes of community health center patients, NACHC continues to emphasize the need for comprehensive, accurate, and interoperable women's health data. By reaffirming our support for these essential elements, we aim to drive informed decision-making, policy development, and targeted interventions that address the root causes of health disparities. This underscores NACHC's belief in the transformative potential of this data in building healthier, more equitable communities.

See attached letter of support containing comments on data elements across USCDI submissions and versions, harmonized with ACOG comments

2023-09-20 NACHC USCDIv5 Letter of Support_14.pdf

Submitted by RUy on

Gestational Age is a fundamental for the practice of Obstetrics

NACHC would like to support Age of Gestation data element for consideration / inclusion to USCDIv4. Age of Gestation is a fundamental and vital data point that primary care and OBGYN physicians across the world need to do proper H&P, diagnosis and scheduling of prenatal care. 

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