HL7 FHIR® Implementation Guide: Electronic Case Reporting (eCR) - US Realm
2.1.2 - STU 2 United States of America flag

HL7 FHIR® Implementation Guide: Electronic Case Reporting (eCR) - US Realm, published by HL7 International / Public Health. This guide is not an authorized publication; it is the continuous build for version 2.1.2 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/case-reporting/ and changes regularly. See the Directory of published versions

Resource Profile: US Public Health Travel History

Official URL: http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-travel-history Version: 2.1.2
Active as of 2024-10-30 Computable Name: USPublicHealthTravelHistory
Other Identifiers: OID:2.16.840.1.113883.4.642.40.46.42.76

This Observation profile represents a patient's travel history.

The following data for a patient can be recorded:

  • travel history as a string, an address, or a coded location
  • the date or period of time spent in the location (Observation.effectiveTime)
    • it is important to accurately capture the most accurate dates possible
    • the focus should be on date of arrival and date of departure
    • the concepts of dates as related to travel are especially useful for determining need for Federal Public Health Notifications (FPHNs) and these dates are used to alert foreign ministries of health about their residents who may have been contacts of cases, or if a flight that was outbound from the USA had an infectious traveler on it
  • most uses will involve a single location (Observation.component), however, it is possible to specify multiple locations (but there is only a single effectiveTime)
    • this allows for cases where a patient cannot remember exact dates of travel (e.g. I traveled to London, Paris, and Berlin in July and August 2016)
  • free text describing the travel history details and location (Observation.component.valueCodeableConcept.text element)
  • use Observation.component.codeableConcept to record a coded location
  • use Observationcomponent.extension to record a specific address
  • where a more granular address than state is known (e.g. city, street) it is appropriate to use the extension to record an address rather than using the coded location

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Observation

NameFlagsCard.TypeDescription & Constraintsdoco
.. Observation 0..* Observation US Public Health Travel History
... code S 1..1 CodeableConcept Type of observation (code / type)
Required Pattern: At least the following
.... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
..... system 1..1 uri Identity of the terminology system
Fixed Value: http://snomed.info/sct
..... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 420008001
... subject S 1..1 Reference(US Public Health Patient) Who and/or what the observation is about
... effective[x] S 1..1 dateTime, Period, Timing, instant Date or period of time spent in the location
... Slices for component S 1..* BackboneElement Component results
Slice: Unordered, Open by value:code
.... component:travelLocation S 1..* BackboneElement Travel location
..... Slices for extension S 0..* Extension Extension
Slice: Unordered, Open by value:url
...... travelHistoryAddress S 0..1 Address Travel history address
URL: http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-address-extension
..... code S 1..1 CodeableConcept Type of component observation (code / type)
Required Pattern: At least the following
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://terminology.hl7.org/CodeSystem/v3-ParticipationType
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: LOC
....... display 1..1 string Representation defined by the system
Fixed Value: Location
..... value[x] S 0..1 CodeableConcept Actual component result
...... coding S 0..* Coding Code defined by a terminology system
Binding: Geographical location history (extensible): Geographical Location History

...... text S 0..1 string Plain text representation of the concept
.... component:travelPurpose S 0..* BackboneElement Purpose of travel
..... code S 1..1 CodeableConcept Type of component observation (code / type)
Required Pattern: At least the following
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://snomed.info/sct
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 280147009
..... value[x] S 1..1 CodeableConcept Actual component result
Binding: Travel Purpose (CDC) (preferred): Travel Purpose


doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
Observation.component:travelLocation.value[x].codingextensiblePHVS_GeographicLocationHistory_CDC
http://phinvads.cdc.gov/fhir/ValueSet/2.16.840.1.114222.4.11.3201
Observation.component:travelPurpose.value[x]preferredPHVS_TravelPurpose_CDC
http://phinvads.cdc.gov/fhir/ValueSet/2.16.840.1.114222.4.11.8064

 

Other representations of profile: CSV, Excel, Schematron