FHIR:V1.0 FHIR Profiling Guidelines STU3 - Bewerkingsoverzicht

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

2022-10-25T09:36:39Z

Beveiligde "FHIR:V1.0 FHIR Profiling Guidelines STU3": 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:39Z

Publish prepub to live environment

← Oudere versie		Versie van 25 okt 2022 09:36
Regel 1:		Regel 1:
	~~__NOINDEX__~~
	{{DISPLAYTITLE:FHIR Profiling Guidelines}}		{{DISPLAYTITLE:FHIR Profiling Guidelines}}
	==Introduction==		==Introduction==

Pieter Edelman: Gekopieerd van FHIR:Vprepub-1.0 FHIR Profiling Guidelines STU3, versie 46387

2022-10-25T09:36:34Z

Gekopieerd van FHIR:Vprepub-1.0 FHIR Profiling Guidelines STU3, versie 46387

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

Pieter Edelman: MM-1752: Add guidance on identity of examples and fixtures

2021-03-30T12:43:34Z

MM-1752: Add guidance on identity of examples and fixtures

← Oudere versie		Versie van 30 mrt 2021 12:43
Regel 109:		Regel 109:
	* For profiles: ''<<the final part of the canonical URI>>''.xml		* For profiles: ''<<the final part of the canonical URI>>''.xml
	* For valuesets: ''<<Valueset.name>>''-''<<Valueset.id>>''.xml		* For valuesets: ''<<Valueset.name>>''-''<<Valueset.id>>''.xml

			====Examples and fixtures====
			To ensure ensure consistency of examples and fixtures (example instances used for test/qualification purposes) the {{fhir\|.id}} and file name are standardized in the following way:
			* For fixtures: <code>[profile id]-[3 character project prefix]-[unique string]</code>, capped to 64 characters. The <code>[project prefix]</code> is necessary to prevent the same id from being used by different projects in the same test environment. It is preferably the same as its matching ART-DECOR project prefix.
			* For examples: <code>[profile id]-{[3 character project prefix]-}[unique string]</code>, capped to 64 characters (the <code>[3 character project prefix]</code> is not needed for examples, but may be included to facilitate re-use of tools for both fixtures and examples).

	===Profile meta data===		===Profile meta data===

Pieter Edelman: Create prepub environment from FHIR:V1.0

2021-01-05T13:41:23Z

Create prepub environment from FHIR:V1.0

← Oudere versie		Versie van 5 jan 2021 13:41
Regel 1:		Regel 1:
			__NOINDEX__
	{{DISPLAYTITLE:FHIR Profiling Guidelines}}		{{DISPLAYTITLE:FHIR Profiling Guidelines}}
	==Introduction==		==Introduction==

Pieter Edelman: Gekopieerd van FHIR:V1.0 FHIR Profiling Guidelines STU3, versie 8749

2021-01-05T13:41:22Z

Gekopieerd van FHIR:V1.0 FHIR Profiling Guidelines STU3, versie 8749

← Oudere versie	Versie van 5 jan 2021 13:41
(geen verschil)

Pieter Edelman: Pieter Edelman heeft pagina FHIR:FHIR Profiling Guidelines hernoemd naar FHIR:V1.0 FHIR Profiling Guidelines STU3

2020-12-03T12:07:00Z

Pieter Edelman heeft pagina FHIR:FHIR Profiling Guidelines hernoemd naar FHIR:V1.0 FHIR Profiling Guidelines STU3

← Oudere versie	Versie van 3 dec 2020 12:07
(geen verschil)

Pieter Edelman: Correct title after move to the FHIR namespace

2020-11-05T16:31:07Z

Correct title after move to the FHIR namespace

← Oudere versie		Versie van 5 nov 2020 16:31
Regel 1:		Regel 1:
			{{DISPLAYTITLE:FHIR Profiling Guidelines}}
	==Introduction==		==Introduction==

Pieter Edelman: Pieter Edelman heeft pagina FHIR Profiling Guidelines hernoemd naar FHIR:FHIR Profiling Guidelines: Onboard this page into the FHIR namespace

2020-11-05T16:29:38Z

Pieter Edelman heeft pagina FHIR Profiling Guidelines hernoemd naar FHIR:FHIR Profiling Guidelines: Onboard this page into the FHIR namespace

← Oudere versie	Versie van 5 nov 2020 16:29
(geen verschil)

Pieter Edelman: Fix broken link

2020-09-14T09:18:00Z

Fix broken link

← Oudere versie		Versie van 14 sep 2020 09:18
Regel 224:		Regel 224:
	** The HCIM Dutch concept name is placed in the profile element.alias		** The HCIM Dutch concept name is placed in the profile element.alias
	** {{anchor\|Placing-Info}}''Note: as a rule of thumb, we place this info 'as close as possible' to the elements that actually represent the data. For example: when slicing, the texts are placed on the slice content, not the slice itself. Similarly, in concept containers like Observation.component, this info is placed on the .valueXXX elements. This is also true for [[#Associating_functional_definition_to_StructureDefinition \| the HCIM mappings]].''		** {{anchor\|Placing-Info}}''Note: as a rule of thumb, we place this info 'as close as possible' to the elements that actually represent the data. For example: when slicing, the texts are placed on the slice content, not the slice itself. Similarly, in concept containers like Observation.component, this info is placed on the .valueXXX elements. This is also true for [[#Associating_functional_definition_to_StructureDefinition \| the HCIM mappings]].''
	** Implementation guidance, such as mapping clarification and usage, of HCIM concepts that are mapped to multiple elements is given on the root of the resource. The [http://simplifier.net/resolve?fhirVersion=STU3&scope=nictiz.fhir.nl.stu3.zib2017@2.0.0&canonical=http://fhir.nl/fhir/StructureDefinition/nl-core-address provides a good example.		** Implementation guidance, such as mapping clarification and usage, of HCIM concepts that are mapped to multiple elements is given on the root of the resource. The [http://simplifier.net/resolve?fhirVersion=STU3&scope=nictiz.fhir.nl.stu3.zib2017@2.0.0&canonical=http://fhir.nl/fhir/StructureDefinition/nl-core-address nl-core-address profile] provides a good example.
	* Slices get an UpperCamelCased name based on the HCIM element name.		* Slices get an UpperCamelCased name based on the HCIM element name.
	* New elements defined through extensions get a lowerCamelCased name based on the HCIM element name.		* New elements defined through extensions get a lowerCamelCased name based on the HCIM element name.