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 |
|
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. |
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 nedragarrett_CDC on 2022-04-27
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.