FHIR:Vissue-286 FHIR Profiling Guidelines R4 - Bewerkingsoverzicht

Pieter Edelman: /* Current implementation */

2022-09-07T15:25:19Z

Current implementation

← Oudere versie		Versie van 7 sep 2022 15:25
Regel 114:		Regel 114:
	* The {{fhir\|.mapping.identity}} should be a constructed in the following way:		* The {{fhir\|.mapping.identity}} should be a constructed in the following way:
	** For zibs, this SHOULD be the <q>zib-[English zib name, lowercased]-v[version]-[publication]EN</q>		** For zibs, this SHOULD be the <q>zib-[English zib name, lowercased]-v[version]-[publication]EN</q>
	** For functional models in ART-DECOR, this SHOULD be, all in lowercase, <q>[project prefix][dataset name]-[dataset effectiveDate as 'yyyymmdd']</q>. The dataset name SHOULD be the English name if available, otherwise it SHOULD be the Dutch name. If the project prefix and dataset name are similar, it's better to not repeat it and simply use 'dataset'.		** For functional models in ART-DECOR, this SHOULD be, all in lowercase, <q>[project prefix][dataset name]-[dataset effectiveDate as 'yyyymmdd']</q>. The dataset name SHOULD be the English name if available, otherwise it SHOULD be the Dutch name. All spaces are replaced by dashes. If the project prefix and dataset name are similar, it's better to not repeat it and simply use 'dataset'.
	* The {{fhir\|.mapping.name}} should be constructed in the following way:		* The {{fhir\|.mapping.name}} should be constructed in the following way:
	** For zibs, this SHOULD be <q>zib [English zib name]-v[version]([publication]EN)</q>		** For zibs, this SHOULD be <q>zib [English zib name]-v[version]([publication]EN)</q>
	** For functional models in ART-DECOR, this SHOULD be <q>ART-DECOR Dataset [dataset name] [dataset effectiveDate ~~as 'yyyymmdd'~~]</q>. The dataset name SHOULD be the English name if available, otherwise it SHOULD be the Dutch name. If the dataset name contains the word 'dataset', it SHOULD not be repeated.		** For functional models in ART-DECOR, this SHOULD be <q>ART-DECOR Dataset [dataset name] [dataset effectiveDate]</q>. The dataset name SHOULD be the English name if available, otherwise it SHOULD be the Dutch name. If the dataset name contains the word 'dataset', it SHOULD not be repeated.
	* Functional concepts are referenced based on their id in the functional model, which should be used to populate {{fhir\|.mapping.map}}.		* Functional concepts are referenced based on their id in the functional model, which should be used to populate {{fhir\|.mapping.map}}.
	* The description of the functional concept is ''normally'' placed in {{fhir\|.mapping.comment}}, unless other rules apply (see [[#References that are reversed in FHIR]]).		* The description of the functional concept is ''normally'' placed in {{fhir\|.mapping.comment}}, unless other rules apply (see [[#References that are reversed in FHIR]]).

Pieter Edelman: Adjust the guidance to the latest insights

2022-09-07T15:20:12Z

Adjust the guidance to the latest insights

← Oudere versie		Versie van 7 sep 2022 15:20
Regel 111:		Regel 111:
	* The mapping {{fhir\|.mapping.uri}} SHALL resolve to a description of the functional model:		* The mapping {{fhir\|.mapping.uri}} SHALL resolve to a description of the functional model:
	** For zibs, this SHOULD be the English page on zibs.nl.		** For zibs, this SHOULD be the English page on zibs.nl.
	** For functional models in ART-DECOR, this SHOULD be the link to the ~~publication~~ on ART-DECOR.		** For functional models in ART-DECOR, this SHOULD be the link to the dataset on ART-DECOR v3 in the format of <q>[host]/ad/#/[prefix]/datasets/dataset/[dataset id]/[dataset effectiveDate]</q>
	* The {{fhir\|.mapping.identity}} should be a constructed in the following way:		* The {{fhir\|.mapping.identity}} should be a constructed in the following way:
	** For zibs, this SHOULD be the <q>zib-[English zib name, lowercased]-v[version]-[publication]EN</q>		** For zibs, this SHOULD be the <q>zib-[English zib name, lowercased]-v[version]-[publication]EN</q>
	** For functional models in ART-DECOR, this SHOULD be <q>[~~English~~ name ~~of the project~~]-v[~~major.minor~~]</q>~~, where spaces are replaced by dashes in the~~ name of the ~~project and "major" and "minor" are the major and minor numbers of the version. If no~~ English name is available, the Dutch name ~~SHOULD be used instead~~.		** For functional models in ART-DECOR, this SHOULD be, all in lowercase, <q>[project prefix][dataset name]-[dataset effectiveDate as 'yyyymmdd']</q>. The dataset name SHOULD be the English name if available, otherwise it SHOULD be the Dutch name. If the project prefix and dataset name are similar, it's better to not repeat it and simply use 'dataset'.
	* The {{fhir\|.name}} should be constructed in the following way:		* The {{fhir\|.mapping.name}} should be constructed in the following way:
	** For zibs, this SHOULD be <q>zib [English zib name]-v[version]([publication]EN)</q>		** For zibs, this SHOULD be <q>zib [English zib name]-v[version]([publication]EN)</q>
	** For functional models in ART-DECOR, this SHOULD be <q>[~~English~~ name ~~of the project~~]-v[~~major.minor~~]</q>~~, where "major" and "minor" are~~ the ~~major and minor numbers of the version. If no~~ English name is available, the Dutch name SHOULD be ~~used instead~~.		** For functional models in ART-DECOR, this SHOULD be <q>ART-DECOR Dataset [dataset name] [dataset effectiveDate as 'yyyymmdd']</q>. The dataset name SHOULD be the English name if available, otherwise it SHOULD be the Dutch name. If the dataset name contains the word 'dataset', it SHOULD not be repeated.
	* Functional concepts are referenced based on their id in the functional model, which should be used to populate {{fhir\|.mapping.map}}.		* Functional concepts are referenced based on their id in the functional model, which should be used to populate {{fhir\|.mapping.map}}.
	* The description of the functional concept is ''normally'' placed in {{fhir\|.mapping.comment}}, unless other rules apply (see [[#References that are reversed in FHIR]]).		* The description of the functional concept is ''normally'' placed in {{fhir\|.mapping.comment}}, unless other rules apply (see [[#References that are reversed in FHIR]]).

Pieter Edelman: Improve text layout

2022-07-28T08:26:52Z

Improve text layout

← Oudere versie		Versie van 28 jul 2022 08:26
Regel 100:		Regel 100:
	Any StructureDefinition that profiles a Resource does so because there is some kind of logical definition ''dictating'' how. Profiles SHALL have a traceable relationship with their functional counterpart(s).		Any StructureDefinition that profiles a Resource does so because there is some kind of logical definition ''dictating'' how. Profiles SHALL have a traceable relationship with their functional counterpart(s).

	The FHIR specification contains several solutions for this problem, [http://hl7.org/fhir/conceptmap.html ConceptMap] (>=STU1), [http://hl7-fhir.github.io/structuredefinition.html StructureMap] (>=STU3), [http://hl7.org/fhir/elementdefinition-definitions.html ElementDefinition.mapping]. Neither of these solutions are mature and cover our use case.		The FHIR specification contains several solutions for this problem, [http://hl7.org/fhir/conceptmap.html ConceptMap] (>=STU1), [http://hl7-fhir.github.io/structuredefinition.html StructureMap] (>=STU3), [http://hl7.org/fhir/elementdefinition-definitions.html {{fhir\|ElementDefinition.mapping}}]. Neither of these solutions are mature and cover our use case.

	* ConceptMap: works best for value sets and codes.		* ConceptMap: works best for value sets and codes.
	* StructureMap: overcomplicated and unclear how to apply and whether or not this has a future.		* StructureMap: overcomplicated and unclear how to apply and whether or not this has a future.
	* ElementDefinition.mapping: is a free text mapping ''inside'' the profile. This means we cannot add mappings to profiles from third parties without updating their resource.		* {{fhir\|ElementDefinition.mapping}}: is a free text mapping ''inside'' the profile. This means we cannot add mappings to profiles from third parties without updating their resource.

	===Current implementation===		===Current implementation===

Pieter Edelman: #286: Lay down guidelines for mapping metadata

2022-07-28T08:22:27Z

#286: Lay down guidelines for mapping metadata

← Oudere versie		Versie van 28 jul 2022 08:22
Regel 108:		Regel 108:
	===Current implementation===		===Current implementation===

	We use the mapping elements in profiles to map functional ~~elements~~ to resource elements. ~~Functional elements are referenced based on their id in the functional model~~. ~~The~~ mapping SHALL resolve to a description of the functional model. For zibs, this SHOULD be the English page on zibs.nl.		We use the {{fhir\|StructureDefinition.mapping}} and {{fhir\|ElementDefinition.mapping}} elements in profiles to map functional concepts to resource elements. The following rules apply:
			* The mapping {{fhir\|.mapping.uri}} SHALL resolve to a description of the functional model:
			** For zibs, this SHOULD be the English page on zibs.nl.
			** For functional models in ART-DECOR, this SHOULD be the link to the publication on ART-DECOR.
			* The {{fhir\|.mapping.identity}} should be a constructed in the following way:
			** For zibs, this SHOULD be the <q>zib-[English zib name, lowercased]-v[version]-[publication]EN</q>
			** For functional models in ART-DECOR, this SHOULD be <q>[English name of the project]-v[major.minor]</q>, where spaces are replaced by dashes in the name of the project and "major" and "minor" are the major and minor numbers of the version. If no English name is available, the Dutch name SHOULD be used instead.
			* The {{fhir\|.name}} should be constructed in the following way:
			** For zibs, this SHOULD be <q>zib [English zib name]-v[version]([publication]EN)</q>
			** For functional models in ART-DECOR, this SHOULD be <q>[English name of the project]-v[major.minor]</q>, where "major" and "minor" are the major and minor numbers of the version. If no English name is available, the Dutch name SHOULD be used instead.
			* Functional concepts are referenced based on their id in the functional model, which should be used to populate {{fhir\|.mapping.map}}.
			* The description of the functional concept is ''normally'' placed in {{fhir\|.mapping.comment}}, unless other rules apply (see [[#References that are reversed in FHIR]]).
			* When slicing, the mapping is made on the ''content'' of the slice, not the slice itself (see also [[#Placing-Info]]).

	~~When slicing, the mapping is made~~ on ~~the ''content'' of the slice, not the slice itself (see also [[#Placing-Info]]).~~		So on the root of the StructureDefinition, the mapping for a zib should be defined as:

	On the root ~~element~~ of the StructureDefinition, the mapping should ~~thus~~ be defined as:
	<syntaxhighlight lang="xml">		<syntaxhighlight lang="xml">
	<mapping>		<mapping>

Pieter Edelman: Clone of V1.0 production page for issue 286

2022-07-28T07:58:13Z

Clone of V1.0 production page for issue 286

Wijzigingen bekijken