DiagnosticReport (70)

#NameSourceVerDescription
1ADHA Core DiagnosticReportau.digitalhealth.r4#currentR4The purpose of this profile is to define a core representation of a diagnostic report issued by the diagnostic service provider to support the electronic exchange of the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. This profile is intended to be capable of supporting reporting for specialist and other diagnostic disciplines that are not pathology or imaging.
2ADHA Pathology Reportau.digitalhealth.r4#currentR4The purpose of this profile is to represent a pathology report issued by a diagnostic service provider to support the electronic exchange of the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. This profile is intended to be capable of supporting reporting for all pathology disciplines (e.g. including microbiology, histopathology, cytology, blood transfusion) with the exception of genomics.
3Argonaut DiagnosticReport Profilefhir.argonaut.r2#1.0.0R2
4Argonaut Imaging Reportsfhir.argonaut.clinicalnotes#1.0.0R3
5AU Base Diagnostic Imaging Reporthl7.fhir.au.base#currentR4This profile defines a diagnostic report structure to represent a diagnostic imaging report issued by a diagnostic service provider in an Australian context.
6AU Base Diagnostic Reporthl7.fhir.au.base#currentR4This profile defines a diagnostic report structure that localises core concepts, including identifiers and terminology, for use in an Australian 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.
7AU Base Pathology Reporthl7.fhir.au.base#currentR4This profile defines a diagnostic report structure to represent a pathology report issued by a diagnostic service provider in an Australian context. This profile is intended to be capable of supporting reporting for all pathology disciplines (e.g. including microbiology, histopathology, cytology, blood transfusion) with the exception of genomics. This profile does not provide full support for structured pathology reporting. It is expected that this support is best handled by a set of profiles that represent the structured reporting requirements for each specific protocol (see for example [RCPA’s structured pathology reporting of cancer](https://www.rcpa.edu.au/Library/Practising-Pathology/Structured-Pathology-Reporting-of-Cancer)); this is not in the scope of this implementation guide at this time.
8AU Core DiagnosticReporthl7.fhir.au.core#currentR4This profile sets minimum expectations for a DiagnosticReport resource to record, search, and fetch diagnostic reports associated with a patient. It is based on the [AU Base Diagnostic Report](http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-diagnosticreport.html) profile and identifies the *additional* mandatory core elements, extensions, vocabularies and value sets that **SHALL** be present in the DiagnosticReport when conforming to this profile. It provides the floor for standards development for specific uses cases in an Australian context.
9Batch Analysishl7.fhir.us.pq-cmc#currentR5Batch or lot release testing to ensure that pharmaceutical products meet the product specification.
10BeLaboratoryReporthl7.fhir.be.lab#currentR4Belgian profile for a laboratory report
11BioSignalReport-IEHRfhir.uv.crossborderdataexchange#currentR4
12Breast Imaging Reporthl7.fhir.us.breast-radiology#currentR4Breast Imaging Diagnostic Report.
13CH ELM DiagnosticReport: Laboratory Reportch.fhir.ig.ch-elm#currentR4This CH ELM base profile constrains the DiagnosticReport resource for the purpose of laboratory test reports.
14CH Lab DiagnosticReport: Laboratory Reportch.fhir.ig.ch-lab-report#currentR4This profile constrains the DiagnosticReport resource for the purpose of laboratory test reports in Switzerland.
15CH Lab DiagnosticReport: Laboratory Reportch.fhir.ig.ch-laboratory-report#currentR4This profile constrains the DiagnosticReport resource for the purpose of laboratory test reports in Switzerland.
16Diagnostic Report for Report and Note Exchange Profilehl7.fhir.ca.baseline#currentR4Proposed constraints and extensions on the Diagnostic Report Resource to support collection of diagnostic report information for reports and notes. Generated as a first step toward creating a set of Canadian Baseline FHIR profiles.
17DiagnosticReport (AU IPS)hl7.fhir.au.ips#currentR4This profile is based on the UV profile, with Australian rules added as well (by reference to the Australian profile)
18DiagnosticReport (IPS)hl7.fhir.uv.ips#currentR4This profile constrains the DiagnosticReport resource to represent diagnostic test and procedure reports in a patient summary.
19DiagnosticReport - At-Home In-Vitro Resultshl7.fhir.us.home-lab-report#currentR4This profile constrains the US Core Diagnostic Report for Laboratory Results profile to At-Home In-Vitro Tests.
20DiagnosticReport - At-Home In-Vitro Results - COVID-19hl7.fhir.us.home-lab-report#currentR4This profile further constrains the DiagnosticReport - At-Home In-Vitro Results profile to COVID-19 At-Home In-Vitro Tests.
21DiagnosticReport - Lab Reporthl7.fhir.it.lab-report#currentR4Descrizione della risorsa DiagnosticReport per la descrizione delle informazioni cliniche del dominio di Lab Report.
22DiagnosticReport - Stability Study Results dx-PQhl7.fhir.uv.dx-pq#currentR5Section 11 - Stability Study - Results
23DiagnosticReport - Toxicology Lab Result to MDIhl7.fhir.us.mdi#currentR4This profile contains constraints to the US Core Diagnostic Report Profile to address the use case for sending data from a forensic toxicology LIMS to an MDI CMS. Each analyzed specimen, represented by a Specimen - Toxicology Lab resource, must be referenced by at least one Observation - Toxicology Lab Result and may be referenced by more than one Observation - Toxicology Lab Result. For specimens received but not analyzed, the laboratory should provide a reason for no analysis in the DiagnosticReport.conclusion and/or each unanalyzed specimen’s Specimen - Toxicology Lab Specimen.note.
24DiagnosticReport - Toxicology Lab Result to MDIhl7.fhir.us.vrsandbox#currentR4This profile contains constraints to the US Core Diagnostic Report Profile to address the use case for sending data from a forensic toxicology LIMS to an MDI CMS. Each analyzed specimen, represented by a Specimen - Toxicology Lab resource, must be referenced by at least one Observation - Toxicology Lab Result and may be referenced by more than one Observation - Toxicology Lab Result. For specimens received but not analyzed, the laboratory should provide a reason for no analysis in the DiagnosticReport.conclusion and/or each unanalyzed specimen’s Specimen - Toxicology Lab Specimen.note.
25DiagnosticReport Contextihe.rad.ira#currentR5IHE IRA DiagnosticReport-open report context
26DiagnosticReport Profile for Results Reportinghl7.fhir.ca.baseline#currentR4Proposed constraints on the DiagnosticReport resource for the minimal set of data to query and retrieve diagnostic reports associated with laboratory and other results
27DiagnosticReport-IEHRfhir.uv.crossborderdataexchange#currentR4
28DiagnosticReport: Laboratory Reporthl7.fhir.eu.laboratory#currentR4DiagnosticReport used to represent an entry of a Laboratory Report, including its context, for the scope of the HL7 Europe project.
29DiagnosticReport: Laboratory Reporthl7.eu.fhir.xpandh.lab#currentR4CDiagnosticReport used to represent an entry of a Laboratory Report, including its context, for the scope of the XPanDH project.
30DiagnosticReport: Laboratory Reportncez.cz.fhir.lab#currentR4Diagnostic Report used to represent an entry of a Laboratory Report, including its context, for the scope of the Czech national interoperability project.
31DiagnosticReport: Laboratory Report - Microbiology Culture & Susceptibilityhl7.fhir.eu.laboratory#currentR4DiagnosticReport used to represent an entry of a specialized Laboratory Report for representing microbiology culture & susceptibility results, including its context, for the scope of the HL7 Europe project.
32DiagnosticReportImagingndhm.in#currentR4This profile represents the set of information related to the Imaging diagnosis report generated by imaging services like Radiology, Cardiology, Endoscopy, etc. are ordered for the patient.
33DiagnosticReportLabndhm.in#currentR4This profile represents the set of information related to the Laboratory diagnosis report generated by the laboratory services like Complete Blood Count, Basic Metabolic Panel, Lipid Panel, Urinalysis, etc. are ordered for the patient.
34FHIRcast Diagnostic Report for Open Eventshl7.fhir.uv.fhircast#currentR4BProvides guidance as to which DiagnosticReport attributes should be present and considerations as to how each attribute should be valued in all [FHIR resource]-open events. At least one business identifier of the DiagnosticReport SHALL be provided in a [FHIR resource]-open request. Typically the report is associated with an order from an information system. In this case the accession number of the order is provided in the DiagnosticReport's `basedOn` array attribute as a reference using a ServiceRequest reference type and the “ACSN” identifier type. The accession number SHALL be included as a business identifier if it is known. A reporting system may also include its own identifier and should use an appropriate identifier type and system when supplying such a business identifier. In radiology reports or other image related uses of FHIRcast, at least one imaging study would likely be the subject of the report and included in the event's context. In this case, the reference to one or more ImagingStudy resources would be provided. **FHIR R4 versus FHIR R5** In the FHIR R4 DiagnosticReport resource image study references would be placed in the `imagingStudy` attribute. In a FHIR R5 (or above) DiagnosticReport this attribute has been renamed `study` since the allowed reference types has been expanded to include references to GenomicStudy resources. This is obviously a breaking change. In FHIRcast deployments based on FHIR R5, the attribute `study` SHALL be used rather than the `imagingStudy` attribute. Additionally FHIR R5 includes a `supportingInfo` attribute. While not yet formally provided for in FHIR R5, it has been recommended that the next release of FHIR allow an ImagingStudy reference be included in this attribute so that the DiagnosticReport could indicate one or more image studies were consulted during the creation of the report. As such in FHIR R5 deployments, this field is considered labeled as must support.
35FHIRcast DiagnosticReport for Close Eventshl7.fhir.uv.fhircast#currentR4BProvides guidance as to which DiagnosticReport attributes should be present and considerations as to how each attribute should be valued in all [FHIR resource]-close events. **FHIR R4 versus FHIR R5** In the FHIR R4 DiagnosticReport resource image study references would be placed in the `imagingStudy` attribute. In a FHIR R5 (or above) DiagnosticReport this attribute has been renamed `study` since the allowed reference types has been expanded to include references to GenomicStudy resources. This is obviously a breaking change. In FHIRcast deployments based on FHIR R5, the attribute `study` SHALL be used rather than the `imagingStudy` attribute. Additionally FHIR R5 includes a `supportingInfo` attribute. While not yet formally provided for in FHIR R5, it has been recommended that the next release of FHIR allow an ImagingStudy reference be included in this attribute so that the DiagnosticReport could indicate one or more image studies were consulted during the creation of the report. As such in FHIR R5 deployments, this field is considered labeled as must support.
36Genomics Reporthl7.fhir.uv.genomics-reporting#currentR4Genomics profile of DiagnosticReport.
37Genomics Report Profilehl7.fhir.us.mcode#currentR4Genomic analysis summary report. The report may include one or more tests, with two distinct test types. The first type is a targeted mutation test, where a specific mutation on a specific gene is tested for. The result is either positive or negative for that mutation. The second type is a more general test for variants. This type of test returns the identity of variants found in a certain region of the genome.
38HCIM LaboratoryTestResult DiagnosticReportnictiz.fhir.nl.stu3.zib2017#2.2.15R3A LaboratoryTestResult as defined by the Dutch Health and Care Information models (Dutch: Zorginformatiebouwsteen or ZIB) version 4.1, release 2017.
39HCIM OutcomeOfCarenictiz.fhir.nl.stu3.zib2017#2.2.15R3A derived profile on zib-TextResult to represent the the Dutch Health and Care Information models (Dutch: Zorginformatiebouwsteen or ZIB) OutcomeOfCare version 3.1, release 2017. The OutcomeOfCare concept describes the determined status of the patient in terms of a certain problem. Comparing the healthcare result with the treatment objective provides insight into the effectively of the nursing interventions/activities carried out for this problem. It is a part of the nursing process, together with nursing diagnoses/problems, the treatment objective and nursing interventions.
40HCIM TextResultnictiz.fhir.nl.stu3.zib2017#2.2.15R3A TextResult as defined by the Dutch Health and Care Information models (Dutch: Zorginformatiebouwsteen or ZIB) version 4.1. Textual results describe the findings and interpretation of diagnostic or therapeutic procedures carried out on patients or on specimens from the patient. Note that the HCIM TextResult-v4.1 has NL-CM:13.2.5 Procedure as property of the report. FHIR has this relationship reversed, so the procedure points to the report.
41IHE SDC/eCP on FHIR DiagnosticReporthl7.fhir.uv.ihe-sdc-ecc#currentR4A DiagnosticReport Profile meant to capture what should be represented in a report parsed from an IHE SDC Form
42Imaging Result Report (CZ)ncez.cz.fhir.imaging#currentR4Czech profile for an imaging result report
43ImagingReport-IEHRfhir.uv.crossborderdataexchange#currentR4
44IMR DiagnosticReportihe.rad.imr#currentR4IHE Interactive Multimedia Report (IMR) profile on DiagnosticReport
45Laboratory Report (CZ)ncez.cz.fhir.lab#currentR4Czech profile for a laboratory report
46LaboratoryReport-IEHRfhir.uv.crossborderdataexchange#currentR4
47MedComCoreDiagnosticReportmedcom.fhir.dk.homecareobservation#currentR4Report conating all observations results.
48MedComHomeCareDiagnosticReportmedcom.fhir.dk.homecareobservation#currentR4This resource is intenden to be used in relation when a HomeCareObservation message
49MIPHRDiagnosticReportImaginghl7.fhir.mi.phr#currentR4
50MIPHRDiagnosticReportPathologyhl7.fhir.mi.phr#currentR4
51MRI DiagnosticReportil.moh.mri.r4#currentR4מטרת פרופיל זה להגדיר ייצוג של דו"ח רפואי כתוצאה מהליך MRI, כחלק ממעקב אחר זמני רשימת ההמתנה למשרד הבריאות הישראלי.
52Multiple Chronic Condition Care Plan Diagnostic Report and Notehl7.fhir.us.mcc#currentR4This profile constrains [US Core Diagnostic Report and Note](http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-note) for use in the MCC FHIR Care Plan or other FHIR Care Plans.
53NZIPS-DiagnosticReporttewhatuora.fhir.ig.nzips#currentR4This profile constrains the DiagnosticReport resource to represent diagnostic test and procedure reports in a patient summary.
54OCT macula Diagnostic Reporthl7.fhir.uv.eyecare#currentR4The DiagnosticReport profile for an OCT macula
55OCT RNFL Diagnostic Reporthl7.fhir.uv.eyecare#currentR4The DiagnosticReport profile for an OCT RNFL
56OpenMRS Diagnostic Reportopenmrs.fhir.core#currentR4DiagnosticReport resource created by a OpenMRS that representing results of diagnostic tests that are performed in a given clinical context.
57Ophthalmic diagnostic test reporthl7.fhir.uv.eyecare#currentR4Base profile specifically constrained for describing ophthalmic reports
58PA Intervention Reporthl7.fhir.us.physical-activity#currentR4Conveys a summary of the interventions and patient interactions that have occurred over the course of the services delivered by a Service Provider, typically in response to a referral
59Personal Functioning and Engagement Narrative History of Statushl7.fhir.us.pacio-pfe#currentR4An exchange of a narrative summary regarding the most recent prior status immediately preceding the current admission, illness, or exacerbation for a patient. The use of this profile is encouraged in the absence of formal prior level assessments. For formal assessments conducted with for example, an assessment instrument, use the [collection](StructureDefinition-pfe-collection.html) and [single observation](StructureDefinition-pfe-observation-single.html) profiles defined in this IG to capture assessment data.
60Primary Care Diagnostic Reportau.csiro.fhir.au-primarycare#currentR4Basic diagnostic report
61QICore DiagnosticReport Profile for Laboratory Results Reportinghl7.fhir.us.qicore#currentR4Profile of DiagnosticReport for laboratory results for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors.
62QICore DiagnosticReport Profile for Report and Note Exchangehl7.fhir.us.qicore#currentR4Profile of DiagnosticReport for Note exchange for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors.
63Stability Study Interval Reporthl7.fhir.us.pq-cmc#currentR5Batch or lot stability testing to ensure that pharmaceutical products continue to meet the product specification or determine the expiry period.
64Tumor Morphologyhl7.fhir.us.pedcan#currentR4ICD-O-3 morphology determined from examination of tumor sample, composed of three parts: histologic type, the malignant potential of the tumor (behavior) and the tumor grade (degree of differentiation).
65TW Core DiagnosticReporttw.gov.mohw.twcore#0.1.1R4此臺灣核心-診斷報告(TW Core DiagnosticReport) Profile說明本IG如何進一步定義FHIR的DiagnosticReport Resource以呈現診斷報告 [[*FMM1*](http://build.fhir.org/versions.html#maturity)] - 2023/8/25異動說明： category改為slice，否則實作無法自定義欄位以綁定代碼。
66US Core DiagnosticReport Profile for Laboratory Results Reportinghl7.fhir.us.core#currentR4Laboratory results are grouped and summarized using the DiagnosticReport resource which typically reference Observation resource(s). Each Observation resource represents an individual laboratory test and result value or component result values, or a nested panel (such as a microbial susceptibility panel) which references other observations. They can also be presented in report form or as free text. This profile sets minimum expectations for the DiagnosticReport resource to record, search, and fetch laboratory results associated with a 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.
67US Core DiagnosticReport Profile for Report and Note Exchangehl7.fhir.us.core#currentR4To promote interoperability and adoption through common implementation, this profile sets minimum expectations for searching and fetching Diagnostic Reports and Notes using the DiagnosticReport resource. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present and constrains the way the elements are used when using the profile. It provides the floor for standards development for specific use cases. Prior to reviewing this profile, implementers are encouraged to read the Clinical Notes Guidance to understand the overlap of US Core DiagnosticReport Profile for Report and Note exchange and US Core DocumentReference Profile.
68US Pathology Diagnostic Reporthl7.fhir.us.cancer-reporting#currentR4It is expected that labs will populate dateTimes with the most specific time information known when sending to EHRs (YYYY-MM-DD).
69VF Diagnostic Report hl7.fhir.uv.eyecare#currentR4The DiagnosticReport profile for a visual field DT
70VitalSignReport-IEHRfhir.uv.crossborderdataexchange#currentR4
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70
DiagnosticReport I D C D I I I I D D D D D D I D I D I D D I D I D
DiagnosticReport.imagingStudy C C C D D C D C C C D C
DiagnosticReport.imagingStudy.reference C C
DiagnosticReport.id C D C D C D
DiagnosticReport.context C
DiagnosticReport.image C C
DiagnosticReport.meta D
DiagnosticReport.meta.profile C
DiagnosticReport.meta.security C F
DiagnosticReport.implicitRules C D
DiagnosticReport.language C D D B M
DiagnosticReport.text C D
DiagnosticReport.text.status F
DiagnosticReport.contained D
DiagnosticReport.extension S C (2) S C (2) S C (2) S C (2) S D D S C (3) S C D (2) S C (2) S C D (6) S C (2) S C (2) S C (2) S C (2) S (2) S C D (3) S C D (4) D
DiagnosticReport.extension.valueReference S D
DiagnosticReport.extension.value[x] C C C C
DiagnosticReport.modifierExtension C D
DiagnosticReport.identifier C D D D C C S C D (2) I C D I D D D C C C C C D
DiagnosticReport.identifier.value C C C
DiagnosticReport.identifier.system C F C C
DiagnosticReport.basedOn C D C D D D C D S C (2) C D S C (2) D
DiagnosticReport.status B M C B M C I B M B M D D F B M F F I B M F F I D D D B M F F B M D D B M B M B M
DiagnosticReport.status.extension S C D (2) S C D B M (2)
DiagnosticReport.status.extension.valueCodeableConcept S B M
DiagnosticReport.category C B M S C F D B M (2) C F C B M C D B M C B M C B M C D C B M S C F (2) F C D C C I D B M S C D (2) S C I D B M (3) C S C (2) S (2) C D B M C B M D B M C B M C B M C S C F D (2) S C F B M (3) S F B M (2) S C S C F D B M (2) S C F (2) S C B M (2)
DiagnosticReport.category.text
DiagnosticReport.category.coding S B M (2) S C (2) C F C S C F D B M (3) C C S C (2)
DiagnosticReport.category.coding.display C F (2) C C
DiagnosticReport.category.coding.code C F (2) C C F C C C F F
DiagnosticReport.category.coding.system C F C F (2) C F F F F C F C F C F F
DiagnosticReport.code B M C D B M C D B M B M B M B M B M F D I S C D (3) I D B M B M D B M B M B M B M B M B M C D B M F D B M D B M D B M
DiagnosticReport.code.text C C
DiagnosticReport.code.coding C S C (2) S C (2) S C (2) B M C S C B M (3) S C (2)
DiagnosticReport.code.coding.display F C C
DiagnosticReport.code.coding.code F C F (2) C C C F C C C F C F C (2) C F
DiagnosticReport.code.coding.system F C F (2) F F C F C F C F C F C F C F (2) C F
DiagnosticReport.subject C I C C C C C C C C C C C I D D C C I D C C D C D C C C C C C C C D C C
DiagnosticReport.subject.reference C C C C
DiagnosticReport.encounter I I D C C D D
DiagnosticReport.encounter.reference C C
DiagnosticReport.effective[x] C I C D C D C C C I S C D (2) D C C C D C D D C C C C D I
DiagnosticReport.effective[x].extension S C D
DiagnosticReport.issued C C C C C C C C C D
DiagnosticReport.performer C I C C C C D C D C I D C D I C D S C (2) C D S C I (3) C C D D
DiagnosticReport.performer.role
DiagnosticReport.performer.role.coding S D B M (2) S D B M (2)
DiagnosticReport.performer.actor C
DiagnosticReport.performer.actor.extension S C (2) S C (2)
DiagnosticReport.resultsInterpreter C I C D I C C C C D C C C D
DiagnosticReport.resultsInterpreter.reference C C
DiagnosticReport.specimen C C C C D D S C D (3) C C C D C
DiagnosticReport.result C C C C S S D (2) C C D D S C D (3) C S C (10) S (3) S C D (3) C S C (2) S C D (4) D
DiagnosticReport.result.reference C C
DiagnosticReport.note
DiagnosticReport.study
DiagnosticReport.supportingInfo
DiagnosticReport.supportingInfo.extension
DiagnosticReport.supportingInfo.modifierExtension
DiagnosticReport.supportingInfo.type
DiagnosticReport.supportingInfo.reference
DiagnosticReport.media D C C D C
DiagnosticReport.media.id D
DiagnosticReport.media.extension D
DiagnosticReport.media.modifierExtension D
DiagnosticReport.media.comment D
DiagnosticReport.media.link D
DiagnosticReport.media.link.reference C C
DiagnosticReport.composition
DiagnosticReport.conclusion C C D D C C D
DiagnosticReport.conclusionCode B M B M B M S C D B M (2) D B M D B M
DiagnosticReport.conclusionCode.text
DiagnosticReport.conclusionCode.coding
DiagnosticReport.conclusionCode.coding.display C C
DiagnosticReport.conclusionCode.coding.code C C
DiagnosticReport.conclusionCode.coding.system F F
DiagnosticReport.presentedForm C C C D S C I (3) I C D
DiagnosticReport.presentedForm.url
DiagnosticReport.presentedForm.hash C
DiagnosticReport.presentedForm.size C
DiagnosticReport.presentedForm.data C C
DiagnosticReport.presentedForm.contentType C C C F (3) F D
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