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))

2022-10-25T09:36:53Z

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))

← Oudere versie	Versie van 25 okt 2022 09:36
(geen verschil)

Pieter Edelman: Publish prepub to live environment

2022-10-25T09:36:52Z

Publish prepub to live environment

← Oudere versie		Versie van 25 okt 2022 09:36
Regel 1:		Regel 1:
	~~__NOINDEX__~~
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{DISPLAYTITLE:FHIR IG Error handling examples}}		{{DISPLAYTITLE:FHIR IG Error handling examples}}

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

2022-10-25T09:36:36Z

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

← Oudere versie	Versie van 25 okt 2022 09:36
(geen verschil)

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

← Oudere versie		Versie van 24 aug 2022 06:14
Regel 81:		Regel 81:
	\|		\|
	* HTTP 404 Not Found		* 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		* 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}}		{{Collapse top\|XML contents - response}}
Regel 167:		Regel 167:
	\|-		\|-
	\| '''Response'''		\| '''Response'''
	\| * HTTP ~~Status code 404 Not Found<br />~~* OperationOutcome		\|
			* HTTP 400 Bad Request
			* OperationOutcome. There are various issue type codes that could be used, depending on the nature of the error.
	\|}		\|}

	{{Collapse top\|XML contents - response}}		{{Collapse top\|XML contents - response}}
	<syntaxhighlight lang="xml">		<syntaxhighlight lang="xml">
Regel 192:		Regel 195:
	\|-		\|-
	\| '''Scenario'''		\| '''Scenario'''
	\| The id is not known by the server		\| The id is not known by the server.
	\|-		\|-
	\| '''Request'''		\| '''Request'''
Regel 198:		Regel 201:
	\|-		\|-
	\| '''Response'''		\| '''Response'''
	\| * HTTP ~~Status code~~ 404 Not Found~~<br />~~* OperationOutcome		\|
			* HTTP 404 Not Found
			* OperationOutcome with {{fhir\|OperationOutcome.issue.code}} set to {{term\|not-found}}.
	\|}		\|}

	{{Collapse top\|XML contents - response}}		{{Collapse top\|XML contents - response}}
	<syntaxhighlight lang="xml">		<syntaxhighlight lang="xml">
Regel 229:		Regel 235:
	\|		\|
	* HTTP 400 Bad Request		* 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>		</syntaxhighlight>
	{{Collapse bottom}}		{{Collapse bottom}}

	===Resource syntax or data is incorrect, invalid or unsupported===		===Resource syntax or data is incorrect, invalid or unsupported===
	{\| class="wikitable"		{\| class="wikitable"
Regel 275:		Regel 282:
	\| '''Response'''		\| '''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.		* OperationOutcome with {{fhir\|OperationOutcome.issue.code}} set to {{term\|invalid}} or a more specific child code.
	\|}		\|}
Regel 328:		Regel 335:
	\| '''Response'''		\| '''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.		* OperationOutcome with {{fhir\|OperationOutcome.issue.code}} set to {{term\|invalid}} or a more specific child code.
	\|}		\|}

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

← Oudere versie		Versie van 13 apr 2022 13:26
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}}

Niek van Galen: MM-2205: added Observation example

2021-07-26T12:09:22Z

MM-2205: added Observation example

@@ 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}}

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

2021-05-25T09:29:11Z

MM-1882: Add a "not authorized" example

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

Pieter Edelman: Remove MedMij issuebox

2021-01-22T11:42:49Z

Remove MedMij issuebox

← Oudere versie		Versie van 22 jan 2021 11:42
Regel 2:		Regel 2:
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{DISPLAYTITLE:FHIR IG Error handling examples}}		{{DISPLAYTITLE:FHIR IG Error handling examples}}
	~~{{MedMij:V2020.01/Issuebox_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.		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.

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

← Oudere versie		Versie van 22 jan 2021 11:40
Regel 18:		Regel 18:
	\| '''Response'''		\| '''Response'''
	\|		\|
	* HTTP ~~401 Unauthorized~~		* HTTP 403 Forbidden
	* OperationOutcome with {{fhir\|OperationOutcome.code}} set to {{term\|security}} or if applicable a more specific child code.		* OperationOutcome with {{fhir\|OperationOutcome.code}} set to {{term\|security}} or if applicable a more specific child code.
	\|}		\|}
Regel 32:		Regel 32:
	<code value="security"/>		<code value="security"/>
	<details>		<details>
	<text value="~~User authentication failed.~~"/>		<text value="Read access forbidden"/>
	</details>		</details>
	</issue>		</issue>

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 20 jan 2021 11:16
Regel 19:		Regel 19:
	\|		\|
	* HTTP 401 Unauthorized		* HTTP 401 Unauthorized
	* OperationOutcome with <code~~>code</code>~~ set to ~~"''~~security~~''"~~ or if applicable a more specific child code.		* OperationOutcome with {{fhir\|OperationOutcome.code}} set to {{term\|security}} or if applicable a more specific child code.
	\|}		\|}
	{{Collapse top\|XML contents - response}}		{{Collapse top\|XML contents - response}}
Regel 38:		Regel 38:
	</syntaxhighlight>		</syntaxhighlight>
	{{Collapse bottom}}		{{Collapse bottom}}

	===Resource is not supported===		===Resource is not supported===
	{\| class="wikitable"		{\| class="wikitable"
Regel 50:		Regel 51:
	\|		\|
	* HTTP 404 Not Found		* HTTP 404 Not Found
	* OperationOutcome with <code~~>code</code>~~ set to ~~"''~~not-supported~~''"~~		* OperationOutcome with {{fhir\|OperationOutcome.code}} set to {{term\|not-supported}}
	\|}		\|}

Regel 70:		Regel 71:
	</syntaxhighlight>		</syntaxhighlight>
	{{Collapse bottom}}		{{Collapse bottom}}

	==Search==		==Search==
	===Unkown or unsupported search parameter value===		===Unkown or unsupported search parameter value===
Regel 84:		Regel 86:
	\|		\|
	* HTTP 200 OK		* HTTP 200 OK
	* Empty Bundle of ~~<code>~~type~~</code> "''~~searchset~~''"~~		* Empty Bundle of {{fhir\|.type}} {{term\|searchset}}
	* OperationOutcome in Bundle as an entry marked with ~~<code>~~Bundle.entry.search.mode~~</code>~~ of ~~"''~~outcome~~''"~~		* OperationOutcome in Bundle as an entry marked with {{fhir\|Bundle.entry.search.mode}} of {{term\|outcome}}
	* OperationOutcome with <code~~>code</code>~~ set to ~~"''~~not-found~~''"~~ and ~~<code>~~severity~~</code>~~ not set to ~~"''~~fatal~~''"~~ or ~~"''~~error~~''"~~		* OperationOutcome with {{fhir\|OperationOutcome.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 197:		Regel 199:
	\|		\|
	* HTTP 400 Bad Request		* HTTP 400 Bad Request
	OperationOutcome with <code~~>code</code>~~ set to ~~"''~~invalid~~''"~~		OperationOutcome with {{fhir\|OperationOutcome.code}} set to {{term\|invalid}}
	\|}		\|}

Regel 244:		Regel 246:
	\|		\|
	* HTTP 400 Bad Request or HTTP 422 Uprocessable Entity		* HTTP 400 Bad Request or HTTP 422 Uprocessable Entity
	* OperationOutcome with <code~~>code</code>~~ set to ~~"''~~invalid~~''"~~ or a more specific child code.		* OperationOutcome with {{fhir\|OperationOutcome.code}} set to {{term\|invalid}} or a more specific child code.
	\|}		\|}
	{{Collapse top\|XML contents - request}}		{{Collapse top\|XML contents - request}}