Encounter (76)

#	Name	Source	Ver	Description
1	Abteilungskontakt (IST)	fhir.qpath4ms#current	R4	Profil eines Abteilungskontaktes (IST)
2	ADHA Core Encounter	au.digitalhealth.r4#current	R4	The purpose of this profile is to provide a core representation of an encounter for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia.
3	ANC Base Encounter	who.fhir.anc-cds#current	R4	ANC Base Encounter
4	ANC Encounter	who.fhir.anc-cds#current	R4	ANC Encounter
5	AU Base Encounter	hl7.fhir.au.base#current	R4	This profile defines an encounter structure that localises core concepts, including terminology, for use in an Australian context. This profile is intended to be applicable for recording details of ambulatory and non-ambulatory patient encounters in an Australian healthcare context. The purpose of this profile is to provide national level agreement on core localised concepts. This profile does not force conformance to core localised concepts. It enables implementers and modellers to make their own rules, i.e. [profiling](http://hl7.org/fhir/profiling.html), about how to support these concepts for specific implementation needs.
6	AU Core Encounter	hl7.fhir.au.core#current	R4	This profile sets minimum expectations for an Encounter resource to record, search, and fetch basic encounter information for a patient. It is based on the [AU Base Encounter](http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-encounter.html) profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets that SHALL be present in the Encounter when conforming to this profile. It provides the floor for standards development for specific uses cases in an Australian context.
7	AU Primary Care Encounter	au.csiro.fhir.au-primarycare#current	R4	Record of a patient encounter including timing, reason, type and participating practitoner. Usage Reason for Encounter - Use to record the reason, or reasons, for initiation of any type of healthcare encounter or contact between a healthcare provider and an individual who is the subject of care. The reason may be for clinical, social or administrative purposes.
8	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.
9	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.
10	CareEncounter	kl.dk.fhir.gateway#current	R4	Encounter for following up on conditions, care plans, or observations.
11	CDMH Encounter	hl7.fhir.us.cdmh#current	R4	This is the Encounter Resource profile for the IG.
12	CH ALIS Encounter Profile	ch.fhir.ig.ch-alis#current	R4	Base definition for the Encounter resource in the context of ALIS-Connect.
13	CH Core Encounter	ch.fhir.ig.ch-core#current	R4	The Encounter referenced in the CH Core profiles.
14	CH CRL Encounter Treatment Decision	ch.fhir.ig.ch-crl#0.9.0	R4	Definition of the Encounter for the treatment decision
15	CH EMS Encounter Profile	ch.fhir.ig.ch-ems#1.9.0	R4	Definition of the encounter
16	CH ORF Requested Encounter	ch.fhir.ig.ch-orf#current	R4	Profile to describe which details are represented at the requested encounter for the fulfillment of the service request. These are, for example, the status of the encounter or the class and the desired accomodation during the encounter.
17	CL Encuentro	hl7.fhir.cl.corecl#current	R4	Definición de un Encuentro clínico remoto para las necesidades de interoperabilidad en Chile.
18	CL Encuentro	hl7.fhir.cl.clcore#1.8.4	R4	Definición de un Encuentro clínico remoto para las necesidades de interoperabilidad en Chile.
19	CPG Encounter	hl7.fhir.uv.cpg#current	R4	CPG encounter represents the minimum expectations for communicating encounter information as part of a CPG case
20	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.
21	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.
22	Diagnostic Encounter	hl7.fhir.au.draft.diagnostic-orders#current	R4	Minimum Encounter for Diagnostic Request
23	EEBase Encounter	hl7.fhir.ee.base#current	R5	Encounter is an interaction between a patient and healthcare provider(s) to provide healthcare service(s) or assess a patient's health status. There are many types of encounters (such as ambulatory, inpatient, home visits, emergency and the like) which is the reason why the resource encompasses the lifecycle from pre-admission to the actual encounter (for ambulatory encounters) and admission, stay and discharge (for inpatient encounters). Encounter is primarily used to record information about the actual activities that occurred, where Appointment is used to record planned activities.
24	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.
25	Einrichtungskontakt (IST)	fhir.qpath4ms#current	R4	Profil eines Einrichtungskontaktes (IST)
26	Encounter	ndhm.in#current	R4	This profile sets minimum expectations for the Encounter resource to record, search, and fetch basic encounter information for an individual patient.
27	Encounter	kl.dk.fhir.core#current	R4	Encounters used for care and social services in Danish municipalities.
28	Encounter	hl7.eu.fhir.xpandh.hdr#current	R4	This profile defines how to represent Encounter in FHIR for the purpose of the XpanDH Hospital Discharge Report.
29	Encounter (Gatekeeper - Aragon)	hl7.eu.fhir.gk#current	R4	This profile defines how to represent Encounter in the Aragon Pilot.
30	Encounter - Birth	hl7.fhir.us.vrsandbox#current	R4	This Encounter profile represents the child's birth encounter.
31	Encounter - Birth	hl7.fhir.us.bfdr#current	R4	This Encounter profile represents the child's birth encounter.
32	Encounter - Lab Report	hl7.fhir.it.lab-report#current	R4	Profilo della risorsa Encounter utile a descrivere i dati dell'incontro per la richiesta specifica nel dominio di Referto di Laboratorio.
33	Encounter - Maternity	hl7.fhir.us.vrsandbox#current	R4	This Encounter profile represents the mother's maternity encounter.
34	Encounter - Maternity	hl7.fhir.us.bfdr#current	R4	This Encounter profile represents the mother's maternity encounter.
35	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.
36	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.
37	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.
38	Encounter Profile	hl7.fhir.ca.baseline#current	R4	Proposed constraints and extensions on the Encounter Resource
39	Encounter-IEHR	fhir.uv.crossborderdataexchange#current	R4
40	Encounter: Treatment Center	hl7.eu.fhir.idea4rc#current	R4	This profile defines how to represent data of arrival to the center and Center information in FHIR for the purpose of the IDEA4RC project.
41	Encounter: Treatment Center	hl7.eu.fhir.pcsp#current	R4	This profile defines how to represent data of arrival to the center and Center information in FHIR for the purpose of the PanCareSurPass project.
42	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.
43	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.
44	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.
45	FI Base Encounter	hl7.fhir.fi.base#current	R4	This is the Finnish base profile for the Encounter resource.
46	FollowUpEncounter	kl.dk.fhir.ffbreporting#current	R4	Encounter for following up on care plans and interventions
47	gp-Encounter	nictiz.fhir.nl.stu3.zib2017#2.2.15	R3	Contact as defined by the Dutch General Practitioners Association (Nederlands Huisartsengenootschap or NHG) based on the Dutch Health and Care Information models (Dutch: Zorginformatiebouwsteen or ZIB) version 1.0. A contact is any interaction, regardless of the situation, between a patient and the healthcare provider, in which the healthcare provider has primary responsibility for diagnosing, evaluating and treating the patient’s condition and informing the patient. These can be visits, appointments or non face-to-face interactions. A general practitioner encounter could be used to discuss multiple 'episodes'. Based on the axis op 'episode', one FHIR Encounter (Dutch: 'consult' or 'contactmoment') there will be multiple virtual partial encounters (Dutch: 'deelcontact'). The FHIR Encounter is always about the whole encounter spanning everything that was discussed, regardless of the number of 'episodes'. This profile only deals with past contacts. Future contacts can be documented in the PlannedCareActivity information model.
48	HCIM Encounter	nictiz.fhir.nl.stu3.zib2017#2.2.15	R3	Contact as defined by the Dutch Health and Care Information models (Dutch: Zorginformatiebouwsteen or ZIB) version 3.1. A contact is any interaction, regardless of the situation, between a patient and the healthcare provider, in which the healthcare provider has primary responsibility for diagnosing, evaluating and treating the patient’s condition and informing the patient. These can be visits, appointments or non face-to-face interactions. Contacts can be visits to the general practitioner or other practices, home visits, admissions (in hospitals, nursing homes or care homes, psychiatric institutions or convalescent homes) or other relevant contacts. This only includes past contacts. Future contacts can be documented in the PlannedCareActivity information model.
49	HIV Encounter	fhir.nachc.hiv-cds#current	R4	HIV Encounter
50	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
51	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
52	KLGatewayChildrenEncounter	kl.fhir.dk.children#current	R4	Encounter for health prevention and need-based visits from childrens nurses
53	ManaakiNgaTahiEncounter	cinc.fhir.ig#current	R4	Encounter FHIR resource for Manaaki Nga Tahi
54	MedComCoreEncounter	medcom.fhir.dk.core#current	R4	An 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.
55	MedComHospitalNotificationEncounter	medcom.fhir.dk.hospitalnotification#current	R4	Encounter 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.
56	MedNet Interface (MNI) - Encounter	swiss.mednet.fhir#0.15.0	R4	MedNet Interface (MNI) - Encounter Profile. An encounter will provide information about the context in which the form will be filled It is mainly used to deliver MedNet the Visit Nr (or Case Nr), and/or the orderNr from the calling System. The goal of those values is to allow saving the copy of the form and/or the later resulting report in the calling system to an internal event. It can also include informations about the priority of the request (if it is urgent or not), or the type of form that should be filled.
57	MIBaseEncounterProfile	hl7.fhir.mi.base#current	R4	MI Base Encounter Profile
58	MIPHREncounter	hl7.fhir.mi.phr#current	R4
59	NZIPS-Encounter	tewhatuora.fhir.ig.nzips#current	R4	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. Encounter is primarily used to record information about the actual activities that occurred, where Appointment is used to record planned activities.
60	Openmrs Encounter	openmrs.fhir.core#current	R4	A FHIR Encounter as understood by OpenMRS
61	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
62	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.
63	Place of delivery	who.fhir.anc-cds#current	R4	Place where the woman delivered
64	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.
65	Population Screening Encounter	hl7.fhir.be.public-health#current	R4	Encounter Profile for screening - participation in population screening
66	Pregnancy Encounters	fhir.nachc.hiv-cds#current	R4	Pregnancy Encounters
67	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.
68	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.
69	Swissnoso Encounter	ch.fhir.ig.swissnoso#1.0.0	R4	This profile constrains the Encounter resource to represent the characteristics of an encounter in the context of a report to Swissnoso.
70	Third Trimester Encounters	fhir.nachc.hiv-cds#current	R4	Third Trimester Encounters
71	TW Core Encounter	tw.gov.mohw.twcore#0.1.1	R4	此臺灣核心-就醫事件(TW Core Encounter) Profile說明本IG如何進一步定義FHIR的Encounter Resource以呈現就醫事件 [[FMM1](http://build.fhir.org/versions.html#maturity)]
72	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.
73	US Public Health Encounter	hl7.fhir.us.ph-library#current	R4	This Encounter profile represents the encounter related to a public health event
74	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.
75	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.
76	WHO Encounter	who.fhir.anc-cds#current	R4	WHO Encounter

Encounter

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.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.id

C D

Encounter.reasonReference

S C (3)

Encounter.reasonReference.type

C F (2)

Encounter.reasonReference.reference

Encounter.classHistory

Encounter.classHistory.period

Encounter.classHistory.modifierExtension

Encounter.classHistory.extension

Encounter.classHistory.id

Encounter.classHistory.class

B M

D B M

Encounter.statusHistory

Encounter.statusHistory.period

Encounter.statusHistory.status

D B M

Encounter.statusHistory.modifierExtension

Encounter.statusHistory.extension

Encounter.statusHistory.id

Encounter.hospitalization

Encounter.hospitalization.specialArrangement

D B M

Encounter.hospitalization.specialCourtesy

D B M

Encounter.hospitalization.dietPreference

D B M

Encounter.hospitalization.reAdmission

D B M

Encounter.hospitalization.preAdmissionIdentifier

Encounter.hospitalization.modifierExtension

Encounter.hospitalization.id

Encounter.hospitalization.destination

Encounter.hospitalization.destination.reference

Encounter.hospitalization.admitSource

B M

D B M

B M

D B M

Encounter.hospitalization.origin

Encounter.hospitalization.extension

S C B M (2)

S C (6)

Encounter.hospitalization.dischargeDisposition

D B M

C B M

B M

D B M

B M

Encounter.reasonReference[x]

Encounter.reasonCode

C D B M

C D

D B M

Encounter.reasonCode.coding

Encounter.reasonCode.coding.display

Encounter.reasonCode.coding.code

Encounter.reasonCode.coding.system

Encounter.reasonCode.text

Encounter.reasonCode.extension

S C D (2)

Encounter.period

C D

C I

C D

Encounter.period.end

Encounter.period.start

C D

Encounter.meta

Encounter.meta.tag

Encounter.implicitRules

Encounter.language

D B M

Encounter.text

Encounter.contained

Encounter.extension

S C

S (3)

S C B M (2)

S C (2)

S C (3)

S C (2)

S C (4)

S C (2)

S C (3)

S C (4)

S C

Encounter.extension.value[x]

B M

Encounter.modifierExtension

Encounter.identifier

S C F (2)

C D

Encounter.identifier.assigner

Encounter.identifier.period

Encounter.identifier.use

D B M

Encounter.identifier.extension

Encounter.identifier.id

Encounter.identifier.type

C F

D B M

Encounter.identifier.value

C D

Encounter.identifier.system

C D

Encounter.status

B M

D B M

Encounter.class

B M

C B M

D B M

B M

D B M

B M

C D B M

B M

D B M

Encounter.class.system

Encounter.class.code

Encounter.class.userSelected

Encounter.class.display

Encounter.class.version

Encounter.priority

B M

C B M

D B M

Encounter.priority.text

Encounter.priority.coding

Encounter.priority.coding.display

Encounter.priority.coding.code

Encounter.type

B M

C B M

C I B M

C D

B M

D B M

C B M

C D B M

C B M

B M

C B M

C D B M

D B M

C D B M

D B M

C B M

Encounter.type.extension

S C D (2)

Encounter.type.text

Encounter.type.coding

C F

Encounter.type.coding.code

Encounter.type.coding.system

Encounter.type.coding.userSelected

Encounter.type.coding.display

Encounter.type.coding.version

Encounter.serviceType

B M

C F

C D

C B M

C D B M

D B M

Encounter.serviceType.text

Encounter.serviceType.coding

Encounter.serviceType.coding.display

Encounter.serviceType.coding.code

Encounter.serviceType.extension

S C (2)

Encounter.subject

C I

C D

Encounter.subject.reference

Encounter.subjectStatus

Encounter.episodeOfCare

S C D (2)

Encounter.episodeOfCare.reference

C (2)

Encounter.episodeOfCare.identifier

C D (2)

C (2)

Encounter.basedOn

Encounter.basedOn.extension

S C

Encounter.basedOn.reference

Encounter.careTeam

Encounter.partOf

C D

Encounter.serviceProvider

C D

Encounter.serviceProvider.reference

Encounter.serviceProvider.display

Encounter.serviceProvider.identifier

Encounter.participant

C I

S C (2)

S C D (2)

S C (3)

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.id

Encounter.participant.participantRole

Encounter.participant.typeCode

C F

Encounter.participant.individual

(2)

C (2)

C D

Encounter.participant.individual.extension

S C (2)

Encounter.participant.individual.reference

Encounter.participant.individual.display

Encounter.participant.individual.type

C F

Encounter.participant.extension

S C (2)

S C D (4)

Encounter.participant.modifierExtension

Encounter.participant.type

C F

B M

C D B M (2)

C F (2)

C F D (2)

D B M

C F

Encounter.participant.type.text

Encounter.participant.type.coding

S D B M (2)

Encounter.participant.type.coding.display

Encounter.participant.type.coding.code

C F (2)

Encounter.participant.period

Encounter.participant.period.start

Encounter.participant.actor

Encounter.appointment

C D

Encounter.appointment.display

C D

Encounter.virtualService

Encounter.actualPeriod

Encounter.plannedStartDate

Encounter.plannedEndDate

Encounter.length

C D

Encounter.reason

Encounter.reason.text

Encounter.reason.extension

Encounter.reason.modifierExtension

Encounter.reason.use

Encounter.reason.value

Encounter.diagnosis

S C D (3)

Encounter.diagnosis.id

Encounter.diagnosis.rank

Encounter.diagnosis.extension

S C B M

S C (2)

S C D (2)

Encounter.diagnosis.modifierExtension

Encounter.diagnosis.condition

(2)

Encounter.diagnosis.condition.reference

Encounter.diagnosis.use

C B M

B M

C F (2)

D B M

Encounter.diagnosis.use.coding

Encounter.diagnosis.use.coding.display

Encounter.diagnosis.use.coding.code

Encounter.diagnosis.use.coding.system

Encounter.diagnosis.use.text

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

S C (5)

C D

Encounter.location.id

Encounter.location.physicalType

D B M

B M

F (4)

D B M

Encounter.location.extension

Encounter.location.modifierExtension

Encounter.location.location

C B M

Encounter.location.location.reference

Encounter.location.status

D B M

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