Implementierungsleitfaden ISiK-Basismodul (4.0.1)

ISiKProzedur

Dieses Profil spezifiziert die Minimalanforderungen für die Bereitstellung von Informationen über die Behandlungen/Prozeduren eines Patienten im Rahmen des Bestätigungsverfahrens der gematik.

Motivation

Die Möglichkeit auf eine Übersicht der Prozeduren eines Patienten zuzugreifen, Patienten anhand durchgeführter oder geplanter Prozeduren zu suchen, oder zu prüfen, ob eine konkrete Prozedur bei einem Patienten durchgeführt wurde, sind wichtige Funktionen im klinischen Behandlungsablauf.

In FHIR werden Prozeduren mit der Procedure-Ressource repräsentiert.

Da die Prozeduren in klinischen Primärsystemen, in der Regel, in OPS-codierter Form vorliegen, fordert ISiK in erster Linie diese Form des Austausches. Falls eine Prozedur zwar dokumentiert aber noch nicht codiert wurde (z.B. wenn die Kodierung erst nach der Entlassung erfolgt), ist alternativ eine Repräsentation als Freitext-Prozedur möglich.

Kompatibilität

Für das Profil ISIKProzedur wird eine Kompatibilität mit folgenden Profilen angestrebt; allerdings kann nicht sichergestellt werden, dass Instanzen, die gegen ISIKProzedur valide sind, auch valide sind gegen:

Profil Prozedur der Medizininformatik Initiative
Hinweise zu Inkompatibilitäten können über die Portalseite gemeldet werden.

Bestätigungsrelevanz

Verbindlichkeit	SHALL

Metadaten

Canonical	https://gematik.de/fhir/isik/StructureDefinition/ISiKProzedur
Status	active
Version	4.0.1
Basis	http://hl7.org/fhir/StructureDefinition/Procedure

Inhalt

ISiKProzedur (Procedure)	I		Procedure	Element id Procedure Short description An action that is being or was performed on a patient Definition An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy. Data type Procedure Constraints dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources `contained.contained.empty()` dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated `contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()` dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource `contained.where((('#'+id in (%resource.descendants().reference \| %resource.descendants().as(canonical) \| %resource.descendants().as(uri) \| %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()` dom-6: A resource should have narrative for robust management text.`div`.exists() dom-5: If a resource is contained in another resource, it SHALL NOT have a security label `contained.meta.security.empty()` proc-ISiK-1: Falls die Prozedur per OPS kodiert wird, MUSS eine SNOMED-CT kodierte Category abgebildet werden `code.coding.where(system = 'http://fhir.de/CodeSystem/bfarm/ops').exists() implies category.coding.where(system = 'http://snomed.info/sct').exists()` proc-ISiK-2: Falls eine codierte Prozedur vorliegt MUSS eine kodierte Category abgebildet werden `code.coding.exists() implies category.coding.exists()` Mappings rim: Entity. Role, or Act workflow: Event rim: Procedure[moodCode=EVN]
id	Σ	0..1	string	There are no (further) constraints on this element Element id Procedure.id Short description Logical id of this artifact Definition The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. Comments The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Data type string
meta	Σ	0..1	Meta	There are no (further) constraints on this element Element id Procedure.meta Short description Metadata about the resource Definition 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. Data type Meta Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
implicitRules	Σ ?!	0..1	uri	There are no (further) constraints on this element Element id Procedure.implicitRules Short description A set of rules under which this content was created Definition 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. Comments 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. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
language		0..1	codeBinding	There are no (further) constraints on this element Element id Procedure.language Short description Language of the resource content Definition The base language in which the resource is written. Comments 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). Data type code Binding A human language. CommonLanguages (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
text		0..1	Narrative	There are no (further) constraints on this element Element id Procedure.text Short description Text summary of the resource, for human interpretation Alternate names narrative, html, xhtml, display Definition 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. Comments 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. Data type Narrative Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A rim: Act.text?
contained		0..*	Resource	There are no (further) constraints on this element Element id Procedure.contained Short description Contained, inline Resources Alternate names inline resources, anonymous resources, contained resources Definition 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. Comments 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. Data type Resource Mappings rim: Entity. Role, or Act rim: N/A
extension	S I	0..*	Extension	There are no (further) constraints on this element Element id Procedure.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the resource. 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. Comments 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
Dokumentationsdatum	S I	0..1	Extension(dateTime)	Element id Procedure.extension:Dokumentationsdatum Short description Dokumentationsdatum Alternate names extensions, user content Definition Dokumentationsdatum der Prozedur, falls abweichend vom Durchführungsdatum Comments Datum, an dem die Prozedur dokumentiert wurde. Es handelt sich hierbei um das fachliche Dokumentationsdatum, nicht zu verwechseln mit dem Datum der technischen Anlage des Datensatzes im Primärsystem. Diese beiden Daten können jedoch identisch sein. Data type Extension(dateTime) Extension URL http://fhir.de/StructureDefinition/ProzedurDokumentationsdatum Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
modifierExtension	?! I	0..*	Extension	There are no (further) constraints on this element Element id Procedure.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content Definition 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). Requirements 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. Comments 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
identifier	Σ	0..*	Identifier	There are no (further) constraints on this element Element id Procedure.identifier Short description External Identifiers for this procedure Definition Business identifiers assigned to this procedure by the performer or other systems which remain constant as the resource is updated and is propagated from server to server. Requirements Allows identification of the procedure as it is known by various participating systems and in a way that remains consistent across servers. Comments This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and Person resource instances might share the same social insurance number. Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CX / EI (occasionally, more often EI maps to a resource id or a URL) rim: II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT] servd: Identifier workflow: Event.identifier w5: FiveWs.identifier v2: Some combination of ORC-2 / ORC-3 / OBR-2 / OBR-3 / IPC-1 / IPC-2 / IPC-3 / IPC-4 rim: .id
instantiatesCanonical	Σ	0..*	canonical(PlanDefinition \| ActivityDefinition \| Measure \| OperationDefinition \| Questionnaire)	There are no (further) constraints on this element Element id Procedure.instantiatesCanonical Short description Instantiates FHIR protocol or definition Definition The URL pointing to a FHIR-defined protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure. Comments see Canonical References Data type canonical(PlanDefinition \| ActivityDefinition \| Measure \| OperationDefinition \| Questionnaire) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Event.instantiatesCanonical rim: .outboundRelationship[typeCode=DEFN].target
instantiatesUri	Σ	0..*	uri	There are no (further) constraints on this element Element id Procedure.instantiatesUri Short description Instantiates external protocol or definition Definition The URL pointing to an externally maintained protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure. Comments This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Event.instantiatesUri rim: .outboundRelationship[typeCode=DEFN].target
basedOn	Σ I	0..*	Reference(CarePlan \| ServiceRequest)	There are no (further) constraints on this element Element id Procedure.basedOn Short description A request for this procedure Alternate names fulfills Definition A reference to a resource that contains details of the request for this procedure. Comments 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. Data type Reference(CarePlan \| ServiceRequest) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Event.basedOn rim: .outboundRelationship[typeCode=FLFS].target[classCode=(various e.g. PROC, OBS, PCPR, ACT, moodCode=RQO].code
partOf	Σ I	0..*	Reference(Procedure \| Observation \| MedicationAdministration)	There are no (further) constraints on this element Element id Procedure.partOf Short description Part of referenced event Alternate names container Definition A larger event of which this particular procedure is a component or step. Comments The MedicationAdministration resource has a partOf reference to Procedure, but this is not a circular reference. For example, the anesthesia MedicationAdministration is part of the surgical Procedure (MedicationAdministration.partOf = Procedure). For example, the procedure to insert the IV port for an IV medication administration is part of the medication administration (Procedure.partOf = MedicationAdministration). Data type Reference(Procedure \| Observation \| MedicationAdministration) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Event.partOf rim: .inboundRelationship[typeCode=COMP].source[classCode=SBADM or PROC or OBS, moodCode=EVN]
status	S Σ ?!	1..1	codeBinding	Element id Procedure.status Short description Status Definition A code specifying the state of the procedure. Generally, this will be the in-progress or completed state. Comments Zeigt den aktuellen Status der Prozedur an. WICHTIGER Hinweis für Implementierer: Alle server-seitigen Implementierungen MÜSSEN in der Lage sein, die systemintern möglichen Statuswerte korrekt in FHIR abzubilden, mindestens jedoch die Werte `completed` und `unknown`. Alle client-seitigen Implementierungen MÜSSEN in der Lage sein, sämtliche Status-Codes zu interpretieren und dem Anwender in angemessener Form darstellen zu können, beispielsweise durch Ausblenden/Durchstreichen von Prozeduren mit dem status `entered-in-error` und Ausgrauen von Prozeduren, die noch nicht stattgefunden haben, o.ä. Data type code Binding A code specifying the state of the procedure. EventStatus (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Event.status w5: FiveWs.status rim:** statusCode
statusReason	Σ	0..1	CodeableConcept	There are no (further) constraints on this element Element id Procedure.statusReason Short description Reason for current status Alternate names Suspended Reason, Cancelled Reason Definition Captures the reason for the current state of the procedure. Comments This is generally only used for "exception" statuses such as "not-done", "suspended" or "aborted". The reason for performing the event at all is captured in reasonCode, not here. Data type CodeableConcept Binding A code that identifies the reason a procedure was not performed. ProcedureNotPerformedReason(SNOMED-CT) (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD workflow: Event.statusReason rim: .reason.Observation.value
category	S Σ	0..1	CodeableConcept	Element id Procedure.category Short description Kategorie Definition A code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure"). Comments Die Kategorisierung erfolg vorzugsweise auf Basis von SNOMED. Für OPS-codierte Prozeduren MUSS die Kategorie angegeben werden: Sie kann ermittelt werden, indem das erste Zeichen des OPS-Codes mit Hilfe einer ConceptMap auf die zutreffende SNOMED-Kategorie gemappt wird. Begründung MS: Die Kategorisierung dient der Verbesserung von Suche und Darstellung. Data type CodeableConcept Binding A code that classifies a procedure for searching, sorting and display purposes. ProcedureCategoryCodes(SNOMEDCT) (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD w5: FiveWs.class rim: .outboundRelationship[typeCode="COMP].target[classCode="LIST", moodCode="EVN"].code
id		0..1	string	There are no (further) constraints on this element Element id Procedure.category.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Procedure.category.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition 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. Comments 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
coding	Σ	0..*	Coding	Element id Procedure.category.coding Short description Code defined by a terminology system Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments 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. Data type Coding Sliced: Unordered, Open, by system(Pattern) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
SNOMED-CT	S Σ	0..1	ISiKSnomedCTCodingBinding	Element id Procedure.category.coding:SNOMED-CT Short description A reference to a code defined by a terminology system Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments 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. Data type ISiKSnomedCTCoding Binding ProzedurenKategorieSCT (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
text	Σ	0..1	string	There are no (further) constraints on this element Element id Procedure.category.text Short description Plain text representation of the concept Definition 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. Requirements 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. Comments Very often the text is the same as a displayName of one of the codings. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.9. But note many systems use CE.2 for this rim: ./originalText[mediaType/code="text/plain"]/data orim: fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
code	S Σ I	1..1	CodeableConcept	Element id Procedure.code Short description Prozeduren-Code Alternate names type Definition The specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy"). Requirements 0..1 to account for primarily narrative only resources. Comments Prozeduren SOLLEN mindestens entweder mit einem OPS-Code oder einem SNOMED-Code aus dem angegebenen ValueSet codiert werden. Ist keine Codierung möglich, MUSS statt dessen eine textuelle Beschreibung der Prozedur angegeben werden. Begründung Pflichtfeld: Ist weder eine Codierung noch eine textuelle Beschreibung vorhanden, besitzt diese Ressource keine medizinische Aussagefähigkeit. Data type CodeableConcept Binding A code to identify a specific procedure . ProcedureCodes(SNOMEDCT) (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` sct-ops-1: Falls die Prozedur kodiert vorliegt, SOLL mindestens ein OPS oder SNOMED-CT Code angegeben werden. `coding.exists() implies coding.where(system = 'http://snomed.info/sct').exists() or coding.where(system = 'http://fhir.de/CodeSystem/bfarm/ops').exists()` proc-ISiK-3: Entweder MUSS eine kodierte Prozedur vorliegen oder eine textuelle Beschreibung. Stattdessen nur Extensions hinzuzufügen (vgl. https://www.hl7.org/fhir/element.html - ele-1), ist explizit nicht erlaubt. `coding.exists().not() implies text.exists()` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD workflow: Event.code w5: FiveWs.what[x] v2: OBR-44/OBR-45 rim: .code
id		0..1	string	There are no (further) constraints on this element Element id Procedure.code.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Procedure.code.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition 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. Comments 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
coding	S Σ	0..*	Coding	Element id Procedure.code.coding Short description Codierte Darstellung der Prozedur Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments 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. Data type Coding Sliced: Unordered, Open, by system(Pattern) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
OPS	S Σ	0..1	CodingOPSBinding	Element id Procedure.code.coding:OPS Short description OPS-codierte Darstellung der Prozedur Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments 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. Data type CodingOPS Binding OpsVS (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
id		0..1	string	There are no (further) constraints on this element Element id Procedure.code.coding:OPS.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Procedure.code.coding:OPS.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition 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. Comments 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
Seitenlokalisation	S I	0..1	Extension(Coding)	Element id Procedure.code.coding:OPS.extension:Seitenlokalisation Short description Seitenlokalisation Alternate names extensions, user content Definition Optional Extension Element - found in all resources. Comments Begründung MS: Bei OPS-codierten Prozeduren an paarigen Organen oder Körperteilen müssen die Zusatzkennzeichen für die Seitigkeit (R, L oder B) angeben werden Data type Extension(Coding) Extension URL http://fhir.de/StructureDefinition/seitenlokalisation Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
system	S Σ	1..1	uriFixed Value	Element id Procedure.code.coding:OPS.system Short description Namensraum des Prozeduren-Codes Definition The identification of the code system that defines the meaning of the symbol in the code. Requirements Need to be unambiguous about the source of the definition of the symbol. Comments Hier ist stets der Wert `http://fhir.de/CodeSystem/bfarm/ops` anzugeben. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Fixed value http://fhir.de/CodeSystem/bfarm/ops Mappings rim: n/a v2: CE.3 rim:* ./codeSystem orim: fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
version	S Σ	1..1	string	Element id Procedure.code.coding:OPS.version Short description Die Jahresversion des OPS Kataloges. Angegeben wird immer die vierstellige Jahreszahl (z.B. `2017`) Definition Bie Verwendung von OPS ist die Angabe der Version zwingend erforderlich. Hierdurch wird der Tatsache Rechnung getragen, dass jede der jährlich neu erscheinenden Fassung von OPS ein neues Codesystem darstellt. Comments Begründung Pflichtfeld: Bei Verwendung von OPS ist die Angabe der Version zwingend erforderlich. Hierdurch wird der Tatsache Rechnung getragen, dass jede der jährlich neu erscheinenden Fassung von OPS ein neues Codesystem darstellt. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.7 rim:* ./codeSystemVersion orim: fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
code	S Σ I	1..1	code	Element id Procedure.code.coding:OPS.code Short description OPS-Code Definition 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). Requirements Need to refer to a particular code in the system. Comments Hier ist der OPS-Code ohne jegliche Zusatzkennzeichen (z.B. Seitenlokalisation) oder Versionsnummern anzugeben. Data type code Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ops-regex: In code sind nur gültige OPS-Codes ohne Zusätze erlaubt `matches('^[1\|3\|5\|6\|8\|9]-[a-zA-Z0-9]{3}([.][a-zA-Z0-9]{1,2})?$')` Examples Einfacher OPS-Code 5-470 Mappings rim: n/a v2: CE.1 rim:* ./code orim: fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
display	Σ	0..1	string	There are no (further) constraints on this element Element id Procedure.code.coding:OPS.display Short description Representation defined by the system Definition A representation of the meaning of the code in the system, following the rules of the system. Requirements Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.2 - but note this is not well followed rim:* CV.displayName orim: fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
userSelected	Σ	0..1	boolean	There are no (further) constraints on this element Element id Procedure.code.coding:OPS.userSelected Short description If this coding was chosen directly by the user Definition Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Requirements 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. Comments 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. Data type boolean Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: Sometimes implied by being first rim: CD.codingRationale orim: fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
SNOMED-CT	S Σ	0..1	ISiKSnomedCTCodingBinding	Element id Procedure.code.coding:SNOMED-CT Short description SNOMED-codierte Darstellung der Prozedur Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments 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. Data type ISiKSnomedCTCoding Binding ProzedurenCodesSCT (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
text	S Σ	0..1	string	Element id Procedure.code.text Short description Freitextiche Beschreibung der Prozedur Definition 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. Requirements 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. Comments Die freitextliche Beschreibung kann ergänzend oder anstelle einer codierten Angabe der Prozedur erfolgen. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.9. But note many systems use CE.2 for this rim: ./originalText[mediaType/code="text/plain"]/data orim: fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
subject	S Σ I	1..1	Reference(Patient \| Group)	Element id Procedure.subject Short description Patientenbezug Alternate names patient Definition The person, animal or group on which the procedure was performed. Comments 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. Data type Reference(Patient \| Group) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Event.subject w5: FiveWs.subject[x] v2: PID-3 rim: .participation[typeCode=SBJ].role w5: FiveWs.subject
id		0..1	string	There are no (further) constraints on this element Element id Procedure.subject.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Procedure.subject.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition 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. Comments 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
reference	S Σ I	1..1	string	Element id Procedure.subject.reference Short description Patienten-Link Definition 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. Comments Die Verlinkung auf eine Patienten-Ressource dient der technischen Zuordnung der Dokumentation zu einem Patienten und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
type	Σ	0..1	uriBinding	There are no (further) constraints on this element Element id Procedure.subject.type Short description Type the reference refers to (e.g. "Patient") Definition The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). Comments This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Data type uri Binding Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
identifier	Σ	0..1	Identifier	There are no (further) constraints on this element Element id Procedure.subject.identifier Short description Logical reference, when literal reference is not known Definition 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. Comments 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). Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CX / EI (occasionally, more often EI maps to a resource id or a URL) rim: II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT] servd: Identifier rim: .identifier
display	Σ	0..1	string	There are no (further) constraints on this element Element id Procedure.subject.display Short description Text alternative for the resource Definition Plain text narrative that identifies the resource in addition to the resource reference. Comments 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. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
encounter	S Σ I	0..1	Reference(Encounter)	Element id Procedure.encounter Short description Aufenthaltsbezug Definition The Encounter during which this Procedure was created or performed or to which the creation of this record is tightly associated. Comments This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. Data type Reference(Encounter) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Event.context w5: FiveWs.context v2: PV1-19 rim: .inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN]
id		0..1	string	There are no (further) constraints on this element Element id Procedure.encounter.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Procedure.encounter.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition 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. Comments 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
reference	S Σ I	1..1	string	Element id Procedure.encounter.reference Short description Encounter-Link Definition 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. Comments Begründung Pflichtfeld: Die Verlinkung auf eine Encounter-Ressource dient der technischen Zuordnung der Dokumentation zu einem Aufenthalt und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc. WICHTIGER Hinweis für Implementierer: Die Zuordnung MUSS auf auf einen Encounter der Ebene "Abteilungskontakt" (siehe hierzu {{pagelink:Fall}}) erfolgen. Bei der Auswahl des Encounters ist zu beachten, dass unter einer (Abrechnungs-)"Fallnummer" (hier: `Encounter.account`) unter Umständen mehrere Encounter gruppiert sein können (z.B. stationärer Besuch mit mehreren vor- und nachstationären Aufenthalten.) Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
type	Σ	0..1	uriBinding	There are no (further) constraints on this element Element id Procedure.encounter.type Short description Type the reference refers to (e.g. "Patient") Definition The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). Comments This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Data type uri Binding Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
identifier	Σ	0..1	Identifier	There are no (further) constraints on this element Element id Procedure.encounter.identifier Short description Logical reference, when literal reference is not known Definition 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. Comments 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). Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CX / EI (occasionally, more often EI maps to a resource id or a URL) rim: II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT] servd: Identifier rim: .identifier
display	Σ	0..1	string	There are no (further) constraints on this element Element id Procedure.encounter.display Short description Text alternative for the resource Definition Plain text narrative that identifies the resource in addition to the resource reference. Comments 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. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
performed[x]	S Σ	1..1		Element id Procedure.performed[x] Short description Durchführungsdatum oder -Zeitraum Definition Estimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured. Comments Es muss mindestens entweder ein (partielles) Durchführungsdatum oder der Beginn des Durchführungszeitraumes angegeben werden. Begründung Pflichtfeld: Die zeitliche Einordnung einer Prozedur ist in vielen Fällen maßgeblich für deren medizinische Relevanz. Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Event.occurrence[x] w5: FiveWs.done[x] v2: OBR-7 rim: .effectiveTime
performedDateTime			dateTime	Data type dateTime
performedPeriod			Period	Data type Period
recorder	Σ I	0..1	Reference(Patient \| RelatedPerson \| Practitioner \| PractitionerRole)	There are no (further) constraints on this element Element id Procedure.recorder Short description Who recorded the procedure Definition Individual who recorded the record and takes responsibility for its content. Comments 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. Data type Reference(Patient \| RelatedPerson \| Practitioner \| PractitionerRole) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) w5: FiveWs.author rim: .participation[typeCode=AUT].role
asserter	Σ I	0..1	Reference(Patient \| RelatedPerson \| Practitioner \| PractitionerRole)	There are no (further) constraints on this element Element id Procedure.asserter Short description Person who asserts this procedure Definition Individual who is making the procedure statement. Comments 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. Data type Reference(Patient \| RelatedPerson \| Practitioner \| PractitionerRole) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) w5: FiveWs.source rim: .participation[typeCode=INF].role
performer	Σ	0..*	BackboneElement	There are no (further) constraints on this element Element id Procedure.performer Short description The people who performed the procedure Definition Limited to "real" people rather than equipment. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Event.performer rim: .participation[typeCode=PRF]
id		0..1	string	There are no (further) constraints on this element Element id Procedure.performer.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Procedure.performer.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition 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. Comments 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Procedure.performer.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition May 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). Requirements 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. Comments 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. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
function	Σ	0..1	CodeableConcept	There are no (further) constraints on this element Element id Procedure.performer.function Short description Type of performance Definition Distinguishes the type of involvement of the performer in the procedure. For example, surgeon, anaesthetist, endoscopist. Requirements Allows disambiguation of the types of involvement of different performers. Comments 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. Data type CodeableConcept Binding A code that identifies the role of a performer of the procedure. ProcedurePerformerRoleCodes (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD workflow: Event.performer.function v2: Some combination of STF-18 / PRA-3 / PRT-4 / ROL-3 / ORC-12 / OBR-16 / PV1-7 / PV1-8 / PV1-9 / PV1-17 / OBX-25 rim: .functionCode
actor	Σ I	1..1	Reference(Practitioner \| PractitionerRole \| Organization \| Patient \| RelatedPerson \| Device)	There are no (further) constraints on this element Element id Procedure.performer.actor Short description The reference to the practitioner Definition The practitioner who was involved in the procedure. Requirements A reference to Device supports use cases, such as pacemakers. Comments 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. Data type Reference(Practitioner \| PractitionerRole \| Organization \| Patient \| RelatedPerson \| Device) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Event.performer.actor w5: FiveWs.actor v2: ORC-19/PRT-5 rim: .role
onBehalfOf	I	0..1	Reference(Organization)	There are no (further) constraints on this element Element id Procedure.performer.onBehalfOf Short description Organization the device or practitioner was acting for Definition The organization the device or practitioner was acting on behalf of. Requirements Practitioners and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when performing the action. Comments 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. Data type Reference(Organization) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) rim: .scoper
location	Σ I	0..1	Reference(Location)	There are no (further) constraints on this element Element id Procedure.location Short description Where the procedure happened Definition The location where the procedure actually happened. E.g. a newborn at home, a tracheostomy at a restaurant. Requirements Ties a procedure to where the records are likely kept. Comments 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. Data type Reference(Location) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) w5: FiveWs.where[x] rim: .participation[typeCode=LOC].role[classCode=SDLOC]
reasonCode	Σ	0..*	CodeableConcept	There are no (further) constraints on this element Element id Procedure.reasonCode Short description Coded reason procedure performed Definition The coded reason why the procedure was performed. This may be a coded entity of some type, or may simply be present as text. Comments Use Procedure.reasonCode when a code sufficiently describes the reason. Use Procedure.reasonReference when referencing a resource, which allows more information to be conveyed, such as onset date. Procedure.reasonCode and Procedure.reasonReference are not meant to be duplicative. For a single reason, either Procedure.reasonCode or Procedure.reasonReference can be used. Procedure.reasonCode may be a summary code, or Procedure.reasonReference may be used to reference a very precise definition of the reason using Condition \| Observation \| Procedure \| DiagnosticReport \| DocumentReference. Both Procedure.reasonCode and Procedure.reasonReference can be used if they are describing different reasons for the procedure. Data type CodeableConcept Binding A code that identifies the reason a procedure is required. ProcedureReasonCodes (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD workflow: Event.reasonCode w5: FiveWs.why[x] rim: .reasonCode
reasonReference	Σ I	0..*	Reference(Condition \| Observation \| Procedure \| DiagnosticReport \| DocumentReference)	There are no (further) constraints on this element Element id Procedure.reasonReference Short description The justification that the procedure was performed Definition The justification of why the procedure was performed. Comments It is possible for a procedure to be a reason (such as C-Section) for another procedure (such as an epidural). Other examples include endoscopy for dilatation and biopsy (a combination of diagnostic and therapeutic use). Use Procedure.reasonCode when a code sufficiently describes the reason. Use Procedure.reasonReference when referencing a resource, which allows more information to be conveyed, such as onset date. Procedure.reasonCode and Procedure.reasonReference are not meant to be duplicative. For a single reason, either Procedure.reasonCode or Procedure.reasonReference can be used. Procedure.reasonCode may be a summary code, or Procedure.reasonReference may be used to reference a very precise definition of the reason using Condition \| Observation \| Procedure \| DiagnosticReport \| DocumentReference. Both Procedure.reasonCode and Procedure.reasonReference can be used if they are describing different reasons for the procedure. Data type Reference(Condition \| Observation \| Procedure \| DiagnosticReport \| DocumentReference) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Event.reasonReference w5: FiveWs.why[x] rim: .reasonCode
bodySite	Σ	0..*	CodeableConcept	There are no (further) constraints on this element Element id Procedure.bodySite Short description Target body sites Definition Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion. Comments If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension procedure-targetbodystructure. Data type CodeableConcept Binding Codes describing anatomical locations. May include laterality. SNOMEDCTBodyStructures (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD v2: OBX-20 rim: .targetSiteCode
outcome	Σ	0..1	CodeableConcept	There are no (further) constraints on this element Element id Procedure.outcome Short description The result of procedure Definition The outcome of the procedure - did it resolve the reasons for the procedure being performed? Comments If outcome contains narrative text only, it can be captured using the CodeableConcept.text. Data type CodeableConcept Binding An outcome of a procedure - whether it was resolved or otherwise. ProcedureOutcomeCodes(SNOMEDCT) (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD rim: .outboundRelationship[typeCode=OUT].target.text
report	I	0..*	Reference(DiagnosticReport \| DocumentReference \| Composition)	There are no (further) constraints on this element Element id Procedure.report Short description Any report resulting from the procedure Definition This could be a histology result, pathology report, surgical report, etc. Comments There could potentially be multiple reports - e.g. if this was a procedure which took multiple biopsies resulting in a number of anatomical pathology reports. Data type Reference(DiagnosticReport \| DocumentReference \| Composition) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) rim: .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN]
complication		0..*	CodeableConcept	There are no (further) constraints on this element Element id Procedure.complication Short description Complication following the procedure Definition Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the notes, which will typically describe the procedure itself rather than any 'post procedure' issues. Comments If complications are only expressed by the narrative text, they can be captured using the CodeableConcept.text. Data type CodeableConcept Binding Codes describing complications that resulted from a procedure. Condition/Problem/DiagnosisCodes (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD rim: .outboundRelationship[typeCode=OUTC].target[classCode=OBS, code="complication", moodCode=EVN].value
complicationDetail	I	0..*	Reference(Condition)	There are no (further) constraints on this element Element id Procedure.complicationDetail Short description A condition that is a result of the procedure Definition Any complications that occurred during the procedure, or in the immediate post-performance period. Requirements This is used to document a condition that is a result of the procedure, not the condition that was the reason for the procedure. Comments 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. Data type Reference(Condition) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) rim: .outboundRelationship[typeCode=OUTC].target[classCode=OBS, code="complication", moodCode=EVN].value
followUp		0..*	CodeableConcept	There are no (further) constraints on this element Element id Procedure.followUp Short description Instructions for follow up Definition If the procedure required specific follow up - e.g. removal of sutures. The follow up may be represented as a simple note or could potentially be more complex, in which case the CarePlan resource can be used. Comments 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. Data type CodeableConcept Binding Specific follow up required for a procedure e.g. removal of sutures. ProcedureFollowUpCodes(SNOMEDCT) (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD rim: .outboundRelationship[typeCode=COMP].target[classCode=ACT, moodCode=INT].code
note	S	0..*	Annotation	Element id Procedure.note Short description Notizen Definition Any other notes and comments about the procedure. Comments Ergänzende Hinweise und Anmerkungen zur Prozedur Data type Annotation Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: N/A rim: Act workflow: Event.note v2: NTE rim: .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="annotation"].value
focalDevice		0..*	BackboneElement	There are no (further) constraints on this element Element id Procedure.focalDevice Short description Manipulated, implanted, or removed device Definition A device that is implanted, removed or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: .participation[typeCode=DEV].role[classCode=MANU]
id		0..1	string	There are no (further) constraints on this element Element id Procedure.focalDevice.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Procedure.focalDevice.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition 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. Comments 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Procedure.focalDevice.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition May 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). Requirements 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. Comments 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. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
action		0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Procedure.focalDevice.action Short description Kind of change to device Definition The kind of change that happened to the device during the procedure. Comments 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. Data type CodeableConcept Binding A kind of change that happened to the device during the procedure. ProcedureDeviceActionCodes (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD rim: .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="procedure device action"].value=:procedure device action codes
manipulated	I	1..1	Reference(Device)	There are no (further) constraints on this element Element id Procedure.focalDevice.manipulated Short description Device that was changed Definition The device that was manipulated (changed) during the procedure. Comments 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. Data type Reference(Device) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) rim: .participation[typeCode=DEV].role[classCode=SDLOC]
usedReference	I	0..*	Reference(Device \| Medication \| Substance)	There are no (further) constraints on this element Element id Procedure.usedReference Short description Items used during procedure Definition Identifies medications, devices and any other substance used as part of the procedure. Requirements Used for tracking contamination, etc. Comments For devices actually implanted or removed, use Procedure.device. Data type Reference(Device \| Medication \| Substance) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) rim: .participation[typeCode=DEV].role[classCode=MANU] or .participation[typeCode=CSM].role[classCode=ADMM] (for Medication or Substance)
usedCode		0..*	CodeableConcept	There are no (further) constraints on this element Element id Procedure.usedCode Short description Coded items used during the procedure Definition Identifies coded items that were used as part of the procedure. Comments For devices actually implanted or removed, use Procedure.device. Data type CodeableConcept Binding Codes describing items used during a procedure. FHIRDeviceTypes (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD rim: participation[typeCode=Dev].role[classCode=MANU]

<StructureDefinition xmlns="http://hl7.org/fhir">
    <id value="ISiKProzedur" />
    <url value="https://gematik.de/fhir/isik/StructureDefinition/ISiKProzedur" />
    <version value="4.0.1" />
    <name value="ISiKProzedur" />
    <status value="active" />
    <experimental value="false" />
    <date value="2024-11-25" />
    <publisher value="gematik GmbH" />
    <description value="Dieses Profil spezifiziert die Minimalanforderungen f&#252;r die Bereitstellung von Informationen &#252;ber die Behandlungen/Prozeduren eines Patienten im Rahmen des Best&#228;tigungsverfahrens der gematik.\n### Motivation\nDie M&#246;glichkeit auf eine &#220;bersicht der Prozeduren eines Patienten zuzugreifen, Patienten anhand durchgef&#252;hrter oder geplanter Prozeduren zu suchen, oder zu pr&#252;fen, ob eine konkrete Prozedur bei einem Patienten durchgef&#252;hrt wurde, sind wichtige Funktionen im klinischen Behandlungsablauf.\n\nIn FHIR werden Prozeduren mit der Procedure-Ressource repr&#228;sentiert.\n\nDa die Prozeduren in klinischen Prim&#228;rsystemen, in der Regel, in OPS-codierter Form vorliegen, fordert ISiK in erster Linie diese Form des Austausches. Falls eine Prozedur zwar dokumentiert aber noch nicht codiert wurde (z.B. wenn die Kodierung erst nach der Entlassung erfolgt), ist alternativ eine Repr&#228;sentation als Freitext-Prozedur m&#246;glich.\n\n### Kompatibilit&#228;t\nF&#252;r das Profil ISIKProzedur wird eine Kompatibilit&#228;t mit folgenden Profilen angestrebt; allerdings kann nicht sichergestellt werden, dass Instanzen, die gegen ISIKProzedur valide sind, auch valide sind gegen:\n\n* [Profil Prozedur](https://www.medizininformatik-initiative.de/fhir/core/modul-prozedur/StructureDefinition/Procedure) der Medizininformatik Initiative  \nHinweise zu Inkompatibilit&#228;ten k&#246;nnen &#252;ber die [Portalseite](https://service.gematik.de/servicedesk/customer/portal/16) gemeldet werden." />
    <fhirVersion value="4.0.1" />
    <kind value="resource" />
    <abstract value="false" />
    <type value="Procedure" />
    <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Procedure" />
    <derivation value="constraint" />
    <differential>
        <element id="Procedure">
            <path value="Procedure" />
            <constraint>
                <key value="proc-ISiK-1" />
                <severity value="error" />
                <human value="Falls die Prozedur per OPS kodiert wird, MUSS eine SNOMED-CT kodierte Category abgebildet werden" />
                <expression value="code.coding.where(system = &#39;http://fhir.de/CodeSystem/bfarm/ops&#39;).exists() implies category.coding.where(system = &#39;http://snomed.info/sct&#39;).exists()" />
                <source value="https://gematik.de/fhir/isik/StructureDefinition/ISiKProzedur" />
            </constraint>
            <constraint>
                <key value="proc-ISiK-2" />
                <severity value="error" />
                <human value="Falls eine codierte Prozedur vorliegt MUSS eine kodierte Category abgebildet werden" />
                <expression value="code.coding.exists() implies category.coding.exists()" />
                <source value="https://gematik.de/fhir/isik/StructureDefinition/ISiKProzedur" />
            </constraint>
        </element>
        <element id="Procedure.extension">
            <path value="Procedure.extension" />
            <mustSupport value="true" />
        </element>
        <element id="Procedure.extension:Dokumentationsdatum">
            <path value="Procedure.extension" />
            <sliceName value="Dokumentationsdatum" />
            <short value="Dokumentationsdatum" />
            <comment value="Datum, an dem die Prozedur dokumentiert wurde.  \n  Es handelt sich hierbei um das fachliche Dokumentationsdatum, nicht zu verwechseln mit dem Datum der technischen Anlage des Datensatzes im Prim&#228;rsystem. \n  Diese beiden Daten *k&#246;nnen* jedoch identisch sein." />
            <min value="0" />
            <max value="1" />
            <type>
                <code value="Extension" />
                <profile value="http://fhir.de/StructureDefinition/ProzedurDokumentationsdatum" />
            </type>
            <mustSupport value="true" />
        </element>
        <element id="Procedure.status">
            <path value="Procedure.status" />
            <short value="Status" />
            <comment value="Zeigt den aktuellen Status der Prozedur an.     \n  **WICHTIGER Hinweis f&#252;r Implementierer:  \n  * Alle server-seitigen Implementierungen M&#220;SSEN in der Lage sein, \n  die systemintern m&#246;glichen Statuswerte korrekt in FHIR abzubilden, mindestens jedoch die Werte `completed` und `unknown`.\n  * Alle client-seitigen Implementierungen M&#220;SSEN in der Lage sein, s&#228;mtliche Status-Codes zu interpretieren und dem Anwender in angemessener Form darstellen zu k&#246;nnen, \n  beispielsweise durch Ausblenden/Durchstreichen von Prozeduren mit dem status `entered-in-error` und Ausgrauen von Prozeduren, die noch nicht stattgefunden haben, o.&#228;." />
            <mustSupport value="true" />
        </element>
        <element id="Procedure.category">
            <path value="Procedure.category" />
            <short value="Kategorie" />
            <comment value="Die Kategorisierung erfolg vorzugsweise auf Basis von SNOMED. F&#252;r OPS-codierte Prozeduren MUSS die Kategorie angegeben werden: Sie kann ermittelt werden, \n  indem das erste Zeichen des OPS-Codes mit Hilfe einer [ConceptMap](http://fhir.de/ConceptMap/OPS-SNOMED-Category) auf die zutreffende SNOMED-Kategorie gemappt wird.\n  **Begr&#252;ndung MS:** Die Kategorisierung dient der Verbesserung von Suche und Darstellung." />
            <mustSupport value="true" />
        </element>
        <element id="Procedure.category.coding">
            <path value="Procedure.category.coding" />
            <slicing>
                <discriminator>
                    <type value="pattern" />
                    <path value="system" />
                </discriminator>
                <rules value="open" />
            </slicing>
        </element>
        <element id="Procedure.category.coding:SNOMED-CT">
            <path value="Procedure.category.coding" />
            <sliceName value="SNOMED-CT" />
            <min value="0" />
            <max value="1" />
            <type>
                <code value="Coding" />
                <profile value="https://gematik.de/fhir/isik/StructureDefinition/ISiKSnomedCTCoding" />
            </type>
            <mustSupport value="true" />
            <binding>
                <strength value="preferred" />
                <valueSet value="https://gematik.de/fhir/isik/ValueSet/ProzedurenKategorieSCT" />
            </binding>
        </element>
        <element id="Procedure.code">
            <path value="Procedure.code" />
            <short value="Prozeduren-Code" />
            <comment value="Prozeduren SOLLEN mindestens entweder mit einem OPS-Code oder einem SNOMED-Code aus dem angegebenen ValueSet codiert werden. \n  Ist keine Codierung m&#246;glich, MUSS statt dessen eine textuelle Beschreibung der Prozedur angegeben werden.  \n  **Begr&#252;ndung Pflichtfeld:** Ist *weder* eine Codierung *noch* eine textuelle Beschreibung vorhanden, besitzt diese Ressource keine medizinische Aussagef&#228;higkeit." />
            <min value="1" />
            <constraint>
                <key value="sct-ops-1" />
                <severity value="error" />
                <human value="Falls die Prozedur kodiert vorliegt, SOLL mindestens ein OPS oder SNOMED-CT Code angegeben werden." />
                <expression value="coding.exists() implies coding.where(system = &#39;http://snomed.info/sct&#39;).exists() or coding.where(system = &#39;http://fhir.de/CodeSystem/bfarm/ops&#39;).exists()" />
                <source value="https://gematik.de/fhir/isik/StructureDefinition/ISiKProzedur" />
            </constraint>
            <constraint>
                <key value="proc-ISiK-3" />
                <severity value="error" />
                <human value="Entweder MUSS eine kodierte Prozedur vorliegen oder eine textuelle Beschreibung. Stattdessen nur Extensions hinzuzuf&#252;gen (vgl. https://www.hl7.org/fhir/element.html - ele-1), ist explizit nicht erlaubt." />
                <expression value="coding.exists().not() implies text.exists()" />
                <source value="https://gematik.de/fhir/isik/StructureDefinition/ISiKProzedur" />
            </constraint>
            <mustSupport value="true" />
        </element>
        <element id="Procedure.code.coding">
            <path value="Procedure.code.coding" />
            <slicing>
                <discriminator>
                    <type value="pattern" />
                    <path value="system" />
                </discriminator>
                <rules value="open" />
            </slicing>
            <short value="Codierte Darstellung der Prozedur" />
            <mustSupport value="true" />
        </element>
        <element id="Procedure.code.coding:OPS">
            <path value="Procedure.code.coding" />
            <sliceName value="OPS" />
            <short value="OPS-codierte Darstellung der Prozedur" />
            <min value="0" />
            <max value="1" />
            <type>
                <code value="Coding" />
                <profile value="http://fhir.de/StructureDefinition/CodingOPS" />
            </type>
            <mustSupport value="true" />
            <binding>
                <strength value="required" />
                <valueSet value="http://fhir.de/ValueSet/bfarm/ops" />
            </binding>
        </element>
        <element id="Procedure.code.coding:OPS.extension:Seitenlokalisation">
            <path value="Procedure.code.coding.extension" />
            <sliceName value="Seitenlokalisation" />
            <short value="Seitenlokalisation" />
            <comment value="**Begr&#252;ndung MS:** Bei OPS-codierten Prozeduren an paarigen Organen oder K&#246;rperteilen m&#252;ssen die Zusatzkennzeichen f&#252;r die Seitigkeit (R, L oder B) angeben werden" />
            <mustSupport value="true" />
        </element>
        <element id="Procedure.code.coding:OPS.system">
            <path value="Procedure.code.coding.system" />
            <short value="Namensraum des Prozeduren-Codes" />
            <comment value="Hier ist stets der Wert `http://fhir.de/CodeSystem/bfarm/ops` anzugeben." />
            <mustSupport value="true" />
        </element>
        <element id="Procedure.code.coding:OPS.version">
            <path value="Procedure.code.coding.version" />
            <short value="Die Jahresversion des OPS Kataloges. Angegeben wird immer die vierstellige Jahreszahl (z.B. `2017`)" />
            <comment value="**Begr&#252;ndung Pflichtfeld:** Bei Verwendung von OPS ist die Angabe der Version zwingend erforderlich. \n      Hierdurch wird der Tatsache Rechnung getragen, dass jede der j&#228;hrlich neu erscheinenden Fassung von OPS ein neues Codesystem darstellt." />
            <mustSupport value="true" />
        </element>
        <element id="Procedure.code.coding:OPS.code">
            <path value="Procedure.code.coding.code" />
            <short value="OPS-Code" />
            <comment value="Hier ist der OPS-Code ohne jegliche Zusatzkennzeichen (z.B. Seitenlokalisation) oder Versionsnummern anzugeben." />
            <mustSupport value="true" />
        </element>
        <element id="Procedure.code.coding:SNOMED-CT">
            <path value="Procedure.code.coding" />
            <sliceName value="SNOMED-CT" />
            <short value="SNOMED-codierte Darstellung der Prozedur" />
            <min value="0" />
            <max value="1" />
            <type>
                <code value="Coding" />
                <profile value="https://gematik.de/fhir/isik/StructureDefinition/ISiKSnomedCTCoding" />
            </type>
            <mustSupport value="true" />
            <binding>
                <strength value="required" />
                <valueSet value="https://gematik.de/fhir/isik/ValueSet/ProzedurenCodesSCT" />
            </binding>
        </element>
        <element id="Procedure.code.text">
            <path value="Procedure.code.text" />
            <short value="Freitextiche Beschreibung der Prozedur" />
            <comment value="Die freitextliche Beschreibung kann erg&#228;nzend oder anstelle einer codierten Angabe der Prozedur erfolgen." />
            <mustSupport value="true" />
        </element>
        <element id="Procedure.subject">
            <path value="Procedure.subject" />
            <short value="Patientenbezug" />
            <mustSupport value="true" />
        </element>
        <element id="Procedure.subject.reference">
            <path value="Procedure.subject.reference" />
            <short value="Patienten-Link" />
            <comment value="Die Verlinkung auf eine Patienten-Ressource dient der technischen Zuordnung der Dokumentation zu einem Patienten und erm&#246;glicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc." />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Procedure.encounter">
            <path value="Procedure.encounter" />
            <short value="Aufenthaltsbezug" />
            <mustSupport value="true" />
        </element>
        <element id="Procedure.encounter.reference">
            <path value="Procedure.encounter.reference" />
            <short value="Encounter-Link" />
            <comment value="**Begr&#252;ndung Pflichtfeld:** Die Verlinkung auf eine Encounter-Ressource dient der technischen Zuordnung der Dokumentation zu einem Aufenthalt \n    und erm&#246;glicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc.    \n    **WICHTIGER Hinweis f&#252;r Implementierer:** Die Zuordnung MUSS auf auf einen Encounter der Ebene &amp;quot;Abteilungskontakt&amp;quot; (siehe hierzu {{pagelink:Fall}}) erfolgen. \n    Bei der Auswahl des Encounters ist zu beachten, dass unter einer (Abrechnungs-)&amp;quot;Fallnummer&amp;quot; (hier: `Encounter.account`) \n    unter Umst&#228;nden mehrere Encounter gruppiert sein k&#246;nnen (z.B. station&#228;rer Besuch mit mehreren vor- und nachstation&#228;ren Aufenthalten.)" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Procedure.performed[x]">
            <path value="Procedure.performed[x]" />
            <short value="Durchf&#252;hrungsdatum oder -Zeitraum" />
            <comment value="Es muss mindestens entweder ein (partielles) Durchf&#252;hrungsdatum oder der Beginn des Durchf&#252;hrungszeitraumes angegeben werden.\n  **Begr&#252;ndung Pflichtfeld:** Die zeitliche Einordnung einer Prozedur ist in vielen F&#228;llen ma&#223;geblich f&#252;r deren medizinische Relevanz." />
            <min value="1" />
            <type>
                <code value="dateTime" />
            </type>
            <type>
                <code value="Period" />
            </type>
            <mustSupport value="true" />
        </element>
        <element id="Procedure.note">
            <path value="Procedure.note" />
            <short value="Notizen" />
            <comment value="Erg&#228;nzende Hinweise und Anmerkungen zur Prozedur" />
            <mustSupport value="true" />
        </element>
    </differential>
</StructureDefinition>

{
    "resourceType": "StructureDefinition",
    "id": "ISiKProzedur",
    "url": "https://gematik.de/fhir/isik/StructureDefinition/ISiKProzedur",
    "version": "4.0.1",
    "name": "ISiKProzedur",
    "status": "active",
    "experimental": false,
    "date": "2024-11-25",
    "publisher": "gematik GmbH",
    "description": "Dieses Profil spezifiziert die Minimalanforderungen für die Bereitstellung von Informationen über die Behandlungen/Prozeduren eines Patienten im Rahmen des Bestätigungsverfahrens der gematik.\n### Motivation\nDie Möglichkeit auf eine Übersicht der Prozeduren eines Patienten zuzugreifen, Patienten anhand durchgeführter oder geplanter Prozeduren zu suchen, oder zu prüfen, ob eine konkrete Prozedur bei einem Patienten durchgeführt wurde, sind wichtige Funktionen im klinischen Behandlungsablauf.\n\nIn FHIR werden Prozeduren mit der Procedure-Ressource repräsentiert.\n\nDa die Prozeduren in klinischen Primärsystemen, in der Regel, in OPS-codierter Form vorliegen, fordert ISiK in erster Linie diese Form des Austausches. Falls eine Prozedur zwar dokumentiert aber noch nicht codiert wurde (z.B. wenn die Kodierung erst nach der Entlassung erfolgt), ist alternativ eine Repräsentation als Freitext-Prozedur möglich.\n\n### Kompatibilität\nFür das Profil ISIKProzedur wird eine Kompatibilität mit folgenden Profilen angestrebt; allerdings kann nicht sichergestellt werden, dass Instanzen, die gegen ISIKProzedur valide sind, auch valide sind gegen:\n\n* [Profil Prozedur](https://www.medizininformatik-initiative.de/fhir/core/modul-prozedur/StructureDefinition/Procedure) der Medizininformatik Initiative  \nHinweise zu Inkompatibilitäten können über die [Portalseite](https://service.gematik.de/servicedesk/customer/portal/16) gemeldet werden.",
    "fhirVersion": "4.0.1",
    "kind": "resource",
    "abstract": false,
    "type": "Procedure",
    "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Procedure",
    "derivation": "constraint",
    "differential": {
        "element":  [
            {
                "id": "Procedure",
                "path": "Procedure",
                "constraint":  [
                    {
                        "key": "proc-ISiK-1",
                        "severity": "error",
                        "human": "Falls die Prozedur per OPS kodiert wird, MUSS eine SNOMED-CT kodierte Category abgebildet werden",
                        "expression": "code.coding.where(system = 'http://fhir.de/CodeSystem/bfarm/ops').exists() implies category.coding.where(system = 'http://snomed.info/sct').exists()",
                        "source": "https://gematik.de/fhir/isik/StructureDefinition/ISiKProzedur"
                    },
                    {
                        "key": "proc-ISiK-2",
                        "severity": "error",
                        "human": "Falls eine codierte Prozedur vorliegt MUSS eine kodierte Category abgebildet werden",
                        "expression": "code.coding.exists() implies category.coding.exists()",
                        "source": "https://gematik.de/fhir/isik/StructureDefinition/ISiKProzedur"
                    }
                ]
            },
            {
                "id": "Procedure.extension",
                "path": "Procedure.extension",
                "mustSupport": true
            },
            {
                "id": "Procedure.extension:Dokumentationsdatum",
                "path": "Procedure.extension",
                "sliceName": "Dokumentationsdatum",
                "short": "Dokumentationsdatum",
                "comment": "Datum, an dem die Prozedur dokumentiert wurde.  \n  Es handelt sich hierbei um das fachliche Dokumentationsdatum, nicht zu verwechseln mit dem Datum der technischen Anlage des Datensatzes im Primärsystem. \n  Diese beiden Daten *können* jedoch identisch sein.",
                "min": 0,
                "max": "1",
                "type":  [
                    {
                        "code": "Extension",
                        "profile":  [
                            "http://fhir.de/StructureDefinition/ProzedurDokumentationsdatum"
                        ]
                    }
                ],
                "mustSupport": true
            },
            {
                "id": "Procedure.status",
                "path": "Procedure.status",
                "short": "Status",
                "comment": "Zeigt den aktuellen Status der Prozedur an.     \n  **WICHTIGER Hinweis für Implementierer:  \n  * Alle server-seitigen Implementierungen MÜSSEN in der Lage sein, \n  die systemintern möglichen Statuswerte korrekt in FHIR abzubilden, mindestens jedoch die Werte `completed` und `unknown`.\n  * Alle client-seitigen Implementierungen MÜSSEN in der Lage sein, sämtliche Status-Codes zu interpretieren und dem Anwender in angemessener Form darstellen zu können, \n  beispielsweise durch Ausblenden/Durchstreichen von Prozeduren mit dem status `entered-in-error` und Ausgrauen von Prozeduren, die noch nicht stattgefunden haben, o.ä.",
                "mustSupport": true
            },
            {
                "id": "Procedure.category",
                "path": "Procedure.category",
                "short": "Kategorie",
                "comment": "Die Kategorisierung erfolg vorzugsweise auf Basis von SNOMED. Für OPS-codierte Prozeduren MUSS die Kategorie angegeben werden: Sie kann ermittelt werden, \n  indem das erste Zeichen des OPS-Codes mit Hilfe einer [ConceptMap](http://fhir.de/ConceptMap/OPS-SNOMED-Category) auf die zutreffende SNOMED-Kategorie gemappt wird.\n  **Begründung MS:** Die Kategorisierung dient der Verbesserung von Suche und Darstellung.",
                "mustSupport": true
            },
            {
                "id": "Procedure.category.coding",
                "path": "Procedure.category.coding",
                "slicing": {
                    "discriminator":  [
                        {
                            "type": "pattern",
                            "path": "system"
                        }
                    ],
                    "rules": "open"
                }
            },
            {
                "id": "Procedure.category.coding:SNOMED-CT",
                "path": "Procedure.category.coding",
                "sliceName": "SNOMED-CT",
                "min": 0,
                "max": "1",
                "type":  [
                    {
                        "code": "Coding",
                        "profile":  [
                            "https://gematik.de/fhir/isik/StructureDefinition/ISiKSnomedCTCoding"
                        ]
                    }
                ],
                "mustSupport": true,
                "binding": {
                    "strength": "preferred",
                    "valueSet": "https://gematik.de/fhir/isik/ValueSet/ProzedurenKategorieSCT"
                }
            },
            {
                "id": "Procedure.code",
                "path": "Procedure.code",
                "short": "Prozeduren-Code",
                "comment": "Prozeduren SOLLEN mindestens entweder mit einem OPS-Code oder einem SNOMED-Code aus dem angegebenen ValueSet codiert werden. \n  Ist keine Codierung möglich, MUSS statt dessen eine textuelle Beschreibung der Prozedur angegeben werden.  \n  **Begründung Pflichtfeld:** Ist *weder* eine Codierung *noch* eine textuelle Beschreibung vorhanden, besitzt diese Ressource keine medizinische Aussagefähigkeit.",
                "min": 1,
                "constraint":  [
                    {
                        "key": "sct-ops-1",
                        "severity": "error",
                        "human": "Falls die Prozedur kodiert vorliegt, SOLL mindestens ein OPS oder SNOMED-CT Code angegeben werden.",
                        "expression": "coding.exists() implies coding.where(system = 'http://snomed.info/sct').exists() or coding.where(system = 'http://fhir.de/CodeSystem/bfarm/ops').exists()",
                        "source": "https://gematik.de/fhir/isik/StructureDefinition/ISiKProzedur"
                    },
                    {
                        "key": "proc-ISiK-3",
                        "severity": "error",
                        "human": "Entweder MUSS eine kodierte Prozedur vorliegen oder eine textuelle Beschreibung. Stattdessen nur Extensions hinzuzufügen (vgl. https://www.hl7.org/fhir/element.html - ele-1), ist explizit nicht erlaubt.",
                        "expression": "coding.exists().not() implies text.exists()",
                        "source": "https://gematik.de/fhir/isik/StructureDefinition/ISiKProzedur"
                    }
                ],
                "mustSupport": true
            },
            {
                "id": "Procedure.code.coding",
                "path": "Procedure.code.coding",
                "slicing": {
                    "discriminator":  [
                        {
                            "type": "pattern",
                            "path": "system"
                        }
                    ],
                    "rules": "open"
                },
                "short": "Codierte Darstellung der Prozedur",
                "mustSupport": true
            },
            {
                "id": "Procedure.code.coding:OPS",
                "path": "Procedure.code.coding",
                "sliceName": "OPS",
                "short": "OPS-codierte Darstellung der Prozedur",
                "min": 0,
                "max": "1",
                "type":  [
                    {
                        "code": "Coding",
                        "profile":  [
                            "http://fhir.de/StructureDefinition/CodingOPS"
                        ]
                    }
                ],
                "mustSupport": true,
                "binding": {
                    "strength": "required",
                    "valueSet": "http://fhir.de/ValueSet/bfarm/ops"
                }
            },
            {
                "id": "Procedure.code.coding:OPS.extension:Seitenlokalisation",
                "path": "Procedure.code.coding.extension",
                "sliceName": "Seitenlokalisation",
                "short": "Seitenlokalisation",
                "comment": "**Begründung MS:** Bei OPS-codierten Prozeduren an paarigen Organen oder Körperteilen müssen die Zusatzkennzeichen für die Seitigkeit (R, L oder B) angeben werden",
                "mustSupport": true
            },
            {
                "id": "Procedure.code.coding:OPS.system",
                "path": "Procedure.code.coding.system",
                "short": "Namensraum des Prozeduren-Codes",
                "comment": "Hier ist stets der Wert `http://fhir.de/CodeSystem/bfarm/ops` anzugeben.",
                "mustSupport": true
            },
            {
                "id": "Procedure.code.coding:OPS.version",
                "path": "Procedure.code.coding.version",
                "short": "Die Jahresversion des OPS Kataloges. Angegeben wird immer die vierstellige Jahreszahl (z.B. `2017`)",
                "comment": "**Begründung Pflichtfeld:** Bei Verwendung von OPS ist die Angabe der Version zwingend erforderlich. \n      Hierdurch wird der Tatsache Rechnung getragen, dass jede der jährlich neu erscheinenden Fassung von OPS ein neues Codesystem darstellt.",
                "mustSupport": true
            },
            {
                "id": "Procedure.code.coding:OPS.code",
                "path": "Procedure.code.coding.code",
                "short": "OPS-Code",
                "comment": "Hier ist der OPS-Code ohne jegliche Zusatzkennzeichen (z.B. Seitenlokalisation) oder Versionsnummern anzugeben.",
                "mustSupport": true
            },
            {
                "id": "Procedure.code.coding:SNOMED-CT",
                "path": "Procedure.code.coding",
                "sliceName": "SNOMED-CT",
                "short": "SNOMED-codierte Darstellung der Prozedur",
                "min": 0,
                "max": "1",
                "type":  [
                    {
                        "code": "Coding",
                        "profile":  [
                            "https://gematik.de/fhir/isik/StructureDefinition/ISiKSnomedCTCoding"
                        ]
                    }
                ],
                "mustSupport": true,
                "binding": {
                    "strength": "required",
                    "valueSet": "https://gematik.de/fhir/isik/ValueSet/ProzedurenCodesSCT"
                }
            },
            {
                "id": "Procedure.code.text",
                "path": "Procedure.code.text",
                "short": "Freitextiche Beschreibung der Prozedur",
                "comment": "Die freitextliche Beschreibung kann ergänzend oder anstelle einer codierten Angabe der Prozedur erfolgen.",
                "mustSupport": true
            },
            {
                "id": "Procedure.subject",
                "path": "Procedure.subject",
                "short": "Patientenbezug",
                "mustSupport": true
            },
            {
                "id": "Procedure.subject.reference",
                "path": "Procedure.subject.reference",
                "short": "Patienten-Link",
                "comment": "Die Verlinkung auf eine Patienten-Ressource dient der technischen Zuordnung der Dokumentation zu einem Patienten und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc.",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Procedure.encounter",
                "path": "Procedure.encounter",
                "short": "Aufenthaltsbezug",
                "mustSupport": true
            },
            {
                "id": "Procedure.encounter.reference",
                "path": "Procedure.encounter.reference",
                "short": "Encounter-Link",
                "comment": "**Begründung Pflichtfeld:** Die Verlinkung auf eine Encounter-Ressource dient der technischen Zuordnung der Dokumentation zu einem Aufenthalt \n    und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc.    \n    **WICHTIGER Hinweis für Implementierer:** Die Zuordnung MUSS auf auf einen Encounter der Ebene &quot;Abteilungskontakt&quot; (siehe hierzu {{pagelink:Fall}}) erfolgen. \n    Bei der Auswahl des Encounters ist zu beachten, dass unter einer (Abrechnungs-)&quot;Fallnummer&quot; (hier: `Encounter.account`) \n    unter Umständen mehrere Encounter gruppiert sein können (z.B. stationärer Besuch mit mehreren vor- und nachstationären Aufenthalten.)",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Procedure.performed[x]",
                "path": "Procedure.performed[x]",
                "short": "Durchführungsdatum oder -Zeitraum",
                "comment": "Es muss mindestens entweder ein (partielles) Durchführungsdatum oder der Beginn des Durchführungszeitraumes angegeben werden.\n  **Begründung Pflichtfeld:** Die zeitliche Einordnung einer Prozedur ist in vielen Fällen maßgeblich für deren medizinische Relevanz.",
                "min": 1,
                "type":  [
                    {
                        "code": "dateTime"
                    },
                    {
                        "code": "Period"
                    }
                ],
                "mustSupport": true
            },
            {
                "id": "Procedure.note",
                "path": "Procedure.note",
                "short": "Notizen",
                "comment": "Ergänzende Hinweise und Anmerkungen zur Prozedur",
                "mustSupport": true
            }
        ]
    }
}

ISiKProzedur

Constraints/Invarianten

Name	Schweregrad	Beschreibung	Ausdruck
proc-ISiK-1	error	Falls die Prozedur per OPS kodiert wird, MUSS eine SNOMED-CT kodierte Category abgebildet werden	code.coding.where(system = 'http://fhir.de/CodeSystem/bfarm/ops').exists() implies category.coding.where(system = 'http://snomed.info/sct').exists()
proc-ISiK-2	error	Falls eine codierte Prozedur vorliegt MUSS eine kodierte Category abgebildet werden	code.coding.exists() implies category.coding.exists()
sct-ops-1	error	Falls die Prozedur kodiert vorliegt, SOLL mindestens ein OPS oder SNOMED-CT Code angegeben werden.	coding.exists() implies coding.where(system = 'http://snomed.info/sct').exists() or coding.where(system = 'http://fhir.de/CodeSystem/bfarm/ops').exists()
proc-ISiK-3	error	Entweder MUSS eine kodierte Prozedur vorliegen oder eine textuelle Beschreibung. Stattdessen nur Extensions hinzuzufügen (vgl. https://www.hl7.org/fhir/element.html - ele-1), ist explizit nicht erlaubt.	coding.exists().not() implies text.exists()

Terminology-Bindings

Element	Staerke	ValueSet
Procedure.category.coding:SNOMED-CT	preferred	https://gematik.de/fhir/isik/ValueSet/ProzedurenKategorieSCT
Procedure.code.coding:OPS	required	http://fhir.de/ValueSet/bfarm/ops
Procedure.code.coding:SNOMED-CT	required	https://gematik.de/fhir/isik/ValueSet/ProzedurenCodesSCT