Tutorials

Use Cases

Interface

Resources

Operations

Examples & Testing

Endpoints

Diagnostic Report

4.0.1. (R4) 3.0.1. (STU3) 1.0.2 (DSTU2)

A Diagnostic Report represents the results or findings of a diagnostic test.

Sample Query

Find reports for a specific patient:

https://fhir.careevolution.com/Master.Adapter1.WebClient/api/fhir/DiagnosticReport?patient=f4968df0-3121-e611-8128-0a69c1b3225b

Overview

See the FHIR documentation for more information about Diagnostic Report resources.

Mapped Concepts in HIEBus

  • Report
  • LabReport

Supported Interactions

Diagnostic Report resources support the following interactions.

Search Parameters

When searching for Diagnostic Report resources, the following search parameters are supported.

Name Type Prefixes
Modifiers 		Can be Chained? Description
_id Token Resource id.
_lastUpdated Date ne  lt  le  gt  ge  sa  eb  ap  When the resource last changed.
_source Uri :missing  Where the resource comes from.
category Token :missing  The classification of the type of report - path DiagnosticReport.category. Matches CareEvolution reports whose type is in a term subset with scope 'http://hl7.org/fhir/v2/0074' and name equal to one of the specified codes with system 'http://hl7.org/fhir/v2/0074'. Matches any CareEvolution lab reports if one of the specified category codes is 'LAB' with system 'http://hl7.org/fhir/v2/0074'. So for example 'category=http://hl7.org/fhir/v2/0074|Hematology' (and 'category=Hematology') matches no lab reports and matches reports whose type is in the term subset with scope 'http://hl7.org/fhir/v2/0074' and name 'Hematology'. 'category=http://hl7.org/fhir/v2/0074|LAB' (and 'category=LAB') matches any lab report whose type is in the term subset with scope 'http://hl7.org/fhir/v2/0074' and name 'LAB'. 'category=http://snomed.info/sct|laboratory' matches no lab reports and matches no reports.
code Token :not  :in  :not-in  :missing  The code for the report as a whole, as opposed to codes for the atomic results, which are the names on the observation resource referred to from the result.
date Date ne  lt  le  gt  ge  sa  eb  ap  :missing  The clinically relevant time of the report.
encounter Reference :missing  yes The Encounter when the order was made.
patient Reference :missing  yes The subject of the report if a patient.
performer Reference :missing  yes Who was the source of the report (organization).
provenance-agent Reference :missing  yes Search by provenance, specified by its author (aka originator) Organization.
request Reference :missing  yes Reference to the test or procedure request.
result Reference :missing  yes Link to an atomic result (observation resource).
status Token :missing  The status of the report.
subject Reference :missing  yes The subject of the report.

Sortable Parameters

When searching Diagnostic Report resources, it is possible to sort the returned values by the following search parameters.

  • date
  • _id

Only one sort parameter may be specified.

Supported Includes

When searching Diagnostic Report resources, it is possible to include the resources referenced by the following field names.

  • Encounter
  • Patient
  • Performer
  • Provenance Agent
  • Request
  • Result
  • Subject

Supported Operations

Diagnostic Report supports the following extended operations.

Back to Resources

Have questions about the HIEBus FHIR interface? Contact us at fhir@careevolution.com.

Terms of Use

© 2023 CareEvolution, LLC