Encounter (4)

#NameSourceVerDescription
1CareEncounterkl.dk.fhir.gateway#currentR4Encounter for following up on conditions, care plans, or observations.
2FollowUpEncounterkl.dk.fhir.ffbreporting#currentR4Encounter for following up on care plans and interventions
3MedComCoreEncountermedcom.fhir.dk.core#currentR4An interaction between a patient/citizen and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient/citizen.
4MedComHospitalNotificationEncountermedcom.fhir.dk.hospitalnotification#currentR4Encounter derivation that handles hospital notification when a patient is admitted to a hospital. The hospital notification is always send from a hospital. The receiver of the message is the patients home municipalicy. The hospital notification is send for example when patient is admitted, on leave, returned from leave, finished hospital stay.
1 2 3 4
Encounter I
Encounter.hospitalization C C C
Encounter.reasonReference C C C
Encounter.reasonCode C C C
Encounter.period C C C D
Encounter.period.end C C D
Encounter.period.start C C C D
Encounter.classHistory C C
Encounter.statusHistory C C
Encounter.meta
Encounter.implicitRules
Encounter.language
Encounter.text
Encounter.contained
Encounter.extension S C (2)
Encounter.modifierExtension
Encounter.identifier C C
Encounter.status F B M
Encounter.class F F B M B M
Encounter.class.userSelected C C
Encounter.class.display C C
Encounter.class.version C C
Encounter.priority C C C
Encounter.type C B M C B M C
Encounter.type.text C C
Encounter.type.coding C F C F
Encounter.type.coding.userSelected C C
Encounter.type.coding.display C C
Encounter.type.coding.version C C
Encounter.serviceType C C C
Encounter.subject C C C
Encounter.subjectStatus
Encounter.episodeOfCare C C S C D (2) S C D (2)
Encounter.episodeOfCare.reference C (2)
Encounter.episodeOfCare.identifier C D (2) C (2)
Encounter.basedOn C C C
Encounter.careTeam
Encounter.partOf C C C
Encounter.serviceProvider C C C
Encounter.participant C C C
Encounter.participant.extension
Encounter.participant.modifierExtension
Encounter.participant.type
Encounter.participant.period
Encounter.participant.actor
Encounter.appointment C C C
Encounter.virtualService
Encounter.actualPeriod
Encounter.plannedStartDate
Encounter.plannedEndDate
Encounter.length C C C
Encounter.reason
Encounter.reason.extension
Encounter.reason.modifierExtension
Encounter.reason.use
Encounter.reason.value
Encounter.diagnosis C C C
Encounter.diagnosis.extension
Encounter.diagnosis.modifierExtension
Encounter.diagnosis.condition
Encounter.diagnosis.use
Encounter.account C C C D
Encounter.dietPreference
Encounter.specialArrangement
Encounter.specialCourtesy
Encounter.admission
Encounter.admission.extension
Encounter.admission.modifierExtension
Encounter.admission.preAdmissionIdentifier
Encounter.admission.origin
Encounter.admission.admitSource
Encounter.admission.reAdmission
Encounter.admission.destination
Encounter.admission.dischargeDisposition
Encounter.location C C C
Encounter.location.extension
Encounter.location.modifierExtension
Encounter.location.location
Encounter.location.status
Encounter.location.form
Encounter.location.period
S: There is slicing defined in the element(s)
C: There is cardinality erstrictions defined in the element(s)
I: There is invariants defined in the element(s)
F: There is a fixed or pattern value defined in the element(s)
D: There is document provided in the element(s)
B: There is terminology bindings defined in the element(s)
M: At least one of the element(s) has must-support = true
(N): The number of elements if > 1

Produced 08 Sep 2023