A Diagnostic report holds findings and interpretations of diagnostic tests performed on patients.
The diagnostic report by itself does not hold any relevant clinical information, all clinical information are stored as Observations, references to observations created through a diagnostic report is maintained in both Diagnostic report and Observations.
To start with Diagnostic reports can only be created from Service Requests, But in theory, a diagnostic report could be created based off of any resource
The spec for Diagnostic Report is as follows
{
"id": "<str>", // Internal Identifier
"service_request" : "<id|fk>", // Points to the service request for which this report was created
"status" : "<string>", // Bound to registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown
"category" : "<code>", // Bound to https://build.fhir.org/valueset-diagnostic-service-sections.html
"code" : "<code>", // Fetched from SR, Bound to https://build.fhir.org/valueset-report-codes.html
"patient" : "<id|fk>", // Patient Associated
"encounter" : "<id|fk>", // Encounter associated
"specimen" : ["<id>"], // Specimens this report is based on -- Ignored
"result" : ["id"], // Observations
"note" : "<markdown>", // Comments about the diagnostic report
"conclusion" : "<markdown>", // Clinical conclusion (interpretation) of test results
}Files can be uploaded to a Diagnostic report as well, DICOM support is required and will be added as a plug to systems that support DICOM