HL7 Terminology
2.0.0 - Publication
This page is part of the HL7 Terminology (v2.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions
Summary
Defining URL: | http://terminology.hl7.org/ValueSet/v2-0234 |
Version: | 2.0.0 |
Name: | Hl7VSReportTiming |
Title: | hl7VS-reportTiming |
Status: | Active as of 2019-12-01 |
Definition: | Value Set of codes that identify the time span of a report or the reason for a report sent to a regulatory agency. |
Publisher: | HL7, Inc |
Copyright: | Copyright HL7. Licensed under creative commons public domain |
OID: | 2.16.840.1.113883.21.145 (for OID based terminology systems) |
Source Resource: | XML / JSON / Turtle |
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/v2-0234
This value set contains 10 concepts
Expansion based on reportTiming v2.1.0 (CodeSystem)
All codes from system http://terminology.hl7.org/CodeSystem/v2-0234
Code | Display | Definition |
CO | Correction | Correction |
AD | Additional information | Additional information |
RQ | Requested information | Requested information |
DE | Device evaluation | Device evaluation |
PD | Periodic | Periodic |
3D | 3 day report | 3 day report |
7D | 7 day report | 7 day report |
10D | 10 day report | 10 day report |
15D | 15 day report | 15 day report |
30D | 30 day report | 30 day report |
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 |
Source | 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 |
History
Date | Action | Custodian | Author | Comment |
2020-05-06 | revise | Vocabulary WG | Ted Klein | Migrated to the UTG maintenance environment and publishing tooling. |