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.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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 uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc.

In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used.

This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.

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.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

A human language.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

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).

An Extension

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

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.

Code that represents the included structure.

Angabe der Körperstelle als SNOMED CT®-Code, beispielsweise:

• Vene: 120579003 | Vein part (body structure)
• Arterie: 119205003 | Arterial part (body structure)
• Kapillargefäß: 20982000 | Structure of capillary blood vessel (organ) (body structure)
• Spinalkanal: 61853006 | Spinal canal structure (body structure)
• Urethra: 13648007 | Urethral structure (body structure)
• Harnblase: 89837001 | Urinary bladder structure (body structure)
• Respirationstrakt: 321667001 | Respiratory tract structure (body structure)

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.

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

Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).

Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

Freitext Bezeichnung der Körperstelle. Mögliche Verwendung:

• Ersatzweise, wenn keine passende Codierung zugeordnet werden kann
• Als Freitextergänzung, wenn die Körperstelle nicht ausreichend spezifisch codiert werden kann.

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.

Achtung: Die Codes "links", "rechts" und "bilateral" können sowohl am Datenelement "Lateralität" als auch bei "Lokalisation" angegeben werden. Sie haben in beiden Fällen jedoch unterschiedliche Bedeutungen. Mit Lateralität beschreiben sie die Seitenangabe bei paarigen Organen und Körperteilen. Mit Lokalisation beschreiben sie die nähere Lokalisation innerhalb eines (meist unpaarig vorliegendem) Organs/ Körperteils (z.B. linke Seitenwand der Blase). Theoretisch ist die Angabe des selben Codes an beiden Stellen möglich, jedoch fachlich meist nicht sinnvoll (z.B. "links an der linken Niere"; korrekt wäre stattdessen "lateral an der linken Niere").

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.

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.

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

Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).

Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

Hier wird die Lateralität als Freitext angegeben.

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

An 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.

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

Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).

Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

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

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.

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

An 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.

Achtung: Die Codes "links", "rechts" und "bilateral" können sowohl am Datenelement "Lateralität" als auch bei "Lokalisation" angegeben werden. Sie haben in beiden Fällen jedoch unterschiedliche Bedeutungen. Mit Lateralität beschreiben sie die Seitenangabe bei paarigen Organen und Körperteilen. Mit Lokalisation beschreiben sie die nähere Lokalisation innerhalb eines (meist unpaarig vorliegendem) Organs/ Körperteils (z.B. linke Seitenwand der Blase). Theoretisch ist die Angabe des selben Codes an beiden Stellen möglich, jedoch fachlich meist nicht sinnvoll (z.B. "links an der linken Niere"; korrekt wäre stattdessen "lateral an der linken Niere").

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.

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.

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

Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).

Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

Hier wird die Lokalisierung als Freitext angegeben.

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.

Identifier for this instance of the anatomical structure.

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.

Hier wird die Morphologie als SNOMED CT®-Code angegeben, beispielsweise:

• 35566002 |Haematoma (morphologic abnormality)|
• 76197007 |Hyperplasia (morphologic abnormality)|
• 367643001 |Cyst (morphologic abnormality)|
• 367646009 |Pus (morphologic abnormality)|
• 783806000 |Vascular malformation (morphologic abnormality)|

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.

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

Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).

Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

Hier wird die Morphologie als Freitext angegeben.

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.

Codes describing anatomical locations. May include laterality.

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

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.

Image or images used to identify a location.

Hier wird die zu behandelnde Person referenziert.

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).

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.

Angabe der Körperstelle als SNOMED CT®-Code, beispielsweise:

• Vene: 120579003 | Vein part (body structure)
• Arterie: 119205003 | Arterial part (body structure)
• Kapillargefäß: 20982000 | Structure of capillary blood vessel (organ) (body structure)
• Spinalkanal: 61853006 | Spinal canal structure (body structure)
• Urethra: 13648007 | Urethral structure (body structure)
• Harnblase: 89837001 | Urinary bladder structure (body structure)
• Respirationstrakt: 321667001 | Respiratory tract structure (body structure)

Freitext Bezeichnung der Körperstelle. Mögliche Verwendung:

• Ersatzweise, wenn keine passende Codierung zugeordnet werden kann
• Als Freitextergänzung, wenn die Körperstelle nicht ausreichend spezifisch codiert werden kann.

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.

Achtung: Die Codes "links", "rechts" und "bilateral" können sowohl am Datenelement "Lateralität" als auch bei "Lokalisation" angegeben werden. Sie haben in beiden Fällen jedoch unterschiedliche Bedeutungen. Mit Lateralität beschreiben sie die Seitenangabe bei paarigen Organen und Körperteilen. Mit Lokalisation beschreiben sie die nähere Lokalisation innerhalb eines (meist unpaarig vorliegendem) Organs/ Körperteils (z.B. linke Seitenwand der Blase). Theoretisch ist die Angabe des selben Codes an beiden Stellen möglich, jedoch fachlich meist nicht sinnvoll (z.B. "links an der linken Niere"; korrekt wäre stattdessen "lateral an der linken Niere").

Hier wird die Lateralität als Freitext angegeben.

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.

Achtung: Die Codes "links", "rechts" und "bilateral" können sowohl am Datenelement "Lateralität" als auch bei "Lokalisation" angegeben werden. Sie haben in beiden Fällen jedoch unterschiedliche Bedeutungen. Mit Lateralität beschreiben sie die Seitenangabe bei paarigen Organen und Körperteilen. Mit Lokalisation beschreiben sie die nähere Lokalisation innerhalb eines (meist unpaarig vorliegendem) Organs/ Körperteils (z.B. linke Seitenwand der Blase). Theoretisch ist die Angabe des selben Codes an beiden Stellen möglich, jedoch fachlich meist nicht sinnvoll (z.B. "links an der linken Niere"; korrekt wäre stattdessen "lateral an der linken Niere").

Hier wird die Lokalisierung als Freitext angegeben.

(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.

Hier wird die Morphologie als SNOMED CT®-Code angegeben, beispielsweise:

• 35566002 |Haematoma (morphologic abnormality)|
• 76197007 |Hyperplasia (morphologic abnormality)|
• 367643001 |Cyst (morphologic abnormality)|
• 367646009 |Pus (morphologic abnormality)|
• 783806000 |Vascular malformation (morphologic abnormality)|

Hier wird die Morphologie als Freitext angegeben.

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.

Hier wird die zu behandelnde Person referenziert.

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.

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.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

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 uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc.

In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used.

This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.

A list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url.

It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.

Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.

The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.

Security Labels from the Healthcare Privacy and Security Classification System.

Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.

The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.

Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".

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.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

A human language.

A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data.

The status of a resource narrative.