Extensions for Using Data Elements from FHIR STU3 in FHIR R5 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R3-v2-0906-for-R5 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R3V20906ForR5 | ||
This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/v2-0906|2.8.2 for use in FHIR R5.
This value set is part of the cross-version definitions generated to enable use of the
value set http://hl7.org/fhir/ValueSet/v2-0906|2.8.2 as defined in FHIR STU3
in FHIR R5.
The source value set is bound to the following FHIR STU3 elements:
Note that all concepts are included in this cross-version definition because no concepts have compatible representations
Following are the generation technical comments:
FHIR ValueSet http://hl7.org/fhir/ValueSet/v2-0906|2.8.2, defined in FHIR STU3 does not have any mapping to FHIR R5
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://hl7.org/fhir/v2/0906 version 📍2.8.2| Code | Display |
| A | ASAP - As soon as possible, next highest priority after stat |
| CR | Callback results - filler should contact the placer as soon as results are available, even for preliminary results |
| CS | Callback for scheduling - Filler should contact the placer (or target) to schedule the service. |
| CSP | Callback placer for scheduling - filler should contact the placer to schedule the service |
| CSR | Contact recipient for scheduling - Filler should contact the service recipient (target) to schedule the service |
| EL | Elective - Beneficial to the patient but not essential for survival. |
| EM | Emergency - An unforeseen combination of circumstances or the resulting state that calls for immediate action |
| P | Preop - Used to indicate that a service is to be performed prior to a scheduled surgery. When ordering a service and using the pre-op priority, a check is done to see the amount of time that must be allowed for performance of the service. When the order |
| PRN | As needed - An "as needed" order should be accompanied by a description of what constitutes a need. This description is represented by an observation service predicate as a precondition. |
| R | Routine - Routine service, do at usual work hours |
| RR | Rush reporting - A report should be prepared and sent as quickly as possible |
| S | Stat - With highest priority (e.g. emergency). |
| T | Timing critical - It is critical to come as close as possible to the requested time (e.g. for a through antimicrobial level). |
| UD | Use as directed - Drug is to be used as directed by the prescriber. |
| UR | Urgent - Calls for prompt action |
This value set expansion contains 15 concepts.
| System | Version | Code | Display | JSON | XML |
http://hl7.org/fhir/v2/0906 | 2.8.2 | A | ASAP - As soon as possible, next highest priority after stat | ||
http://hl7.org/fhir/v2/0906 | 2.8.2 | CR | Callback results - filler should contact the placer as soon as results are available, even for preliminary results | ||
http://hl7.org/fhir/v2/0906 | 2.8.2 | CS | Callback for scheduling - Filler should contact the placer (or target) to schedule the service. | ||
http://hl7.org/fhir/v2/0906 | 2.8.2 | CSP | Callback placer for scheduling - filler should contact the placer to schedule the service | ||
http://hl7.org/fhir/v2/0906 | 2.8.2 | CSR | Contact recipient for scheduling - Filler should contact the service recipient (target) to schedule the service | ||
http://hl7.org/fhir/v2/0906 | 2.8.2 | EL | Elective - Beneficial to the patient but not essential for survival. | ||
http://hl7.org/fhir/v2/0906 | 2.8.2 | EM | Emergency - An unforeseen combination of circumstances or the resulting state that calls for immediate action | ||
http://hl7.org/fhir/v2/0906 | 2.8.2 | P | Preop - Used to indicate that a service is to be performed prior to a scheduled surgery. When ordering a service and using the pre-op priority, a check is done to see the amount of time that must be allowed for performance of the service. When the order | ||
http://hl7.org/fhir/v2/0906 | 2.8.2 | PRN | As needed - An "as needed" order should be accompanied by a description of what constitutes a need. This description is represented by an observation service predicate as a precondition. | ||
http://hl7.org/fhir/v2/0906 | 2.8.2 | R | Routine - Routine service, do at usual work hours | ||
http://hl7.org/fhir/v2/0906 | 2.8.2 | RR | Rush reporting - A report should be prepared and sent as quickly as possible | ||
http://hl7.org/fhir/v2/0906 | 2.8.2 | S | Stat - With highest priority (e.g. emergency). | ||
http://hl7.org/fhir/v2/0906 | 2.8.2 | T | Timing critical - It is critical to come as close as possible to the requested time (e.g. for a through antimicrobial level). | ||
http://hl7.org/fhir/v2/0906 | 2.8.2 | UD | Use as directed - Drug is to be used as directed by the prescriber. | ||
http://hl7.org/fhir/v2/0906 | 2.8.2 | UR | Urgent - Calls for prompt action |
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 |