This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3
Vocabulary Work Group | Maturity Level: N/A | Standards Status: Informative |
Raw XML (canonical form + also see XML Format Specification)
A set of codes (e.g., for routine, emergency), specifying the urgency under which the Act happened, can happen, is happening, is intended to happen, or is requested/demanded to happen.
<?xml version="1.0" encoding="UTF-8"?> <CodeSystem xmlns="http://hl7.org/fhir"> <id value="v3-ActPriority"/> <meta> <lastUpdated value="2019-07-31T00:00:00.000+10:00"/> </meta> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <p> Release Date: 2019-07-31</p> <table class="grid"> <tr> <td> <b> Level</b> </td> <td> <b> Code</b> </td> <td> <b> Display</b> </td> <td> <b> Definition</b> </td> </tr> <tr> <td> 1</td> <td> A <a name="v3-ActPriority-A"> </a> </td> <td> ASAP</td> <td> As soon as possible, next highest priority after stat. <br/> </td> </tr> <tr> <td> 1</td> <td> CR <a name="v3-ActPriority-CR"> </a> </td> <td> callback results</td> <td> 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.) <br/> </td> </tr> <tr> <td> 1</td> <td> CS <a name="v3-ActPriority-CS"> </a> </td> <td> callback for scheduling</td> <td> Filler should contact the placer (or target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.) <br/> </td> </tr> <tr> <td> 2</td> <td> Â Â CSP <a name="v3-ActPriority-CSP"> </a> </td> <td> callback placer for scheduling</td> <td> Filler should contact the placer to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.) <br/> </td> </tr> <tr> <td> 2</td> <td> Â Â CSR <a name="v3-ActPriority-CSR"> </a> </td> <td> contact recipient for scheduling</td> <td> Filler should contact the service recipient (target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.) <br/> </td> </tr> <tr> <td> 1</td> <td> EL <a name="v3-ActPriority-EL"> </a> </td> <td> elective</td> <td> Beneficial to the patient but not essential for survival. <br/> </td> </tr> <tr> <td> 1</td> <td> EM <a name="v3-ActPriority-EM"> </a> </td> <td> emergency</td> <td> An unforeseen combination of circumstances or the resulting state that calls for immediate action. <br/> </td> </tr> <tr> <td> 1</td> <td> P <a name="v3-ActPriority-P"> </a> </td> <td> preop</td> <td> 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. <br/> </td> </tr> <tr> <td> 1</td> <td> PRN <a name="v3-ActPriority-PRN"> </a> </td> <td> as needed</td> <td> 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. <br/> </td> </tr> <tr> <td> 1</td> <td> R <a name="v3-ActPriority-R"> </a> </td> <td> routine</td> <td> Routine service, do at usual work hours. <br/> </td> </tr> <tr> <td> 1</td> <td> RR <a name="v3-ActPriority-RR"> </a> </td> <td> rush reporting</td> <td> A report should be prepared and sent as quickly as possible. <br/> </td> </tr> <tr> <td> 1</td> <td> S <a name="v3-ActPriority-S"> </a> </td> <td> stat</td> <td> With highest priority (e.g., emergency). <br/> </td> </tr> <tr> <td> 1</td> <td> T <a name="v3-ActPriority-T"> </a> </td> <td> timing critical</td> <td> It is critical to come as close as possible to the requested time (e.g., for a through antimicrobial level). <br/> </td> </tr> <tr> <td> 1</td> <td> UD <a name="v3-ActPriority-UD"> </a> </td> <td> use as directed</td> <td> Drug is to be used as directed by the prescriber. <br/> </td> </tr> <tr> <td> 1</td> <td> UR <a name="v3-ActPriority-UR"> </a> </td> <td> urgent</td> <td> Calls for prompt action. <br/> </td> </tr> </table> </div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status"> <valueCode value="draft"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm"> <valueInteger value="1"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"> <valueCode value="pa"/> </extension> <url value="http://terminology.hl7.org/CodeSystem/v3-ActPriority"/> <identifier> <system value="urn:ietf:rfc:3986"/> <value value="urn:oid:2.16.840.1.113883.5.7"/> </identifier> <version value="2019-07-31"/> <name value="v3.ActPriority"/> <title value="v3 Code System ActPriority"/> <status value="active"/> <experimental value="false"/> <date value="2019-07-31T00:00:00+10:00"/> <publisher value="HL7, Inc"/> <contact> <telecom> <system value="url"/> <value value="http://hl7.org"/> </telecom> </contact> <description value=" A set of codes (e.g., for routine, emergency), specifying the urgency under which the Act happened, can happen, is happening, is intended to happen, or is requested/demanded to happen."/> <caseSensitive value="true"/> <valueSet value="http://terminology.hl7.org/ValueSet/v3-ActPriority"/> <hierarchyMeaning value="is-a"/> <content value="complete"/> <concept> <code value="A"/> <display value="ASAP"/> <definition value="As soon as possible, next highest priority after stat."/> </concept> <concept> <code value="CR"/> <display value="callback results"/> <definition value="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.)"/> </concept> <concept> <code value="CS"/> <display value="callback for scheduling"/> <definition value="Filler should contact the placer (or target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)"/> <concept> <code value="CSP"/> <display value="callback placer for scheduling"/> <definition value="Filler should contact the placer to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)"/> </concept> <concept> <code value="CSR"/> <display value="contact recipient for scheduling"/> <definition value="Filler should contact the service recipient (target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)"/> </concept> </concept> <concept> <code value="EL"/> <display value="elective"/> <definition value="Beneficial to the patient but not essential for survival."/> </concept> <concept> <code value="EM"/> <display value="emergency"/> <definition value="An unforeseen combination of circumstances or the resulting state that calls for immediate action."/> </concept> <concept> <code value="P"/> <display value="preop"/> <definition value="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."/> </concept> <concept> <code value="PRN"/> <display value="as needed"/> <definition value="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."/> </concept> <concept> <code value="R"/> <display value="routine"/> <definition value="Routine service, do at usual work hours."/> </concept> <concept> <code value="RR"/> <display value="rush reporting"/> <definition value="A report should be prepared and sent as quickly as possible."/> </concept> <concept> <code value="S"/> <display value="stat"/> <definition value="With highest priority (e.g., emergency)."/> </concept> <concept> <code value="T"/> <display value="timing critical"/> <definition value="It is critical to come as close as possible to the requested time (e.g., for a through antimicrobial level)."/> </concept> <concept> <code value="UD"/> <display value="use as directed"/> <definition value="Drug is to be used as directed by the prescriber."/> </concept> <concept> <code value="UR"/> <display value="urgent"/> <definition value="Calls for prompt action."/> </concept> </CodeSystem>
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.