Condition
Options to work with FHIR R4 Condition resources.
- Search Condition
- Read Condition
- Read Condition Version
- Create Condition
- Update Condition
- Delete Condition
- Hard Delete Condition
- Purge Deleted Condition
The following example shows one possible Condition workflow. Every Condition requires a subject that references a Patient or Group. An encounter reference is optional.
[Condition Identified]
|
v
[Condition Resource Created]
|
+-----+-------------------+
| |
[Required subject] [Optional encounter]
[Patient or Group] [Encounter reference]Successful HTTP Responses
This table lists successful HTTP responses for this resource.
| Endpoint | Method | Successful status code |
|---|---|---|
/api/fhir/r4/Condition | GET | 200 |
/api/fhir/r4/Condition | POST | 201 |
/api/fhir/r4/Condition/$purgeDeleted | POST | 200 |
/api/fhir/r4/Condition/{rid} | DELETE | 204 |
/api/fhir/r4/Condition/{rid} | GET | 200 |
/api/fhir/r4/Condition/{rid} | PUT | 200 |
/api/fhir/r4/Condition/{rid}/$hardDelete | POST | 200 |
/api/fhir/r4/Condition/{rid}/_history/{vid} | GET | 200 |
For cross-resource interaction summaries, see FHIR status codes.
See also
For permanent deletion guidance, see Data deletion and purge operations.