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

Pieter Edelman: /* With a functional counterpart with a lower cardinality of 0 */

2021-12-17T09:44:26Z

With a functional counterpart with a lower cardinality of 0

← Oudere versie		Versie van 17 dec 2021 09:44
Regel 238:		Regel 238:
	* Other metadata ({{fhir\|.definition}}, {{fhir\|.short}}, {{fhir\|.alias}}) isn't populated according to the normal guidelines.		* Other metadata ({{fhir\|.definition}}, {{fhir\|.short}}, {{fhir\|.alias}}) isn't populated according to the normal guidelines.

	==With a functional counterpart with a ~~lower~~ cardinality of 0==		==With a functional counterpart with a minimal cardinality of 0==
	On occasion, a ~~zib~~ concept with a ~~lower~~ (conceptual) cardinality of 0 is mapped to a mandatory FHIR element. ~~The profile may give~~ guidance on how to populate the element if no meaningful value can be derived from the zib. For example, the concept TextResultStatus of zib TextResult is mapped to {{fhir\|DiagnosticReport.status}}, where value 'unknown' can be used if the value of zib concept TextResultStatus is not present.		On occasion, a functional concept with a minimal (conceptual) cardinality of 0 is mapped to a mandatory FHIR element. Ann effort should be made to provide guidance on how to populate the element if no meaningful value can be derived from the zib. For example, the concept TextResultStatus of zib TextResult is mapped to {{fhir\|DiagnosticReport.status}}, where value {{term\|unknown}} can be used if the value of zib concept TextResultStatus is not present.

	If no guidance can be provided in the profile, it is up to sending systems to populate the element with a meaningful value from the context of their data~~. Except for elements with required bindings, an implementer can indicate that~~ the ~~content of the element is missing (e.g. using the data-absent-reason extension). The~~ implementation guide should describe how the implementer should deal with this situation.		If no guidance can be provided in the profile, it is up to sending systems to populate the element with a meaningful value from the context of their data and the implementation guide should describe how the implementer should deal with this situation.

	=Practical guidelines=		=Practical guidelines=

Ardon Toonstra: /* With a functional counterpart with a lower cardinality of 0 */

2021-11-29T10:14:49Z

With a functional counterpart with a lower cardinality of 0

← Oudere versie		Versie van 29 nov 2021 10:14
Regel 241:		Regel 241:
	On occasion, a zib concept with a lower (conceptual) cardinality of 0 is mapped to a mandatory FHIR element. The profile may give guidance on how to populate the element if no meaningful value can be derived from the zib. For example, the concept TextResultStatus of zib TextResult is mapped to {{fhir\|DiagnosticReport.status}}, where value 'unknown' can be used if the value of zib concept TextResultStatus is not present.		On occasion, a zib concept with a lower (conceptual) cardinality of 0 is mapped to a mandatory FHIR element. The profile may give guidance on how to populate the element if no meaningful value can be derived from the zib. For example, the concept TextResultStatus of zib TextResult is mapped to {{fhir\|DiagnosticReport.status}}, where value 'unknown' can be used if the value of zib concept TextResultStatus is not present.

	If the profile ~~does not give any guidance~~, it is up to sending systems to populate the element with a meaningful value from the context of their data. ~~If the FHIR element has a~~ required ~~binding, this is mandatory. Otherwise~~, ~~the~~ implementer ~~has the option to~~ indicate that the content of the element is missing; the implementation guide should describe how the implementer should deal with this situation~~, probably using the data-absent-reason extension~~.		If no guidance can be provided in the profile, it is up to sending systems to populate the element with a meaningful value from the context of their data. Except for elements with required bindings, an implementer can indicate that the content of the element is missing (e.g. using the data-absent-reason extension). The implementation guide should describe how the implementer should deal with this situation.

	=Practical guidelines=		=Practical guidelines=

Jorn Duwel: Mandatory FHIR elements with a functional counterpart with a lower cardinality of 0

2021-11-18T12:54:54Z

Mandatory FHIR elements with a functional counterpart with a lower cardinality of 0

← Oudere versie		Versie van 18 nov 2021 12:54
Regel 227:		Regel 227:
	* A datatype profile may be created that can be re-used across resource profiles (using {{fhir\|type.profile}}). This datatype profile may include special guidance aimed at profilers. An example of this approach is described in [[#Referencing zib HealthProfessional]].		* A datatype profile may be created that can be re-used across resource profiles (using {{fhir\|type.profile}}). This datatype profile may include special guidance aimed at profilers. An example of this approach is described in [[#Referencing zib HealthProfessional]].

	=Mandatory FHIR elements ~~without~~ a functional counterpart=		=Mandatory FHIR elements=
			==Without a functional counterpart==
	On occasion, FHIR requires an element to be populated while the functional model doesn't specify it. For example, the Procedure resource has the required element {{fhir\|Procedure.status}}, but the zib Procedure, which is mapped to this FHIR resource, doesn't specify such a field.		On occasion, FHIR requires an element to be populated while the functional model doesn't specify it. For example, the Procedure resource has the required element {{fhir\|Procedure.status}}, but the zib Procedure, which is mapped to this FHIR resource, doesn't specify such a field.

Regel 236:		Regel 237:
	* The {{fhir\|mapping}} element is populated with the mapped concept, but the description is altered to: <q>[concept name] (implicit, main mapping is on [element name])</q>.		* The {{fhir\|mapping}} element is populated with the mapped concept, but the description is altered to: <q>[concept name] (implicit, main mapping is on [element name])</q>.
	* Other metadata ({{fhir\|.definition}}, {{fhir\|.short}}, {{fhir\|.alias}}) isn't populated according to the normal guidelines.		* Other metadata ({{fhir\|.definition}}, {{fhir\|.short}}, {{fhir\|.alias}}) isn't populated according to the normal guidelines.

			==With a functional counterpart with a lower cardinality of 0==
			On occasion, a zib concept with a lower (conceptual) cardinality of 0 is mapped to a mandatory FHIR element. The profile may give guidance on how to populate the element if no meaningful value can be derived from the zib. For example, the concept TextResultStatus of zib TextResult is mapped to {{fhir\|DiagnosticReport.status}}, where value 'unknown' can be used if the value of zib concept TextResultStatus is not present.

			If the profile does not give any guidance, it is up to sending systems to populate the element with a meaningful value from the context of their data. If the FHIR element has a required binding, this is mandatory. Otherwise, the implementer has the option to indicate that the content of the element is missing; the implementation guide should describe how the implementer should deal with this situation, probably using the data-absent-reason extension.

	=Practical guidelines=		=Practical guidelines=

Jorn Duwel: Clone of V1.0 production page for issue github-97

2021-11-18T12:33:41Z

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

Wijzigingen bekijken