Encounter (28)

#	Name	Source	Ver	Description
1	Abteilungskontakt (IST)	fhir.qpath4ms#current	R4	Profil eines Abteilungskontaktes (IST)
2	BC Encounter Profile	hl7.fhir.us.breastcancer#0.2.0	R3	A description of an interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.
3	Cancer Encounter	hl7.fhir.us.central-cancer-registry-reporting#current	R4	This Encounter profile represents the encounter related to the cancer event. It is based on the US Core Encounter.
4	CDMH Encounter	hl7.fhir.us.cdmh#current	R4	This is the Encounter Resource profile for the IG.
5	CRD Encounter	hl7.fhir.us.davinci-crd#current	R4	This profile specifies additional extensions and constraints on the US Core Encounter profile to support coverage requirements discovery.
6	Da Vinci Admit/Discharge/Transfer Notification Encounter Profile	hl7.fhir.us.davinci-alerts#current	R4	The Da Vinci Admit/Discharge/Transfer Notification Encounter Profile is based on the [US Core Encounter Profile](http://hl7.org/fhir/us/core/STU3.1.1/StructureDefinition-us-core-encounter.html) and constrains the resources referenced by the `Encounter.Subject` to the [US Core patient Profile](http://hl7.org/fhir/us/core/STU3.1.1/StructureDefinition-us-core-patient.html) ,`Encounter.participant.individual` to the [US Core Practitioner Profile](http://hl7.org/fhir/us/core/STU3.1.1/StructureDefinition-us-core-practitioner.html), and `Encounter.Location` to the [US Core Location Profile](http://hl7.org/fhir/us/core/STU3.1.1/StructureDefinition-us-core-location.html). It also constrains these referenced resources to be found in the same message Bundle.
7	eICR Encounter	hl7.fhir.us.ecr#current	R4	This Encounter profile represents the encounter related to the event. It is based on the US Public Health Encounter profile.
8	Einrichtungskontakt (IST)	fhir.qpath4ms#current	R4	Profil eines Einrichtungskontaktes (IST)
9	Encounter - Birth	hl7.fhir.us.vrsandbox#current	R4	This Encounter profile represents the child's birth encounter.
10	Encounter - Birth	hl7.fhir.us.bfdr#current	R4	This Encounter profile represents the child's birth encounter.
11	Encounter - Maternity	hl7.fhir.us.vrsandbox#current	R4	This Encounter profile represents the mother's maternity encounter.
12	Encounter - Maternity	hl7.fhir.us.bfdr#current	R4	This Encounter profile represents the mother's maternity encounter.
13	Encounter Activity	hl7.cda.us.ccdar2dot2#current	R5	This clinical statement describes an interaction between a patient and clinician. Interactions may include in-person encounters, telephone conversations, and email exchanges.
14	Encounter Atender LE	fhir.minsal.ListaDeEspera#current	R4	Encounter Atender LE recurso que se utiliza para representar el encuentro médico, cuando se comienza a ejecutar la atención de la interconsulta.
15	Encounter Inicio LE	fhir.minsal.ListaDeEspera#current	R4	Encounter Inicio LE recurso que se utiliza para representar el encuentro médico, que representa el encuentro de cuando se solicita la interconsulta.
16	Encounter-IEHR	fhir.uv.crossborderdataexchange#current	R4
17	HIV Encounter	fhir.nachc.hiv-cds#current	R4	HIV Encounter
18	PAS Encounter	hl7.fhir.us.davinci-pas#current	R4	PAS constraints on the Encounter resource mandating support for elements relevant to details of a requested institutional stay on the prior authorization request
19	PhCP Encounter	hl7.fhir.us.phcp#1.0.0	R4	This is where the main encounter information is recorded. It includes codes for describing the care environment. This profile constrains the US Core Encounter profile. It includes value sets intended for use by pharmacy systems. Everywhere it is referenced, an unconstrained US Core Encounter reference is also allowed.
20	Planned Encounter	hl7.cda.us.ccdar2dot2#current	R5	This template represents a planned or ordered encounter. The type of encounter (e.g., comprehensive outpatient visit) is represented. Clinicians participating in the encounter and the location of the planned encounter may be captured. The priority that the patient and providers place on the encounter may be represented.
21	Pregnancy Encounters	fhir.nachc.hiv-cds#current	R4	Pregnancy Encounters
22	QICore Encounter	hl7.fhir.us.qicore#current	R4	Profile of Encounter for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors.
23	Re-Assessment Timepoints Encounter	hl7.fhir.us.pacio-rt#current	R4	Re-Assessment Timepoints Encounter is a profile of the Encounter resource that allows longer-term post-acute admissions to be structured into smaller more consumable components, in line with the longer-term clinical care and progression of a patient.
24	Third Trimester Encounters	fhir.nachc.hiv-cds#current	R4	Third Trimester Encounters
25	US Core Encounter Profile	hl7.fhir.us.core#current	R4	This profile sets minimum expectations for the Encounter resource to record, search, and fetch basic encounter information for an individual patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases.
26	US Public Health Encounter	hl7.fhir.us.ph-library#current	R4	This Encounter profile represents the encounter related to a public health event
27	US Public Health Encounter	hl7.fhir.us.ecr#current	R4	This Encounter profile represents the encounter related to the event. It is based on the US Core Encounter.
28	US Public Health Encounter	hl7.fhir.us.ph-library#current	R4	This Encounter profile represents the encounter related to the event. It is based on the US Core Encounter.

Encounter

Encounter.reasonCode

C D

Encounter.classHistory

Encounter.classHistory.class

B M

Encounter.statusHistory

Encounter.statusHistory.status

D B M

Encounter.author

Encounter.statusCode

Encounter.statusCode.code

C F

Encounter.entryRelationship

S C (3)

Encounter.entryRelationship.act

Encounter.entryRelationship.observation

C (2)

Encounter.entryRelationship.typeCode

C F

C F (2)

Encounter.performer

S C (2)

Encounter.performer.assignedEntity

Encounter.performer.assignedEntity.code

C B M

Encounter.dischargeDispositionCode

C I

Encounter.effectiveTime

Encounter.code

C B M

Encounter.code.translation

Encounter.code.originalText

Encounter.code.originalText.reference

Encounter.code.originalText.reference.value

C I

Encounter.id

Encounter.templateId

S C (2)

Encounter.templateId.extension

C F

Encounter.templateId.root

C F

Encounter.moodCode

C F

C B M

Encounter.classCode

C F

Encounter.reasonReference

S C (3)

Encounter.reasonReference.type

C F (2)

Encounter.hospitalization

Encounter.hospitalization.admitSource

B M

Encounter.hospitalization.destination

Encounter.hospitalization.dischargeDisposition

C B M

D B M

B M

Encounter.hospitalization.origin

Encounter.hospitalization.extension

S C B M (2)

Encounter.period

C D

Encounter.period.end

Encounter.period.start

Encounter.meta

Encounter.implicitRules

Encounter.language

Encounter.text

Encounter.contained

Encounter.extension

S C B M (2)

S C (2)

S C (3)

Encounter.extension.value[x]

B M

Encounter.modifierExtension

Encounter.identifier

C D

Encounter.identifier.system

Encounter.identifier.type

C F

Encounter.identifier.value

Encounter.status

D B M

Encounter.class

C B M

B M

D B M

Encounter.priority

Encounter.type

B M

C D B M

B M

C B M

C D B M

D B M

C D B M

C B M

Encounter.serviceType

C D B M

Encounter.subject

Encounter.subject.reference

Encounter.subjectStatus

Encounter.episodeOfCare

Encounter.basedOn

Encounter.basedOn.extension

S C

Encounter.careTeam

Encounter.partOf

C D

Encounter.serviceProvider

C D

Encounter.participant

S C D (2)

S C D (3)

S D (3)

S C D (3)

S D (3)

S C (2)

C D

S C D (2)

Encounter.participant.participantRole

Encounter.participant.typeCode

C F

Encounter.participant.individual

C (2)

C D

Encounter.participant.individual.reference

Encounter.participant.extension

Encounter.participant.modifierExtension

Encounter.participant.type

C F

C F D (2)

C F

Encounter.participant.period

Encounter.participant.period.start

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

S C B M

S C D (2)

Encounter.diagnosis.modifierExtension

Encounter.diagnosis.condition

Encounter.diagnosis.use

C B M

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

C D

Encounter.location.physicalType

D B M

B M

Encounter.location.extension

Encounter.location.modifierExtension

Encounter.location.location

Encounter.location.location.reference

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