Data Element

Information from the submission form
Purpose of Travel
Description

Purpose of travel (business, tourism, etc.)

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.
Estimated number of stakeholders capturing, accessing using or exchanging 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 Travel History profile (Observation.component)

HL7 CDA: Purpose of Travel Observation template

SNOMED: 280147009 "Travel Purpose"

PHIN VADS Value Set: Purpose of Travel

https://loinc.org/75274-1/ https://vsac.nlm.nih.gov/valueset/2.16.840.1.113883.11.20.9.49/expansion https://www.hl7.org/implement/standards/product_brief.cfm?product_id=519 https://www.hl7.org/implement/standards/product_brief.cfm?product_id=436
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 Travel History profile

HL7 CDA: Purpose of Travel Observation template
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
Number of organizations/individuals with which this data element has been electronically exchanged 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 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 2 - Demonstrates exchange between 4 or more organizations with different EHR/HIT systems
Breadth of Applicability - # Stakeholders Impacted Comment Level - Used by few stakeholders, or for narrowly defined conditions or events

Comment

Submitted by nedragarrett_CDC on 2022-04-27

CDC's Consolidated Comment

  • Please note that there is SNOMED code for "Type of activity" which is likely broader in scope and not limited to travel.
  • There is a LOINC code available for Travel Reason: 66415-1 for consideration.

Log in or register to post comments