| ARCHETYPE ID | openEHR-EHR-INSTRUCTION.request-report.v0 |
|---|---|
| Concept | Diagnostic report request |
| Description | Request for a diagnostic report involving the study of specific diagnostic tests. |
| Purpose | Formal request for the study of a specific number of diagnostic tests. |
| References | |
| Copyright | © Nasjonal IKT HF |
| Authors | Forfatternavn: Aitor Eguzkitza Organisasjon: Universidad Pública de Navarra - Complejo Hospitalario de Navarra E-post: aitor.eguzkiza@unavarra.es Opprinnelig skrevet dato: 2014-06-30 |
| Other Details Language | Forfatternavn: Aitor Eguzkitza Organisasjon: Universidad Pública de Navarra - Complejo Hospitalario de Navarra E-post: aitor.eguzkiza@unavarra.es Opprinnelig skrevet dato: 2014-06-30 |
| Other Details (Language Independent) |
|
| Keywords | request, diagnostic tests, report |
| Lifecycle | in_development |
| UID | 5e674d4d-bcf3-4f5d-afcb-427b1baaa937 |
| Language used | en |
| Citeable Identifier | 1078.36.823 |
| Revision Number | 0.0.1-alpha |
| activities | |
| Request | Request: Current Activity. |
| Service requested | Service requested: Identification of the service requested. This is often coded with an external terminology. |
| Description of service | Description of service: A detailed narrative description of the service requested. |
| Specific details | Specific details: Structured detail defining the service requested eg CLUSTER archetype specifying the specific catheter that is to be inserted. Inkluder: Alle ikke eksplisitt ekskluderte arketyper |
| 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. |
| Intent | Intent: Stated intent of the request by the referrer. |
| 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. Tillatte verdier: {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. Inkluder: Alle ikke eksplisitt ekskluderte arketyper |
| 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. Inkluder: Alle ikke eksplisitt ekskluderte arketyper |
| 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. Inkluder: Alle ikke eksplisitt ekskluderte arketyper |
| 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. Inkluder: openEHR-EHR-CLUSTER.distribution.v1 |
| Localisation | Localisation: Local detailed information such as billing requirements. Inkluder: Alle ikke eksplisitt ekskluderte arketyper |
| Other contributors | Heather Leslie, Ocean Informatics, Australia Ian McNicoll, Ocean Informatics, United Kingdom |
| Translators |
|