| ARCHETYPE ID | openEHR-EHR-ACTION.whole_transfusion_management.v0 |
|---|
| Concept | Whole transfusion management |
|---|
| Description | Procedure to transfer blood or its components from a donor to a recipient to replenish depleted blood elements. |
|---|
| Use | This archetype is used to record all or part of a blood transfusion procedure.
It represents the global capture of information about the transfusion process, i.e., the set or summary of all actions related to the administration of blood products during a clinical episode. It is not an EVALUATION archetype, as it does not represent a clinical assessment, but rather reflects the care process as it actually occurred, fulfilling legal and clinical requirements to document the execution of a prescribed transfusion.
Each administered blood product unit should be recorded using separate instances of the ACTION.unit_transfusion_management.v0 archetype, to ensure full traceability of each transfused product. This allows detailed and structured information to be captured for each unit (e.g., bag identifier, product type, transfusion start and end time, adverse reactions, etc.).
This archetype should be used to describe the transfusion procedure in an aggregated or global manner. It is especially useful when the overall process needs to be documented for legal, clinical traceability or reporting purposes. It is recommended to use it in combination with:
ACTION.unit_transfusion_management.v0, to document each transfused unit.
CLUSTER.transfusion_details (or similar), inserted in the "Additional details" slot, when more structured information is needed.
Date and time records related to the transfusion process can be managed in two ways:
Using the reference model: the time attribute of any ACTION instance indicates when the current state of the action was recorded (e.g., scheduled, started, completed).
Using archetyped data elements:
The “Scheduled date/time” element is intended to record the precise time at which the transfusion is planned to occur.
The end time of the overall transfusion process should match the end time of the last unit administered.
In cases where the transfusion of more than one type of blood product is prescribed (e.g., red blood cells and platelets), it is recommended to record a separate instance of ACTION.unit_transfusion_management for each product, as they are usually transfused separately and not simultaneously.
This main ACTION.transfusion archetype summarizes the complete transfusion process, in alignment with clinical practice, and can be complemented by individual transfusion actions to ensure comprehensive and traceable documentation of each component of the procedure. |
|---|
| Misuse | This archetype must not be used to record the instruction for a transfusion. Use the INSTRUCTION.service_request.v1 archetype for that purpose.
It must not be used to record other types of transfusions (e.g., bone marrow transfusions [transplants], stem cell transfusions, immunoglobulin therapy, platelet-rich plasma [PRP] injections, or coagulation factor concentrates).
It must also not be used to record the intravenous administration of blood-derived products when the therapeutic intent is different from that of a transfusion in the strict sense —that is, the replacement of lost blood or blood components (such as in cases of hemorrhage) or the treatment of hematopoietic deficiencies. In cases such as immunoglobulin therapy, platelet-rich plasma (PRP), or other products used as medications, these products should be considered medicinal products and the appropriate medication administration archetype should be used instead. |
|---|
| Purpose | To record detailed information about a blood transfusion procedure globally, including data on all units of blood products administered during the transfusion episode. |
|---|
| References | https://www.sciencedirect.com/science/article/pii/S2211419X13000724#:~:text=The%20bone%20marrow%20consists%20of,administered%20through%20the%20IO%20route |
|---|
| Copyright | © Departament de Salut de la Generalitat de Catalunya, openEHR Foundation |
|---|
| Authors | Author name: Ana Pascual Segura
Organisation: Modelatge del Coneixement Clínic Catsalut
Email: anapascual@catsalut.cat
Date originally authored: 2025-03-24
|
|---|
| Other Details Language | Author name: Ana Pascual Segura
Organisation: Modelatge del Coneixement Clínic Catsalut
Email: anapascual@catsalut.cat
Date originally authored: 2025-03-24
|
|---|
| Other Details (Language Independent) | - Licence: This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/.
- Custodian Organisation: openEHR Foundation
- References: https://www.sciencedirect.com/science/article/pii/S2211419X13000724#:~:text=The%20bone%20marrow%20consists%20of,administered%20through%20the%20IO%20route
- Original Namespace: org.openehr
- Original Publisher: openEHR Foundation
- Custodian Namespace: org.openehr
- MD5-CAM-1.0.1: A23FB32ED0C27B4BCE18584DD516FDF4
- Build Uid: 5d33a217-0189-4aad-9563-f5f3f3c7ead9
- Revision: 0.0.1-alpha
|
|---|
| Keywords | transfusion, blood, plasma, blood products, platelets |
|---|
| Lifecycle | in_development |
|---|
| UID | bacbf674-c06e-4e69-be97-3af78b108010 |
|---|
| Language used | en |
|---|
| Citeable Identifier | 1246.145.2986 |
|---|
| Revision Number | 0.0.1-alpha |
|---|
| description | |
|---|
| Blood product name | Blood product name: The blood product transfused.
Examples: red cells, platelets, plasma...
Choice of:
 Coded Text
 Text
|
|---|
| Number of units | Number of units: Number of units of product transfused. |
|---|
| Unit volume | Unit volume: The amount of blood product contained in each unit.
In case it is necessary to record different unit volumes for the same product, use the CLUSTER openEHR-EHR-CLUSTER.transfusion_unit. |
|---|
| Product location | Product location: The physical location of the product after delivery and prior to administration.
Choice of:
- Coded Text
- Text
|
|---|
| Description | Description: Narrative description about the transfusion. |
|---|
| Total volume administered | Total volume administered: The cumulative total volume of the blood product that has been administered. |
|---|
| Comment | Comment: Additional narrative about the activity or pathway step not captured in other fields, including details of any variance between the intended action and the action actually performed. |
|---|
| Scheduled date/time | Scheduled date/time: The date and/or time on which the transfusion is intended to be performed. |
|---|
| Additional details | Additional details: Further structured details of the action, possibly specific to a pathway step.
Include:
All not explicitly excluded archetypes |
|---|
| Adverse reaction | Adverse reaction: Additional information regarding a specific adverse reaction event caused by exposure to a specific substance.
It is strongly recommended to use the CLUSTER "Adverse reaction event".
Include:
All not explicitly excluded archetypes |
|---|
| Device details | Device details: Use to record details about durable or persisting medical device used during the transfusion.
It is strongly recommended to use the CLUSTER "Medical Device".
Include:
All not explicitly excluded archetypes |
|---|
| protocol | |
|---|
| Transfusion identifier | Transfusion identifier: Unique identifier for the transfusion, normally defined by the transfusion request.
This identifier allows linking the corresponding request with its transfusion process. |
|---|
| Requestor order identifier | Requestor order identifier: The local ID assigned to the order by the healthcare provider or organisation requesting the service.
This is equivalent to Placer Order Number in HL7 v2 specifications. |
|---|
| Receiver order identifier | Receiver order identifier: The ID assigned to the order by the healthcare provider or organisation receiving the request for service. This is also referred to as Filler Order Identifier.
This is equivalent to Filler Order Number in HL7 v2 specifications. |
|---|
| Requestor | Requestor: Details about the healthcare provider or organisation requesting the service.
Include:
All not explicitly excluded archetypes |
|---|
| Receiver | Receiver: Details about the healthcare provider or organisation receiving the request for service.
Include:
All not explicitly excluded archetypes |
|---|
| Extension | Extension: Additional information required to capture local content or to align with other reference models/formalisms.
Include:
All not explicitly excluded archetypes |
|---|
| ism_transition | |
|---|
| Transfusion planned | Transfusion planned: Transfusion has been planned.
Current state: planned |
|---|
| Blood products ordered | Blood products ordered: The blood products have been ordered.
Current state: planned |
|---|
| Blood products delivered | Blood products delivered: The blood products have been delivered to the physical place where the transfusion will take place.
Current state: planned |
|---|
| Transfusion scheduled | Transfusion scheduled: Transfusion has been scheduled to be performed.
Current state: scheduled |
|---|
| Transfusion postponed | Transfusion postponed: Transfusion has been postponed.
Current state: postponed |
|---|
| Transfusion cancelled | Transfusion cancelled: The transfusion has been cancelled as no longer appropriate or required.
Current state: cancelled |
|---|
| Transfusion started | Transfusion started: Administration of the first unit of blood product has commenced.
Current state: active |
|---|
| Transfusion restarted | Transfusion restarted: Administration of one unit of blood product has commenced again.
Current state: active |
|---|
| Transfusion suspended | Transfusion suspended: The transfusion has been suspended and may restart.
Current state: suspended |
|---|
| Transfusion abandoned | Transfusion abandoned: An ongoing blood transfusion is discontinued before its completion.
Current state: aborted |
|---|
| Transfusion completed | Transfusion completed: All blood products have been administered.
Current state: completed |
|---|
| Other contributors | Laura Moral López, Modelatge del Coneixement Clínic Catsalut, Spain |
|---|
| Translators | - Catalan: Ana Pascual Segura, Laura Moral López, Modelatge del Coneixement Clínic Catsalut, anapascual@catsalut.cat, lauramoral@catsalut.cat
- Spanish (Spain): Ana Pascual Segura, Laura Moral López, Modelatge del Coneixement Clínic Catsalut, anapascual@catsalut.cat, lauramoral@catsalut.cat
|
|---|