FHIR:V1.0 FHIR Error handling examples - Bewerkingsoverzicht

Pieter Edelman: Beveiligde "FHIR:V1.0 FHIR Error handling examples": Protect production page from accidental edits ([Bewerken=Alleen beheerders toestaan] (vervalt niet) [Hernoemen=Alleen beheerders toestaan] (vervalt niet))

2025-07-31T14:11:18Z

Beveiligde "FHIR:V1.0 FHIR Error handling examples": Protect production page from accidental edits ([Bewerken=Alleen beheerders toestaan] (vervalt niet) [Hernoemen=Alleen beheerders toestaan] (vervalt niet))

Pieter Edelman: Publish prepub to live environment

2025-07-31T14:11:18Z

Publish prepub to live environment

Pieter Edelman: Gekopieerd van FHIR:Vprepub-1.0 FHIR Error handling examples, versie 46479

2025-07-31T14:10:50Z

Gekopieerd van FHIR:Vprepub-1.0 FHIR Error handling examples, versie 46479

Luud Slagter: MM-3475: Changed incorrect HTTP status code of request with syntactically incorrect parameter, fixed several typos and inconsistencies

2022-08-24T06:14:36Z

MM-3475: Changed incorrect HTTP status code of request with syntactically incorrect parameter, fixed several typos and inconsistencies

Ashwin Djorai: MM-3096: .code changes to issue.code conform the FHIR specs

2022-04-13T13:26:19Z

MM-3096: .code changes to issue.code conform the FHIR specs

Niek van Galen: MM-2205: added Observation example

2021-07-26T12:09:22Z

MM-2205: added Observation example

Pieter Edelman: MM-1882: Add a "not authorized" example

2021-05-25T09:29:11Z

MM-1882: Add a "not authorized" example

Pieter Edelman: Remove MedMij issuebox

2021-01-22T11:42:49Z

Remove MedMij issuebox

Pieter Edelman: MM-1651: Changed the authorization example from an HTTP Status Code 401 to a 403 HTTP status code, as the OperationOutcome.text value

2021-01-22T11:40:37Z

MM-1651: Changed the authorization example from an HTTP Status Code 401 to a 403 HTTP status code, as the OperationOutcome.text value

Pieter Edelman: MM-1292: Apply writing guidelines and templates

2021-01-20T11:16:34Z

MM-1292: Apply writing guidelines and templates

← Oudere versie		Versie van 31 jul 2025 om 14:11
Regel 1:		Regel 1:
−	~~__NOINDEX__~~
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{DISPLAYTITLE:FHIR IG Error handling examples}}		{{DISPLAYTITLE:FHIR IG Error handling examples}}

@@ Regel 81: / Regel 81: @@
+|
 * HTTP 404 Not Found
-* OperationOutcome with {{fhir|OperationOutcome.issue.code}} set to {{term|not-supported}}
+* OperationOutcome with {{fhir|OperationOutcome.issue.code}} set to {{term|not-supported}}.
 |}
@@ Regel 116: / Regel 116: @@
+|
 * HTTP 200 OK
-* 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}} set to {{term|outcome}}.
-* OperationOutcome with {{fhir|OperationOutcome.issue.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}}
@@ Regel 167: / Regel 167: @@
 |-
 | '''Response'''
-| * HTTP Status code 404 Not Found<br />* OperationOutcome
 |}
 {{Collapse top|XML contents - response}}
 <syntaxhighlight lang="xml">
@@ Regel 192: / Regel 195: @@
 |-
 | '''Scenario'''
-| The id is not known by the server
+| The id is not known by the server.
 |-
 | '''Request'''
@@ Regel 198: / Regel 201: @@
 |-
 | '''Response'''
-| * HTTP Status code 404 Not Found<br />* OperationOutcome
 |}
 {{Collapse top|XML contents - response}}
 <syntaxhighlight lang="xml">
@@ Regel 229: / Regel 235: @@
+|
 * HTTP 400 Bad Request
-OperationOutcome with {{fhir|OperationOutcome.issue.code}} set to {{term|invalid}}
+* OperationOutcome with {{fhir|OperationOutcome.issue.code}} set to {{term|invalid}}.
 |}
@@ Regel 264: / Regel 270: @@
 </syntaxhighlight>
 {{Collapse bottom}}
 ===Resource syntax or data is incorrect, invalid or unsupported===
 {| class="wikitable"
@@ Regel 275: / Regel 282: @@
 | '''Response'''
+|
-* HTTP 400 Bad Request or HTTP 422 Uprocessable Entity
+* HTTP 400 Bad Request or HTTP 422 Unprocessable Entity
 * OperationOutcome with {{fhir|OperationOutcome.issue.code}} set to {{term|invalid}} or a more specific child code.
 |}
@@ Regel 328: / Regel 335: @@
 | '''Response'''
+|
-* HTTP 400 Bad Request or HTTP 422 Uprocessable Entity
+* HTTP 400 Bad Request or HTTP 422 Unprocessable Entity
 * OperationOutcome with {{fhir|OperationOutcome.issue.code}} set to {{term|invalid}} or a more specific child code.
 |}

@@ Regel 18: / Regel 18: @@
+|
 * 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}}
@@ Regel 49: / Regel 49: @@
+|
 * 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}}
@@ Regel 81: / Regel 81: @@
+|
 * 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}}
 * 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}}
@@ Regel 229: / Regel 229: @@
+|
 * 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
-* 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}}
@@ Regel 329: / Regel 329: @@
+|
 * 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}}

@@ Regel 264: / Regel 264: @@
 </syntaxhighlight>
 {{Collapse bottom}}
-===Resource syntax or data is incorrect or invalid===
+===Resource syntax or data is incorrect, invalid or unsupported===
 {| class="wikitable"
 |-
 | '''Scenario'''
-| Resource syntax or data is incorrect or invalid.
+| Resource syntax or data is incorrect, invalid or unsupported.
 |-
 | '''Request'''
@@ Regel 313: / Regel 313: @@
          <diagnostics value="value.empty() or system.exists()" />
          <location value="Patient.telecom[0]" />
      </issue>
 </OperationOutcome>
 </syntaxhighlight>
 {{Collapse bottom}}

@@ Regel 6: / Regel 6: @@
 ==All interactions==
 ===Invalid authorization===
 {| class="wikitable"

← Oudere versie	Versie van 31 jul 2025 om 14:11
(geen verschil)

← Oudere versie	Versie van 31 jul 2025 om 14:10
(geen verschil)

@@ Regel 2: / Regel 2: @@
 __NUMBEREDHEADINGS__
 {{DISPLAYTITLE:FHIR IG Error handling examples}}
 =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.