Vital Records Death Reporting (VRDR) FHIR Implementation Guide
3.0.0 - STU3

Vital Records Death Reporting (VRDR) FHIR Implementation Guide, published by HL7 International / Public Health. This guide is not an authorized publication; it is the continuous build for version 3.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/QRPH.VRDR/ and changes regularly. See the Directory of published versions

## ValueSet: Transportation Incident Role ValueSet

Official URL: http://hl7.org/fhir/us/vrdr/ValueSet/vrdr-transportation-incident-role-vs | Version: 3.0.0
Active as of 2024-10-23 | Computable Name: TransportationIncidentRoleVS
Other Identifiers: OID:2.16.840.1.113883.4.642.40.10.48.24
Copyright/Legal: This value set includes content from SNOMED CT, which is copyright © 2002+ International Health Terminology Standards Development Organisation (IHTSDO), and distributed by agreement between IHTSDO and HL7. Implementer use of SNOMED CT is not covered by this agreement

Role of the decedent in a transportation incident resulting in a death-related injury.

Mapping to IJE codes here.

References

- Injury Incident

Changes since version true:

### Logical Definition (CLD)

Generated Narrative: ValueSet vrdr-transportation-incident-role-vs

This value set includes codes based on the following rules:

- Include these codes as defined in `http://snomed.info/sct`

  Code | Display
  236320001 | Vehicle driver
  257500003 | Passenger
  257518000 | Pedestrian

- Include these codes as defined in `http://terminology.hl7.org/CodeSystem/v3-NullFlavor`

  Code | Display | Definition
  OTH | Other | **Description:**The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system). **Usage Notes**: This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to \*any\* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc. With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE.
  UNK | unknown | **Description:**A proper value is applicable, but not known. **Usage Notes**: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless: 1. Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown') 2. Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of "H" and a URL prefix of "tel:" to convey that it is the home phone number that is unknown.)
  NA | not applicable | Known to have no proper value (e.g., last menstrual period for a male).

### Expansion

Generated Narrative: ValueSet

Expansion based on:

- SNOMED CT United States edition 01-Sep 2024
- codesystem NullFlavor v3.0.0 (CodeSystem)

This value set contains 6 concepts

Code | System | Display | Definition
236320001 | http://snomed.info/sct | Vehicle driver |
257500003 | http://snomed.info/sct | Passenger |
257518000 | http://snomed.info/sct | Pedestrian |
OTH | http://terminology.hl7.org/CodeSystem/v3-NullFlavor | Other | **Description:**The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system). Usage Notes: This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to *any* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc. With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE.
UNK | http://terminology.hl7.org/CodeSystem/v3-NullFlavor | unknown | **Description:**A proper value is applicable, but not known. Usage Notes: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless: Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown') Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of "H" and a URL prefix of "tel:" to convey that it is the home phone number that is unknown.)
NA | http://terminology.hl7.org/CodeSystem/v3-NullFlavor | not applicable | Known to have no proper value (e.g., last menstrual period for a male).

Explanation of the columns that may appear on this page:

Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System | The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code | The code (used as the code in the resource instance)
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition | An explanation of the meaning of the concept
Comments | Additional notes about how to use the code