Luud Slagter: MM-4102: Corrected several typos

2022-12-07T06:15:54Z

MM-4102: Corrected several typos

← Oudere versie		Versie van 7 dec 2022 06:15
Regel 55:		Regel 55:
	</syntaxhighlight>		</syntaxhighlight>

	==Use of the ~~reference~~ datatype==		==Use of the Reference datatype==
	A key feature of FHIR is the ability of resources to reference each other. This is done using the [https://hl7.org/fhir/STU3/references.html#Reference {{datatype\|Reference}} datatype]. This datatype supports two modes of referencing:		A key feature of FHIR is the ability of resources to reference each other. This is done using the [https://hl7.org/fhir/STU3/references.html#Reference {{datatype\|Reference}} datatype]. This datatype supports two modes of referencing:
	; [https://hl7.org/fhir/STU3/references.html#literal Literal references], using the {{fhir\|.reference}} element: A relative or absolute REST endpoint containing {{fhir\|.id}} of the referenced resource. In a Bundle context, this may also be a reference to a {{fhir\|Bundle.resource.fullUrl}}.		; [https://hl7.org/fhir/STU3/references.html#literal Literal references], using the {{fhir\|.reference}} element: A relative or absolute REST endpoint containing {{fhir\|.id}} of the referenced resource. In a Bundle context, this may also be a reference to a {{fhir\|Bundle.resource.fullUrl}}.
Regel 169:		Regel 169:
	Servers may not support read interactions, but all references from search results need to be resolvable (see [[#Use of the reference datatype]]). Therefore servers MAY choose to include the referenced resources in the ''searchset'' Bundle, even if the client didn't use any <code>_include</code> parameters ([[FHIR:V1.0 Search result examples#Server doesn't support read operations\|example]]). These resources SHALL have <code>Bundle.entry.mode</code> set to "''include''". Servers SHOULD NOT use contained resources for this purpose.		Servers may not support read interactions, but all references from search results need to be resolvable (see [[#Use of the reference datatype]]). Therefore servers MAY choose to include the referenced resources in the ''searchset'' Bundle, even if the client didn't use any <code>_include</code> parameters ([[FHIR:V1.0 Search result examples#Server doesn't support read operations\|example]]). These resources SHALL have <code>Bundle.entry.mode</code> set to "''include''". Servers SHOULD NOT use contained resources for this purpose.

	The [[FHIR:V1.0 Search result examples\|examples page]] illustrates how servers can provide ~~resolveable~~ references in different situations.		The [[FHIR:V1.0 Search result examples\|examples page]] illustrates how servers can provide resolvable references in different situations.

	====Paging====		====Paging====
Regel 315:		Regel 315:
	* 401 Unauthorized - authorization is required for the interaction that was attempted (usually emitted by the authorization server)		* 401 Unauthorized - authorization is required for the interaction that was attempted (usually emitted by the authorization server)
	* 403 Forbidden - the server was unable to execute the search, due to an authorization failure (usually emitted by the resource server)		* 403 Forbidden - the server was unable to execute the search, due to an authorization failure (usually emitted by the resource server)
	* 404 Not Found - resource type not supported, or not an FHIR endpoint		* 404 Not Found - resource type not supported, or not a FHIR endpoint
	* 422 Unprocessable Entity - the proposed resource violated applicable FHIR profiles or server business rules		* 422 Unprocessable Entity - the proposed resource violated applicable FHIR profiles or server business rules

Regel 329:		Regel 329:
	\|		\|
	* HTTP 401 Unauthorized		* HTTP 401 Unauthorized
	* OperationOutcome with {{fhir\|.code}} set to {{term\|security}}		* OperationOutcome with {{fhir\|.code}} set to {{term\|security}}.
	\| [[FHIR:V1.0 FHIR_Error_handling_examples#Not_authorized\|Example]]		\| [[FHIR:V1.0 FHIR_Error_handling_examples#Not_authorized\|Example]]
	\|-		\|-
Regel 335:		Regel 335:
	\|		\|
	* HTTP 403 Forbidden		* HTTP 403 Forbidden
	* OperationOutcome with {{fhir\|.code}} set to {{term\|security}}		* OperationOutcome with {{fhir\|.code}} set to {{term\|security}}.
	\| [[FHIR:V1.0 FHIR_Error_handling_examples#Invalid_authorization\|Example]]		\| [[FHIR:V1.0 FHIR_Error_handling_examples#Invalid_authorization\|Example]]
	\|-		\|-
Regel 341:		Regel 341:
	\|		\|
	* HTTP 404 Not Found		* HTTP 404 Not Found
	* OperationOutcome with {{fhir\|.code}} set to {{term\|not-supported}}		* OperationOutcome with {{fhir\|.code}} set to {{term\|not-supported}}.
	\| [[FHIR:V1.0 FHIR_Error_handling_examples#Resource_is_not_supported\|Example]]		\| [[FHIR:V1.0 FHIR_Error_handling_examples#Resource_is_not_supported\|Example]]
	\|-		\|-
Regel 354:		Regel 354:
	\|		\|
	* HTTP 400 Bad Request		* HTTP 400 Bad Request
	* OperationOutcome. There are various issue type codes that could be used, depending on the nature of the error		* OperationOutcome. There are various issue type codes that could be used, depending on the nature of the error.
	\| [[FHIR:V1.0 FHIR_Error_handling_examples#Syntactically_incorrect_parameter\|Example]]		\| [[FHIR:V1.0 FHIR_Error_handling_examples#Syntactically_incorrect_parameter\|Example]]
	\|-		\|-
Regel 360:		Regel 360:
	\|		\|
	* 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 with {{fhir\|Bundle.entry.search.mode}} set to {{term\|outcome}}.
	* OperationOutcome with {{fhir\|.code}} set to {{term\|not-found}} and {{fhir\|.severity}} not set to {{term\|fatal}} or {{term\|error}}.		* OperationOutcome with {{fhir\|.code}} set to {{term\|not-found}} and {{fhir\|.severity}} not set to {{term\|fatal}} or {{term\|error}}.
	\| [[FHIR:V1.0 FHIR_Error_handling_examples#Unkown_or_unsupported_search_parameter_value\|Example]]		\| [[FHIR:V1.0 FHIR_Error_handling_examples#Unkown_or_unsupported_search_parameter_value\|Example]]
Regel 369:		Regel 369:
	\|		\|
	* HTTP 404 Not Found		* HTTP 404 Not Found
	* OperationOutcome with {{fhir\|.code}} set to {{term\|not-found}}		* OperationOutcome with {{fhir\|.code}} set to {{term\|not-found}}.
	\| [[FHIR:V1.0 FHIR_Error_handling_examples#Request_on_an_unknown_id\|Example]]		\| [[FHIR:V1.0 FHIR_Error_handling_examples#Request_on_an_unknown_id\|Example]]
	\|-		\|-
Regel 376:		Regel 376:
	\|		\|
	* HTTP 400 Bad Request		* HTTP 400 Bad Request
	* OperationOutcome with {{fhir\|.code}} set to {{term\|invalid}}		* OperationOutcome with {{fhir\|.code}} set to {{term\|invalid}}.
	\| [[FHIR:V1.0 FHIR_Error_handling_examples#No_or_incorrect_Resource_id\|Example]]		\| [[FHIR:V1.0 FHIR_Error_handling_examples#No_or_incorrect_Resource_id\|Example]]
	\|-		\|-

Luud Slagter: Clone of V1.0 production page for issue MM-4102

2022-12-07T06:08:29Z

Clone of V1.0 production page for issue MM-4102

Wijzigingen bekijken

FHIR:Vissue-MM-4102 FHIR IG STU3 - Bewerkingsoverzicht

Luud Slagter: MM-4102: Corrected several typos

Luud Slagter: Clone of V1.0 production page for issue MM-4102