The description of Encounter.diagnosis leaves space for interpretation whether this is

1. the diagnosis as is known when creating the Encounter resource (in which case seems overlapping with Encounter.reasonReference), or

2. new findings that may be added during/after the Encounter creation (which does not seem a good approach to me. as it would make Encounter not a standalone resource, but a document-like placeholder for the evolution of the encounter).

Suggest updating the description of Encounter.diagnosis and reason, to clarify the scope of these elements. Suggest updating the resource scope to include something like "The Encounter resource contains the information about the encounter itself, and is linked to by the additional resources that may be trigggered during or because of the encounter. For example, Encounter contains the initial reason (procedure or diagnostic) that triggered the encounter, but normally Encounter does not contain additional diagnosis that are discovered during the encounter. These are created as their own resource instances, and can point to this Encounter resource.