ARCHETYPE Problem list (openEHR-EHR-SECTION.problem_list.v0)

ARCHETYPE IDopenEHR-EHR-SECTION.problem_list.v0
ConceptProblem list
DescriptionFramework for consistent modelling of content within a template for a Problem list.
Use

Use to provide a framework and design guidance for consistent modelling of content within a template for a Problem list as a persistent and managed list of any combination of diagnoses, problems and/or procedures that may influence clinical decision-making and care provision for the individual.

This archetype is intended to be used within the COMPOSITION.problem_list or as one component of other COMPOSITION archetypes. For example: complex documents, such as a discharge summary or referral.

This list can be comprised of three types of statements, each represented by specific archetypes:

  • statements about the positive presence of problems, diagnoses or previous procedures are recorded using the EVALUATION.problem_diagnosis and/or ACTION.procedure archetypes; OR
  • statements about the positive exclusion of problems, diagnoses or previous procedures can be recorded using the specific EVALUATION.exclusion_global archetype - for example: 'No significant problems or diagnoses' and/or 'No history of significant operations or procedures'; OR
  • statements about no information being available - neither a positive presence of a problem, diagnosis or procedure performed nor a positive exclusion - can be recorded using the EVALUATION.absence archetype.

While it may be ideal to have only one Problem list for each subject of care, it is more realistic to expect that in a distributed environment, multiple Problem lists for a single individual may coexist, each managed and prioritised for a specific clinician, episode of care or other context. For example, a Problem list for a primary care clinician may be a very different configuration to that which is useful for a specialist surgeon or for reference during a hospital inpatient episode. In primary care it is common to organise the Problem list based on active or inactive problems or diagnoses; specialists may prefer to see their list organised around primary diagnoses which are related to their specific speciality and secondary ones which are not; an inpatient admission may include additional issues related to immediate nursing priorities that would not be relevant once discharged home. For these purposes, the CLUSTER.problem_qualifier archetype, nested within the Status SLOT in the Problem/Diagnosis archetype supports the use of qualifiers that will supprt clinical systems to organise Problem lists according to the preference of the clinical users of the system, without perpetuating these contextual status labels to other clinical scenarios or for persistence.

In order for this list to be accurate and safe to use as the basis for decision support activities and for exchange, the content of this Problem List should ideally be curated by a clinician responsible for the health record, rather than managed automatically by the clinical system through business rules alone.

PurposeTo provide a framework and design guidance for consistent modelling of content within a template for a Problem list.
References
Copyright© openEHR Foundation
AuthorsNom de l'autor: Heather Leslie
Organització: Atomica Informatics
Correu electrònic: heather.leslie@atomicainformatics.com
Data d'autor original: 2010-07-03
Other Details LanguageNom de l'autor: Heather Leslie
Organització: Atomica Informatics
Correu electrònic: heather.leslie@atomicainformatics.com
Data d'autor original: 2010-07-03
Other Details (Language Independent)
  • Licence: This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/.
  • Custodian Organisation: openEHR Foundation
  • References:
  • Current Contact: Heather Leslie, Atomica Informatics
  • Original Namespace: org.openehr
  • Original Publisher: openEHR Foundation
  • Custodian Namespace: org.openehr
  • MD5-CAM-1.0.1: 8367D4F2CF2BA5BE59DC4442FD28C085
  • Build Uid: 46c18c89-3428-4e56-8aaa-33e4907ea711
  • Revision: 0.0.1-alpha
Keywordsproblem, diagnosis, exclusion, absence, known, list, diagnoses, procedure
Lifecyclein_development
UID496598a7-dcfa-45fb-8886-f5b76c2333d9
Language useden
Citeable Identifier1380.146.110
Revision Number0.0.1-alpha
Archetype Concept CommentIntended to be used within the COMPOSITION.problem_list.
items
Problems, diagnoses, concerns or health issue threadsProblems, diagnoses, concerns or health issue threads: Positive statements about the presence of problems, diagnoses, concerns or health issue threads.
Incloure:
openEHR-EHR-EVALUATION.problem_diagnosis.v1 i especialitzacions
ProceduresProcedures: Positive statements about the presence of procedures that have been performed.
Incloure:
openEHR-EHR-ACTION.procedure.v1 i especialitzacions
Exclusion statementExclusion statement: A positive statement about the exclusion of known problems, diagnoses and procedures.
For example: "No problems or diagnoses" or No operations or procedures".
Incloure:
openEHR-EHR-EVALUATION.exclusion_global.v1 i especialitzacions
Absent informationAbsent information: A positive statement that no information is available about problems, diagnoses or procedures.
For example: "No information available concerning procedures".
Incloure:
openEHR-EHR-EVALUATION.absence.v2 i especialitzacions
Other contributorsNadim Anani, Karolinska Institutet, Sweden
Vebjoern Arntzen, Oslo university hospital, Norway
Koray Atalag, University of Auckland, New Zealand
Silje Ljosland Bakke, Bergen Hospital Trust, Norway (openEHR Editor)
Sistine Barretto-Daniels, Ocean Informatics, Australia
Lars Bitsch-Larsen, Haukeland University hospital, Norway
Shahla Foozonkhah, Ocean Informatics, Australia
Einar Fosse, National Centre for Integrated Care and Telemedicine, Norway
Sebastian Garde, Ocean Informatics, Germany
Heather Grain, Llewelyn Grain Informatics, Australia
Sam Heard, Ocean Informatics, Australia
Lars Karlsen, DIPS ASA, Norway
Shinji Kobayashi, Kyoto University, Japan
Heather Leslie, Ocean Informatics, Australia (openEHR Editor)
Hallvard Lærum, Oslo University Hospital, Norway
Ian McNicoll, freshEHR Clinical Informatics, United Kingdom (openEHR Editor)
Andrej Orel, Marand d.o.o., Slovenia
Jussara Rotzsch, UNB, Brazil
Rowan Thomas, St. Vincent's Hospital Melbourne, Australia
Heath Frankel, Ocean Informatics, Australia
Translators
  • alemany: Natalia Strauch, Medizinische Hochschule Hannover, Strauch.Natalia@mh-hannover.de
  • espanyol (Argentina): Alan March, Hospital Universiatario Austral, Pilar, Buenos Aires, Argentina., alandmarch@gmail.com, MD
  • portuguès (Brasil): Adriana Kitajima, Débora Farage, Fernanda Maia, Laíse Figueiredo, Marivan Abrahão, Core Consulting, contato@coreconsulting.com.br, Hospital Alemão Oswaldo Cruz (HAOC)