<<<<<<< HEAD ======= >>>>>>> med01


0.1.3 - ci-build

MED - Local Development build (v0.1.3) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

ValueSet: Encounter Priorities

Official URL: https://fhir.medicaia.ar/ValueSet/PrioritiesVS Version: 0.1.3
Standards status: Draft Maturity Level: 1 Computable Name: PrioritiesVS

Encounter Priorities

References

Logical Definition (CLD)

Generated Narrative: ValueSet PrioritiesVS

Last updated: 2018-08-12 00:00:00+1000

Profile: Shareable ValueSet

 

Expansion

Generated Narrative: ValueSet

Last updated: 2018-08-12 00:00:00+1000

Profile: Shareable ValueSet

Expansion based on codesystem Priorities v0.1.3 (CodeSystem)

This value set contains 13 concepts

CodeSystemDisplayDefinition
  Ahttps://fhir.medicaia.ar/CodeSystem/PrioritiesCSASAP

As soon as possible, next highest priority after stat.

  CRhttps://fhir.medicaia.ar/CodeSystem/PrioritiesCScallback 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.)

  CShttps://fhir.medicaia.ar/CodeSystem/PrioritiesCScallback for scheduling

Filler should contact the placer (or target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)

  ELhttps://fhir.medicaia.ar/CodeSystem/PrioritiesCSelective

Beneficial to the patient but not essential for survival.

  EMhttps://fhir.medicaia.ar/CodeSystem/PrioritiesCSemergency

An unforeseen combination of circumstances or the resulting state that calls for immediate action.

  Phttps://fhir.medicaia.ar/CodeSystem/PrioritiesCSpreop

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.

  PRNhttps://fhir.medicaia.ar/CodeSystem/PrioritiesCSas 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.

  Rhttps://fhir.medicaia.ar/CodeSystem/PrioritiesCSroutine

Routine service, do at usual work hours.

  RRhttps://fhir.medicaia.ar/CodeSystem/PrioritiesCSrush reporting

A report should be prepared and sent as quickly as possible.

  Shttps://fhir.medicaia.ar/CodeSystem/PrioritiesCSstat

With highest priority (e.g., emergency).

  Thttps://fhir.medicaia.ar/CodeSystem/PrioritiesCStiming critical

It is critical to come as close as possible to the requested time (e.g., for a through antimicrobial level).

  UDhttps://fhir.medicaia.ar/CodeSystem/PrioritiesCSuse as directed

Drug is to be used as directed by the prescriber.

  URhttps://fhir.medicaia.ar/CodeSystem/PrioritiesCSurgent

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