Use to record a formal assessment regarding the health status of an individual, usually asserted by the treating clinician and intended for sharing with third parties.
Use cases asserted by a healthcare professional include, but are not limited to:
- reduced capacity for work duties or hours;
- death certificate - using the content of the EVALUATION.cause_of_death archetype to carry the specific death-related information within a Death Certificate template;
- functional capacity;
- fitness for specific activities, including driving, flying or diving; or
- certificate of vaccination status.
Use cases asserted by an administrator include, but are not limited to: - attendance at a health facility.
Organisation: Atomica Informatics
Email: heather.leslie@atomicainformatics.com
Date originally authored: 2021-10-05
Organisation: Atomica Informatics
Email: heather.leslie@atomicainformatics.com
Date originally authored: 2021-10-05
- 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
- Original Namespace: org.openehr
- Original Publisher: openEHR Foundation
- Custodian Namespace: org.openehr
- MD5-CAM-1.0.1: 2B3CB0C5E69EAAB446A04927F70E6002
- Build Uid: 553c3f10-2917-4487-a7dd-c7417983ed96
- Revision: 1.0.0
- event
This SLOT identifies the subject of the certificate. In comprehensive openEHR EHRs this may be redundant if the formal demographics service or master patient index supplies details about the subject of the certificate. If the subject of the certificate is not the subject of care, this information may need to be entered manually, for example a parent of the child patient. In addition, when creating a screen layout or template for printing, a subset of the CLUSTER.person could be constrained to represent the precise details appropriate for the use case.
Include:
openEHR-EHR-CLUSTER.person.v1
Choice of:
Identifier
Text
For example: local information requirements or additional metadata to align with FHIR.
Include:
All not explicitly excluded archetypes
For example: Vaccination status; Fitness for flying; Medical certificate.
Vebjørn Arntzen, Oslo University Hospital, Norway (openEHR Editor)
Silje Ljosland Bakke, Helse Vest IKT AS, Norway (Nasjonal IKT redaktør)
Malin Berg, DIPS ASA, Norway
SB Bhattacharyya, Bhattacharyyas Clinical Records Research & Informatics LLP, India
Gunn Elin Blakkisrud, DIPS ASA, Norway
Marte Rime Bø, Direktoratet for e-helse, Norway
Richard Conings, Open Line, Netherlands
Kåre Flø, DIPS ASA, Norway
Rosane Gotardo, Systema Ltda., Brazil
Heather Grain, Llewelyn Grain Informatics, Australia
Mikkel Johan Gaup Grønmo, Helse Nord IKT, Norway (Nasjonal IKT redaktør)
Evelyn Hovenga, EJSH Consulting, Australia
Kanika Kuwelker, Helse Vest IKT, Norway (openEHR Editor)
Jörgen Kuylenstierna, eWeave AB, Sweden
Liv Laugen, Oslo University Hospital, Norway, Norway (openEHR Editor)
Heather Leslie, Atomica Informatics, Australia (openEHR Editor)
Hanne Marte Bårholm, Helse Vest IKT, Norway (openEHR Editor)
Paul Miller, NES Digital Service, NHS Scotland, United Kingdom
Arunakiry Natarajan, medondo, Germany
Mikael Nyström, Cambio Healthcare Systems AB, Sweden
Norwegian Review Summary, Norwegian Public Hospitals, Norway
Terje Sagmyr, Helse Vest IKT, Norway
Natalia Strauch, Medizinische Hochschule Hannover, Germany
Anders Thurin, VGR, Sweden
John Tore Valand, Helse Vest IKT, Norway
Ina Wille, Helse-Vest RHF, Norway
- German: Natalia Strauch, Medizinische Hochschule Hannover, Strauch.Natalia@mh-hannover.de
- Norwegian Bokmål: Mikkel Johan Gaup Grønmo, Helse Nord IKT, mikkel.johan.gaup.gronmo@hnikt.no, Nasjonal IKT