Establishing a Citizen as a Patient
The Patient resource is a central resource in the eHealth Infrastructure. It plays a number of different roles:
Conveys basic information about the patient (name, address, birth date, gender, civil registration number, demographics information, etc.)
Conveys extended information about the patient
Contact information
Language / Need for an interpreter
Temporary addresses
General practitioner
A Patient is considered a 'singleton' in the eHealth Infrastructure. The patient is primarily a container for demographic information. While it is allowed according to the FHIR specification to have multiple different logical Patient for the same person, it does not fit the case for the infrastructure and the Danish modelling of patient information. As such, the patient resource is shared across different episode of cares and other clinical resources.
Ensuring Match Between CRN and Citizen
In order to verify correspondence between Citizen name and CRN, a lookup can be made with Person name lookup, based on the CRN given in the input Person resource.
Establishing the Patient
Adding a Related Person
Creating and Maintaining an EpisodeOfCare
See EpisodeOfCare for introduction to use and elements.
Creating the EpisodeOfCare
The EpisodeOfCare is created by invoking $create-episode-of-care.
Preparing Conditions
An EpisodeOfCare relates to one or more conditions. These must be created as part of the $create-episode-of-care operation by including them in the input bundle.
Creating a Consent
Prerequisite to activating the EpisodeOfCare, the citizen’s consent to undergo/be enrolled to the EpisodeOfCare and comprised CarePlan resources must be registered in a Consent. The Consent is created through Consent Create and must contain details as described in the Consent introduction.
Activating the EpisodeOfCare
An EpisodeOfCare is activated by setting the status
to active
through a EpisodeOfCare Update.