Encounter (11)

#	Name	Source	Ver	Description
1	ANC Base Encounter	who.fhir.anc-cds#current	R4	ANC Base Encounter
2	ANC Encounter	who.fhir.anc-cds#current	R4	ANC Encounter
3	CPG Encounter	hl7.fhir.uv.cpg#current	R4	CPG encounter represents the minimum expectations for communicating encounter information as part of a CPG case
4	Encounter-IEHR	fhir.uv.crossborderdataexchange#current	R4
5	EncounterRwd	hl7.fhir.uv.vulcan-rwd#current	R4	A profile on Encounter that indicates the minimum set of attributes required for finding patients who were hospitalized.
6	FHIRcast Encounter for Close Events	hl7.fhir.uv.fhircast#current	R4B	Provides guidance as to which Encounter attributes should be present and considerations as to how each attribute should be valued in all [FHIR resource]-close events.
7	FHIRcast Encounter for Open Events	hl7.fhir.uv.fhircast#current	R4B	Provides guidance as to which Encounter attributes should be present and considerations as to how each attribute should be valued in all [FHIR resource]-open events.
8	IHE PCS Encounter Clinical Subset	ihe.pcc.pcs#current	R4	An IHE PCS Encounter Complete Report resource is used to deffine the emergency medical transport encounter of a patient,with only clinically relevant infromaiton. - Identifier is Required - encounter type is Required - Service type is required if known - priority is required if known - diagnosis are required if known - service request (dispatch info) required if know
9	IHE PCS Encounter Complete Report	ihe.pcc.pcs#current	R4	An IHE PCS Encounter Complete Report resource is used to deffine the full emergency medical transport encounter of a patient, - identifiers are Required if Known - Status SHALL be Finished - Status History is required - Status History Observations are Required if Known - Class is required - Type is Required - Service type is required - Priority is required - Priority Descriptors are required if KNown - Subject is required - Based on is Required if Known - Participants are required - Participant types are required if known - Period is required - Reason code is required - Diagnosis is required - Barriers to care are required if known - MassCasualty incident is required if Known - Transport elements are required if known OPEN ISSUE: How to properly represent location type in relation to the encounter : dispatch, Scene, ambulance, destination - Location ambulance is required - Location Vehical dispatch is required if known - Location Scene is required - Location Destination is Required - Location.type in the location resource directed to a value set - Location.type extension in the location section in the encounter
10	Place of delivery	who.fhir.anc-cds#current	R4	Place where the woman delivered
11	WHO Encounter	who.fhir.anc-cds#current	R4	WHO Encounter

Encounter

Encounter.statusHistory

Encounter.id

C D

Encounter.hospitalization

Encounter.hospitalization.dischargeDisposition

Encounter.reasonReference

Encounter.reasonCode

C D B M

Encounter.period

Encounter.period.start

C D

Encounter.meta

Encounter.implicitRules

Encounter.language

Encounter.text

Encounter.contained

Encounter.extension

S C

S C (2)

S C (4)

S C

Encounter.modifierExtension

Encounter.identifier

C D

Encounter.identifier.value

Encounter.identifier.system

Encounter.identifier.use

Encounter.status

Encounter.class

Encounter.priority

C B M

Encounter.type

C B M

Encounter.serviceType

C B M

Encounter.subject

C D

Encounter.subjectStatus

Encounter.episodeOfCare

Encounter.basedOn

Encounter.careTeam

Encounter.partOf

Encounter.serviceProvider

Encounter.participant

Encounter.participant.individual

Encounter.participant.extension

Encounter.participant.modifierExtension

Encounter.participant.type

Encounter.participant.period

Encounter.participant.actor

Encounter.appointment

Encounter.virtualService

Encounter.actualPeriod

Encounter.plannedStartDate

Encounter.plannedEndDate

Encounter.length

Encounter.reason

Encounter.reason.extension

Encounter.reason.modifierExtension

Encounter.reason.use

Encounter.reason.value

Encounter.diagnosis

Encounter.diagnosis.rank

Encounter.diagnosis.extension

Encounter.diagnosis.modifierExtension

Encounter.diagnosis.condition

Encounter.diagnosis.use

Encounter.account

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

S C (5)

Encounter.location.physicalType

F (4)

Encounter.location.extension

Encounter.location.modifierExtension

Encounter.location.location

C B M

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