Following the Baltimore connectathon and PC/SD joint meeting on Tues Q2, this tracker is being logged to request an update to the clinical safety checklist.

Refer to the attached PPT and Excel spreadsheet to view the Venn diagram illustrating that there is overlap between DocumentReference and DiagnosticReport. For example, a scanned CBC report could be considered both a DocumentReference (since it was a scanned document) as well as a DiagnosticReport (due to the document type / contents).

If a client is querying to get all Lab Reports, Radiology Reports, or Cardiology Reports using DiagnosticReport alone, then they might miss those reports that are only exposed as a DocumentReference. Likewise, if a client is querying to get all documents available, then they might miss those documents that were exposed via DiagnosticReport only.

Other trackers were logged to update DiagnosticReport (GF#19249) and DocumentReference (GF#19250) boundaries. This tracker is focused only on the clinical safety checklist.

While the attached materials are specific to DiagnosticReport and DocumentReference, the checklist item could be broader in nature given there could be other resources using Attachment data type that may have similar considerations (e.g. overlap with DocumentReference). Or, even more broadly, per Grahame, degenerate poorly populated resources are hard to differentiate, which is a risk that should at least be acknowledged, do clients can decide how to best mitigate (e.g. query multiple resources to get all of the desired data)