Data Element
Transportation Details
Description

Information about transportation details such as the type of transport along with any associated information (e.g., name of cruise ship, flight number, airport, seat number, cabin number).
Submitted By: Nedra Garrett / CDC
Data Element Information
Use Case Description(s)
Use Case Description The detection of, and response to, communicable diseases related to travel and imported pathogens.
Estimate the breadth of applicability of the use case(s) for this data element This data is exchanged as part of the extensive implementation of electronic case reporting in the US. Target is nationwide, currently 5400+ sites are reporting. There are between 56 and 2400 public health agencies using this data. Electronic case reporting is also cited in the Cares Act regulations.
Link to use case project page https://www.cdc.gov/ecr/index.html
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) HL7 FHIR: US Public Health Transportation Details profile

HL7 CDA: Transportation Details Organizer/Transportation Details Observation templates

VSAC Value Set: Transport vehicle type
https://www.hl7.org/implement/standards/product_brief.cfm?product_id=519 https://www.hl7.org/implement/standards/product_brief.cfm?product_id=436 https://vsac.nlm.nih.gov/valueset/2.16.840.1.113762.1.4.1099.50/expansion/Latest (SNOMED)
Additional Specifications HL7 FHIR® Implementation Guide: Electronic Case Reporting (eCR) based on FHIR R4

HL7 CDA® R2 Implementation Guide: Public Health Case Report - the Electronic Initial Case Report (eICR)

HL7 FHIR: US Public Health Transportation Details profile

HL7 CDA: Transportation Details Organizer/Transportation Details Observation templates
Current Use In limited use in test environments only
Supporting Artifacts Soon to be published: HL7 FHIR® Implementation Guide: Electronic Case Reporting (eCR) STU Release 2

Soon to be published: HL7 CDA® R2 Implementation Guide: Public Health Case Report - the Electronic Initial Case Report (eICR) Release 1, STU Release 3.0
https://www.hl7.org/implement/standards/product_brief.cfm?product_id=519 https://www.hl7.org/implement/standards/product_brief.cfm?product_id=436
Extent of exchange 5 or more. This data element has been tested at scale between multiple different production environments to support the majority of anticipated stakeholders.
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) These data elements are straightforward in nature and should not present a large burden to implement provided the EHR system is capturing the data.
Restrictions on Use (e.g. licensing, user fees) These data elements are straightforward in nature and should not present a large burden to implement provided the EHR system is capturing the data.
Privacy and Security Concerns These data elements are straightforward in nature and should not present a large burden to implement provided the EHR system is capturing the 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.
ONC 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 0 - Data element is captured, stored, or accessed in limited settings such as a pilot or proof of concept demonstration.
Criterion #3
Maturity - Current Exchange		 Level 2 - Data element is electronically exchanged between more than two production EHRs or other HIT modules of different developers using available interoperability standards.
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.

Comment

Submitted by nedragarrett_CDC on

CDC's Consolidated Comment

Additional use case:

CDC's Division of Migration and Quarantine's Quarantine Branch is responsible for responding to and assessing individual exposure risks due to mode of transportation used for given dates. This data element facilitates these processes specifically for aircraft-related or cruiseship-related contacts in order to reach potential contacts for post-exposure prophylaxis needs.

Log in or register to post comments