| ARCHETYPE ID | openEHR-EHR-CLUSTER.problem_qualifier_local.v0 |
|---|---|
| Concept | Problem/Diagnosis qualifier |
| Description | Contextual or temporal qualifier for a specified problem or diagnosis. |
| Use | Use to record a relevant context-specific or time-specific qualifier that provides additional detail which is relevant at the time of recording or within the clinical context where a problem or diagnosis is recorded. The qualifier may not be appropriate at another time or in another clinical context. This archetype is designed to be included in Status SLOT in the EVALUATION.problem_diagnosis archetype. The intent is for the EVALUATION.problem_diagnosis archetype to hold all of the information that applies in all contexts, in contrast to this archetype describing only information that depends on the context of use. IMPORTANT NOTES FOR IMPLEMENTATION:
Full DRG coding will require the DRG-related data elements from this archetype in combination with data elements from other archetypes. |
| Misuse | Not to be used to represent a differential diagnosis - use the archetype EVALUATION.differential_diagnosis for this purpose. Not to be used to represent diagnostic certainty - use the 'Diagnostic certainty' data element within the EVALUATION.problem_diagnosis archetype. |
| Purpose | To record a clinical context-specific or time-specific qualifier for a specified problem or diagnosis. |
| References | Derived from: <Add reference to original resource here> |
| Copyright | © openEHR Foundation, HiGHmed |
| Authors | Author name: Dr Ian McNicoll Organisation: freshEHR Clinical Informatics, United Kingdom Email: ian@freshehr.com Date originally authored: 2013-05-29 |
| Other Details Language | Author name: Dr Ian McNicoll Organisation: freshEHR Clinical Informatics, United Kingdom Email: ian@freshehr.com Date originally authored: 2013-05-29 |
| Other Details (Language Independent) |
|
| Keywords | problem, active, inactive, status, episode, diagnosis |
| Lifecycle | rejected |
| UID | 72c2594f-25df-4153-91f1-e831fef5e49b |
| Language used | en |
| Citeable Identifier | 1246.145.346 |
| Revision Number | 0.0.1 |
| items | |
| Diagnostic status | Diagnostic status: Stage or phase of diagnostic process. The status is usually determined by a combination of the timing of diagnosis plus level of clinical certainty resulting from diagnostic tests and clinical evidence available. This data element and 'Diagnostic certainty' in EVALUATION.problem_diagnosis are two important axes of the diagnostic process, and valid combinations will need to be presented by software that exposes both data elements, so it is not possible for users to select conflicting combinations. Preliminary or working diagnoses are intended to represent the single most likely choice out of all differential diagnosis options.
|
| Current/Past? | Current/Past?: Category that supports division of problems and diagnoses into Current or Past problem lists. The Current/Past and Active/Inactive data elements have similar clinical impact but represent slightly different semantics. Both are actively used in different clinical settings, but usually not together. If an Active/Inactive qualifier is recorded, then this data element is likely to be redundant. An exception where a condition can be current but inactive is asthma that is not causing acute symptoms.
|
| Active/Inactive? | Active/Inactive?: Category that supports division of problems and diagnoses into Active or Inactive problem lists. The Active/Inactive and Current/Past data elements have similar clinical impact but represent slightly different semantics. Both are actively used in different clinical settings, but usually not together. If a Current/Past qualifier is recorded, then this data element is likely to be redundant. An exception where a condition can be current but inactive is asthma that is not causing acute symptoms.
|
| Resolution phase | Resolution phase: Phase of healing for an acute problem or diagnosis. For example: tracking the progress of resolution of a middle ear infection.
|
| Remission status | Remission status: Status of the remission of an incurable diagnosis. For example: the status of a cancer or haematological diagnosis.
|
| Episodicity | Episodicity: Category of this episode for the identified problem/diagnosis. For example: 'New' will enable clinicians to distinguish a new, acute episode of otitis media that may have arisen soon after a previous diagnosis, to distinguish it from an unresolved or 'Ongoing' diagnosis of chronic otitis media. Treatment of recurring, new and acute, episodes of a condition may differ significantly from the same condition that is not resolving or responding to treatment. In many situations the clinician will not be able to tell, and so indeterminate may be appropriate.
|
| Occurrence | Occurrence: Category of the occurrence for this problem or diagnosis. This data element can be an additional qualifier to the 'New' value in the 'Episodicity' value set, that is a condition such as asthma can have recurring new episodes that have periods of resolution in between. However it can be important to identify the first ever episode of asthma from all of the other episodes.
|
| Course label | Course label: Category reflecting the speed of onset and/or duration and persistence of the problem or diagnosis. Definitions of acute vs chronic will differ for each diagnosis.
|
| Diagnostic category | Diagnostic category: Category of the problem or diagnosis within a specified episode of care and/or local care context. This data element contains a value set commonly used in diagnostic categorisation. In episodic care contexts (commonly secondary care) it is common to categorise/organise diagnoses according to their relationship to the principal diagnosis being addressed during that episode of care. These categories may also be used for clinical coding, reporting and billing purposes. In some countries the diagnostic category may be known as a DRG. In addition, the free text choice permits use of other local value sets, as required. Choice of:
|
| Admission diagnosis? | Admission diagnosis?: Was the problem or diagnosis present at admission? Record as True if the problem or diagnosis was present on admission. This data element is a requirement from DRG reporting in some countries. Allowed values: {true} |
| Other contributors | Nadim Anani, Karolinska Institutet, Sweden Erling Are Hole, Helse Bergen, Norway Vebjørn Arntzen, Oslo University Hospital, Norway Koray Atalag, University of Auckland, New Zealand Silje Ljosland Bakke, Nasjonal IKT HF, Norway (openEHR Editor) Malin Berg, DIPS ASA, Norway Lars Bitsch-Larsen, Haukeland University hospital, Norway Alexander Davey, HSC NI, United Kingdom Aitor Eguzkitza, UPNA (Public University of Navarre) - CHN (Complejo Hospitalario de Navarra), Spain Arild Faxvaag, NTNU, Norway Shahla Foozonkhah, Iran ministry of health and education, Iran Einar Fosse, National Centre for Integrated Care and Telemedicine, Norway Bente Gjelsvik, Helse Bergen, Norway Heather Grain, Llewelyn Grain Informatics, Australia Sam Heard, Ocean Informatics, Australia Andreas Hering, Helse Bergen HF, Haukeland universitetssjukehus, Norway Anca Heyd, DIPS ASA, Norway Hilde Hollås, DIPS AS, Norway Evelyn Hovenga, EJSH Consulting, Australia Lars Ivar Mehlum, Helse Bergen HF, Norway Tom Jarl Jakobsen, Helse Bergen, Norway Lars Morgan Karlsen, DIPS ASA, Norway Shinji Kobayashi, Kyoto University, Japan Sabine Leh, Haukeland University Hospital, Department of Pathology, Norway Heather Leslie, Atomica Informatics, Australia (openEHR Editor) Hugh Leslie, Ocean Informatics, Australia Hallvard Lærum, Norwegian Directorate of e-health, Norway Chunlan Ma, Ocean Informatics, Australia Luis Marco Ruiz, NST, Spain Ian McNicoll, freshEHR Clinical Informatics, United Kingdom (openEHR Editor) Bjørn Næss, DIPS ASA, Norway Andrej Orel, Marand d.o.o., Slovenia Jussara Rotzsch, Hospital Alemão Oswaldo Cruz, Brazil Thomas Schopf, University Hospital of North-Norway, Norway Anoop Shah, University College London, United Kingdom Line Silsand, Universitetssykehuset i Nord-Norge, Norway Line Sæle, Nasjonal IKT HF, Norway Nyree Taylor, Ocean Informatics, Australia Richard Townley-O'Neill, Australian Digital Health Agency, Australia Jon Tysdahl, Furst medlab AS, Norway Gro-Hilde Ulriksen, Norwegian center for ehealthresearch, Norway John Tore Valand, Helse Bergen, Norway (openEHR Editor) |
| Translators |
|