| ARCHETYPE ID | openEHR-EHR-OBSERVATION.investigation_screening-JM.v0 |
|---|---|
| Concept | Diagnostic investigation screening questionnaire |
| Description | Series of questions and associated answers used to screen whether diagnostic investigations have been carried out. |
| Use | Use to create a framework for recording answers to pre-defined screening questions about diagnostic investigations or groups of investigations. The scope of diagnostic investigations includes all modalities of imaging examinations and the broadest range of laboratory and anatomical pathology tests. In addition, this archetype can also be used to record when other diagnostic tests have been carried out, such as cardiac stress testing, hearing and vision testing, electrocardiography (ECG) and electroencephalography (EEG). Common use cases include, but are not limited to:
The semantics of this archetype are intentionally loose, and querying this archetype would normally only be useful or safe within the context of each specific template. Each data element would usually be renamed in a template to represent the specific question asked. Where value sets have been proposed for common use cases, these can be adapted to align with local requirements by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. Utilising this framework within a template can enable documentation of a broad range of question/answer pairs such as:
The EVENT structure from the reference model can be used to specify whether the questions relate to a point in time or over a period of time. Use a separate instance of this archetype to distinguish between a questionnaire recording information about an investigation or test that has been done at any time in the past and information about an investigation or test done within a specified time interval - for example, the difference between "Have you ever had an INR test?" compared to "Have you had an INR test during the last four weeks?". The source of the information in a questionnaire response may vary in different contexts but can be specifically identified using the 'Information provider' element in the Reference Model. This archetype has been designed to be used as a screening tool or to record simple questionnaire-format data for use in situations such as a disease registry. If the screening questionnaire identifies an investigation has been carried out, additional details required for persistence as part of a clinical record can be captured using specific test result archetypes. |
| Misuse | Not to be used for recording an order for an investigation - use INSTRUCTION.service_request for this purpose. Not to be used for recording the progress of activities performed as part of an investigation - use appropriate ACTION archetypes for this purpose. Not to be used to record formal diagnostic test results - use appropriate OBSERVATIONS for this purpose. For example, the OBSERVATION.laboratory_test_result or OBSERVATION.imaging_examination_result. |
| Purpose | To create a framework for recording answers to pre-defined screening questions about diagnostic investigations or group of investigations, including but not limited to imaging examinations and laboratory tests. |
| References | |
| Copyright | © openEHR Foundation |
| Authors | Author name: Heather Leslie Organisation: Atomica Informatics Email: heather.leslie@atomicainformatics.com Date originally authored: 2022-10-21 |
| Other Details Language | Author name: Heather Leslie Organisation: Atomica Informatics Email: heather.leslie@atomicainformatics.com Date originally authored: 2022-10-21 |
| Other Details (Language Independent) |
|
| Keywords | investigation, screening, questionnaire, prevention, imaging, laboratory, pathology, blood, sample, sputum, EMG, ECG, hearing, test, examination, spinal fluid, biopsy, EEG, MRI, CT, X-ray, PET, ultrasound, spirometry |
| Lifecycle | in_development |
| UID | d2db06eb-f82a-41b8-b306-78f1145a1b91 |
| Language used | en |
| Citeable Identifier | 1013.1.7671 |
| Revision Number | 0.0.1-alpha |
| Archetype Concept Comment | The answers may be self-reported. |
| events | |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| data | |
| Screening purpose | Screening purpose: The context or reason for screening. This data element is intended to provide collection context for the question/answer groups when queried at a later date. It is not expected that this data element will be exposed to the individual, but only stored in data. For example: pre-admission screening, the name of the actual questionnaire or screening for previous investigations. |
| Any investigations? | Any investigations?: Is there a history of any diagnostic tests or investigations related to the screening purpose? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. Choice of:
|
| Description | Description: Narrative description about the history of any investigations relevant for the screening purpose. |
| Specific investigation | Specific investigation: Details about a specified investigation or grouping of investigations relevant for the screening purpose. Use separate instances of this CLUSTER to differentiate between specific investigations or groupings of investigations. |
| Investigation name | Investigation name: Name of the diagnostic investigation or grouping of investigations. For example: 'Blood gas', Chest Xray', 'ECG'; or 'Hearing test'. Coding of the 'Investigation name' with a terminology is preferred, where possible. |
| Done? | Done?: Is there a history of the investigation being carried out? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. Choice of:
|
| Timing | Timing: Indication of timing related to the investigation. The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when an investigation was carried out. The specific and intended semantics can be further clarified in a template. For example: the actual date and/or time; the start and stop time for the investigation; the interval of time during which the investigation was carried out; the duration of the investigation; the age of the individual at the time of the investigation; or the duration of time since it occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year. Choice of:
|
| Conclusion | Conclusion: Brief description, summary or interpretation of the investigation outcome. For example: 'All results within normal range', 'Normal', 'Further investigations needed'. This data element is not to contain a representation of the actual results or findings. In that situation, nest an appropriate CLUSTER archetype within the following 'Additional details' SLOT. |
| Additional details | Additional details: Structured details or questions about the specific investigation or group of investigations. Include: openEHR-EHR-CLUSTER.imaging_ openEHR-EHR-CLUSTER.organisation.v1 or openEHR-EHR-CLUSTER.lab_ openEHR-EHR-CLUSTER.lab_ openEHR-EHR-CLUSTER.laboratory_ openEHR-EHR-CLUSTER.lab_ openEHR-EHR-CLUSTER.lab_ openEHR-EHR-CLUSTER.lab_ openEHR-EHR-CLUSTER.lab_ openEHR-EHR-CLUSTER.lab_ openEHR-EHR-CLUSTER.specimen.v1 |
| Comment | Comment: Additional narrative about the diagnostic investigation test not captured in other fields. |
| Result details | Result details: Include: All not explicitly excluded archetypes |
| Additional details | Additional details: Structured details or questions about screening for diagnostic investigations. |
| protocol | |
| Extension | Extension: Additional information required to extend the model with local content or to align with other reference models or formalisms. For example: local information requirements; or additional metadata to align with FHIR. Include: All not explicitly excluded archetypes |
| Other contributors | Vebjørn Arntzen, Oslo University Hospital, Norway (openEHR Editor) Astrid Askeland, Dips AS, Norway Silje Ljosland Bakke, Helse Vest IKT AS, Norway (openEHR Editor) Terje Bektesevic Holmlund, UiT Norges arktiske universitet, Norway Ivar Berge, Oslo Universitetssykehus, Norway SB Bhattacharyya, Bhattacharyyas Clinical Records Research & Informatics LLP, India Randi Brendberg, Helse Nord RHF, Norway Yexuan Cheng, 浙江大学, China Are Edvardsen, SKDE, Helse Nord RHF, Norway Heike Eichele, Regionalt fagmiljø for autimse, ADHD, Tourettes syndrom og narkolepsi Helse Vest, Kronstad DPS, Haukeland universitetssykehus, Bergen, Norway Alexander Eikrem-Lüthi, Lovisenberg Diakonale Sykehus, Norway Gunn Elin Blakkisrud, DIPS ASA, Norway Kåre Flø, DIPS ASA, Norway Grant Forrest, Lunaria Ltd, United Kingdom Anca Heyd, DIPS ASA, Norway Joost Holslag, Nedap, Netherlands Evelyn Hovenga, EJSH Consulting, Australia Mikkel Johan Gaup Grønmo, Helse Nord IKT, Norway (Nasjonal IKT redaktør) Gunnar Jårvik, Helse Vest IKT AS, Norway Runar Kristiansen, DIPS AS, Norway Anjali Kulkarni, Karkinos, India Kanika Kuwelker, Helse Vest IKT, Norway (Nasjonal IKT redaktør) Jörgen Kuylenstierna, eWeave AB, Sweden Liv Laugen, Oslo universitetssykehus, Norway (Nasjonal IKT redaktør) Øygunn Leite Kallevik, Helse Bergen, Norway Heather Leslie, Atomica Informatics, Australia (openEHR Editor) Nina Louise Jebsen, Haukeland Universitetssykehus, Norway Martine Louise Nalum, DIPS AS, Norway Hanne Marte Bårholm, Helse Vest IKT, Norway (Nasjonal IKT redaktør) Svenne Naumann, Finnmarkssykehuset, Norway Terje Nordberg, Helse Bergen, Norway Mikael Nyström, Cambio Healthcare Systems AB, Sweden Bjørn Næss, DIPS ASA, Norway Jussara Rotzsch, Hospital Alemão Oswaldo Cruz, Brazil Kritika Sarkar, Karkinos Healthcare, India Ragnhild Schultz, OUS, Norway Andre Smitt-Ingebretsen, Sørlandet sykehus HF, Norway Tove Stenquist, Helseforetak, Norway Frode Stenvik, Helse Sør-Øst, Norway Natalia Strauch, Medizinische Hochschule Hannover, Germany Norwegian Review Summary, Norwegian Public Hospitals, Norway John Tore Valand, Helse Bergen, Norway (openEHR Editor) Marit Alice Venheim, Helse Vest IKT, Norway (openEHR Editor) Ina Wille, Helse-Vest RHF, Norway |
| Translators |
|