ID

23531

Description

Derived from www.openehr.org . Use to record information about the activities required to carry out a procedure, including the planning, scheduling, performance, suspension, cancellation, documentation and completion. This is done by the recording of data against specific activities, as defined by the 'Pathway' careflow steps in this archetype. The scope of this archetype encompasses activities for a broad range of clinical procedures performed for evaluative, investigative, screening, diagnostic, curative, therapeutic or palliative purposes. Examples range from the relatively simple activities, such as insertion of an intravenous cannula, through to complex surgical operations. Additional structured and detailed information about the procedure can be captured using purpose-specific archetypes inserted into the 'Procedure detail' slot, where required. Timings related to a procedure can be managed in one of two ways: - Using the reference model - the time for performance of any pathway step will use the ACTION time attribute for each step. - Archetyped data elements: --- the 'Scheduled date/time' data element is intended to record the precise time when the procedure is planned. Note: the corresponding ACTION time attribute for the Scheduled pathway step will record the time that the procedure was scheduled into a system, not the intended date/time on which the procedure is intended to be carried out; and --- the 'Final end date/time' is intended to record the precise time when the procedure was ended. It can be used to document the complex procedures with multiple components. Note: the corresponding ACTION time attribute for the 'Procedure performed' will document the time each component performed was commenced. This 'Final end date/time' data element will record the date/time of the final active component of the procedure. This will enable a full duration of the active procedure to be calculated. Within the context of an Operation Report, this archetype will be used to record only what was done during the procedure. Separate archetypes will be used to record the other required components of the Operation Report, including the taking of tissue specimen samples, use of imaging guidance, operation findings, post-operative instructions and plans for follow up. Within the context of a Problem list or summary, this archetype may be used to represent procedures that have been performed. The EVALUATION.problem_diagnosis will be used to represent the patient's problems and diagnoses. In practice, many procedures (for example, in ambulatory care) will occur once and not be ordered in advance. The details about the procedure will be added against the pathway step, 'Procedure completed'. In some cases a recurring procedure will be ordered, and in this situation data against the 'Procedure performed' step will be recorded on each occasion, leaving the instruction in the active state. When the last occurrence is recorded the 'Procedure completed' action is recorded showing that this order is now in the completed state. In other situations, such as secondary care, there may be a formal order for a procedure using a corresponding INSTRUCTION archetype. This ACTION archetype can then be used to record the workflow of when and how the order has been carried out. Recording information using this ACTION archetype indicates that some sort of activity has actually occurred; this will usually be the procedure itself but may be a failed attempt or another activity such as postponing the procedure. If there is a formal order for the procedure, the state of this order is represented by the Pathway step against which the data is recorded. For example, using this archetype the progressing state of a Gastroscopy order may be recorded through separate entries in the EHR progress notes at each 'Pathway' step: - record the scheduled Start date/time for the gastroscopy (Procedure scheduled); and - record that the gastroscopy procedure has been completed, including information about the procedure details (Procedure completed). Please note that in the openEHR Reference Model there is a 'Time' attribute, which is intended to record the date and time at which each pathway step of the Action was performed. This is the attribute to use to record the start of the procedure (using the 'Procedure performed' pathway step) or the time that the procedure was aborted (using the 'Procedure aborted' pathway step).

Link

www.openehr.org

Keywords

  1. 7/8/17 7/8/17 - Martin Dugas
  2. 7/8/17 7/8/17 - Martin Dugas
Uploaded on

July 8, 2017

DOI

To request one please log in.

License

Creative Commons BY-SA 3.0

Model comments :

You can comment on the data model here. Via the speech bubbles at the itemgroups and items you can add comments to those specificially.

Itemgroup comments for :

Item comments for :


No comments

In order to download data models you must be logged in. Please log in or register for free.

Procedure (EHR Archetype)

openEHR-EHR-ACTION.procedure.v1

  1. StudyEvent: openEHR-EHR-ACTION.procedure.v1
    1. openEHR-EHR-ACTION.procedure.v1
openEHR-EHR-ACTION.procedure.v1.xml
Description

openEHR-EHR-ACTION.procedure.v1.xml

Procedure
Description

A clinical activity carried out for screening, investigative, diagnostic, curative, therapeutic, evaluative or palliative purposes.

Data type

text

Alias
UMLS CUI [1]
C0184661
Tree
Description

@ internal @

Data type

text

Procedure name
Description

Identification of the procedure by name.

Data type

text

Alias
UMLS CUI [1]
C0184661
Procedure detail
Description

Structured information about the procedure.

Data type

text

Comment
Description

Additional narrative about the activity or care pathway step not captured in other fields.

Data type

text

Complication
Description

Details about any complication arising from the procedure.

Data type

text

Alias
UMLS CUI [1]
C0009566
Reason
Description

Reason that the activity or care pathway step for the identified procedure was carried out.

Data type

text

Alias
UMLS CUI [1]
C0566251
Outcome
Description

Outcome of procedure performed.

Data type

text

Alias
UMLS CUI [1]
C0085565
Description
Description

Narrative description about the procedure, as appropriate for the pathway step.

Data type

text

Tree
Description

@ internal @

Data type

text

Requestor order identifier
Description

The local ID assigned to the order by the healthcare provider or organisation requesting the service.

Data type

text

Requestor
Description

Details about the healthcare provider or organisation requesting the service.

Data type

text

Receiver order identifier
Description

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.

Data type

text

Receiver
Description

Details about the healthcare provider or organisation receiving the request for service.

Data type

text

Urgency
Description

Urgency of the procedure.

Data type

text

Alias
UMLS CUI [1]
C4049774
Final end date/time
Description

The date and/or time when the entire procedure, or the last component of a multicomponent procedure, was finished.

Data type

datetime

Total duration
Description

The total amount of time taken to complete the procedure, which may include time spent during the active phase of the procedure plus time during which the procedure was suspended.

Data type

text

Multimedia
Description

Mulitimedia representation of a performed procedure.

Data type

text

Body site
Description

Identification of the body site for the procedure.

Data type

text

Alias
UMLS CUI [1]
C1515974
Extension
Description

Additional information required to capture local content or to align with other reference models/formalisms.

Data type

text

Method
Description

Identification of specific method or technique for the procedure.

Data type

text

Scheduled date/time
Description

The date and/or time on which the procedure is intended to be performed.

Data type

datetime

Procedure type
Description

The type of procedure.

Data type

text

Procedural difficulty
Description

Difficulties or issues encountered during performance of the procedure.

Data type

text

Similar models

openEHR-EHR-ACTION.procedure.v1

  1. StudyEvent: openEHR-EHR-ACTION.procedure.v1
    1. openEHR-EHR-ACTION.procedure.v1
Name
Type
Description | Question | Decode (Coded Value)
Data type
Alias
Procedure
Item
Procedure
text
C0184661 (UMLS CUI [1])
Tree
Item
Tree
text
Procedure name
Item
Procedure name
text
C0184661 (UMLS CUI [1])
Procedure detail
Item
Procedure detail
text
Comment
Item
Comment
text
Complication
Item
Complication
text
C0009566 (UMLS CUI [1])
Reason
Item
Reason
text
C0566251 (UMLS CUI [1])
Outcome
Item
Outcome
text
C0085565 (UMLS CUI [1])
Description
Item
Description
text
Tree
Item
Tree
text
Requestor order identifier
Item
Requestor order identifier
text
Requestor
Item
Requestor
text
Receiver order identifier
Item
Receiver order identifier
text
Receiver
Item
Receiver
text
Urgency
Item
Urgency
text
C4049774 (UMLS CUI [1])
Final end date/time
Item
Final end date/time
datetime
Total duration
Item
Total duration
text
Multimedia
Item
Multimedia
text
Body site
Item
Body site
text
C1515974 (UMLS CUI [1])
Extension
Item
Extension
text
Method
Item
Method
text
Scheduled date/time
Item
Scheduled date/time
datetime
Procedure type
Item
Procedure type
text
Procedural difficulty
Item
Procedural difficulty
text

Do you need help on how to use the search function? Please watch the corresponding tutorial video for more details and learn how to use the search function most efficiently.

Watch Tutorial