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

Pieter Edelman: Tweak the text

2021-11-17T16:07:07Z

Tweak the text

← Oudere versie		Versie van 17 nov 2021 16:07
Regel 156:		Regel 156:

	=Mapping start and end dates to profiles=		=Mapping start and end dates to profiles=
	~~A number of~~ zibs ~~contain~~ a ~~concept for both~~ a StartDate and EndDate ~~that can be used to record~~ an instantaneous moment by using only the StartDate (~~sometimes~~ the definition text of those concepts may provide an indication) ~~or as a period. Zibs don't have a Period datatype but do have a part zib named TimeInterval which is however not applied to all zibs~~. FHIR ~~does have~~ Period datatype, ~~consisting of a {{fhir\|Period.start}} and {{fhir\|Period.end}} element. A FHIR Period contains additional meaning:~~ a missing {{fhir\|Period.end}} element implies an ongoing period which in turn affects the functioning of searches.		There are several zibs that record either a period using a combination of the StartDate and EndDate concept<ref>Zibs don't have a period datatype, although a partial zib named TimeInterval exists. This is not widely applied however.</ref>, or an instantaneous moment using only the StartDate concept (note that this is not consequently applied; the definition text of those concepts may provide an indication when this is the case). This differs from the FHIR Period datatype, where a missing {{fhir\|Period.end}} element implies an ongoing period, which in turn affects the functioning of searches.

	Because a zib StartDate concept can sometimes be ~~interperted~~ as an instantaneous moment and sometimes as the start of a period the following guidelines ~~are made~~:		Because the zib StartDate concept can sometimes be interpreted as an instantaneous moment and sometimes as the start of a period, the following guidelines apply:
	* When a mapping can be made to a polymorphic FHIR element (e.g. {{fhir\|Procedure.perfomed[x]}}) that contains both a Period and a DateTime, the element will be type sliced and will hold a mapping to the StartDate concept on the DateTime and ~~Period slice (at~~ {{fhir\|Period.start}}).		* When a mapping can be made to a polymorphic FHIR element (e.g. {{fhir\|Procedure.perfomed[x]}}) that contains both a Period and a DateTime, the element will be type sliced and will hold a mapping to the StartDate concept on the DateTime, and on {{fhir\|Period.start}} in the Period slice.
	* When mapped to an element of Period datatype only (e.g. Encounter.period), the element should contain documentation that an equal value for {{fhir\|Period.start}} and {{fhir\|Period.end}} can be used for instantaneous ~~momements~~. (Please note that in R4 Period contains an invariant that has an incorrect description stating this is not possible. The expression ~~it self~~ is correct. The invariant description will be fixed in R5.)		* When mapped to an element of Period datatype only (e.g. {{fhir\|Encounter.period}}), the element should contain documentation that an equal value for {{fhir\|Period.start}} and {{fhir\|Period.end}} can be used for instantaneous moments. (Please note that in R4 Period contains an invariant that has an incorrect description stating this is not possible. The expression itself is correct. The invariant description will be fixed in R5.)

	=Slicing=		=Slicing=

Ardon Toonstra: /* Mapping start and end dates to profiles */

2021-11-15T16:11:53Z

Mapping start and end dates to profiles

← Oudere versie		Versie van 15 nov 2021 16:11
Regel 159:		Regel 159:

	Because a zib StartDate concept can sometimes be interperted as an instantaneous moment and sometimes as the start of a period the following guidelines are made:		Because a zib StartDate concept can sometimes be interperted as an instantaneous moment and sometimes as the start of a period the following guidelines are made:
	* When a mapping can be made to a polymorphic FHIR element (e.g. {{fhir\|Procedure.perfomed[x]}}) that contains both a Period and a DateTime, the element will be type sliced and will hold a mapping to the StartDate concept on the {{fhir\|Period.start}} ~~and {{fhir\|DateTime}}~~.		* When a mapping can be made to a polymorphic FHIR element (e.g. {{fhir\|Procedure.perfomed[x]}}) that contains both a Period and a DateTime, the element will be type sliced and will hold a mapping to the StartDate concept on the DateTime and Period slice (at {{fhir\|Period.start}}).
	* When mapped to a Period datatype only (e.g. Encounter.period) the element should contain documentation that an equal value for {{fhir\|Period.start}} and {{fhir\|Period.end}} can be used for instantaneous momements. (Please note that in R4 Period contains an invariant that has an incorrect description stating this is not possible. The expression it self is correct. The invariant description will be fixed in R5.)		* When mapped to an element of Period datatype only (e.g. Encounter.period), the element should contain documentation that an equal value for {{fhir\|Period.start}} and {{fhir\|Period.end}} can be used for instantaneous momements. (Please note that in R4 Period contains an invariant that has an incorrect description stating this is not possible. The expression it self is correct. The invariant description will be fixed in R5.)

	=Slicing=		=Slicing=

Ardon Toonstra: /* Mapping start and end dates to profiles */

2021-11-15T16:09:53Z

Mapping start and end dates to profiles

← Oudere versie		Versie van 15 nov 2021 16:09
Regel 161:		Regel 161:
	* When a mapping can be made to a polymorphic FHIR element (e.g. {{fhir\|Procedure.perfomed[x]}}) that contains both a Period and a DateTime, the element will be type sliced and will hold a mapping to the StartDate concept on the {{fhir\|Period.start}} and {{fhir\|DateTime}}.		* When a mapping can be made to a polymorphic FHIR element (e.g. {{fhir\|Procedure.perfomed[x]}}) that contains both a Period and a DateTime, the element will be type sliced and will hold a mapping to the StartDate concept on the {{fhir\|Period.start}} and {{fhir\|DateTime}}.
	* When mapped to a Period datatype only (e.g. Encounter.period) the element should contain documentation that an equal value for {{fhir\|Period.start}} and {{fhir\|Period.end}} can be used for instantaneous momements. (Please note that in R4 Period contains an invariant that has an incorrect description stating this is not possible. The expression it self is correct. The invariant description will be fixed in R5.)		* When mapped to a Period datatype only (e.g. Encounter.period) the element should contain documentation that an equal value for {{fhir\|Period.start}} and {{fhir\|Period.end}} can be used for instantaneous momements. (Please note that in R4 Period contains an invariant that has an incorrect description stating this is not possible. The expression it self is correct. The invariant description will be fixed in R5.)


	=Slicing=		=Slicing=

Ardon Toonstra: Added guidance for mapping start and end dates to profiles

2021-11-15T16:09:06Z

Added guidance for mapping start and end dates to profiles

← Oudere versie		Versie van 15 nov 2021 16:09
Regel 154:		Regel 154:

	These codes are profiled as required elements using a {{fhir\|ElementDefinition.pattern}} on the element that should contain the code. This allows to add additional codings on the same element.		These codes are profiled as required elements using a {{fhir\|ElementDefinition.pattern}} on the element that should contain the code. This allows to add additional codings on the same element.

			=Mapping start and end dates to profiles=
			A number of zibs contain a concept for both a StartDate and EndDate that can be used to record an instantaneous moment by using only the StartDate (sometimes the definition text of those concepts may provide an indication) or as a period. Zibs don't have a Period datatype but do have a part zib named TimeInterval which is however not applied to all zibs. FHIR does have Period datatype, consisting of a {{fhir\|Period.start}} and {{fhir\|Period.end}} element. A FHIR Period contains additional meaning: a missing {{fhir\|Period.end}} element implies an ongoing period which in turn affects the functioning of searches.

			Because a zib StartDate concept can sometimes be interperted as an instantaneous moment and sometimes as the start of a period the following guidelines are made:
			* When a mapping can be made to a polymorphic FHIR element (e.g. {{fhir\|Procedure.perfomed[x]}}) that contains both a Period and a DateTime, the element will be type sliced and will hold a mapping to the StartDate concept on the {{fhir\|Period.start}} and {{fhir\|DateTime}}.
			* When mapped to a Period datatype only (e.g. Encounter.period) the element should contain documentation that an equal value for {{fhir\|Period.start}} and {{fhir\|Period.end}} can be used for instantaneous momements. (Please note that in R4 Period contains an invariant that has an incorrect description stating this is not possible. The expression it self is correct. The invariant description will be fixed in R5.)


	=Slicing=		=Slicing=

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

2021-11-15T15:24:48Z

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

Wijzigingen bekijken