Use to record detailed information about conditions, problems or diagnoses recognized by a clinician. There are many uses e.g. recording a diagnosis during an encounter; populating a problem list or a summary statement, such as a discharge summary.

0. References

1. Read

Return a single Condition for the specified id.

All requests SHALL contain a valid ‘Authorization’ header and SHALL contain an ‘Accept’ header. The `Accept` header indicates the format of the response the client is able to understand, this will be one of the following application/json+fhir or application/xml+fhir.

1.1. Response

A full set of response codes can be found here API Response Codes. FHIR Servers SHALL support the following response codes:

200 successful operation
404 resource not found
410 resource deleted

Search for all problems and health concerns for a patient. Fetches a bundle of all Condition resources for the specified patient.

All requests SHALL contain a valid ‘Authorization’ header and SHALL contain an ‘Accept’ header. The `Accept` header indicates the format of the response the client is able to understand, this will be one of the following application/json+fhir or application/xml+fhir.

2.1. Search Parameters

This implementation guide outlines some suggested search parameters for the Condition resource in the table below. To be conformant, provider systems are required to implement all of the SHALL parameters. Provider systems may implement the full list of search parameters for the Condition resource (HL7 FHIR DSTU2 Condition).


Name Type Description Conformance Path
category token The category of the condition SHOULD Condition.category
clinicalstatus token The clinical status of the condition SHOULD Condition.clinicalStatus
date-recorded date A date, when the Condition statement was documented MAY Condition.dateRecorded
patient reference Who has the condition? SHALL Condition.patient
(Patient)

Systems SHOULD support the following search combinations:

  • patient + clinicalstatus
  • patient + category

2.1.1. category

See token for details on this parameter.

To filter on category ( complaint | symptom | finding | diagnosis | problem | need )

GET [baseUrl]/Condition?patient=1&category=symptom

Return all Condition resources with a category of symptom and Patient with a logical id of 1.

2.1.2. clinicalstatus

See token for details on this parameter.

To filter on clinicalstatus ( active | inactive | relapse | remission | resolved )

GET [baseUrl]/Condition?patient=1&clinicalstatus=relapse

Return all Condition resources with a clinicalstatus of relapse and Patient with a logical id of 1.

2.1.3. date-recorded

See date for details on this parameter. ‘date-recorded’ can be used multiple times as a search parameter

GET [baseUrl]/Condition?patient=1&date-recorded=ge2010-01-01&date-recorded=le2011-12-31

Return all Condition resources that have a date-recorded greater than or equal to 1st Jan 2010, a date less than or equal to 31st Dec 2011 and Patient with a logical id of 1.

2.1.4. patient

See reference for details on this parameter. The patient parameter can be used two ways:

This SHALL be supported for all endpoint provider systems.

id is the logical id of the patient on the server which can be obtained by a Patient resource query.

GET [baseUrl]/Condition?patient=42

Return all Condition resources for Patients with a logical id of 42

This SHOULD be supported by middleware systems (e.g. enterprise application integration (EAI) and the enterprise service bus (ESB)) and MAY be supported for endpoint provider systems.

system is a uniform resource identifier which defines which CodeSystem the identifer belongs to. For NHS Number this would be https://fhir.nhs.uk/Id/nhs-number and code would be the NHS Number.

GET [baseUrl]/Condition?patient.identifier=https://fhir.nhs.uk/Id/nhs-number|9876543210

Return all Condition resources for Patients with a NHS Number of 9876543210

2.2. Search Response

If the search fails (cannot be executed, not that there is no matches), the return value is a status code 4xx or 5xx with an OperationOutcome.

If the search succeeds, the return content is a Bundle with type = searchset containing the results of the search as a list of resources in a defined order. The result list can be long, so servers MAY use paging. If they do, they SHALL use this Paging method for breaking the list into pages if appropriate. The server MAY also return an OperationOutcome resource with additional information about the search; if one is sent it SHALL NOT include any errors, and it shall be marked with an entry mode of include.

A full set of response codes can be found here API Response Codes. FHIR Servers SHALL support the following response codes:

200 successful operation
404 resource not found
410 resource deleted

3. Example

3.1 Request Query

Return all Condition resources for Patient with a NHS Number of 9876543210, the format of the response body will be xml. Replace ‘baseUrl’ with the actual base Url of the FHIR Server.

3.1.1. cURL

curl -H 'Accept: application/xml+fhir' -H 'Authorization: BEARER [token]' -X GET  '[baseUrl]/Condition?patient.identifier=https://fhir.nhs.uk/Id/nhs-number|9876543210'

3.2 Query Response

3.2.1 Http Headers

3.2.2 Http Body