FHIR:Vprepub-1.0 FHIR Error handling examples: verschil tussen versies
(MM-2205: added Observation example) |
(MM-3096: .code changes to issue.code conform the FHIR specs) |
||
| Regel 18: | Regel 18: | ||
| | | | ||
* HTTP 401 Unauthorized | * HTTP 401 Unauthorized | ||
| − | * OperationOutcome with {{fhir|OperationOutcome.code}} set to {{term|security}} or if applicable a more specific child code. | + | * OperationOutcome with {{fhir|OperationOutcome.issue.code}} set to {{term|security}} or if applicable a more specific child code. |
|} | |} | ||
{{Collapse top|XML contents - response}} | {{Collapse top|XML contents - response}} | ||
| Regel 49: | Regel 49: | ||
| | | | ||
* HTTP 403 Forbidden | * HTTP 403 Forbidden | ||
| − | * OperationOutcome with {{fhir|OperationOutcome.code}} set to {{term|security}} or if applicable a more specific child code. | + | * OperationOutcome with {{fhir|OperationOutcome.issue.code}} set to {{term|security}} or if applicable a more specific child code. |
|} | |} | ||
{{Collapse top|XML contents - response}} | {{Collapse top|XML contents - response}} | ||
| Regel 81: | Regel 81: | ||
| | | | ||
* HTTP 404 Not Found | * HTTP 404 Not Found | ||
| − | * OperationOutcome with {{fhir|OperationOutcome.code}} set to {{term|not-supported}} | + | * OperationOutcome with {{fhir|OperationOutcome.issue.code}} set to {{term|not-supported}} |
|} | |} | ||
| Regel 118: | Regel 118: | ||
* Empty Bundle of {{fhir|.type}} {{term|searchset}} | * Empty Bundle of {{fhir|.type}} {{term|searchset}} | ||
* OperationOutcome in Bundle as an entry marked with {{fhir|Bundle.entry.search.mode}} of {{term|outcome}} | * OperationOutcome in Bundle as an entry marked with {{fhir|Bundle.entry.search.mode}} of {{term|outcome}} | ||
| − | * OperationOutcome with {{fhir|OperationOutcome.code}} set to {{term|not-found}} and {{fhir|OperationOutcome.severity}} not set to {{term|fatal}} or {{term|error}} | + | * OperationOutcome with {{fhir|OperationOutcome.issue.code}} set to {{term|not-found}} and {{fhir|OperationOutcome.severity}} not set to {{term|fatal}} or {{term|error}} |
|} | |} | ||
{{Collapse top|XML contents - response}} | {{Collapse top|XML contents - response}} | ||
| Regel 229: | Regel 229: | ||
| | | | ||
* HTTP 400 Bad Request | * HTTP 400 Bad Request | ||
| − | OperationOutcome with {{fhir|OperationOutcome.code}} set to {{term|invalid}} | + | OperationOutcome with {{fhir|OperationOutcome.issue.code}} set to {{term|invalid}} |
|} | |} | ||
| Regel 276: | Regel 276: | ||
| | | | ||
* HTTP 400 Bad Request or HTTP 422 Uprocessable Entity | * HTTP 400 Bad Request or HTTP 422 Uprocessable Entity | ||
| − | * OperationOutcome with {{fhir|OperationOutcome.code}} set to {{term|invalid}} or a more specific child code. | + | * OperationOutcome with {{fhir|OperationOutcome.issue.code}} set to {{term|invalid}} or a more specific child code. |
|} | |} | ||
{{Collapse top|XML contents - request}} | {{Collapse top|XML contents - request}} | ||
| Regel 329: | Regel 329: | ||
| | | | ||
* HTTP 400 Bad Request or HTTP 422 Uprocessable Entity | * HTTP 400 Bad Request or HTTP 422 Uprocessable Entity | ||
| − | * OperationOutcome with {{fhir|OperationOutcome.code}} set to {{term|invalid}} or a more specific child code. | + | * OperationOutcome with {{fhir|OperationOutcome.issue.code}} set to {{term|invalid}} or a more specific child code. |
|} | |} | ||
{{Collapse top|XML contents - request}} | {{Collapse top|XML contents - request}} | ||
Versie van 13 apr 2022 om 15:26
Inhoud
[verbergen]1 Error handling examples
This page provides guidance on how a server could handle errors. Examples are provided in XML format but could have been in JSON format as well. Please note: these examples are not considered to be part of the normative content of the implementation guide.
1.1 All interactions
1.1.1 Not authorized
| Scenario | Not authorized. |
| Request | GET [base]/Practitioner/86475712701 |
| Response |
|
| [tonen]XML contents - response |
|---|
1.1.2 Invalid authorization
| Scenario | Invalid authorization. |
| Request | GET [base]/Patient/20118482245 |
| Response |
|
| [tonen]XML contents - response |
|---|
1.1.3 Resource is not supported
| Scenario | The Resource is not supported by the resource server. |
| Request | GET [base]/Questionnaire |
| Response |
|
| [tonen]XML contents - response |
|---|
1.2 Search
1.2.1 Unkown or unsupported search parameter value
| Scenario |
Unknown or unsupported search parameter value. In this example scenario, the Consent endpoint is supported. Although a system has implemented support for the HCIM TreatmentDirective ( |
| Request | GET [base]/Consent?category=http://snomed.info/sct|11341000146107 |
| Response |
|
| [tonen]XML contents - response |
|---|
1.2.2 Syntactically incorrect parameter
| Scenario | Syntactically incorrect parameter in the search request. |
| Request | GET [base]/Procedure?patient:john |
| Response | * HTTP Status code 404 Not Found * OperationOutcome |
| [tonen]XML contents - response |
|---|
1.3 Read
1.3.1 Request on an unknown id
| Scenario | The id is not known by the server |
| Request | GET [base]/Patient/wrong-id |
| Response | * HTTP Status code 404 Not Found * OperationOutcome |
| [tonen]XML contents - response |
|---|
1.4 Create/Update
1.4.1 No or incorrect Resource id
| Scenario | Update an existing Patient resource, using a wrong id in the Resource. |
| Request | PUT [base]/Patient/34235234 |
| Response |
OperationOutcome with |
| [tonen]XML contents - request |
|---|
| [tonen]XML contents - response |
|---|
1.4.2 Resource syntax or data is incorrect, invalid or unsupported
| Scenario | Resource syntax or data is incorrect, invalid or unsupported. |
| Request | POST [base]/Patient |
| Response |
|
| [tonen]XML contents - request |
|---|
| [tonen]XML contents - response |
|---|
| Scenario | Resource syntax or data is incorrect, invalid or unsupported. |
| Request | POST [base]/Observation |
| Response |
|
| [tonen]XML contents - request |
|---|
| [tonen]XML contents - response |
|---|
