| ARCHETYPE ID | openEHR-EHR-INSTRUCTION.transfusion_order.v0 |
|---|---|
| Concept | Transfusion order |
| Description | The instructions for giving a transfusion. |
| Use | Used to record information about an order for blood products (products that are ordered from a blood bank). |
| Misuse | Not to be used for ordering medications - use INSTRUCTION.medication_order for this purpose. |
| Purpose | For recording the instructions relating to transfusion. |
| References | |
| Copyright | © openEHR Foundation |
| Authors | Author name: Sam Heard Organisation: Ocean Informatics, Australia Email: sam.heard@oceaninformatics.com Date originally authored: 2008-07-23 |
| Other Details Language | Author name: Sam Heard Organisation: Ocean Informatics, Australia Email: sam.heard@oceaninformatics.com Date originally authored: 2008-07-23 |
| Other Details (Language Independent) |
|
| Keywords | transfusion, blood |
| Lifecycle | in_development |
| UID | 62a634b5-4b1f-4314-abe3-dea1ba7546a9 |
| Language used | en |
| Citeable Identifier | 1246.145.2812 |
| Revision Number | 0.0.1-alpha |
| activities | |
| new activity | new activity: * |
| Type of blood product | Type of blood product: The blood product to be administered. |
| Amount | Amount: The amount of blood product to be transfused. |
| Number of units | Number of units: The number of units to be transfused. min: >=0 |
| Volume | Volume: The volume of the product to be transfused for paediatric and some specific purposes. Property: Volume Units: >=0.0 ml Limit decimal places: 0 |
| Clinical indication | Clinical indication: The clinical reason for ordering the tranfusion. For example: 'low hemoglobin level'. Coding of the clinical indication with a terminology is preferred, where possible. This data element allows multiple occurrences. It is not intended to carry an indication for administrative authorisation purposes. |
| Urgency | Urgency: The urgency of the transfusion. |
| Administration pattern | Administration pattern: * Include: All not explicitly excluded archetypes |
| Special requirement | Special requirement: Special requirements for blood products. |
| protocol | |
| Extension | Extension: Additional information required to capture local content or to align with other reference models/formalisms. For example: local information requirements or additional metadata to align with FHIR or CIMI equivalents. Include: All not explicitly excluded archetypes |
| Other contributors | Silje Ljosland Bakke, Nasjonal IKT HF, Norway (openEHR Editor) Heather Leslie, Atomica Informatics, Australia (openEHR Editor) Ian McNicoll, freshEHR Clinical Informatics, United Kingdom (openEHR Editor) Line Silsand, University Hospital of Northern Norway, Norway Kristian Berg, University Hospital of Northern Norway, Norway Gro Hilde Ulriksen, University Hospital of Northern Norway, Norway Ole Martin Sand, DIPS ASA, Norway Ingunn Skjervold, University Hospital of Northern Norway, Norway Merethe Appelbom, Northern Norway Regional Health Authority, Norway Øystein Berg Sletteng, Helse Nord IKT, Norway Kristian Andreassen, Helse Nord IKT, Norway John Tore Valand, Helse Bergen HF, Norway Tore Trondsen, Helse Nord IKT, Norway |
| Translators |