This page is part of the HL7 Terminology (v1.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-0256 |
Version: | 2.0.0 |
Name: | Hl7VSTimeDelayPostChallenge |
Status: | Active |
Title: | hl7VS-timeDelayPostChallenge |
Definition: | Value Set of codes that classify an observation definition as being a component of a challenge test. |
Publisher: | HL7, Inc |
OID: | 2.16.840.1.113883.21.163 (for OID based terminology systems) |
Copyright: | Copyright HL7. Licensed under creative commons public domain |
Source Resource: | XML / JSON / Turtle |
References
This value set is not used
http://terminology.hl7.org/CodeSystem/v2-0256
This value set contains 44 concepts
Expansion based on timeDelayPostChallenge v2.1.0 (CodeSystem)
All codes from system http://terminology.hl7.org/CodeSystem/v2-0256
Code | Display | Definition |
BS | Baseline (time just before the challenge) | Baseline (time just before the challenge) |
PEAK | The time post drug dose at which the highest drug level is reached (differs by drug) | The time post drug dose at which the highest drug level is reached (differs by drug) |
TROUGH | The time post drug dose at which the lowest drug level is reached (varies with drug) | The time post drug dose at which the lowest drug level is reached (varies with drug) |
RANDOM | Time from the challenge, or dose not specified. (random) | Time from the challenge, or dose not specified. (random) |
1M | 1 minute post challenge | 1 minute post challenge |
2M | 2 minutes post challenge | 2 minutes post challenge |
3M | 3 minutes post challenge | 3 minutes post challenge |
4M | 4 minutes post challenge | 4 minutes post challenge |
5M | 5 minutes post challenge | 5 minutes post challenge |
6M | 6 minutes post challenge | 6 minutes post challenge |
7M | 7 minutes post challenge | 7 minutes post challenge |
8M | 8 minutes post challenge | 8 minutes post challenge |
9M | 9 minutes post challenge | 9 minutes post challenge |
10M | 10 minutes post challenge | 10 minutes post challenge |
15M | 15 minutes post challenge | 15 minutes post challenge |
20M | 20 minutes post challenge | 20 minutes post challenge |
25M | 25 minutes post challenge | 25 minutes post challenge |
30M | 30 minutes post challenge | 30 minutes post challenge |
1H | 1 hour post challenge | 1 hour post challenge |
2H | 2 hours post challenge | 2 hours post challenge |
2.5H | 2 1/2 hours post challenge | 2 1/2 hours post challenge |
3H | 3 hours post challenge | 3 hours post challenge |
4H | 4 hours post challenge | 4 hours post challenge |
5H | 5 hours post challenge | 5 hours post challenge |
6H | 6 hours post challenge | 6 hours post challenge |
7H | 7 hours post challenge | 7 hours post challenge |
8H | 8 hours post challenge | 8 hours post challenge |
8H SHIFT | 8 hours aligned on nursing shifts | 8 hours aligned on nursing shifts |
12H | 12 hours post challenge | 12 hours post challenge |
24H | 24 hours post challenge | 24 hours post challenge |
2D | 2 days | 2 days |
3D | 3 days | 3 days |
4D | 4 days | 4 days |
5D | 5 days | 5 days |
6D | 6 days | 6 days |
7D | 7 days | 7 days |
1W | 1 week | 1 week |
10D | 10 days | 10 days |
2W | 2 weeks | 2 weeks |
3W | 3 weeks | 3 weeks |
4W | 4 weeks | 4 weeks |
1L | 1 month (30 days) post challenge | 1 month (30 days) post challenge |
2L | 2 months (60 days) post challenge | 2 months (60 days) post challenge |
3L | 3 months (90 days) post challenge | 3 months (90 days) post challenge |
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 | Author | Custodian | Comment |
2020-05-06 | revise | Ted Klein | Vocabulary WG | Migrated to the UTG maintenance environment and publishing tooling. |