| ARCHETYPE ID | openEHR-EHR-CLUSTER.triage_priority.v0 |
|---|---|
| Concept | Triage Priority |
| Description | Subject's treatment urgency and/or order within a specific clinical care context, such as the scene of an accident or a hospital emergency room, where there are insufficient resources for all to be treated immediately. Triage priority is established after a clinician's, or trained lay person's, assessment of the seriousness of their condition. |
| Use | Use to record a category or required response time for a subject's treatment within a specific clinical care context. This archetype has been designed to provide a framework for any category, which may be specifically defined for a specific clinical location or event within a template for a specified clinical scenario. Similarly the triage priority may be time-related, by recording that the patient must be attended to within a specified timeframe. |
| Purpose | To record a category or required response time for a subject's treatment within a specific clinical care context. |
| References | Derived from: Triage Priority, Draft Archetype [Internet]. Digital Health Agency, Australian Digital Health Agency Clinical Knowledge Manager. No longer available. |
| Copyright | © openEHR Foundation |
| Authors | Author name: Heather Leslie Organisation: Ocean Informatics Email: heather.leslie@oceaninformatics.com Date originally authored: 2013-03-18 |
| Other Details Language | Author name: Heather Leslie Organisation: Ocean Informatics Email: heather.leslie@oceaninformatics.com Date originally authored: 2013-03-18 |
| Other Details (Language Independent) |
|
| Keywords | triage, priority, urgency, emergency, screening |
| Lifecycle | rejected |
| UID | 36daa3d3-8161-497d-a240-2bd5166a1e3f |
| Language used | en |
| Citeable Identifier | 1013.1.1626 |
| Revision Number | 0.0.1 |
| items | |
| Priority Category | Priority Category: Category of triage priority. There are many examples of triage categories in use. This archetype allows for any and all to be modelled by inclusion of specific values in this data element within a template for a specific clinical scenario. For example: High or Low; Now (immediate/life-threatening), Soon (urgent, up to 1 hour), Walk (delayed; up to 3 hours), Dead (no care required); or multiple locally defined categories. |
| Required Response Time | Required Response Time: Time period within which a respose is required. Allowed values: hours, minutes |
| Other contributors | |
| Translators |