DiagnosticReport Conditional Update

put

DiagnosticReport Conditional Update

The conditional update interaction is used to update an existing DiagnosticReport based on some identification criteria, rather than by logical id.

FHIR documentation for DiagnosticReport.

HTTP Basic

OAuth 2.0

API Key

Reset

Make a request and see the response.

Make a request and see the response.

Response Error Details

  • HTTP Code
    Error Code
    Description
  • 400
    400

    DiagnosticReport could not be parsed or failed basic FHIR validation rules (or multiple matches were found).

  • 403
    403

    Not Authorized.

  • 412
    412

    The given criteria is not selective enough.

Environment URL
Live

https://fhirsandbox-prod.apigee.net/fhir/v1/DiagnosticReport

Name Values Description
Authorization

Specify access token for API in the given format: Bearer [access_token].

Accept

The Accept request-header field can be used to specify certain media types which are acceptable for the response.

Content-Type
(required)

Specifies the format of data in body

Name Values Description
_content

Search the contents of the resource's data using a fulltext search

_id

The resource identity

_language

The resource language

_lastUpdated

Only return resources which were last updated as specified by the given range. The date parameter format is yyyy-mm-ddThh:nn:ss(TZ). The prefixes >, >=, <= and < may be used on the parameter value.

_lastUpdated

Only return resources which were last updated as specified by the given range. The date parameter format is yyyy-mm-ddThh:nn:ss(TZ). Two dates can be used to specify an interval. The prefixes >, >=, <= and < may be used on the parameter value.

_profile

Search for resources which have the given profile

_security

Search for resources which have the given security labels

_tag

Search for resources which have the given tag

_text

Search the contents of the resource's narrative using a fulltext search

category

Which diagnostic discipline/department created the report

code

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

The clinically relevant time of the report. The date parameter format is yyyy-mm-ddThh:nn:ss(TZ). The prefixes >, >=, <= and < may be used on the parameter value.

date

The clinically relevant time of the report. The date parameter format is yyyy-mm-ddThh:nn:ss(TZ). Two dates can be used to specify an interval. The prefixes >, >=, <= and < may be used on the parameter value.

diagnosis

A coded diagnosis on the report

encounter

The Encounter when the order was made

identifier

An identifier for the report

image

A reference to the image source.

issued

When the report was issued. The date parameter format is yyyy-mm-ddThh:nn:ss(TZ). The prefixes >, >=, <= and < may be used on the parameter value.

issued

When the report was issued. The date parameter format is yyyy-mm-ddThh:nn:ss(TZ). Two dates can be used to specify an interval. The prefixes >, >=, <= and < may be used on the parameter value.

patient

The subject of the report if a patient

performer

Who was the source of the report (organization)

request

Reference to the test or procedure request.

result

Link to an atomic result (observation resource)

specimen

The specimen details

status

The status of the report

subject

The subject of the report

The request body should be a valid data payload.

Working...