Skip to main content

DiagnosticReport

Overview

The DiagnosticReport resource provides findings and interpretation of diagnostic tests performed on patients, groups, devices, locations, and specimens. This includes laboratory results, imaging reports, and other diagnostic findings.

Resource Schema

Key fields in the DiagnosticReport resource:

{
"resourceType": "DiagnosticReport",
"id": "example-diagnosticreport-123",
"status": "final",
"category": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v2-0074",
"code": "LAB",
"display": "Laboratory"
}
]
}
],
"code": {
"coding": [
{
"system": "http://loinc.org",
"code": "58410-2",
"display": "Complete blood count (hemogram) panel"
}
]
},
"subject": {
"reference": "Patient/123456"
},
"effectiveDateTime": "2023-07-15T09:30:00Z",
"issued": "2023-07-15T14:00:00Z",
"performer": [
{
"reference": "Organization/lab-456"
}
],
"result": [
{
"reference": "Observation/hemoglobin-789"
}
]
}

Operations

The DiagnosticReport resource supports Read and Search operations. Support varies by CareRecord solution.

CareRecord / SolutionReadSearch
GEHRIMED
myAvatar
myEvolv
myUnity
TheraOffice

Read

Retrieves a specific DiagnosticReport resource by ID.

HTTP Method: GET
URL: /DiagnosticReport/{id}

Examples

curl -X GET https://fhir.netsmartcloud.com/uscore/v1/DiagnosticReport/123456 \
-H "Authorization: Bearer {token}" \
-H "Accept: application/fhir+json"

Retrieves DiagnosticReport resources matching specified criteria.

HTTP Method: GET or POST
URL: /DiagnosticReport or /DiagnosticReport/_search

Search Parameters

Patient-based Search:

ParameterTypeRequiredDescriptionExample
patientreferenceYesREQUIRED The subject of the report if a patientpatient=value
categorytokenNoWhich diagnostic discipline/department created the reportcategory=value
codetokenNoThe code for the report, as opposed to codes for the atomic results, which are the names on the observation resource referred to from the resultcode=value
datedateNoThe clinically relevant time of the reportdate=value
pagestringNoZero-based page indexpage=value
statustokenNoThe status of the reportstatus=value
_revincludespecialNoInclude Provenance resource(s) that reference the matched search results. Allowed: "Provenance:target"_revinclude=value

ID-based Search:

ParameterTypeRequiredDescriptionExample
categorytokenNoWhich diagnostic discipline/department created the reportcategory=value
codetokenNoThe code for the report, as opposed to codes for the atomic results, which are the names on the observation resource referred to from the resultcode=value
datedateNoThe clinically relevant time of the reportdate=value
pagestringNoZero-based page indexpage=value
statustokenNoThe status of the reportstatus=value
_revincludespecialNoInclude Provenance resource(s) that reference the matched search results. Allowed: "Provenance:target"_revinclude=value

Examples

POST Method (Recommended)
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"
GET Method
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"

Integration Patterns

Common Workflows

  1. Lab Results Review - Retrieve diagnostic reports for a patient
  2. Report Analysis - Search by category for specific types of reports
  3. Clinical Decision Support - Use diagnostic findings for care planning

Relationships to Other Resources

The DiagnosticReport resource relates to:

  • Patient - Subject of the diagnostic report
  • Observation - Individual test results referenced in the report
  • Practitioner - Who performed or interpreted the diagnostic test
  • Organization - Laboratory or facility that produced the report
  • Encounter - Healthcare encounter when diagnostic test was ordered

Error Handling

For common errors and troubleshooting guidance, see Common Errors.

Supported Profiles

Profiles supported by this resource (as defined in the CapabilityStatement):