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

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

As such, the ask is to clearly articulate in the specification that overlap exists. 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.

A tracker will also be logged to update the clinical safety checklist. GF#19249 will address the DiagnosticReport boundaries. This tracker is focused only on DocumentReference boundaries.