| ARCHETYPE ID | openEHR-EHR-CLUSTER.problem_status.v0 |
|---|---|
| Concept | Problem/Diagnosis status |
| Description | Context- or time-specific qualifiers for a specified problem or diagnosis. |
| Use | Use to record context-specific or time-specific qualifiers that can be used to provide additional detail when recording a problem or diagnosis that are relevant at the time of recording or within the clinical context where it is recorded, but which may not be appropriate to assume as 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. These status qualifiers should be used with care as they are variably applied in practice and interoperability cannot be assured unless usage guidelines are clearly defined within the clinical community in which the 'Problem/Diagnosis' and 'Problem status' archetype pair may be shared. The 'Unspecified' data element has been added to support addition of other qualifiers that might only be used locally or where the use case has not been clearly established at the time of this archetype being published. As other qualifiers are identified they can be added to this archetype as a backwardly compatible revision. |
| Misuse | Not to be used to represent Differential diagnosis - use the archetype EVALUATION.differential_diagnosis for this purpose. |
| Purpose | To record clinical context-specific or time-specific status qualifiers for a specified problem or diagnosis. |
| References | |
| Copyright | © openEHR Foundation |
| Authors | Author name: Dr Ian McNicoll Organisation: Ocean Informatics, United Kingdom Email: ian.mcnicoll@oceaninformatics.com Date originally authored: 2013-05-29 |
| Other Details Language | Author name: Dr Ian McNicoll Organisation: Ocean Informatics, United Kingdom Email: ian.mcnicoll@oceaninformatics.com Date originally authored: 2013-05-29 |
| Other Details (Language Independent) |
|
| Keywords | problem, active, inactive, status, episode, diagnosis |
| Lifecycle | in_development |
| UID | 3a666c91-53ba-4e54-8197-8db6e73b5357 |
| Language used | en |
| Citeable Identifier | 1013.1.1873 |
| Revision Number | 0.0.1-alpha |
| items | |
| Phase | Phase: Stage or phase of diagnostic process. The phase is usually determined by a combination of the timing of diagnosis plus availability of supporting test results and clinical advice. It can also imply a level of clinical certainty. Terms aligned with SNOMED CT.
|
| Current? | Current?: Category that supports division of problems and diagnoses into Current or Past problem lists. Aligned with SNOMEDCT.
|
| Active? | Active?: Category that supports division of problems and diagnoses into Active or Inactive problem lists.
|
| Episodicity | Episodicity: Category new, recurring and ongoing issues, problems or diagnoses. This data element is usually recorded as part of a clinical consultation.
|
| First ever? | First ever?: Is this the first ever occurrence of this problem or diagnosis? Record as True if this is the first ever occurrence of this problem or diagnosis. Allowed values: {true} |
| Course | Course: The pattern or evolution of the problem or diagnosis.
|
| DRG category | DRG category: In episodic care contexts (commonly secondary care) it is common to categorise/ organise problems according to their relationship to the principal problem or diagnosis being addressed during that episode of care. These categories may also be used for clinical coding, reporting and billing purposes.
|
| Present on admission? | Present on admission?: Was the problem or diagnosis present at admission? Record as True if the problem or diagnosis was present on admission. Used to support identification of in-admission complications among secondary diagnoses that arise during admission. Allowed values: {true} |
| Resolution | Resolution: Phase of resolution or healing of an acute problem or diagnosis.
|
| Unspecified | Unspecified: Unspecified qualifier that will be renamed, data type selected and potential value sets specified in a template. For example: The boolean data type could be used to signify that the problem/diagnosis can be included in a patient summary; the text data type could be used to categorise in a similar way to 'Current?' or Active?'; and the count data type could be used to assert a priority key or order to problems and diagnoses in a list. If any uses are identified as frequently required, they could be added explicitly to this archetype as an explicit data element. Choice of:
|
| Other contributors | Nadim Anani, Karolinska Institutet, Sweden Vebjoern Arntzen, Oslo university hospital, Norway Koray Atalag, University of Auckland, New Zealand Silje Ljosland Bakke, National ICT Norway, Norway (openEHR Editor) Lars Bitsch-Larsen, Haukeland University hospital, Norway Aitor Eguzkitza, UPNA (Public University of Navarre) - CHN (Complejo Hospitalario de Navarra), Spain Einar Fosse, National Centre for Integrated Care and Telemedicine, Norway Heather Grain, Llewelyn Grain Informatics, Australia Sam Heard, Ocean Informatics, Australia Lars Karlsen, DIPS ASA, Norway Shinji Kobayashi, Kyoto University, Japan Sabine Leh, Haukeland University Hospital, Department of Pathology, Norway Heather Leslie, Ocean Informatics, Australia (openEHR Editor) Hugh Leslie, Ocean Informatics, Australia Ian McNicoll, freshEHR Clinical Informatics, United Kingdom (openEHR Editor) Andrej Orel, Marand d.o.o., Slovenia Jussara Rotzsch, UNB, Brazil Anoop Shah, University College London, United Kingdom Norwegian Review Summary, Nasjonal IKT, Norway John Tore Valand, Helse Bergen, Norway (openEHR Editor) |
| Translators |