The official and accepted version of the information model for the PROCEDURE module can be found on ART-DECOR. To standardize the representation, the information model was additionally mapped as FHIR Logical Model:
| LogicalModelProzedur (Prozedur) | Element | Element idProzedurShort description Das Basismodul Prozeduren umfasst die Beschreibung diagnostischer oder therapeutischer Maßnahmen, die als Leistungskomplexe auch für die Abrechnung dokumentiert und kodiert werden, z.B. Operationen. DefinitionBase definition for all elements in a resource. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idProzedur.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idProzedur.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
|
| OPSProzedurKodiert | 0..* | BackboneElement | Element idProzedur.OPSProzedurKodiertShort description Kodierung der durchgeführten Prozedur mittels OPS. DefinitionBase definition for all elements that are defined inside a resource - but not those in a data type. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idProzedur.OPSProzedurKodiert.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idProzedur.OPSProzedurKodiert.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
|
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idProzedur.OPSProzedurKodiert.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). 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. 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 cardinality or value of this element may be affected by these constraints: ele-1 Constraints
|
| VollstaendigerProzedurenkode | 0..* | code | Element idProzedur.OPSProzedurKodiert.VollstaendigerProzedurenkodeShort description Der vollständige Prozedurenkode: Tripel aus OPS-Kode, Kodesystem (inkl. Version!) und Katalogtext. DefinitionA string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents Note that FHIR strings SHALL NOT exceed 1MB in size The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |
| Seitenlokalisation | 0..* | code | Element idProzedur.OPSProzedurKodiert.SeitenlokalisationShort description Seitenlokalisation für die durchgeführte Prozedur gemäß DIMDI DefinitionA string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents Note that FHIR strings SHALL NOT exceed 1MB in size The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |
| SNOMEDProzedurKodiert | 0..* | BackboneElement | Element idProzedur.SNOMEDProzedurKodiertShort description Kodierung der durchgeführten Prozedur mittels SNOMED CT. DefinitionBase definition for all elements that are defined inside a resource - but not those in a data type. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idProzedur.SNOMEDProzedurKodiert.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idProzedur.SNOMEDProzedurKodiert.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
|
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idProzedur.SNOMEDProzedurKodiert.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). 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. 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 cardinality or value of this element may be affected by these constraints: ele-1 Constraints
|
| VollstaendigerProzedurenkode | 0..* | code | Element idProzedur.SNOMEDProzedurKodiert.VollstaendigerProzedurenkodeShort description Der vollständige Prozedurenkode: Tripel aus SNOMED-CT-Kode, Kodesystem (Version optional) und Katalogtext. DefinitionA string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents Note that FHIR strings SHALL NOT exceed 1MB in size The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |
| Koerperstelle | 0..* | string | Element idProzedur.KoerperstelleShort description Körperstelle der Prozedur mittels SNOMED CT inkl. Lateralität (R, L, B) DefinitionA sequence of Unicode characters Note that FHIR strings SHALL NOT exceed 1MB in size The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |
| Durchfuehrungsabsicht | 0..* | code | Element idProzedur.DurchfuehrungsabsichtShort description Intention mit der die Prozedur durchgeführt wird DefinitionA string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents Note that FHIR strings SHALL NOT exceed 1MB in size The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |
| Durchfuehrungsdatum | 0..* | date | Element idProzedur.DurchfuehrungsdatumShort description Durchführungsdatum der Prozedur DefinitionA date or partial date (e.g. just year or year + month). There is no time zone. The format is a union of the schema types gYear, gYearMonth and date. Dates SHALL be valid dates. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |
| Dokumentationsdatum | 0..* | date | Element idProzedur.DokumentationsdatumShort description Dokumentationsdatum der Prozedur DefinitionA date or partial date (e.g. just year or year + month). There is no time zone. The format is a union of the schema types gYear, gYearMonth and date. Dates SHALL be valid dates. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |
| Freitextbeschreibung | 0..* | string | Element idProzedur.FreitextbeschreibungShort description Prozedur im Klartext DefinitionA sequence of Unicode characters Note that FHIR strings SHALL NOT exceed 1MB in size The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
|
It should be noted that the Logical Model aims purely at the mapping of data elements and their description. Used data types and cardinalities are not to be regarded as obligatory. This is finally defined by the FHIR profiles. For each element within the Logical Model there is a 1:1 mapping to an element of a concrete FHIR resource.
| Logischer_Datensatz | Beschreibung |
|---|---|
| Prozedur | Das Basismodul Prozeduren umfasst die Beschreibung diagnostischer oder therapeutischer Maßnahmen, die als Leistungskomplexe auch für die Abrechnung dokumentiert und kodiert werden, z.B. Operationen. |
| Prozedur.OPSProzedurKodiert | Kodierung der durchgeführten Prozedur mittels OPS. |
| Prozedur.OPSProzedurKodiert.VollstaendigerProzedurenkode | Der vollständige Prozedurenkode: Tripel aus OPS-Kode, Kodesystem (inkl. Version!) und Katalogtext. |
| Prozedur.OPSProzedurKodiert.Seitenlokalisation | Seitenlokalisation für die durchgeführte Prozedur gemäß DIMDI |
| Prozedur.SNOMEDProzedurKodiert | Kodierung der durchgeführten Prozedur mittels SNOMED CT. |
| Prozedur.SNOMEDProzedurKodiert.VollstaendigerProzedurenkode | Der vollständige Prozedurenkode: Tripel aus SNOMED-CT-Kode, Kodesystem (Version optional) und Katalogtext. |
| Prozedur.Koerperstelle | Körperstelle der Prozedur mittels SNOMED CT inkl. Lateralität (R, L, B) |
| Prozedur.Durchfuehrungsabsicht | Intention mit der die Prozedur durchgeführt wird |
| Prozedur.Durchfuehrungsdatum | Durchführungsdatum der Prozedur |
| Prozedur.Dokumentationsdatum | Dokumentationsdatum der Prozedur |
| Prozedur.Freitextbeschreibung | Prozedur im Klartext |
Powered by SIMPLIFIER.NET
