Consider creation of ADMIN.reason_for_contact

Description

From EVAL.reason_for_encounter discussion - "if we frame the EVALUATION as for prospective use, recorded prior to or at the beginning of an Encounter and the ADMIN entry to support categorisation after post consultation from a contact type/service POV and Problem/Diagnosis to record the conclusion from a clinical POV."
The RfContact could hold national value sets used for reporting desgnated by coders or clinicians after a clinical event or episode.
See more details in the discussion: https://ckm.openehr.org/ckm/archetypes/1013.1.290/discussion

Priority

Lowest

Assignee

Unassigned

Reporter

Heather Leslie

Labels

None
Configure