2.16.840.1.113883.5.7/static-2012-07-24: Unterschied zwischen den Versionen
ADbot (Diskussion | Beiträge) (Automated TermBot page content) |
ADbot (Diskussion | Beiträge) (Automated TermBot page content) |
||
Zeile 9: | Zeile 9: | ||
| colspan=2 bgcolor="#F6F3EE"|''ActPriority'' | | colspan=2 bgcolor="#F6F3EE"|''ActPriority'' | ||
| bgcolor="#F6F3EE"|2.16.840.1.113883.5.7 | | bgcolor="#F6F3EE"|2.16.840.1.113883.5.7 | ||
− | | bgcolor="#F6F3EE"|2012-07- | + | | bgcolor="#F6F3EE"|2012-07-24 |
| bgcolor="#F6F3EE"|definitiv | | bgcolor="#F6F3EE"|definitiv | ||
|- | |- | ||
Zeile 17: | Zeile 17: | ||
| bgcolor="#ECE9E4" colspan="2"|'''Beschreibung''' | | bgcolor="#ECE9E4" colspan="2"|'''Beschreibung''' | ||
|- | |- | ||
+ | |- | ||
+ | |0-L | ||
+ | |'''EL''' | ||
+ | |<font color="grey">(en-US)</font> elective | ||
+ | | colspan="2" |<p>Beneficial to the patient but not essential for survival.</p> | ||
+ | |- | ||
+ | |0-L | ||
+ | |'''UR''' | ||
+ | |<font color="grey">(en-US)</font> urgent | ||
+ | | colspan="2" |<p>Calls for prompt action.</p> | ||
+ | |- | ||
+ | |0-L | ||
+ | |'''EM''' | ||
+ | |<font color="grey">(en-US)</font> emergency | ||
+ | | colspan="2" |<p>An unforeseen combination of circumstances or the resulting state that calls for immediate action.</p> | ||
+ | |- | ||
+ | |0-L | ||
+ | |'''S''' | ||
+ | |<font color="grey">(en-US)</font> stat | ||
+ | | colspan="2" |<p>With highest priority (e.g., emergency).</p> | ||
+ | |- | ||
+ | |0-L | ||
+ | |'''A''' | ||
+ | |<font color="grey">(en-US)</font> ASAP | ||
+ | | colspan="2" |<p>As soon as possible, next highest priority after stat.</p> | ||
+ | |- | ||
+ | |0-L | ||
+ | |'''R''' | ||
+ | |<font color="grey">(en-US)</font> routine | ||
+ | | colspan="2" |<p>Routine service, do at usual work hours.</p> | ||
+ | |- | ||
+ | |0-L | ||
+ | |'''P''' | ||
+ | |<font color="grey">(en-US)</font> preop | ||
+ | | colspan="2" |<p>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.</p> | ||
+ | |- | ||
+ | |0-S | ||
+ | |'''CS''' | ||
+ | |<font color="grey">(en-US)</font> callback for scheduling | ||
+ | | colspan="2" |<p>Filler should contact the placer (or target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)</p> | ||
+ | |- | ||
+ | |1-L | ||
+ | |'''CSP''' | ||
+ | |<font color="grey">(en-US)</font> callback placer for scheduling | ||
+ | | colspan="2" |<p>Filler should contact the placer to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)</p> | ||
+ | |- | ||
+ | |1-L | ||
+ | |'''CSR''' | ||
+ | |<font color="grey">(en-US)</font> contact recipient for scheduling | ||
+ | | colspan="2" |<p>Filler should contact the service recipient (target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)</p> | ||
+ | |- | ||
+ | |0-L | ||
+ | |'''T''' | ||
+ | |<font color="grey">(en-US)</font> timing critical | ||
+ | | colspan="2" |<p>It is critical to come as close as possible to the requested time (e.g., for a through antimicrobial level).</p> | ||
+ | |- | ||
+ | |0-L | ||
+ | |'''PRN''' | ||
+ | |<font color="grey">(en-US)</font> as needed | ||
+ | | colspan="2" |<p>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.</p> | ||
+ | |- | ||
+ | |0-L | ||
+ | |'''CR''' | ||
+ | |<font color="grey">(en-US)</font> callback results | ||
+ | | colspan="2" |<p>Filler should contact the placer as soon as results are available, even for preliminary results. (Was "C" in HL7 verion 2.3's reporting priority.)</p> | ||
+ | |- | ||
+ | |0-L | ||
+ | |'''RR''' | ||
+ | |<font color="grey">(en-US)</font> rush reporting | ||
+ | | colspan="2" |<p>A report should be prepared and sent as quickly as possible.</p> | ||
+ | |- | ||
+ | |0-L | ||
+ | |'''UD''' | ||
+ | |<font color="grey">(en-US)</font> use as directed | ||
+ | | colspan="2" |<p>Drug is to be used as directed by the prescriber.</p> | ||
|} | |} |
Version vom 11. November 2012, 18:53 Uhr
Codesystem Name | Codesystem Id | Version / Eingangsdatum | Status | |
---|---|---|---|---|
ActPriority | 2.16.840.1.113883.5.7 | 2012-07-24 | definitiv | |
Level/Typ | Code | Anzeigename | Beschreibung | |
0-L | EL | (en-US) elective | Beneficial to the patient but not essential for survival. | |
0-L | UR | (en-US) urgent | Calls for prompt action. | |
0-L | EM | (en-US) emergency | An unforeseen combination of circumstances or the resulting state that calls for immediate action. | |
0-L | S | (en-US) stat | With highest priority (e.g., emergency). | |
0-L | A | (en-US) ASAP | As soon as possible, next highest priority after stat. | |
0-L | R | (en-US) routine | Routine service, do at usual work hours. | |
0-L | P | (en-US) 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. | |
0-S | CS | (en-US) 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.) | |
1-L | CSP | (en-US) callback placer for scheduling | Filler should contact the placer to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.) | |
1-L | CSR | (en-US) 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.) | |
0-L | T | (en-US) timing critical | It is critical to come as close as possible to the requested time (e.g., for a through antimicrobial level). | |
0-L | PRN | (en-US) 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. | |
0-L | CR | (en-US) callback results | Filler should contact the placer as soon as results are available, even for preliminary results. (Was "C" in HL7 verion 2.3's reporting priority.) | |
0-L | RR | (en-US) rush reporting | A report should be prepared and sent as quickly as possible. | |
0-L | UD | (en-US) use as directed | Drug is to be used as directed by the prescriber. |