| ARCHETYPE ID | openEHR-EHR-INSTRUCTION.request-pathology_test.v1 |
|---|---|
| Concept | PathologyTest Request |
| Description | Generic request for a pathology request. |
| Use | Use in most requests for a pathology test to be conducted on a patient. If there are more specific details about the test and/or specimen include this information in more detailed CLUSTER archetypes appropriate for the purpose. |
| Purpose | To request a pathology test to be performed and convey supporting clinical details. |
| References | |
| Copyright | © openEHR Foundation |
| Authors | Author name: Ian McNicoll Organisation: Ocean Informatics, United Kingdom Email: ian.mcnicoll@oceaninformatics.com Date originally authored: 08/12/2009 |
| Other Details Language | Author name: Ian McNicoll Organisation: Ocean Informatics, United Kingdom Email: ian.mcnicoll@oceaninformatics.com Date originally authored: 08/12/2009 |
| Other Details (Language Independent) |
|
| Keywords | request, refer, order, service, provide, laboratory, pathology, microbiology, haematology, diagnostic |
| Lifecycle | AuthorDraft |
| Language used | en |
| Citeable Identifier | 1013.1.1433 |
| activities | |
| Request | Request: Current Activity |
| Pathology Test Requested | Pathology Test Requested: Identification of the pathology test requested. This is often coded with an external terminology. |
| Description of Test | Description of Test: A detailed narrative description of the pathology test requested. |
| Specific details | Specific details : Structured detail defining the service requested eg CLUSTER archetype specifying the specific catheter that is to be inserted. Include: All not explicitly excluded archetypes |
| Specimen details | Specimen details: Structured detail defining the specimen. Include: All not explicitly excluded archetypes |
| Reason for request | Reason for request: A short description of the reason for the request. This is often coded with an external terminology. |
| Reason description | Reason description: A narrative description explaining the reason for request including clinical context. |
| Intent | Intent: Stated intent of the request by the referrer. |
| Urgency | Urgency: Urgency of the request.
|
| DateTime test preferred | DateTime test preferred: The preferred date and time by which the service should be performed or completed. |
| Latest DateTime test required | Latest DateTime test 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 |