Data Element
Travel Plans Dates
Description

Dates planned for travel to a location.
Submitted By: Craig Newman / Altarum
Data Element Information
Use Case Description(s)
Use Case Description Exposures to environmental and communicable disease threats through travel play an important role in many emergent public health events and have a significant impact on routine reporting as well. For both reasons it is important for public health investigators to receive travel plan information about patients to appropriately prepare them for travel through education, vaccination or other means. Currently, if travel plans are recorded in clinical care it may be saved in narrative form inside of social history or perhaps some other place. It is important to more specifically identify travel plan information and to structure the storage of these data for use by clinical care personnel and systems such as clinical decision support engines (eg for immunization recommendations).
Estimate the breadth of applicability of the use case(s) for this data element Many providers provide travel services, including vaccinations. Having access to structured travel plan information will also better clinical support.
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) Geographical location history (https://phinvads.cdc.gov/vads/ViewValueSet.action?oid=2.16.840.1.114222.4.11.3201)
ISO 3166 country codes (https://www.iso.org/iso-3166-country-codes.html)
Additional Specifications The Public Health WG is sponsoring a project to develop a FHIR IG for communicating with immunization decision support engines. The first phase of that project is awaiting publication. There is a second phase planned to start later this fall that will expand the scope of that communication to include patient related data that may impact the immunization recommendations. Patient travel plans are expected to be included as part of this second phase.
Current Use Not currently captured or accessed with an organization
Extent of exchange N/A
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 typical 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.

Comment

Log in or register to post comments