Type: openEHR ARCHETYPE
Purpose: To record information about the activities required to carry out a specific test, including the planning, scheduling, performance, suspension, cancellation, documentation and completion.
Use: Use to record information about the activities required to carry out a testing activity, including the planning, scheduling, performance, suspension, cancellation, documentation and completion. This is done by the recording any or all of the data element against appropriate activities, as defined by the 'Pathway' care steps in this archetype.
The scope of this archetype encompasses activities for a broad range of simple clinical testing activities performed for evaluative, investigative, screening or diagnostic purposes. Complex testing activities, in particular where there may be more specific pathway steps or additional data elements, should be recorded using specific archetypes for the purpose.
Additional structured and detailed information about the test can be captured using purpose-specific archetypes inserted into the 'Test detail' slot, where required.
'End date/time' has not been specifically modelled in this archetype as this is the date/time that is recorded (per the reference model) as each action or care pathway step is completed.
Within the context of an test report, this archetype will be used to record only what was done during the test itself. Separate archetypes will be used to record the other required components of the test report, including the actual results (as OBSERVATIONs) and plans for followup (as INSTRUCTIONs).
In practice, many tests (for example, in ambulatory care) will occur once and not be ordered in advance. The pathway step, ‘Test completed’ (or ‘Failed attempt’, or 'Test abandoned’) will be recorded and the details added. In some cases a recurring test will be ordered, and in this situation data against the 'Test performed' step will be recorded on each occasion, leaving the instruction in the active state. When the last occurrence is recorded the ‘Test completed’ action is recorded showing that this order is now in the closed state.
In other situations there may be a formal order for a test 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.
Misuse: null
| ARCHETYPE ID | openEHR-EHR-ACTION.test.v0 |
|---|---|
| Concept | Test |
| Description | A clinical activity carried out for assessment or testing purposes. |
| Use | Use to record information about the activities required to carry out a testing activity, including the planning, scheduling, performance, suspension, cancellation, documentation and completion. This is done by the recording any or all of the data element against appropriate activities, as defined by the 'Pathway' care steps in this archetype. The scope of this archetype encompasses activities for a broad range of simple clinical testing activities performed for evaluative, investigative, screening or diagnostic purposes. Complex testing activities, in particular where there may be more specific pathway steps or additional data elements, should be recorded using specific archetypes for the purpose. Additional structured and detailed information about the test can be captured using purpose-specific archetypes inserted into the 'Test detail' slot, where required. 'End date/time' has not been specifically modelled in this archetype as this is the date/time that is recorded (per the reference model) as each action or care pathway step is completed. Within the context of an test report, this archetype will be used to record only what was done during the test itself. Separate archetypes will be used to record the other required components of the test report, including the actual results (as OBSERVATIONs) and plans for followup (as INSTRUCTIONs). In practice, many tests (for example, in ambulatory care) will occur once and not be ordered in advance. The pathway step, ‘Test completed’ (or ‘Failed attempt’, or 'Test abandoned’) will be recorded and the details added. In some cases a recurring test will be ordered, and in this situation data against the 'Test performed' step will be recorded on each occasion, leaving the instruction in the active state. When the last occurrence is recorded the ‘Test completed’ action is recorded showing that this order is now in the closed state. In other situations there may be a formal order for a test 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. |
| Purpose | To record information about the activities required to carry out a specific test, including the planning, scheduling, performance, suspension, cancellation, documentation and completion. |
| References | |
| Copyright | © openEHR Foundation |
| Authors | Author name: Heather Leslie Organisation: Ocean Informatics Email: heather.leslie@oceaninformatics.com Date originally authored: 2015-01-29 |
| Other Details Language | Author name: Heather Leslie Organisation: Ocean Informatics Email: heather.leslie@oceaninformatics.com Date originally authored: 2015-01-29 |
| Other Details (Language Independent) |
|
| Keywords | test |
| Lifecycle | in_development |
| UID | 9da3cfa9-69c5-41be-8d1b-d1b53002db77 |
| Language used | en |
| Citeable Identifier | 1013.1.1843 |
| Revision Number | 0.0.1-alpha |
| description | |
| Test name | Test name: The name of the test (to be) performed. Coding of the specific procedure with a terminology is preferred, where possible. |
| Description | Description: Narrative description about the identified test (appropriate for the identified pathway step). For example: a description about the performance and findings from the the examination for the 'Test completed' step; details about the failed attempt for the 'Test failed' step. |
| Test detail | Test detail: Structured information about the test. Use to capture detailed, structured information against a pathway step. For example the method & technique planned, for 'Test planned', or the method & technique actually carried out for 'Test completed'. Include: All not explicitly excluded archetypes |
| DateTime Scheduled | DateTime Scheduled: The scheduled time of appointment for the test. This data element is only applicable for the 'Test scheduled' pathway step. |
| Reason | Reason: Reason that the activity or care pathway step for the identified examination was carried out. For example, the reason for the cancellation or suspension of the test. Coding of the specific procedure with a terminology is preferred, where possible. |
| Comment | Comment: Additional narrative about the activity or care pathway step not captured in other fields. |
| ism_transition | |
| Test planned | Test planned: The test is recommended or planned, but not implemented in any way. Current state: planned |
| Test ordered | Test ordered: The test has been ordered or requested. Current state: planned |
| Test postponed | Test postponed: The test was postponed to another time, before commencement of the test. Current state: postponed |
| Test cancelled | Test cancelled: The test was cancelled, before commencement of the test. Current state: cancelled |
| Test declined | Test declined: * Current state: cancelled |
| Test expired | Test expired: * Current state: cancelled |
| Test scheduled | Test scheduled: An appointment has been made for the test. Current state: scheduled |
| Test completed | Test completed: The test has been carried out and fully completed Current state: active |
| Test suspended | Test suspended: The test was stopped part way through, without completion. Current state: suspended |
| Test abandoned | Test abandoned: The test was commenced but abandoned without results. Current state: aborted |
| Activity completed | Activity completed: The entire activity described by the original order or instruction has been completed and closed in the clinical system. Current state: completed |
| protocol | |
| Requestor identifier | Requestor identifier: The local ID assigned to the order by the healthcare provider or organisation requesting the service. This can also be 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 the Test. |
| Receiver | Receiver: Details about the healthcare provider or organisation receiving the request for the Test. Include: All not explicitly excluded archetypes |
| Other contributors | |
| Translators |