|Submitted By: Kensaku Kawamoto, MD, PhD, MHS / University of Utah|
|Data Element Information|
|Use Case Description(s)|
|Use Case Description||A baby’s gestational age at birth has an important influence on their health risks and care needs. E.g., gestational age needs to be considered as a part of neonatal bilirubin management and avoidance of neurotoxicity.|
|Estimated number of stakeholders capturing, accessing using or exchanging||This data element would affect all newborns, or approximately 4 million babies a year.|
|Link to use case project page||https://jamanetwork.com/journals/jamanetworkopen/fullarticle/2755484|
|Maturity of Use and Technical Specifications for Data Element|
|Applicable Standard(s)||LOINC codes are available for gestational age
|Current Use||Extensively used in production environments|
This data element is already supported in the FHIR interface of major EHR systems such as Epic.
|Number of organizations/individuals with which this data element has been electronically exchanged||1|
We answered 1 entity here simply because we are unsure of the extent to which this data has been electronically exchanged with external organizations or individuals. In any case, a primary use case is expected to be use within an institution by standards-based tools such as SMART on FHIR apps and CDS Hooks services. For example, this information is used over 20,000 times a year in just one institution for neonatal bilirubin management (see supporting link).
|Restrictions on Standardization (e.g. proprietary code)||No relevant restrictions are anticipated.|
|Restrictions on Use (e.g. licensing, user fees)||No relevant restrictions are anticipated.|
|Privacy and Security Concerns||No relevant concerns are anticipated.|
|Estimate of Overall Burden||Because gestational age is already routinely captured in structured form in many EHRs, and it would be fine for this information to only be made available if already captured in structured form, there should be minimal burden compared to the current state with regard to 1) supporting the data elements in the EHR and 2) users collecting the information.
With regard to adding this information when available, the effort is expected to be limited as the data element is already widely captured in structured form in EHRs today. For example, Epic already natively supports this data element in its FHIR API.
Information from the submission form
|Gestational Age at Birth||