Given the work done for FHIR-19250 and recent discussions, we will adjust the DiagnosticReport boundary discussions between DiagnosticReport and DocumentReference to read A DiagnosticReport has overlapping characteristics with DocumentReference. The DiagnosticReport is appropriate to reflect a set of discrete results (Observations) and associated contextual details for a specific report, and within those results any further structure within the Observation instances, while a DocumentReference typically reflects a non-FHIR object (e.g., an existing C-CDA document, a scan of a drivers license, or narrative note). There is some overlap potential, such as a scan of a CBC report that can either be referenced via a DocumentReference, or included in a DiagnosticReport as a representedForm together with the structured, discrete data. In some cases, a single in-system entity may be represented as both resources if they provide relevant metadata or workflow-specific attributes. Specific implementation guides would further clarify which approach is more appropriate. In the Boundaries and Relationships section of DocumentReference, we will replace the last sentence with the following: In some cases, a single in-system entity may be represented as both resources if they provide relevant metadata or workflow-specific attributes. Specific implementation guides would further clarify which approach is more appropriate.