Angaben zur Körperstruktur können enthalten:

• Körperstelle (anatomische Benennung)
• Lateralität (für paarige Organe/Strukturen: rechts, links, beidseits)
• Lokalisierung (für räumliche Angaben, z.B. oben, unten)
• Uhrzeigerposition (z.B. 12-Uhr-Position)
• Morphologie (z.B. pathologische Strukturen)

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

The version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted.

The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.

When the resource last changed - e.g. when the version changed.

This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

An Extension

R5: BodyStructure.includedStructure (new:BackboneElement)

Element BodyStructure.includedStructure has a context of BodyStructure based on following the parent source element upwards and mapping to BodyStructure. Element BodyStructure.includedStructure has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Anatomische Benennung eines Körperteils, Körperdetails oder Organs.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Code that represents the included structure.

A reference to a code defined by a terminology system.

Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

Allows for alternative encodings within a code system, and translations to other code systems.

The identification of the code system that defines the meaning of the symbol in the code.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

Note that FHIR strings SHALL NOT exceed 1MB in size

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

Very often the text is the same as a displayName of one of the codings.

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

Das Datenelement Lateralität gibt bei paarigen Organen (z.B. Niere) oder paarigen Körperteilen (z.B. Arm, Bein) an, ob "Rechts", "Links" oder "Bilateral" betroffen ist.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Code that represents the included structure laterality.

A reference to a code defined by a terminology system.

Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

Allows for alternative encodings within a code system, and translations to other code systems.

The identification of the code system that defines the meaning of the symbol in the code.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

Note that FHIR strings SHALL NOT exceed 1MB in size

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

Very often the text is the same as a displayName of one of the codings.

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

An Extension

R5: BodyStructure.includedStructure.bodyLandmarkOrientation.landmarkDescription (new:CodeableConcept)

Element BodyStructure.includedStructure.bodyLandmarkOrientation.landmarkDescription is part of an existing definition because parent element BodyStructure.includedStructure.bodyLandmarkOrientation requires a cross-version extension. Element BodyStructure.includedStructure.bodyLandmarkOrientation.landmarkDescription has a context of BodyStructure based on following the parent source element upwards and mapping to BodyStructure. Element BodyStructure.includedStructure.bodyLandmarkOrientation.landmarkDescription has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Element BodyStructure.includedStructure.bodyLandmarkOrientation.landmarkDescription is part of an existing definition because parent element BodyStructure.includedStructure.bodyLandmarkOrientation requires a cross-version extension. Element BodyStructure.includedStructure.bodyLandmarkOrientation.landmarkDescription has a context of BodyStructure based on following the parent source element upwards and mapping to BodyStructure. Element BodyStructure.includedStructure.bodyLandmarkOrientation.landmarkDescription has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Eine Beschreibung der Richtung, in der sich etwas von einem Orientierungspunkt entfernt befindet, basierend auf einem radialen Zifferblatt, als sogenannte Uhr-Position (Bsp. 3-Uhr-Position, 12 Uhr-Position).

An Extension

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

An description of the direction away from a landmark something is located based on a radial clock dial.

A reference to a code defined by a terminology system.

Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

Allows for alternative encodings within a code system, and translations to other code systems.

The identification of the code system that defines the meaning of the symbol in the code.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

Note that FHIR strings SHALL NOT exceed 1MB in size

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

Very often the text is the same as a displayName of one of the codings.

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

R5: BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark (new:BackboneElement)

Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark is part of an existing definition because parent element BodyStructure.includedStructure.bodyLandmarkOrientation requires a cross-version extension. Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark has a context of BodyStructure based on following the parent source element upwards and mapping to BodyStructure. Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark is part of an existing definition because parent element BodyStructure.includedStructure.bodyLandmarkOrientation requires a cross-version extension. Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark has a context of BodyStructure based on following the parent source element upwards and mapping to BodyStructure. Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark.device (new:CodeableReference(Device))

Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark.device is part of an existing definition because parent element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark requires a cross-version extension. Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark.device has a context of BodyStructure based on following the parent source element upwards and mapping to BodyStructure. Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark.device has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark.device is part of an existing definition because parent element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark requires a cross-version extension. Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark.device has a context of BodyStructure based on following the parent source element upwards and mapping to BodyStructure. Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark.device has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Slice to indicate the presence of a R5 CodeableReference in FHIR R4

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).

Must be: CodeableReference

R5: CodeableReference.concept

Element CodeableReference.concept is mapped to FHIR R4 element CodeableConcept as Equivalent.

Element CodeableReference.concept is mapped to FHIR R4 element CodeableConcept as Equivalent.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

R5: CodeableReference.reference

Element CodeableReference.reference is mapped to FHIR R4 element Reference as Equivalent.

Element CodeableReference.reference is mapped to FHIR R4 element Reference as Equivalent.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).

R5: BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark.value (new:Quantity)

Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark.value is part of an existing definition because parent element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark requires a cross-version extension. Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark.value has a context of BodyStructure based on following the parent source element upwards and mapping to BodyStructure. Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark.value has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark.value is part of an existing definition because parent element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark requires a cross-version extension. Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark.value has a context of BodyStructure based on following the parent source element upwards and mapping to BodyStructure. Element BodyStructure.includedStructure.bodyLandmarkOrientation.distanceFromLandmark.value has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).

R5: BodyStructure.includedStructure.bodyLandmarkOrientation.surfaceOrientation (new:CodeableConcept)

Element BodyStructure.includedStructure.bodyLandmarkOrientation.surfaceOrientation is part of an existing definition because parent element BodyStructure.includedStructure.bodyLandmarkOrientation requires a cross-version extension. Element BodyStructure.includedStructure.bodyLandmarkOrientation.surfaceOrientation has a context of BodyStructure based on following the parent source element upwards and mapping to BodyStructure. Element BodyStructure.includedStructure.bodyLandmarkOrientation.surfaceOrientation has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Element BodyStructure.includedStructure.bodyLandmarkOrientation.surfaceOrientation is part of an existing definition because parent element BodyStructure.includedStructure.bodyLandmarkOrientation requires a cross-version extension. Element BodyStructure.includedStructure.bodyLandmarkOrientation.surfaceOrientation has a context of BodyStructure based on following the parent source element upwards and mapping to BodyStructure. Element BodyStructure.includedStructure.bodyLandmarkOrientation.surfaceOrientation has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).

R5: BodyStructure.includedStructure.spatialReference (new:Reference(ImagingSelection))

Element BodyStructure.includedStructure.spatialReference is part of an existing definition because parent element BodyStructure.includedStructure requires a cross-version extension. Element BodyStructure.includedStructure.spatialReference has a context of BodyStructure based on following the parent source element upwards and mapping to BodyStructure. Element BodyStructure.includedStructure.spatialReference has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Element BodyStructure.includedStructure.spatialReference is part of an existing definition because parent element BodyStructure.includedStructure requires a cross-version extension. Element BodyStructure.includedStructure.spatialReference has a context of BodyStructure based on following the parent source element upwards and mapping to BodyStructure. Element BodyStructure.includedStructure.spatialReference has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

An dieser Stelle kann eine präzisere Beschreibung der Lokalisation innerhalb einer Körperstruktur / eines Organs / Körperteils abgebildet werden. Es geht um räumliche Angaben, beispielsweise: oben, unten, medial, lateral oder Angabe eines Quadranten.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Code that represents the included structure qualifier.

A reference to a code defined by a terminology system.

Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

Allows for alternative encodings within a code system, and translations to other code systems.

The identification of the code system that defines the meaning of the symbol in the code.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

Note that FHIR strings SHALL NOT exceed 1MB in size

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

Very often the text is the same as a displayName of one of the codings.

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Whether this body site is in active use.

This element is labeled as a modifier because it may be used to mark that the resource was created in error.

Need to be able to mark a body site entry as not to be used because it was created in error.

(Abnorm-)Morphologische Ausprägung(en) der Körperstruktur, beispielsweise Gewebeveränderungen, Entzündungsaspekte, Fehlbildungen.

Disclaimer: Da das Element BodyStructure.morphology auf eine Kardinalität von 0..1 beschränkt ist, können mehrere morphologische Erscheinungen nicht in strukturierter Form angegeben werden. Alternativ werden weitere morphologische Ausprägungen als ergänzende Angaben formuliert.

The minimum cardinality of 0 supports the use case of specifying a location without defining a morphology.

Codes describing anatomic morphology.

A reference to a code defined by a terminology system.

Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

Allows for alternative encodings within a code system, and translations to other code systems.

The identification of the code system that defines the meaning of the symbol in the code.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

Note that FHIR strings SHALL NOT exceed 1MB in size

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

Very often the text is the same as a displayName of one of the codings.

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

The anatomical location or region of the specimen, lesion, or body structure.

Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.

Codes describing anatomical locations. May include laterality.

Qualifier to refine the anatomical location. These include qualifiers for laterality, relative location, directionality, number, and plane.

Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.

Concepts modifying the anatomic location.

In diesem Element werden ergänzende Freitext-Angaben zur Körperstruktur gemacht.

Die Notwendigkeit ergänzender Angaben zur Körperstruktur ergibt sich unter anderem aus der Anforderung, weitere morphologische Erscheinungen zu dokumentieren.

Disclaimer: Da das Element BodyStructure.morphology auf eine Kardinalität von 0..1 beschränkt ist, können mehrere morphologische Erscheinungen nicht in strukturierter Form angegeben werden.

This description could include any visual markings used to orientate the viewer e.g. external reference points, special sutures, ink markings.

The person to which the body site belongs.

References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).

The purpose of this identifier.

Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

Establishes the namespace for the value - that is, a URL that describes a set values that are unique.

Identifier.system is always case sensitive.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

The portion of the identifier typically relevant to the user and which is unique within the context of the system.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

Angaben zur Körperstruktur können enthalten:

• Körperstelle (anatomische Benennung)
• Lateralität (für paarige Organe/Strukturen: rechts, links, beidseits)
• Lokalisierung (für räumliche Angaben, z.B. oben, unten)
• Uhrzeigerposition (z.B. 12-Uhr-Position)
• Morphologie (z.B. pathologische Strukturen)

Anatomische Benennung eines Körperteils, Körperdetails oder Organs.

Das Datenelement Lateralität gibt bei paarigen Organen (z.B. Niere) oder paarigen Körperteilen (z.B. Arm, Bein) an, ob "Rechts", "Links" oder "Bilateral" betroffen ist.

Eine Beschreibung der Richtung, in der sich etwas von einem Orientierungspunkt entfernt befindet, basierend auf einem radialen Zifferblatt, als sogenannte Uhr-Position (Bsp. 3-Uhr-Position, 12 Uhr-Position).

An dieser Stelle kann eine präzisere Beschreibung der Lokalisation innerhalb einer Körperstruktur / eines Organs / Körperteils abgebildet werden. Es geht um räumliche Angaben, beispielsweise: oben, unten, medial, lateral oder Angabe eines Quadranten.

(Abnorm-)Morphologische Ausprägung(en) der Körperstruktur, beispielsweise Gewebeveränderungen, Entzündungsaspekte, Fehlbildungen.

Disclaimer: Da das Element BodyStructure.morphology auf eine Kardinalität von 0..1 beschränkt ist, können mehrere morphologische Erscheinungen nicht in strukturierter Form angegeben werden. Alternativ werden weitere morphologische Ausprägungen als ergänzende Angaben formuliert.

In diesem Element werden ergänzende Freitext-Angaben zur Körperstruktur gemacht.

Die Notwendigkeit ergänzender Angaben zur Körperstruktur ergibt sich unter anderem aus der Anforderung, weitere morphologische Erscheinungen zu dokumentieren.

Disclaimer: Da das Element BodyStructure.morphology auf eine Kardinalität von 0..1 beschränkt ist, können mehrere morphologische Erscheinungen nicht in strukturierter Form angegeben werden.

Angaben zur Körperstruktur können enthalten:

• Körperstelle (anatomische Benennung)
• Lateralität (für paarige Organe/Strukturen: rechts, links, beidseits)
• Lokalisierung (für räumliche Angaben, z.B. oben, unten)
• Uhrzeigerposition (z.B. 12-Uhr-Position)
• Morphologie (z.B. pathologische Strukturen)

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.