Skip to main content

DiagnosticReport

The DiagnosticReport resources provides "the findings and interpretation of diagnostic tests performed on patients, groups of patients, devices, and locations, and/or specimens derived from these." (HL7 FHIR R4 DiagnosticReport)

Supported Profiles

This API supports the following FHIR profiles:

Operations

The Certified API DiagnosticReport resources supports the following standard operations. However, support varies by the targeted CareRecord or solution.

CareRecord / SolutionCreateReadUpdateSearch
GEHRIMED-Yes-Yes
myAvatar-Yes-Yes
myEvolv-Yes-Yes
myUnity-Yes-Yes
TheraOffice-Yes-Yes
info

Not all Netsmart solutions support DocumentReference search. See supported operations table above and consult your target solution's documentation for more information.

This operation retrieves a list of resources by these query parameters.

Standard Parameters

NameTypeDescription
patientreferenceREQUIRED The subject of the report if a patient
categorytokenWhich diagnostic discipline/department created the report
codetokenThe code for the report, as opposed to codes for the atomic results, which are the names on the observation resource referred to from the result
datedateThe clinically relevant time of the report
pagestringZero-based page index
statustokenThe status of the report
_revincludespecialInclude Provenance resource(s) that reference the matched search results. Allowed: "Provenance:target"

Search Examples

Via POST

The POST method is recommended as it keeps health information out of the URL.

Search by Patient
curl -X POST https://fhir.netsmartcloud.com/uscore/v1/DiagnosticReport/_search \
-H "Authorization: {Bearer Token}" \
-H "Accept: application/fhir+json" \
-H "Content-Type: application/x-form-urlencoded" \
-d "patient=Patient/123"
Via GET
Search by Patient
curl -X GET https://fhir.netsmartcloud.com/uscore/v1/DiagnosticReport?patient=Patient/123 \
-H "Authorization: {Bearer Token}" \
-H "Accept: application/fhir+json"