Enrolling a Patient in an Episode Of Care
Technical description of how to enrol a patient in an episode of care.
Establishing a Citizen as a Patient
The Patient resource is a central resource in the eHealth Infrastructure. It plays several 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 Patients 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 episodes of care and other clinical resources.
Ensuring a Match Between CRN and Citizen
To verify the correspondence between the Citizen name and CRN, a lookup can be made with a 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 an introduction to use and elements.
Creating the EpisodeOfCare
The EpisodeOfCare is created by invoking $create-episode-of-care on the CarePlan Service.
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
toactive
through an EpisodeOfCare HTTP-Patch.Setting a status change to
active
in theEpisodeOfCare.ehealth-statusschedule
resulting in an automatic status change in the future.
Maintaining EpisodeOfCare Status
EpisodeOfCare.status
can be adjusted in two ways through the use of EpisodeOfCare HTTP-Patch (Update is not exposed):
Setting
EpisodeOfCare.status
directlySetting a scheduled status change by updating
EpisodeOfCare.ehealth-statusschedule
scheduled changes are applied when the ApplyPlannedChangesJob is run. (see Automated Processing | AutomatedProcessing AutomatedApplicationofPlannedChanges(EpisodeOfCare,CarePlan... )
Allowed status changes:
From
planned
toactive
,onhold
,waitlist
,cancelled
, orentered-in-error
From
active
toonhold
,finished
,cancelled
, orentered-in-error
From
waitlist
toplanned
,active
,onhold
,cancelled,
orentered-in-error
From
onhold
toactive
,finished
,cancelled
, orentered-in-error
From
finished
toentered-in-error
oractive
See implementation guide: EpisodeOfCare.status
Maintaining the set of CareTeam involved in the EpisodeOfCare
Over the lifecycle of an EpisodeOfCare, the set of CareTeam involved might change. Adjustment of CareTeam involved can be performed in several ways:
Through EpisodeOfCare Patch
Setting the
EpisodeOfCare.team
Setting the scheduled team changes in
EpisodeOfCare.ehealth-teamschedule
Through EpisodeOfCare$update-care-teams
Adjusting the Period
The period in which the EpisodeOfCare is applicable is reflected in the EpisodeOfCare.period
. Adjustment of EpisodeOfCare.period
is performed through EpisodeOfCare Patch.