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

2022-10-25T09:36:43Z

Beveiligde "FHIR:V1.0 FHIR IG R4": 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:43Z

Publish prepub to live environment

← Oudere versie		Versie van 25 okt 2022 09:36
Regel 1:		Regel 1:
	~~__NOINDEX__~~
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{DISPLAYTITLE:Nictiz FHIR R4 Implementation Guide {{VersieInfo\|FHIR_IG_R4\|release=V1.0}}}}		{{DISPLAYTITLE:Nictiz FHIR R4 Implementation Guide {{VersieInfo\|FHIR_IG_R4\|release=V1.0}}}}
Regel 47:		Regel 46:

	==Profiling guidelines==		==Profiling guidelines==
	All conformance resources created within Nictiz follow the conventions as outlined in the [[FHIR:~~Vprepub-1~~.0_FHIR_Profiling_Guidelines_R4\|FHIR Profiling Guidelines for FHIR R4]].		All conformance resources created within Nictiz follow the conventions as outlined in the [[FHIR:V1.0_FHIR_Profiling_Guidelines_R4\|FHIR Profiling Guidelines for FHIR R4]].

	==HTTP headers==		==HTTP headers==
Regel 115:		Regel 114:
	; [https://hl7.org/fhir/R4/references.html#logical Logical references], using the {{fhir\|.identifier}} element: Meaning a match on the business identifier ({{fhir\|.identifier}}) for the referenced resource, without specifying where to find the referenced resource. Note: confusingly, although this reference type is called "logical reference", it does ''not'' act on the "logical identifier" ({{fhir\|.id}}) of resources.		; [https://hl7.org/fhir/R4/references.html#logical Logical references], using the {{fhir\|.identifier}} element: Meaning a match on the business identifier ({{fhir\|.identifier}}) for the referenced resource, without specifying where to find the referenced resource. Note: confusingly, although this reference type is called "logical reference", it does ''not'' act on the "logical identifier" ({{fhir\|.id}}) of resources.

	Profiles usually do not constrain which resources may be targeted from a given element. For example, {{fhir\|Condition.subject}} may point to a Patient or Group resource. The {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/nl-core-Problem\|title=nl-core-Problem}} profile adds nl-core-Patient as a third option, to adhere both to [[FHIR:~~Vprepub-1~~.0_FHIR_Profiling_Guidelines_R4#Open_vs._closed_world_modeling\|open world modelling]] and a need to provide useful guidance on how this reference should be handled. However, use case specific profiles may constrain the target profiles.		Profiles usually do not constrain which resources may be targeted from a given element. For example, {{fhir\|Condition.subject}} may point to a Patient or Group resource. The {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/nl-core-Problem\|title=nl-core-Problem}} profile adds nl-core-Patient as a third option, to adhere both to [[FHIR:V1.0_FHIR_Profiling_Guidelines_R4#Open_vs._closed_world_modeling\|open world modelling]] and a need to provide useful guidance on how this reference should be handled. However, use case specific profiles may constrain the target profiles.

	The basic requirements for using references in this context are:		The basic requirements for using references in this context are:
Regel 330:		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:~~Vprepub-1~~.0 FHIR_Error_handling_examples#Not_authorized\|Example]]		\| [[FHIR:V1.0 FHIR_Error_handling_examples#Not_authorized\|Example]]
	\|-		\|-
	\| Invalid authorization, scope of the access token is not sufficient for the request		\| Invalid authorization, scope of the access token is not sufficient for the request
Regel 336:		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:~~Vprepub-1~~.0 FHIR_Error_handling_examples#Invalid_authorization\|Example]]		\| [[FHIR:V1.0 FHIR_Error_handling_examples#Invalid_authorization\|Example]]
	\|-		\|-
	\| Resource is not supported		\| Resource is not supported
Regel 342:		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:~~Vprepub-1~~.0 FHIR_Error_handling_examples#Resource_is_not_supported\|Example]]		\| [[FHIR:V1.0 FHIR_Error_handling_examples#Resource_is_not_supported\|Example]]
	\|-		\|-
	\| rowspan=4 \|search		\| rowspan=4 \|search
Regel 355:		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:~~Vprepub-1~~.0 FHIR_Error_handling_examples#Syntactically_incorrect_parameter\|Example]]		\| [[FHIR:V1.0 FHIR_Error_handling_examples#Syntactically_incorrect_parameter\|Example]]
	\|-		\|-
	\| Known but unsupported value. This situation applies to non-supported profiles when the Resource endpoint itself is supported.		\| Known but unsupported value. This situation applies to non-supported profiles when the Resource endpoint itself is supported.
Regel 363:		Regel 362:
	* OperationOutcome in Bundle as an entry marked with {{fhir\|Bundle.entry.search.mode}} set to {{term\|outcome}}.		* OperationOutcome in Bundle as an entry marked 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:~~Vprepub-1~~.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]]
	\|-		\|-
	\| read		\| read
Regel 370:		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:~~Vprepub-1~~.0 FHIR_Error_handling_examples#Request_on_an_unknown_id\|Example]]		\| [[FHIR:V1.0 FHIR_Error_handling_examples#Request_on_an_unknown_id\|Example]]
	\|-		\|-
	\| update		\| update
Regel 377:		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:~~Vprepub-1~~.0 FHIR_Error_handling_examples#No_or_incorrect_Resource_id\|Example]]		\| [[FHIR:V1.0 FHIR_Error_handling_examples#No_or_incorrect_Resource_id\|Example]]
	\|-		\|-
	\| create/update		\| create/update
Regel 384:		Regel 383:
	* HTTP 400 Bad Request or HTTP 422 Unprocessable Entity		* HTTP 400 Bad Request or HTTP 422 Unprocessable Entity
	* OperationOutcome with {{fhir\|.code}} set to {{term\|invalid}} or preferably a more specific child code.		* OperationOutcome with {{fhir\|.code}} set to {{term\|invalid}} or preferably a more specific child code.
	\| [[FHIR:~~Vprepub-1~~.0 FHIR_Error_handling_examples#Resource_syntax_or_data_is_incorrect_or_invalid\|Example]]		\| [[FHIR:V1.0 FHIR_Error_handling_examples#Resource_syntax_or_data_is_incorrect_or_invalid\|Example]]
	\|}		\|}

Pieter Edelman: Gekopieerd van FHIR:Vprepub-1.0 FHIR IG R4, versie 126738

2022-10-25T09:36:34Z

Gekopieerd van FHIR:Vprepub-1.0 FHIR IG R4, versie 126738

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

Pieter Edelman: MM-3790: Verhuis release notes voor de FHIR R4 Implementation Guide naar centrale pagina

2022-10-24T09:26:34Z

MM-3790: Verhuis release notes voor de FHIR R4 Implementation Guide naar centrale pagina

← Oudere versie		Versie van 24 okt 2022 09:26
Regel 468:		Regel 468:
	<section end=OverarchingPrinciples />		<section end=OverarchingPrinciples />
	=Release notes=		=Release notes=
	{~~\| class="wikitable" "cellpadding="10" style="background-color: white;"~~		{{#lsth:Tabellen met release notes\|Nictiz FHIR R4 Implementation Guide 1}}
	~~!style="text-align:left;"\|Release~~
	~~!style="text-align~~:~~left;"\|Version~~
	~~!style="text-align:left;"\|BITS ticket~~
	~~!style="width:850px; text-align:left;"\|Description~~
	\|-
	~~{{ReleaseNotes\|package=1\|~~release~~=1.0.0~~\|~~issues=~~1~~\|MM-2856~~}}
	\|}

	=Support=		=Support=
	For questions and change requests regarding this IG, please create a ticket in [https://bits.nictiz.nl/projects/MM BITS].		For questions and change requests regarding this IG, please create a ticket in [https://bits.nictiz.nl/projects/MM BITS].

Pieter Edelman: Versie 130752 van Pieter Edelman (overleg) ongedaan gemaakt

2022-08-30T19:18:43Z

Versie 130752 van Pieter Edelman (overleg) ongedaan gemaakt

← Oudere versie		Versie van 30 aug 2022 19:18
Regel 1:		Regel 1:
	__NOINDEX__		__NOINDEX__
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{DISPLAYTITLE:Nictiz FHIR R4 Implementation Guide {{VersieInfo\|FHIR_IG_R4}}}}		{{DISPLAYTITLE:Nictiz FHIR R4 Implementation Guide {{VersieInfo\|FHIR_IG_R4\|release=V1.0}}}}

	__TOC__		__TOC__

Pieter Edelman: Remove unneeded "release" parameter for VersieInfo template

2022-08-30T19:14:49Z

Remove unneeded "release" parameter for VersieInfo template

← Oudere versie		Versie van 30 aug 2022 19:14
Regel 1:		Regel 1:
	__NOINDEX__		__NOINDEX__
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{DISPLAYTITLE:Nictiz FHIR R4 Implementation Guide {{VersieInfo\|FHIR_IG_R4~~\|release=V1.0~~}}}}		{{DISPLAYTITLE:Nictiz FHIR R4 Implementation Guide {{VersieInfo\|FHIR_IG_R4}}}}

	__TOC__		__TOC__

Pieter Edelman: MM-2856: First release of the Nictiz FHIR R4 IG

2022-08-30T09:03:24Z

MM-2856: First release of the Nictiz FHIR R4 IG

Wijzigingen bekijken