ARCHETYPE Problem list (openEHR-EHR-COMPOSITION.problem_list.v2)

ARCHETYPE IDopenEHR-EHR-COMPOSITION.problem_list.v2
ConceptProblem list
DescriptionA persistent and managed list of any combination of diagnoses, problems and/or procedures that may influence clinical decision-making and care provision for the subject of care.
UseUse to record a persistent and managed list of diagnoses identified, problems experienced by the subject or previous procedures performed, or, alternatively, positive statements about known exclusions or actual absence of any information about the the medical history. This list can also be utilised as a source of up-to-date medical history data for exchange or as the basis for decision support. 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-problem_diagnosis or EVALUATION.exclusion-procedure archetypes - for example: "No significant problems or diagnoses" 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. In order for this list to be accurate and safe to use as the basis for decision support activities and for exchange, 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. In a closed clinical system, it is expected that provenance of this Problem list can be managed through versioning of this COMPOSITION and its contents, with the additional option of a system-based audit trail. 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 there may be multiple Problem lists for a single subject of care, 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; and an inpatient admission may include additional issues related to immediate nursing priorities that would not be relevant once discharged home - for these purposes there is a Status SLOT in the Problem/Diagnosis archetype, which allow use of an archetype that could support 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. This archetype is usually managed as a persistent list, however there are situations where the list may be used within episodic care and require additional attributes such as context etc to enable accurate recording. The openEHR reference model currently only allows context to be recorded within Event-based COMPOSITION archetypes. As a result, this archetype has been modelled as an Event, rather than Persistent, COMPOSITION, to allow for flexibility so that some clinical systems can safely manage Problem lists for episodes of care, while others will choose to implement this COMPOSITION to act in a persistent manner.
PurposeTo record a persistent and managed list of diagnoses identified, problems experienced by the subject or previous procedures performed, that may influence clinical decision-making and care provision.
ReferencesProblem List, draft archetype [Internet]. National eHealth Transition Authority, NEHTA Clinical Knowledge Manager. Authored: 2013 Feb 19. Available at: http://dcm.nehta.org.au/ckm/#showArchetype_1013.1.1235 [accessed 2015 Apr 28].
Copyright© openEHR Foundation
AuthorsAuthor name: Heather Leslie
Organisation: Atomica Informatics
Email: heather.leslie@atomicainformatics.com
Date originally authored: 2013-02-19
Other Details LanguageAuthor name: Heather Leslie
Organisation: Atomica Informatics
Email: heather.leslie@atomicainformatics.com
Date originally authored: 2013-02-19
OtherDetails 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=Problem List, draft archetype [Internet]. National eHealth Transition Authority, NEHTA Clinical Knowledge Manager. Authored: 2013 Feb 19. Available at: http://dcm.nehta.org.au/ckm/#showArchetype_1013.1.1235 [accessed 2015 Apr 28]., current_contact=Heather Leslie, Atomica Informatics, heather.leslie@atomicainformatics.com, original_namespace=org.openehr, original_publisher=openEHR Foundation, custodian_namespace=org.openehr, MD5-CAM-1.0.1=A198E225F67F0E4A49653AC9C6EBCC0A, build_uid=8db88207-c2e3-4258-b534-84ae6f03b879, revision=2.0.1}
Keywordsproblem, list, diagnosis, diagnoses, procedure, problem list
Lifecyclepublished
UIDc9cbb493-3a5e-4780-9fc5-9384c49ffcce
Language useden
Citeable Identifier1013.1.4726
Revision Number2.0.1
AllArchetype [runtimeNameConstraintForConceptName=null, archetypeConceptBinding=null, archetypeConceptDescription=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 subject of care., archetypeConceptComment=null, otherContributors=Nadim Anani, Karolinska Institutet, Sweden
Vebjørn Arntzen, Oslo University Hospital, Norway
Koray Atalag, University of Auckland, New Zealand
Silje Ljosland Bakke, Nasjonal IKT HF, Norway (openEHR Editor)
Sistine Barretto-Daniels, Ocean Informatics, Australia
Lars Bitsch-Larsen, Haukeland University hospital, Norway
Shahla Foozonkhah, Iran ministry of health and education, Iran
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
Lars Morgan Karlsen, DIPS ASA, Norway
Shinji Kobayashi, Kyoto University, Japan
Heather Leslie, Atomica Informatics, Australia (openEHR Editor)
Hallvard Lærum, Norwegian Directorate of e-health, Norway
Ian McNicoll, freshEHR Clinical Informatics, United Kingdom (openEHR Editor)
Andrej Orel, Marand d.o.o., Slovenia
Jussara Rotzsch, Hospital Alemão Oswaldo Cruz, Brazil
Rowan Thomas, St. Vincent's Hospital Melbourne, Australia
John Tore Valand, Helse Bergen, Norway (openEHR Editor), originalLanguage=en, translators=
  • German: Sarah Ballout, MHH-Hanover, ballout.sarah@mh-hannover.de
  • Korean: Seung-Jong Yu, NOUSCO Co.,Ltd., seungjong.yu@gmail.com, Certified Board of Family Medicine in South Korea
  • Portuguese (Brazil): Vladimir Pizzo, Hospital Sirio Libanes, Brazil, vladimir.pizzo@hsl.org.br
  • Arabic (Syria): Mona Saleh
  • Dutch: Martijn van Eenennaam, Nedap Healthcare, martijn.vaneenennaam@nedap.com
, subjectOfData=unconstrained, archetypeTranslationTree=null, topLevelToAshis={identities=[], other_participations=[], events=[], details=[], provider=[], items=[], description=[], protocol=[], ism_transition=[], context=[ResourceSimplifiedHierarchyItem [path=/context/other_context[at0006]/items[at0008], code=at0008, itemType=SLOT, level=2, text=Extension, description=Additional information required to capture local context or to align with other reference models/formalisms., comment=For example: Local hospital departmental infomation or additional metadata to align with FHIR or CIMI equivalents., uncommonOntologyItems=null, occurencesFormal=0..*, occurencesText=Optional, repeating, cardinalityFormal=null, cardinalityText=null, subCardinalityFormal=null, subCardinalityText=null, dataType=CLUSTER, bindings=null, values=Include:
All not explicitly excluded archetypes, extendedValues=null]], data=[ResourceSimplifiedHierarchyItem [path=/category, code=null, itemType=UNSUPPORTEDTOPLEVELATTRIBUTE, level=0, text=Category, description=, comment=null, uncommonOntologyItems=null, occurencesFormal=null, occurencesText=null, cardinalityFormal=null, cardinalityText=null, subCardinalityFormal=null, subCardinalityText=null, dataType=UNSUPPORTEDTOPLEVELATTRIBUTE, bindings=null, values=null, extendedValues=null], ResourceSimplifiedHierarchyItem [path=/category, code=null, itemType=DV_CODED_TEXT, level=1, text=null, description=null, comment=null, uncommonOntologyItems=null, occurencesFormal=1..1, occurencesText=Mandatory, cardinalityFormal=null, cardinalityText=null, subCardinalityFormal=null, subCardinalityText=null, dataType=DV_CODED_TEXT, bindings=null, values=
  • event
, extendedValues=null]], activities=[], relationships=[], credentials=[], target=[], source=[], state=[], content=[], contacts=[], capabilities=[]}, topLevelItems={context=ResourceSimplifiedHierarchyItem [path=ROOT_/context, code=null, itemType=EVENT_CONTEXT, level=0, text=null, description=null, comment=null, uncommonOntologyItems=null, occurencesFormal=1..1, occurencesText=Mandatory, cardinalityFormal=0..1, cardinalityText=optional, subCardinalityFormal=null, subCardinalityText=null, dataType=EVENT_CONTEXT, bindings=null, values=null, extendedValues=null]}, addHierarchyItemsTo=context, currentHierarchyItemsForAdding=[ResourceSimplifiedHierarchyItem [path=/context/other_context[at0006]/items[at0008], code=at0008, itemType=SLOT, level=2, text=Extension, description=Additional information required to capture local context or to align with other reference models/formalisms., comment=For example: Local hospital departmental infomation or additional metadata to align with FHIR or CIMI equivalents., uncommonOntologyItems=null, occurencesFormal=0..*, occurencesText=Optional, repeating, cardinalityFormal=null, cardinalityText=null, subCardinalityFormal=null, subCardinalityText=null, dataType=CLUSTER, bindings=null, values=Include:
All not explicitly excluded archetypes, extendedValues=null]], minIndents={}, termBindingRetrievalErrorMessage=null]