FHIR:Vissue-github-139 FHIR Profiling Guidelines R4 - Bewerkingsoverzicht

Pieter Edelman: /* SearchParameters */

2022-03-10T09:24:34Z

SearchParameters

← Oudere versie		Versie van 10 mrt 2022 09:24
Regel 312:		Regel 312:
	** A descriptive name for the target if the search parameter applies to more than one resource type, e.g. "Medication" if the search parameter applies to medication related resources.		** A descriptive name for the target if the search parameter applies to more than one resource type, e.g. "Medication" if the search parameter applies to medication related resources.
	*The canonical URL will then be: <code><nowiki>http://nictiz.nl/fhir/SearchParameter/[id]</nowiki></code>		*The canonical URL will then be: <code><nowiki>http://nictiz.nl/fhir/SearchParameter/[id]</nowiki></code>
	*The name will be: <code>[target]-[code]</code> PascalCased and with dashes and such removed in <code>[target]</code> and <code>[code]</code>, unless a better scheme is deemed more appropriate.		*The name will be: <code>[target]_[code]</code> PascalCased and with dashes and such removed in <code>[target]</code> and <code>[code]</code>, unless a better scheme is deemed more appropriate.
	*The description will describe the working of the search parameter.		*The description will describe the working of the search parameter.
	*The purpose will be populated to indicate why the SearchParameter is created.		*The purpose will be populated to indicate why the SearchParameter is created.

Pieter Edelman: /* SearchParameters */

2022-03-09T16:03:54Z

SearchParameters

← Oudere versie		Versie van 9 mrt 2022 16:03
Regel 305:		Regel 305:
	SearchParameters are generally added from the nl-core layer onwards because the zib layer is without an use case definition.		SearchParameters are generally added from the nl-core layer onwards because the zib layer is without an use case definition.
	*The code should consist of one or multiple words in lowercase ASCII characters, with multiple words separated using a dash ("-"):		*The code should consist of one or multiple words in lowercase ASCII characters, with multiple words separated using a dash ("-"):
	** If the search parameter doesn't pertain a specific functional model of use case, the FHIR element that the search parameter acts on should be used.		** If the search parameter doesn't pertain to a specific functional model or use case, the FHIR element that the search parameter acts on should be used.
	** If the search parameter does pertain a specific functional model or use case, the English name of the functional concept should be used.		** If the search parameter does pertain to a specific functional model or use case, the English name of the functional concept should be used.
	** If these guidelines aren't feasible, another descriptive name may be used at the profilers discretion.		** If these guidelines aren't feasible, another descriptive name may be used at the profilers discretion.
	*The id will be: <code>~~SearchParameter-~~[target]-[code]</code>, where <code>[target]</code> is:		*The id will be: <code>[target]-[code]</code>, where <code>[target]</code> is:
	** The resource name if the search parameter applies to a single resource type.		** The resource name if the search parameter applies to a single resource type.
	** A descriptive name for the target if the search parameter applies to more than one resource type, e.g. "Medication" if the search parameter applies to medication related resources.		** A descriptive name for the target if the search parameter applies to more than one resource type, e.g. "Medication" if the search parameter applies to medication related resources.

Pieter Edelman: /* SearchParameters */

2022-03-09T15:52:15Z

SearchParameters

← Oudere versie		Versie van 9 mrt 2022 15:52
Regel 312:		Regel 312:
	** A descriptive name for the target if the search parameter applies to more than one resource type, e.g. "Medication" if the search parameter applies to medication related resources.		** A descriptive name for the target if the search parameter applies to more than one resource type, e.g. "Medication" if the search parameter applies to medication related resources.
	*The canonical URL will then be: <code><nowiki>http://nictiz.nl/fhir/SearchParameter/[id]</nowiki></code>		*The canonical URL will then be: <code><nowiki>http://nictiz.nl/fhir/SearchParameter/[id]</nowiki></code>
	*The name will be: <code>[code]</code> PascalCased and with dashes and such removed, unless a better scheme is deemed more appropriate.		*The name will be: <code>[target]-[code]</code> PascalCased and with dashes and such removed in <code>[target]</code> and <code>[code]</code>, unless a better scheme is deemed more appropriate.
	*The description will describe the working of the search parameter.		*The description will describe the working of the search parameter.
	*The purpose will be populated to indicate why the SearchParameter is created.		*The purpose will be populated to indicate why the SearchParameter is created.

Pieter Edelman: /* SearchParameters */

2022-03-09T15:48:35Z

SearchParameters

← Oudere versie		Versie van 9 mrt 2022 15:48
Regel 304:		Regel 304:
	====SearchParameters====		====SearchParameters====
	SearchParameters are generally added from the nl-core layer onwards because the zib layer is without an use case definition.		SearchParameters are generally added from the nl-core layer onwards because the zib layer is without an use case definition.
	*The code ~~will be constructed as: English translation~~ of ~~the functional concept, using only~~ lowercase ASCII characters ~~and separating~~ multiple words using a dash ("-"). If ~~no direct~~ functional ~~concept exists~~, the FHIR element to search on or ~~an appropriate description can~~ be used.		*The code should consist of one or multiple words in lowercase ASCII characters, with multiple words separated using a dash ("-"):
			** If the search parameter doesn't pertain a specific functional model of use case, the FHIR element that the search parameter acts on should be used.
			** If the search parameter does pertain a specific functional model or use case, the English name of the functional concept should be used.
			** If these guidelines aren't feasible, another descriptive name may be used at the profilers discretion.
	*The id will be: <code>SearchParameter-[target]-[code]</code>, where <code>[target]</code> is:		*The id will be: <code>SearchParameter-[target]-[code]</code>, where <code>[target]</code> is:
	** The resource name if the search parameter applies to a single resource type.		** The resource name if the search parameter applies to a single resource type.

Pieter Edelman: /* SearchParameters */

2022-03-09T15:36:11Z

SearchParameters

← Oudere versie		Versie van 9 mrt 2022 15:36
Regel 304:		Regel 304:
	====SearchParameters====		====SearchParameters====
	SearchParameters are generally added from the nl-core layer onwards because the zib layer is without an use case definition.		SearchParameters are generally added from the nl-core layer onwards because the zib layer is without an use case definition.
	*The code will be constructed as: English translation of the functional concept ~~used to search~~, using only lowercase ASCII characters~~. Multiple~~ words ~~are separated by~~ a dash ("-").		*The code will be constructed as: English translation of the functional concept, using only lowercase ASCII characters and separating multiple words using a dash ("-"). If no direct functional concept exists, the FHIR element to search on or an appropriate description can be used.
	*The id will be: <code>SearchParameter-[target]-[code]</code>, where <code>[target]</code> is:		*The id will be: <code>SearchParameter-[target]-[code]</code>, where <code>[target]</code> is:
	** The resource name if the search parameter applies to a single resource type.		** The resource name if the search parameter applies to a single resource type.

Pieter Edelman: Adjust proposal for SearchParameter metadata

2022-03-09T15:21:50Z

Adjust proposal for SearchParameter metadata

← Oudere versie		Versie van 9 mrt 2022 15:21
Regel 304:		Regel 304:
	====SearchParameters====		====SearchParameters====
	SearchParameters are generally added from the nl-core layer onwards because the zib layer is without an use case definition.		SearchParameters are generally added from the nl-core layer onwards because the zib layer is without an use case definition.
	*The id will be constructed as: English translation of the functional concept used to search, only lowercase ASCII characters. ~~Words~~ separated by a dash ('-').		*The code will be constructed as: English translation of the functional concept used to search, using only lowercase ASCII characters. Multiple words are separated by a dash ("-").
			*The id will be: <code>SearchParameter-[target]-[code]</code>, where <code>[target]</code> is:
			** The resource name if the search parameter applies to a single resource type.
			** A descriptive name for the target if the search parameter applies to more than one resource type, e.g. "Medication" if the search parameter applies to medication related resources.
	*The canonical URL will then be: <code><nowiki>http://nictiz.nl/fhir/SearchParameter/[id]</nowiki></code>		*The canonical URL will then be: <code><nowiki>http://nictiz.nl/fhir/SearchParameter/[id]</nowiki></code>
	*The name will be: <code>[id]</code> ~~capitalized~~ and with dashes and such removed, unless a better scheme is deemed more appropriate.		*The name will be: <code>[code]</code> PascalCased and with dashes and such removed, unless a better scheme is deemed more appropriate.
	*The code will be: <code>[id]</code>
	*The description will describe the working of the search parameter.		*The description will describe the working of the search parameter.
	*The purpose will be populated to indicate why the SearchParameter is created.		*The purpose will be populated to indicate why the SearchParameter is created.

Ardon Toonstra: /* SearchParameters */

2021-11-29T15:09:14Z

SearchParameters

← Oudere versie		Versie van 29 nov 2021 15:09
Regel 310:		Regel 310:
	*The description will describe the working of the search parameter.		*The description will describe the working of the search parameter.
	*The purpose will be populated to indicate why the SearchParameter is created.		*The purpose will be populated to indicate why the SearchParameter is created.
	*The expression ~~is provider rather than xpath~~.		*The search parameter is expressed using {{fhir\|.expression}}.

	====Examples and fixtures====		====Examples and fixtures====

Ardon Toonstra: /* Practical guidelines */

2021-11-29T15:06:01Z

Practical guidelines

← Oudere versie		Versie van 29 nov 2021 15:06
Regel 301:		Regel 301:
	*The name will be constructed as: <code>[source ValueSet.name]_to_[target ValueSet.name]</code>		*The name will be constructed as: <code>[source ValueSet.name]_to_[target ValueSet.name]</code>
	*The title will be constructed as: <code>[source ValueSet.name] to [target ValueSet.name]</code>		*The title will be constructed as: <code>[source ValueSet.name] to [target ValueSet.name]</code>

			====SearchParameters====
			SearchParameters are generally added from the nl-core layer onwards because the zib layer is without an use case definition.
			*The id will be constructed as: English translation of the functional concept used to search, only lowercase ASCII characters. Words separated by a dash ('-').
			*The canonical URL will then be: <code><nowiki>http://nictiz.nl/fhir/SearchParameter/[id]</nowiki></code>
			*The name will be: <code>[id]</code> capitalized and with dashes and such removed, unless a better scheme is deemed more appropriate.
			*The code will be: <code>[id]</code>
			*The description will describe the working of the search parameter.
			*The purpose will be populated to indicate why the SearchParameter is created.
			*The expression is provider rather than xpath.

	====Examples and fixtures====		====Examples and fixtures====
	Examples and fixtures (example instances used for test/qualification purposes) are not conformance resources and lack the {{fhir\|.url}}, {{fhir\|.name}} and {{fhir\|.title}} elements. However, to ensure consistency, the {{fhir\|.id}} is standardized in the following way:		Examples and fixtures (example instances used for test/qualification purposes) are not conformance resources and lack the {{fhir\|.url}}, {{fhir\|.name}} and {{fhir\|.title}} elements. However, to ensure consistency, the {{fhir\|.id}} is standardized in the following way:
Regel 313:		Regel 324:
	; codesystems: <code>resources/terminology/codesystem-[name].xml</code>		; codesystems: <code>resources/terminology/codesystem-[name].xml</code>
	; namingsystems: <code>resources/terminology/[id].xml</code>		; namingsystems: <code>resources/terminology/[id].xml</code>
			; searchparameters: <code>resources/searchparameter-[id].xml</code>
	; examples: <code>examples/[profile id]-[serial number, two digits].xml</code>		; examples: <code>examples/[profile id]-[serial number, two digits].xml</code>

Ardon Toonstra: Clone of V1.0 production page for issue github-139

2021-11-29T14:58:36Z

Clone of V1.0 production page for issue github-139

Wijzigingen bekijken