Interweave Implementation Guide
0.1.0 - ci-build
Interweave Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the R4 profiles here.
| Official URL: https://fhir.yhcr.nhs.uk/ValueSet/Interweave-EncounterPriority-1 | Version: 0.1.0 | |||
| Active as of 2024-07-17 | Computable Name: InterweaveEncounterPriority | |||
Encounter priority codes
References
This value set includes codes based on the following rules:
https://fhir.yhcr.nhs.uk/CodeSystem/Interweave-EncounterPriority-1
This value set contains 16 concepts
Expansion based on:
| Code | System | Display | Definition |
| A | http://hl7.org/fhir/v3/ActPriority | ASAP | As soon as possible, next highest priority after stat. |
| CR | http://hl7.org/fhir/v3/ActPriority | callback results | Filler should contact the placer as soon as results are available, even for preliminary results. (Was "C" in HL7 version 2.3's reporting priority.) |
| CS | http://hl7.org/fhir/v3/ActPriority | callback for scheduling | Filler should contact the placer (or target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.) |
| CSP | http://hl7.org/fhir/v3/ActPriority | callback placer for scheduling | Filler should contact the placer to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.) |
| CSR | http://hl7.org/fhir/v3/ActPriority | contact recipient for scheduling | Filler should contact the service recipient (target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.) |
| EL | http://hl7.org/fhir/v3/ActPriority | elective | Beneficial to the patient but not essential for survival. |
| EM | http://hl7.org/fhir/v3/ActPriority | emergency | An unforeseen combination of circumstances or the resulting state that calls for immediate action. |
| P | http://hl7.org/fhir/v3/ActPriority | 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 is placed, a message can be generated indicating the time needed for the service so that it is not ordered in conflict with a scheduled operation. |
| PRN | http://hl7.org/fhir/v3/ActPriority | 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 | http://hl7.org/fhir/v3/ActPriority | routine | Routine service, do at usual work hours. |
| RR | http://hl7.org/fhir/v3/ActPriority | rush reporting | A report should be prepared and sent as quickly as possible. |
| S | http://hl7.org/fhir/v3/ActPriority | stat | With highest priority (e.g., emergency). |
| T | http://hl7.org/fhir/v3/ActPriority | timing critical | It is critical to come as close as possible to the requested time (e.g., for a through antimicrobial level). |
| UD | http://hl7.org/fhir/v3/ActPriority | use as directed | Drug is to be used as directed by the prescriber. |
| UR | http://hl7.org/fhir/v3/ActPriority | urgent | Calls for prompt action. |
| 2WW | https://fhir.yhcr.nhs.uk/CodeSystem/Interweave-EncounterPriority-1 | two week wait | Two Week Wait |
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 |