| ARCHETYPE ID | openEHR-EHR-INSTRUCTION.request-procedure.v1 |
|---|---|
| Concept | Procedure Request |
| Description | Request for a procedure to be performed. |
| Use | Use to share details about the order or request for a procedure to be performed. This archetype has been designed to provide the core information required for a simple request for most procedures. If more specific detail is required about the procedure it can be added via CLUSTER archetypes inserted into the Specific Details slot. |
| Purpose | Provide simple and generic details about the request for a procedure to be performed. |
| References | |
| Copyright | © openEHR Foundation |
| Authors | Author name: Ian McNicoll Organisation: Ocean Informatics, United Kingdom Email: ian.mcnicoll@oceaninformatics.com Date originally authored: 2009-12-08 |
| Other Details Language | Author name: Ian McNicoll Organisation: Ocean Informatics, United Kingdom Email: ian.mcnicoll@oceaninformatics.com Date originally authored: 2009-12-08 |
| Other Details (Language Independent) |
|
| Keywords | request, refer, order, service, provide |
| Lifecycle | AuthorDraft |
| Language used | en |
| Citeable Identifier | 1013.1.722 |
| activities | |
| Request | Request: Current Activity. Action Archetype ID: openEHR-EHR-ACTION.procedure.v1 |
| Procedure requested | Procedure requested: Identification of the service requested. This is often coded with an external terminology. |
| Type of procedure | Type of procedure: Description about the type of procedure. |
| Description of Procedure | Description of Procedure: A detailed narrative description of the service requested. |
| Specific details | Specific details: Structured detail defining the service requested eg CLUSTER archetype specifying the specific details of the procedure, +/- anaesthetic requirements. Include: All not explicitly excluded archetypes |
| Reason for request | Reason for request: A short description of the reason for the request or indication. This is often coded with an external terminology. |
| Reason description | Reason description: A narrative description explaining the reason for request. |
| Objective | Objective: Details about specific objective or goal to be achieved by procedure. |
| Intent | Intent: Intended impact on underlying health condition or issue eg preventive, curative, palliative, adjunct, adjuvant or supportive. |
| Urgency | Urgency: Urgency of the request.
|
| Date &/or time service required | Date &/or time service required: The date and time that the service should be performed or completed. |
| Latest date service required | Latest date service required: The latest date that is acceptable for the service to be completed. |
| Supplementary information to follow | Supplementary information to follow: True indicates that additional information has been identified and will be forwarded when available eg incomplete pathology test results. Allowed values: {true} |
| Supplementary information expected | Supplementary information expected: Details of the nature of supplementary information that is to follow e.g name of laboratory results. |
| Patient requirements | Patient requirements: Language, transport or other personal requirements to support the patient's attendance or participation in provision of the service. Include: All not explicitly excluded archetypes |
| protocol | |
| Requestor Identifier | Requestor Identifier: The local ID assigned to the order by the healthcare provider or organisation requesting the service. This is also referred to as Placer Order Identifier. |
| Requestor | Requestor: Details about the healthcare provider or organisation requesting the service. Include: All not explicitly excluded archetypes |
| Receiver identifier | Receiver 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. |
| Receiver | Receiver: Details about the healthcare provider or organisation receiving the request for service. Include: All not explicitly excluded archetypes |
| Request status | Request status: The status of the request for service as indicated by the requester. Status is used to denote whether this is the initial request, or a follow-up request to change or provide supplementary information. |
| Distribution list for response | Distribution list for response: A list of person's or organisation who should receive copies of any communication. Include: openEHR-EHR-CLUSTER.distribution.v1 |
| Localisation | Localisation: Local detailed information such as billing requirements. Include: All not explicitly excluded archetypes |
| Other contributors | Heather Leslie, Ocean Informatics, Australia |
| Translators |