Extensions for Using Data Elements from FHIR R5 in FHIR STU3
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R5 in FHIR STU3 - Downloaded Version null See the Directory of published versions

ValueSet: R5V20906ForR3

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-v2-0906-for-R3 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R5V20906ForR3

This cross-version ValueSet represents content from http://terminology.hl7.org/ValueSet/v2-0906|2.0.0 for use in FHIR STU3.

This value set is part of the cross-version definitions generated to enable use of the value set http://terminology.hl7.org/ValueSet/v2-0906|2.0.0 as defined in FHIR R5 in FHIR STU3.

The source value set is bound to the following FHIR R5 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://terminology.hl7.org/ValueSet/v2-0906|2.0.0, defined in FHIR R5 does not have any mapping to FHIR STU3

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v2-0906 version 📍2.1.0
    CodeDisplay
    AASAP - As soon as possible, next highest priority after stat
    CRCallback results - filler should contact the placer as soon as results are available, even for preliminary results
    CSCallback for scheduling - Filler should contact the placer (or target) to schedule the service.
    CSPCallback placer for scheduling - filler should contact the placer to schedule the service
    CSRContact recipient for scheduling - Filler should contact the service recipient (target) to schedule the service
    ELElective - Beneficial to the patient but not essential for survival.
    EMEmergency - An unforeseen combination of circumstances or the resulting state that calls for immediate action
    PPreop - 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
    PRNAs 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.
    RRoutine - Routine service, do at usual work hours
    RRRush reporting - A report should be prepared and sent as quickly as possible
    SStat - With highest priority (e.g. emergency).
    TTiming critical - It is critical to come as close as possible to the requested time (e.g. for a through antimicrobial level).
    UDUse as directed - Drug is to be used as directed by the prescriber.
    URUrgent - Calls for prompt action

 

Expansion

This value set expansion contains 15 concepts.

SystemVersionCodeDisplayJSONXML
http://terminology.hl7.org/CodeSystem/v2-09062.1.0  AASAP - As soon as possible, next highest priority after stat
http://terminology.hl7.org/CodeSystem/v2-09062.1.0  CRCallback results - filler should contact the placer as soon as results are available, even for preliminary results
http://terminology.hl7.org/CodeSystem/v2-09062.1.0  CSCallback for scheduling - Filler should contact the placer (or target) to schedule the service.
http://terminology.hl7.org/CodeSystem/v2-09062.1.0  CSPCallback placer for scheduling - filler should contact the placer to schedule the service
http://terminology.hl7.org/CodeSystem/v2-09062.1.0  CSRContact recipient for scheduling - Filler should contact the service recipient (target) to schedule the service
http://terminology.hl7.org/CodeSystem/v2-09062.1.0  ELElective - Beneficial to the patient but not essential for survival.
http://terminology.hl7.org/CodeSystem/v2-09062.1.0  EMEmergency - An unforeseen combination of circumstances or the resulting state that calls for immediate action
http://terminology.hl7.org/CodeSystem/v2-09062.1.0  PPreop - 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://terminology.hl7.org/CodeSystem/v2-09062.1.0  PRNAs 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://terminology.hl7.org/CodeSystem/v2-09062.1.0  RRoutine - Routine service, do at usual work hours
http://terminology.hl7.org/CodeSystem/v2-09062.1.0  RRRush reporting - A report should be prepared and sent as quickly as possible
http://terminology.hl7.org/CodeSystem/v2-09062.1.0  SStat - With highest priority (e.g. emergency).
http://terminology.hl7.org/CodeSystem/v2-09062.1.0  TTiming critical - It is critical to come as close as possible to the requested time (e.g. for a through antimicrobial level).
http://terminology.hl7.org/CodeSystem/v2-09062.1.0  UDUse as directed - Drug is to be used as directed by the prescriber.
http://terminology.hl7.org/CodeSystem/v2-09062.1.0  URUrgent - 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