Implementierungsleitfaden ISiK-Medikation

ISiKAMTSBewertung (RiskAssessment)

ISiKAMTSBewertung (RiskAssessment)

ISiK AMTS-Bewertung

Dieses Profil ermöglicht die Abbildung von Informationen zur Risikobeurteilung im Rahmen der Arzneimitteltherapiesicherheit (AMTS).

Bestätigungsrelevanz

Metadaten

Canonical	https://gematik.de/fhir/isik/StructureDefinition/ISiKAMTSBewertung
Status	active
Version	4.0.3
Basis	http://hl7.org/fhir/StructureDefinition/RiskAssessment

Inhalt

ISiKAMTSBewertung (RiskAssessment)	I		RiskAssessment	There are no (further) constraints on this element Element id RiskAssessment Short description Potential outcomes for a subject with likelihood Alternate names Prognosis Definition An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome. Data type RiskAssessment Constraints dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources `contained.contained.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-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-5: If a resource is contained in another resource, it SHALL NOT have a security label `contained.meta.security.empty()` dom-6: A resource should have narrative for robust management text.`div`.exists() Mappings rim: Entity. Role, or Act workflow: Event v2: N/A rim: Observation[classCode=OBS, moodCode=EVN, code="Risk Assessment"] openehr: OpenEHR-EHR-EVALUATION.risk.v1
id	Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.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 RiskAssessment.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())`
implicitRules	Σ ?!	0..1	uri	There are no (further) constraints on this element Element id RiskAssessment.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())`
language		0..1	codeBinding	There are no (further) constraints on this element Element id RiskAssessment.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())`
text		0..1	Narrative	There are no (further) constraints on this element Element id RiskAssessment.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: Act.text?
contained		0..*	Resource	There are no (further) constraints on this element Element id RiskAssessment.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: N/A
extension	S I	0..*	Extension	Element id RiskAssessment.extension Short description akzeptiertes (in Kauf genommenes) Risiko 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 Begründung des Must-Support: Die Möglichkeit der freitextlichen Dokumentation dieser Daten wurde von der Fachseite (AG) gewünscht. Hinweis: Hier kann die Begründung und ggf. erforderliche Begleitmaßnahmen für ein in Kauf genommenes Risiko dokumentiert werden. Data type Extension Sliced: Unordered, Open, by url(Value) 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
acceptedRisk	S I	0..1	Extension(string)	Element id RiskAssessment.extension:acceptedRisk Short description Optional Extensions Element Alternate names extensions, user content Definition Optional Extension Element - found in all resources. 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(string) Extension URL https://gematik.de/fhir/isik/StructureDefinition/ExtensionISiKAcceptedRisk 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 RiskAssessment.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 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
identifier	Σ	0..*	Identifier	There are no (further) constraints on this element Element id RiskAssessment.identifier Short description Unique identifier for the assessment Definition Business identifier assigned to the risk assessment. Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.identifier w5: FiveWs.identifier rim: .id openehr: Workflow Identifier
basedOn		0..1	Reference(Resource)	There are no (further) constraints on this element Element id RiskAssessment.basedOn Short description Request fulfilled by this assessment Definition A reference to the request that is fulfilled by this risk assessment. Data type Reference(Resource) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.basedOn
parent		0..1	Reference(Resource)	There are no (further) constraints on this element Element id RiskAssessment.parent Short description Part of this occurrence Definition A reference to a resource that this risk assessment is part of, such as a Procedure. Data type Reference(Resource) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.partOf
status	S Σ	1..1	codeBinding	Element id RiskAssessment.status Short description registered \| preliminary \| final \| amended + Definition The status of the RiskAssessment, using the same statuses as an Observation. Comments Begründung des Must-Support-Support-Flag (MS): Die Angabe des Status ist im Standard vorgeschrieben. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. Data type code Binding The status of the risk assessment; e.g. preliminary, final, amended, etc. ObservationStatus (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.status w5: FiveWs.status
method	Σ	0..1	CodeableConcept	There are no (further) constraints on this element Element id RiskAssessment.method Short description Evaluation mechanism Definition The algorithm, process or mechanism used to evaluate the risk. Requirements The method can influence the results of the assessment. Data type CodeableConcept Binding The mechanism or algorithm used to make the assessment; e.g. TIMI, PRISM, Cardiff Type 2 diabetes, etc. (unbound) (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings w5: FiveWs.class rim: .methodCode
code	S Σ	0..1	CodeableConcept	Element id RiskAssessment.code Short description Art der Risikobeurteilung Definition The type of the risk assessment performed. Comments Begründung des Must-Support-Support-Flag (MS): Es handelt sich um eine Grundinformation zur Risikobewertung. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. Data type CodeableConcept Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.code w5: FiveWs.what[x]
id		0..1	string	There are no (further) constraints on this element Element id RiskAssessment.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 RiskAssessment.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
coding	S Σ	0..*	Coding	There are no (further) constraints on this element Element id RiskAssessment.code.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 Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings 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 RiskAssessment.code.coding.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 RiskAssessment.code.coding.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
system	S Σ	1..1	uri	There are no (further) constraints on this element Element id RiskAssessment.code.coding.system Short description Identity of the terminology system 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 The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings v2: CE.3 rim:* ./codeSystem orim: fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
version	Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.code.coding.version Short description Version of the system - if relevant Definition The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Comments Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings v2: CE.7 rim:* ./codeSystemVersion orim: fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
code	S Σ	1..1	code	There are no (further) constraints on this element Element id RiskAssessment.code.coding.code Short description Symbol in syntax defined by the system 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. Data type code Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings v2: CE.1 rim:* ./code orim: fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
display	S Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.code.coding.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. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings 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 RiskAssessment.code.coding.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 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 ]
text	S Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.code.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 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 Σ	1..1	Reference(Patient)	Element id RiskAssessment.subject Short description Referenz auf den Patienten Definition The patient or group the risk assessment applies to. Comments Begründung des Must-Support-Support-Flag (MS): Eine Risikobewertung muss sich immer auf ein Subjekt (hier: Patient) beziehen. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. Data type Reference(Patient) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.subject w5: FiveWs.subject[x] rim: .participation[typeCode=SBJ].role openehr: Subject of Care w5: FiveWs.subject
id		0..1	string	There are no (further) constraints on this element Element id RiskAssessment.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 RiskAssessment.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
reference	S Σ I	1..1	string	There are no (further) constraints on this element Element id RiskAssessment.subject.reference Short description Literal reference, Relative, internal or absolute URL 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 Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. 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
type	Σ	0..1	uriBinding	There are no (further) constraints on this element Element id RiskAssessment.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
identifier	Σ	0..1	Identifier	There are no (further) constraints on this element Element id RiskAssessment.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: .identifier
display	Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.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
encounter	S Σ	0..1	Reference(Encounter)	Element id RiskAssessment.encounter Short description Referenz auf den Abteilungskontakt Definition The encounter where the assessment was performed. Comments Begründung des Must-Support-Support-Flag (MS): Der Encounter liefert den Kontext zur Risikobeurteilung. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. Data type Reference(Encounter) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.encounter w5: FiveWs.context rim: .inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN]
id		0..1	string	There are no (further) constraints on this element Element id RiskAssessment.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 RiskAssessment.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
reference	S Σ I	1..1	string	There are no (further) constraints on this element Element id RiskAssessment.encounter.reference Short description Literal reference, Relative, internal or absolute URL 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 Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. 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
type	Σ	0..1	uriBinding	There are no (further) constraints on this element Element id RiskAssessment.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
identifier	Σ	0..1	Identifier	There are no (further) constraints on this element Element id RiskAssessment.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: .identifier
display	Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.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
occurrence[x]	S Σ	0..1		Element id RiskAssessment.occurrence[x] Short description Zeitpunkt oder Zeitraum der Beurteilung Definition The date (and possibly time) the risk assessment was performed. Requirements The assessment results lose validity the more time elapses from when they are first made. Comments Begründung des Must-Support-Support-Flag (MS): Die Angabe des Zeitpunkts oder Zeitraums ist essentiell für die Nachvollziehbarkeit. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. Sliced: Unordered, Open, by $this(Type) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.occurrence[x] w5: FiveWs.done[x] rim: .effectiveTime
occurrenceDateTime	S Σ	0..1	dateTime	Element id RiskAssessment.occurrence[x]:occurrenceDateTime Short description When was assessment made? Definition The date (and possibly time) the risk assessment was performed. Requirements The assessment results lose validity the more time elapses from when they are first made. Comments Begründung des Must-Support-Support-Flag (MS): Die Angabe des Zeitpunkts ist essentiell für die Nachvollziehbarkeit. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. Data type dateTime Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.occurrence[x] w5: FiveWs.done[x] rim: .effectiveTime
occurrencePeriod	S Σ	0..1	Period	Element id RiskAssessment.occurrence[x]:occurrencePeriod Short description When was assessment made? Definition The date (and possibly time) the risk assessment was performed. Requirements The assessment results lose validity the more time elapses from when they are first made. Comments Begründung des Must-Support-Support-Flag (MS): Die Angabe des Zeitraums ist essentiell für die Nachvollziehbarkeit. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. Data type Period Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.occurrence[x] w5: FiveWs.done[x] rim: .effectiveTime
condition	S Σ	0..1	Reference(Condition)	Element id RiskAssessment.condition Short description Bezugsdiagnose (Referenz) Definition For assessments or prognosis specific to a particular condition, indicates the condition being assessed. Comments Begründung des Must-Support-Support-Flag (MS): Die Bezugsdiagnose ist eine relevante Hintergrundinformation. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. Data type Reference(Condition) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: .outboundRelationship[typeCode=SUBJ].target[classCode=OBS, moodCode=EVN]
id		0..1	string	There are no (further) constraints on this element Element id RiskAssessment.condition.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 RiskAssessment.condition.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
reference	S Σ I	1..1	string	There are no (further) constraints on this element Element id RiskAssessment.condition.reference Short description Literal reference, Relative, internal or absolute URL 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 Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. 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
type	Σ	0..1	uriBinding	There are no (further) constraints on this element Element id RiskAssessment.condition.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
identifier	Σ	0..1	Identifier	There are no (further) constraints on this element Element id RiskAssessment.condition.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: .identifier
display	Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.condition.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
performer	Σ	0..1	Reference(Practitioner \| PractitionerRole \| Device)	There are no (further) constraints on this element Element id RiskAssessment.performer Short description Who did assessment? Definition The provider or software application that performed the assessment. Data type Reference(Practitioner \| PractitionerRole \| Device) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.performer.actor w5: FiveWs.actor rim: .participation[typeCode=PFM].role[classCode=ASSIGNED] openehr: Information Provider
reasonCode	S	0..*	CodeableConcept	Element id RiskAssessment.reasonCode Short description Grund der Risikobewertung (codiert) Definition The reason the risk assessment was performed. Comments Begründung des Must-Support-Support-Flag (MS): Die Angabe einer Begründung ist fachlich üblich und angebracht. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. Data type CodeableConcept Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.reasonCode w5: FiveWs.why[x]
id		0..1	string	There are no (further) constraints on this element Element id RiskAssessment.reasonCode.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 RiskAssessment.reasonCode.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
coding	S Σ	0..*	Coding	There are no (further) constraints on this element Element id RiskAssessment.reasonCode.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 Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings 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 RiskAssessment.reasonCode.coding.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 RiskAssessment.reasonCode.coding.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
system	S Σ	1..1	uri	There are no (further) constraints on this element Element id RiskAssessment.reasonCode.coding.system Short description Identity of the terminology system 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 The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings v2: CE.3 rim:* ./codeSystem orim: fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
version	Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.reasonCode.coding.version Short description Version of the system - if relevant Definition The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Comments Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings v2: CE.7 rim:* ./codeSystemVersion orim: fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
code	S Σ	1..1	code	There are no (further) constraints on this element Element id RiskAssessment.reasonCode.coding.code Short description Symbol in syntax defined by the system 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. Data type code Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings v2: CE.1 rim:* ./code orim: fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
display	S Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.reasonCode.coding.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. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings 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 RiskAssessment.reasonCode.coding.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 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 ]
text	S Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.reasonCode.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 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
reasonReference	S	0..*	Reference(Condition \| Observation \| DiagnosticReport \| DocumentReference)	Element id RiskAssessment.reasonReference Short description Grund der Risikobewertung (Referenz) Definition Resources supporting the reason the risk assessment was performed. Comments Begründung des Must-Support-Support-Flag (MS): Die Angabe einer Begründung ist fachlich üblich und angebracht. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. Data type Reference(Condition \| Observation \| DiagnosticReport \| DocumentReference) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.reasonReference w5: FiveWs.why[x]
id		0..1	string	There are no (further) constraints on this element Element id RiskAssessment.reasonReference.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 RiskAssessment.reasonReference.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
reference	S Σ I	1..1	string	There are no (further) constraints on this element Element id RiskAssessment.reasonReference.reference Short description Literal reference, Relative, internal or absolute URL 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 Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. 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
type	Σ	0..1	uriBinding	There are no (further) constraints on this element Element id RiskAssessment.reasonReference.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
identifier	Σ	0..1	Identifier	There are no (further) constraints on this element Element id RiskAssessment.reasonReference.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: .identifier
display	Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.reasonReference.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
basis	S	0..*	Reference(Resource)	Element id RiskAssessment.basis Short description Entscheidungsgrundlagen der Risikobewertung (Referenz) Definition Indicates the source data considered as part of the assessment (for example, FamilyHistory, Observations, Procedures, Conditions, etc.). Comments Begründung des Must-Support-Support-Flag (MS): Die Referenz zu den Grundlagen der Beurteilung ermöglicht die Transparenz der Beurteilungs-Findung. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. Data type Reference(Resource) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: .outboundRelationship[typeCode=DRIV].target openehr: Risk Factor; Link to Evidence
id		0..1	string	There are no (further) constraints on this element Element id RiskAssessment.basis.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 RiskAssessment.basis.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
reference	S Σ I	1..1	string	There are no (further) constraints on this element Element id RiskAssessment.basis.reference Short description Literal reference, Relative, internal or absolute URL 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 Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. 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
type	Σ	0..1	uriBinding	There are no (further) constraints on this element Element id RiskAssessment.basis.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
identifier	Σ	0..1	Identifier	There are no (further) constraints on this element Element id RiskAssessment.basis.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: .identifier
display	Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.basis.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
prediction	S I	0..*	BackboneElement	Element id RiskAssessment.prediction Short description Outcome predicted Definition Describes the expected outcome for the subject. Comments Begründung des Must-Support-Support-Flag (MS): Angaben über Outcome und Größe des Risikos. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ras-2: Must be <= 100 `probability is decimal implies (probability as decimal) <= 100` Mappings rim: .outboundRelationship[typeCode=VALUE].target[classCod=OBS, moodCode=RISK]
id		0..1	string	There are no (further) constraints on this element Element id RiskAssessment.prediction.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 RiskAssessment.prediction.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 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
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id RiskAssessment.prediction.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
outcome	S	0..1	CodeableConcept	Element id RiskAssessment.prediction.outcome Short description Mögliches Outcome für den Patienten Definition One of the potential outcomes for the patient (e.g. remission, death, a particular condition). Comments Begründung des Must-Support-Support-Flag (MS): Das erwartete Outcome ist eine Kerninformation der Risikobeurteilung. `Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt.` Data type CodeableConcept Binding The condition or other outcome; e.g. death, remission, amputation, infection, etc. (unbound) (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: .value openehr: Risk
id		0..1	string	There are no (further) constraints on this element Element id RiskAssessment.prediction.outcome.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 RiskAssessment.prediction.outcome.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
coding	S Σ	0..*	Coding	There are no (further) constraints on this element Element id RiskAssessment.prediction.outcome.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 Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings 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 RiskAssessment.prediction.outcome.coding.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 RiskAssessment.prediction.outcome.coding.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
system	S Σ	1..1	uri	There are no (further) constraints on this element Element id RiskAssessment.prediction.outcome.coding.system Short description Identity of the terminology system 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 The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings v2: CE.3 rim:* ./codeSystem orim: fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
version	Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.prediction.outcome.coding.version Short description Version of the system - if relevant Definition The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Comments Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings v2: CE.7 rim:* ./codeSystemVersion orim: fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
code	S Σ	1..1	code	There are no (further) constraints on this element Element id RiskAssessment.prediction.outcome.coding.code Short description Symbol in syntax defined by the system 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. Data type code Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings v2: CE.1 rim:* ./code orim: fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
display	S Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.prediction.outcome.coding.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. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings 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 RiskAssessment.prediction.outcome.coding.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 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 ]
text	S Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.prediction.outcome.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 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
probability[x]	I	0..1		There are no (further) constraints on this element Element id RiskAssessment.prediction.probability[x] Short description Likelihood of specified outcome Definition Indicates how likely the outcome is (in the specified timeframe). Comments If range is used, it represents the lower and upper bounds of certainty; e.g. 40-60% Decimal values are expressed as percentages as well (max = 100). Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ras-1: low and high must be percentages, if present `(low.empty() or ((low.code = '%') and (low.system = %ucum))) and (high.empty() or ((high.code = '%') and (high.system = %ucum)))` Mappings rim: .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="probability"].value openehr: Category
probabilityDecimal			decimal	There are no (further) constraints on this element Data type decimal
probabilityRange			Range	There are no (further) constraints on this element Data type Range
qualitativeRisk	S	0..1	CodeableConceptBinding	Element id RiskAssessment.prediction.qualitativeRisk Short description Risikowahrscheinlichkeit (qualitativ, codiert) Definition Indicates how likely the outcome is (in the specified timeframe), expressed as a qualitative value (e.g. low, medium, or high). Comments Begründung des Must-Support-Support-Flag (MS): Die Risikowahrscheinlichkeit ist eine Kerninformation der Risikobeurteilung. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. Data type CodeableConcept Binding The likelihood of the occurrence of a specified outcome. RiskProbability (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
id		0..1	string	There are no (further) constraints on this element Element id RiskAssessment.prediction.qualitativeRisk.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 RiskAssessment.prediction.qualitativeRisk.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
coding	S Σ	0..*	Coding	There are no (further) constraints on this element Element id RiskAssessment.prediction.qualitativeRisk.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 Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings 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 RiskAssessment.prediction.qualitativeRisk.coding.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 RiskAssessment.prediction.qualitativeRisk.coding.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
system	S Σ	1..1	uri	There are no (further) constraints on this element Element id RiskAssessment.prediction.qualitativeRisk.coding.system Short description Identity of the terminology system 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 The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings v2: CE.3 rim:* ./codeSystem orim: fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
version	Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.prediction.qualitativeRisk.coding.version Short description Version of the system - if relevant Definition The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Comments Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings v2: CE.7 rim:* ./codeSystemVersion orim: fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
code	S Σ	1..1	code	There are no (further) constraints on this element Element id RiskAssessment.prediction.qualitativeRisk.coding.code Short description Symbol in syntax defined by the system 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. Data type code Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings v2: CE.1 rim:* ./code orim: fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
display	S Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.prediction.qualitativeRisk.coding.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. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings 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 RiskAssessment.prediction.qualitativeRisk.coding.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 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 ]
text	S Σ	0..1	string	There are no (further) constraints on this element Element id RiskAssessment.prediction.qualitativeRisk.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 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
relativeRisk		0..1	decimal	There are no (further) constraints on this element Element id RiskAssessment.prediction.relativeRisk Short description Relative likelihood Definition Indicates the risk for this particular subject (with their specific characteristics) divided by the risk of the population in general. (Numbers greater than 1 = higher risk than the population, numbers less than 1 = lower risk.). Requirements Absolute risk is less meaningful than relative risk. Data type decimal Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="relative risk"].value
when[x]		0..1		There are no (further) constraints on this element Element id RiskAssessment.prediction.when[x] Short description Timeframe or age range Definition Indicates the period of time or age range of the subject to which the specified probability applies. Comments If not specified, the risk applies "over the subject's lifespan". Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: .effectiveTime or .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="age"].value
whenPeriod			Period	There are no (further) constraints on this element Data type Period
whenRange			Range	There are no (further) constraints on this element Data type Range
rationale		0..1	string	There are no (further) constraints on this element Element id RiskAssessment.prediction.rationale Short description Explanation of prediction Definition Additional information explaining the basis for the prediction. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: .reasonCode.text openehr: Rationale
mitigation	S	0..1	string	Element id RiskAssessment.mitigation Short description Hinweis zur Risikovermeidung Definition A description of the steps that might be taken to reduce the identified risk(s). Requirements One of the main reasons for assessing risks is to identify whether interventional steps are needed to reduce risk. Comments Begründung des Must-Support-Support-Flag (MS): Hinweise zur Risikovermeidung sind eine Kerninformation der Risikobeurteilung. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: .outboundRelationship[typeCode=MTGT].target[classCode=ACT, moodCode=EVN].text
note	S	0..*	Annotation	Element id RiskAssessment.note Short description Anmerkung zur Risikobewertung Definition Additional comments about the risk assessment. Comments Begründung des Must-Support-Support-Flag (MS): freitextliche Anmerkungen sind fachlich üblich und gewünscht. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. Data type Annotation Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.note

<StructureDefinition xmlns="http://hl7.org/fhir">
    <id value="ISiKAMTSBewertung" />
    <url value="https://gematik.de/fhir/isik/StructureDefinition/ISiKAMTSBewertung" />
    <version value="4.0.3" />
    <name value="ISiKAMTSBewertung" />
    <title value="ISiK AMTS-Bewertung" />
    <status value="active" />
    <experimental value="false" />
    <date value="2025-03-17" />
    <publisher value="gematik GmbH" />
    <description value="Dieses Profil erm&#246;glicht die Abbildung von Informationen zur Risikobeurteilung im Rahmen der Arzneimitteltherapiesicherheit (AMTS)." />
    <fhirVersion value="4.0.1" />
    <kind value="resource" />
    <abstract value="false" />
    <type value="RiskAssessment" />
    <baseDefinition value="http://hl7.org/fhir/StructureDefinition/RiskAssessment" />
    <derivation value="constraint" />
    <differential>
        <element id="RiskAssessment.extension">
            <path value="RiskAssessment.extension" />
            <short value="akzeptiertes (in Kauf genommenes) Risiko" />
            <comment value="Begr&#252;ndung des Must-Support: Die M&#246;glichkeit der freitextlichen Dokumentation dieser Daten wurde von der Fachseite (AG) gew&#252;nscht.\n\n  Hinweis: Hier kann die Begr&#252;ndung und ggf. erforderliche Begleitma&#223;nahmen f&#252;r ein in Kauf genommenes Risiko dokumentiert werden." />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.extension:acceptedRisk">
            <path value="RiskAssessment.extension" />
            <sliceName value="acceptedRisk" />
            <min value="0" />
            <max value="1" />
            <type>
                <code value="Extension" />
                <profile value="https://gematik.de/fhir/isik/StructureDefinition/ExtensionISiKAcceptedRisk" />
            </type>
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.status">
            <path value="RiskAssessment.status" />
            <comment value="Begr&#252;ndung des Must-Support-Support-Flag (MS): Die Angabe des Status ist im Standard vorgeschrieben.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugef&#252;gt und mit den Stakeholdern abgestimmt." />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.code">
            <path value="RiskAssessment.code" />
            <short value="Art der Risikobeurteilung" />
            <comment value="Begr&#252;ndung des Must-Support-Support-Flag (MS): Es handelt sich um eine Grundinformation zur Risikobewertung.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugef&#252;gt und mit den Stakeholdern abgestimmt." />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.code.coding">
            <path value="RiskAssessment.code.coding" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.code.coding.system">
            <path value="RiskAssessment.code.coding.system" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.code.coding.code">
            <path value="RiskAssessment.code.coding.code" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.code.coding.display">
            <path value="RiskAssessment.code.coding.display" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.code.text">
            <path value="RiskAssessment.code.text" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.subject">
            <path value="RiskAssessment.subject" />
            <short value="Referenz auf den Patienten" />
            <comment value="Begr&#252;ndung des Must-Support-Support-Flag (MS): Eine Risikobewertung muss sich immer auf ein Subjekt (hier: Patient) beziehen.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugef&#252;gt und mit den Stakeholdern abgestimmt." />
            <type>
                <code value="Reference" />
                <targetProfile value="http://hl7.org/fhir/StructureDefinition/Patient" />
            </type>
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.subject.reference">
            <path value="RiskAssessment.subject.reference" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.encounter">
            <path value="RiskAssessment.encounter" />
            <short value="Referenz auf den Abteilungskontakt" />
            <comment value="Begr&#252;ndung des Must-Support-Support-Flag (MS): Der Encounter liefert den Kontext zur Risikobeurteilung.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugef&#252;gt und mit den Stakeholdern abgestimmt." />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.encounter.reference">
            <path value="RiskAssessment.encounter.reference" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.occurrence[x]">
            <path value="RiskAssessment.occurrence[x]" />
            <slicing>
                <discriminator>
                    <type value="type" />
                    <path value="$this" />
                </discriminator>
                <ordered value="false" />
                <rules value="open" />
            </slicing>
            <short value="Zeitpunkt oder Zeitraum der Beurteilung" />
            <comment value="Begr&#252;ndung des Must-Support-Support-Flag (MS): Die Angabe des Zeitpunkts oder Zeitraums ist essentiell f&#252;r die Nachvollziehbarkeit.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugef&#252;gt und mit den Stakeholdern abgestimmt." />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.occurrence[x]:occurrenceDateTime">
            <path value="RiskAssessment.occurrence[x]" />
            <sliceName value="occurrenceDateTime" />
            <comment value="Begr&#252;ndung des Must-Support-Support-Flag (MS): Die Angabe des Zeitpunkts ist essentiell f&#252;r die Nachvollziehbarkeit.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugef&#252;gt und mit den Stakeholdern abgestimmt." />
            <min value="0" />
            <max value="1" />
            <type>
                <code value="dateTime" />
            </type>
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.occurrence[x]:occurrencePeriod">
            <path value="RiskAssessment.occurrence[x]" />
            <sliceName value="occurrencePeriod" />
            <comment value="Begr&#252;ndung des Must-Support-Support-Flag (MS): Die Angabe des Zeitraums ist essentiell f&#252;r die Nachvollziehbarkeit.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugef&#252;gt und mit den Stakeholdern abgestimmt." />
            <min value="0" />
            <max value="1" />
            <type>
                <code value="Period" />
            </type>
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.condition">
            <path value="RiskAssessment.condition" />
            <short value="Bezugsdiagnose (Referenz)" />
            <comment value="Begr&#252;ndung des Must-Support-Support-Flag (MS): Die Bezugsdiagnose ist eine relevante Hintergrundinformation.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugef&#252;gt und mit den Stakeholdern abgestimmt." />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.condition.reference">
            <path value="RiskAssessment.condition.reference" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.reasonCode">
            <path value="RiskAssessment.reasonCode" />
            <short value="Grund der Risikobewertung (codiert)" />
            <comment value="Begr&#252;ndung des Must-Support-Support-Flag (MS): Die Angabe einer Begr&#252;ndung ist fachlich &#252;blich und angebracht.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugef&#252;gt und mit den Stakeholdern abgestimmt." />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.reasonCode.coding">
            <path value="RiskAssessment.reasonCode.coding" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.reasonCode.coding.system">
            <path value="RiskAssessment.reasonCode.coding.system" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.reasonCode.coding.code">
            <path value="RiskAssessment.reasonCode.coding.code" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.reasonCode.coding.display">
            <path value="RiskAssessment.reasonCode.coding.display" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.reasonCode.text">
            <path value="RiskAssessment.reasonCode.text" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.reasonReference">
            <path value="RiskAssessment.reasonReference" />
            <short value="Grund der Risikobewertung (Referenz)" />
            <comment value="Begr&#252;ndung des Must-Support-Support-Flag (MS): Die Angabe einer Begr&#252;ndung ist fachlich &#252;blich und angebracht.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugef&#252;gt und mit den Stakeholdern abgestimmt." />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.reasonReference.reference">
            <path value="RiskAssessment.reasonReference.reference" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.basis">
            <path value="RiskAssessment.basis" />
            <short value="Entscheidungsgrundlagen der Risikobewertung (Referenz)" />
            <comment value="Begr&#252;ndung des Must-Support-Support-Flag (MS): Die Referenz zu den Grundlagen der Beurteilung erm&#246;glicht die Transparenz der Beurteilungs-Findung.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugef&#252;gt und mit den Stakeholdern abgestimmt." />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.basis.reference">
            <path value="RiskAssessment.basis.reference" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.prediction">
            <path value="RiskAssessment.prediction" />
            <comment value="Begr&#252;ndung des Must-Support-Support-Flag (MS): Angaben &#252;ber Outcome und Gr&#246;&#223;e des Risikos.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugef&#252;gt und mit den Stakeholdern abgestimmt." />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.prediction.outcome">
            <path value="RiskAssessment.prediction.outcome" />
            <short value="M&#246;gliches Outcome f&#252;r den Patienten" />
            <comment value="Begr&#252;ndung des Must-Support-Support-Flag (MS): Das erwartete Outcome ist eine Kerninformation der Risikobeurteilung.\n\n    Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugef&#252;gt und mit den Stakeholdern abgestimmt." />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.prediction.outcome.coding">
            <path value="RiskAssessment.prediction.outcome.coding" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.prediction.outcome.coding.system">
            <path value="RiskAssessment.prediction.outcome.coding.system" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.prediction.outcome.coding.code">
            <path value="RiskAssessment.prediction.outcome.coding.code" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.prediction.outcome.coding.display">
            <path value="RiskAssessment.prediction.outcome.coding.display" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.prediction.outcome.text">
            <path value="RiskAssessment.prediction.outcome.text" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.prediction.qualitativeRisk">
            <path value="RiskAssessment.prediction.qualitativeRisk" />
            <short value="Risikowahrscheinlichkeit (qualitativ, codiert)" />
            <comment value="Begr&#252;ndung des Must-Support-Support-Flag (MS): Die Risikowahrscheinlichkeit ist eine Kerninformation der Risikobeurteilung.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugef&#252;gt und mit den Stakeholdern abgestimmt." />
            <mustSupport value="true" />
            <binding>
                <strength value="extensible" />
                <valueSet value="http://hl7.org/fhir/ValueSet/risk-probability" />
            </binding>
        </element>
        <element id="RiskAssessment.prediction.qualitativeRisk.coding">
            <path value="RiskAssessment.prediction.qualitativeRisk.coding" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.prediction.qualitativeRisk.coding.system">
            <path value="RiskAssessment.prediction.qualitativeRisk.coding.system" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.prediction.qualitativeRisk.coding.code">
            <path value="RiskAssessment.prediction.qualitativeRisk.coding.code" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.prediction.qualitativeRisk.coding.display">
            <path value="RiskAssessment.prediction.qualitativeRisk.coding.display" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.prediction.qualitativeRisk.text">
            <path value="RiskAssessment.prediction.qualitativeRisk.text" />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.mitigation">
            <path value="RiskAssessment.mitigation" />
            <short value="Hinweis zur Risikovermeidung" />
            <comment value="Begr&#252;ndung des Must-Support-Support-Flag (MS): Hinweise zur Risikovermeidung sind eine Kerninformation der Risikobeurteilung.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugef&#252;gt und mit den Stakeholdern abgestimmt." />
            <mustSupport value="true" />
        </element>
        <element id="RiskAssessment.note">
            <path value="RiskAssessment.note" />
            <short value="Anmerkung zur Risikobewertung" />
            <comment value="Begr&#252;ndung des Must-Support-Support-Flag (MS): freitextliche Anmerkungen sind fachlich &#252;blich und gew&#252;nscht.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugef&#252;gt und mit den Stakeholdern abgestimmt." />
            <mustSupport value="true" />
        </element>
    </differential>
</StructureDefinition>

{
    "resourceType": "StructureDefinition",
    "id": "ISiKAMTSBewertung",
    "url": "https://gematik.de/fhir/isik/StructureDefinition/ISiKAMTSBewertung",
    "version": "4.0.3",
    "name": "ISiKAMTSBewertung",
    "title": "ISiK AMTS-Bewertung",
    "status": "active",
    "experimental": false,
    "date": "2025-03-17",
    "publisher": "gematik GmbH",
    "description": "Dieses Profil ermöglicht die Abbildung von Informationen zur Risikobeurteilung im Rahmen der Arzneimitteltherapiesicherheit (AMTS).",
    "fhirVersion": "4.0.1",
    "kind": "resource",
    "abstract": false,
    "type": "RiskAssessment",
    "baseDefinition": "http://hl7.org/fhir/StructureDefinition/RiskAssessment",
    "derivation": "constraint",
    "differential": {
        "element":  [
            {
                "id": "RiskAssessment.extension",
                "path": "RiskAssessment.extension",
                "short": "akzeptiertes (in Kauf genommenes) Risiko",
                "comment": "Begründung des Must-Support: Die Möglichkeit der freitextlichen Dokumentation dieser Daten wurde von der Fachseite (AG) gewünscht.\n\n  Hinweis: Hier kann die Begründung und ggf. erforderliche Begleitmaßnahmen für ein in Kauf genommenes Risiko dokumentiert werden.",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.extension:acceptedRisk",
                "path": "RiskAssessment.extension",
                "sliceName": "acceptedRisk",
                "min": 0,
                "max": "1",
                "type":  [
                    {
                        "code": "Extension",
                        "profile":  [
                            "https://gematik.de/fhir/isik/StructureDefinition/ExtensionISiKAcceptedRisk"
                        ]
                    }
                ],
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.status",
                "path": "RiskAssessment.status",
                "comment": "Begründung des Must-Support-Support-Flag (MS): Die Angabe des Status ist im Standard vorgeschrieben.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. ",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.code",
                "path": "RiskAssessment.code",
                "short": "Art der Risikobeurteilung",
                "comment": "Begründung des Must-Support-Support-Flag (MS): Es handelt sich um eine Grundinformation zur Risikobewertung.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. ",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.code.coding",
                "path": "RiskAssessment.code.coding",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.code.coding.system",
                "path": "RiskAssessment.code.coding.system",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.code.coding.code",
                "path": "RiskAssessment.code.coding.code",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.code.coding.display",
                "path": "RiskAssessment.code.coding.display",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.code.text",
                "path": "RiskAssessment.code.text",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.subject",
                "path": "RiskAssessment.subject",
                "short": "Referenz auf den Patienten",
                "comment": "Begründung des Must-Support-Support-Flag (MS): Eine Risikobewertung muss sich immer auf ein Subjekt (hier: Patient) beziehen.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. ",
                "type":  [
                    {
                        "code": "Reference",
                        "targetProfile":  [
                            "http://hl7.org/fhir/StructureDefinition/Patient"
                        ]
                    }
                ],
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.subject.reference",
                "path": "RiskAssessment.subject.reference",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.encounter",
                "path": "RiskAssessment.encounter",
                "short": "Referenz auf den Abteilungskontakt",
                "comment": "Begründung des Must-Support-Support-Flag (MS): Der Encounter liefert den Kontext zur Risikobeurteilung.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. ",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.encounter.reference",
                "path": "RiskAssessment.encounter.reference",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.occurrence[x]",
                "path": "RiskAssessment.occurrence[x]",
                "slicing": {
                    "discriminator":  [
                        {
                            "type": "type",
                            "path": "$this"
                        }
                    ],
                    "ordered": false,
                    "rules": "open"
                },
                "short": "Zeitpunkt oder Zeitraum der Beurteilung",
                "comment": "Begründung des Must-Support-Support-Flag (MS): Die Angabe des Zeitpunkts oder Zeitraums ist essentiell für die Nachvollziehbarkeit.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. ",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.occurrence[x]:occurrenceDateTime",
                "path": "RiskAssessment.occurrence[x]",
                "sliceName": "occurrenceDateTime",
                "comment": "Begründung des Must-Support-Support-Flag (MS): Die Angabe des Zeitpunkts ist essentiell für die Nachvollziehbarkeit.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. ",
                "min": 0,
                "max": "1",
                "type":  [
                    {
                        "code": "dateTime"
                    }
                ],
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.occurrence[x]:occurrencePeriod",
                "path": "RiskAssessment.occurrence[x]",
                "sliceName": "occurrencePeriod",
                "comment": "Begründung des Must-Support-Support-Flag (MS): Die Angabe des Zeitraums ist essentiell für die Nachvollziehbarkeit.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. ",
                "min": 0,
                "max": "1",
                "type":  [
                    {
                        "code": "Period"
                    }
                ],
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.condition",
                "path": "RiskAssessment.condition",
                "short": "Bezugsdiagnose (Referenz)",
                "comment": "Begründung des Must-Support-Support-Flag (MS): Die Bezugsdiagnose ist eine relevante Hintergrundinformation.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. ",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.condition.reference",
                "path": "RiskAssessment.condition.reference",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.reasonCode",
                "path": "RiskAssessment.reasonCode",
                "short": "Grund der Risikobewertung (codiert)",
                "comment": "Begründung des Must-Support-Support-Flag (MS): Die Angabe einer Begründung ist fachlich üblich und angebracht.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. ",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.reasonCode.coding",
                "path": "RiskAssessment.reasonCode.coding",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.reasonCode.coding.system",
                "path": "RiskAssessment.reasonCode.coding.system",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.reasonCode.coding.code",
                "path": "RiskAssessment.reasonCode.coding.code",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.reasonCode.coding.display",
                "path": "RiskAssessment.reasonCode.coding.display",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.reasonCode.text",
                "path": "RiskAssessment.reasonCode.text",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.reasonReference",
                "path": "RiskAssessment.reasonReference",
                "short": "Grund der Risikobewertung (Referenz)",
                "comment": "Begründung des Must-Support-Support-Flag (MS): Die Angabe einer Begründung ist fachlich üblich und angebracht.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. ",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.reasonReference.reference",
                "path": "RiskAssessment.reasonReference.reference",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.basis",
                "path": "RiskAssessment.basis",
                "short": "Entscheidungsgrundlagen der Risikobewertung (Referenz)",
                "comment": "Begründung des Must-Support-Support-Flag (MS): Die Referenz zu den Grundlagen der Beurteilung ermöglicht die Transparenz der Beurteilungs-Findung.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. ",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.basis.reference",
                "path": "RiskAssessment.basis.reference",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.prediction",
                "path": "RiskAssessment.prediction",
                "comment": "Begründung des Must-Support-Support-Flag (MS): Angaben über Outcome und Größe des Risikos.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. ",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.prediction.outcome",
                "path": "RiskAssessment.prediction.outcome",
                "short": "Mögliches Outcome für den Patienten",
                "comment": "Begründung des Must-Support-Support-Flag (MS): Das erwartete Outcome ist eine Kerninformation der Risikobeurteilung.\n\n    Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. ",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.prediction.outcome.coding",
                "path": "RiskAssessment.prediction.outcome.coding",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.prediction.outcome.coding.system",
                "path": "RiskAssessment.prediction.outcome.coding.system",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.prediction.outcome.coding.code",
                "path": "RiskAssessment.prediction.outcome.coding.code",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.prediction.outcome.coding.display",
                "path": "RiskAssessment.prediction.outcome.coding.display",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.prediction.outcome.text",
                "path": "RiskAssessment.prediction.outcome.text",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.prediction.qualitativeRisk",
                "path": "RiskAssessment.prediction.qualitativeRisk",
                "short": "Risikowahrscheinlichkeit (qualitativ, codiert)",
                "comment": "Begründung des Must-Support-Support-Flag (MS): Die Risikowahrscheinlichkeit ist eine Kerninformation der Risikobeurteilung.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. ",
                "mustSupport": true,
                "binding": {
                    "strength": "extensible",
                    "valueSet": "http://hl7.org/fhir/ValueSet/risk-probability"
                }
            },
            {
                "id": "RiskAssessment.prediction.qualitativeRisk.coding",
                "path": "RiskAssessment.prediction.qualitativeRisk.coding",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.prediction.qualitativeRisk.coding.system",
                "path": "RiskAssessment.prediction.qualitativeRisk.coding.system",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.prediction.qualitativeRisk.coding.code",
                "path": "RiskAssessment.prediction.qualitativeRisk.coding.code",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.prediction.qualitativeRisk.coding.display",
                "path": "RiskAssessment.prediction.qualitativeRisk.coding.display",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.prediction.qualitativeRisk.text",
                "path": "RiskAssessment.prediction.qualitativeRisk.text",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.mitigation",
                "path": "RiskAssessment.mitigation",
                "short": "Hinweis zur Risikovermeidung",
                "comment": "Begründung des Must-Support-Support-Flag (MS): Hinweise zur Risikovermeidung sind eine Kerninformation der Risikobeurteilung.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. ",
                "mustSupport": true
            },
            {
                "id": "RiskAssessment.note",
                "path": "RiskAssessment.note",
                "short": "Anmerkung zur Risikobewertung",
                "comment": "Begründung des Must-Support-Support-Flag (MS): freitextliche Anmerkungen sind fachlich üblich und gewünscht.\n\n  Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt. ",
                "mustSupport": true
            }
        ]
    }
}

ISiK AMTS-Bewertung

Constraints/Invarianten

Terminology-Bindings

Element	Staerke	ValueSet
RiskAssessment.prediction.qualitativeRisk	extensible	http://hl7.org/fhir/ValueSet/risk-probability

Anmerkungen zu Must-Support-Feldern

Feldname	Kurzbeschreibung	Hinweise
RiskAssessment.extension	akzeptiertes (in Kauf genommenes) Risiko	Begründung des Must-Support: Die Möglichkeit der freitextlichen Dokumentation dieser Daten wurde von der Fachseite (AG) gewünscht. Hinweis: Hier kann die Begründung und ggf. erforderliche Begleitmaßnahmen für ein in Kauf genommenes Risiko dokumentiert werden.
RiskAssessment.extension:acceptedRisk
RiskAssessment.status		Begründung des Must-Support-Support-Flag (MS): Die Angabe des Status ist im Standard vorgeschrieben. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt.
RiskAssessment.code	Art der Risikobeurteilung	Begründung des Must-Support-Support-Flag (MS): Es handelt sich um eine Grundinformation zur Risikobewertung. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt.
RiskAssessment.code.coding
RiskAssessment.code.coding.system
RiskAssessment.code.coding.code
RiskAssessment.code.coding.display
RiskAssessment.code.text
RiskAssessment.subject	Referenz auf den Patienten	Begründung des Must-Support-Support-Flag (MS): Eine Risikobewertung muss sich immer auf ein Subjekt (hier: Patient) beziehen. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt.
RiskAssessment.subject.reference
RiskAssessment.encounter	Referenz auf den Abteilungskontakt	Begründung des Must-Support-Support-Flag (MS): Der Encounter liefert den Kontext zur Risikobeurteilung. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt.
RiskAssessment.encounter.reference
RiskAssessment.occurrence[x]	Zeitpunkt oder Zeitraum der Beurteilung	Begründung des Must-Support-Support-Flag (MS): Die Angabe des Zeitpunkts oder Zeitraums ist essentiell für die Nachvollziehbarkeit. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt.
RiskAssessment.occurrence[x]:occurrenceDateTime		Begründung des Must-Support-Support-Flag (MS): Die Angabe des Zeitpunkts ist essentiell für die Nachvollziehbarkeit. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt.
RiskAssessment.occurrence[x]:occurrencePeriod		Begründung des Must-Support-Support-Flag (MS): Die Angabe des Zeitraums ist essentiell für die Nachvollziehbarkeit. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt.
RiskAssessment.condition	Bezugsdiagnose (Referenz)	Begründung des Must-Support-Support-Flag (MS): Die Bezugsdiagnose ist eine relevante Hintergrundinformation. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt.
RiskAssessment.condition.reference
RiskAssessment.reasonCode	Grund der Risikobewertung (codiert)	Begründung des Must-Support-Support-Flag (MS): Die Angabe einer Begründung ist fachlich üblich und angebracht. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt.
RiskAssessment.reasonCode.coding
RiskAssessment.reasonCode.coding.system
RiskAssessment.reasonCode.coding.code
RiskAssessment.reasonCode.coding.display
RiskAssessment.reasonCode.text
RiskAssessment.reasonReference	Grund der Risikobewertung (Referenz)	Begründung des Must-Support-Support-Flag (MS): Die Angabe einer Begründung ist fachlich üblich und angebracht. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt.
RiskAssessment.reasonReference.reference
RiskAssessment.basis	Entscheidungsgrundlagen der Risikobewertung (Referenz)	Begründung des Must-Support-Support-Flag (MS): Die Referenz zu den Grundlagen der Beurteilung ermöglicht die Transparenz der Beurteilungs-Findung. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt.
RiskAssessment.basis.reference
RiskAssessment.prediction		Begründung des Must-Support-Support-Flag (MS): Angaben über Outcome und Größe des Risikos. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt.
RiskAssessment.prediction.outcome	Mögliches Outcome für den Patienten	Begründung des Must-Support-Support-Flag (MS): Das erwartete Outcome ist eine Kerninformation der Risikobeurteilung. `Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt.`
RiskAssessment.prediction.outcome.coding
RiskAssessment.prediction.outcome.coding.system
RiskAssessment.prediction.outcome.coding.code
RiskAssessment.prediction.outcome.coding.display
RiskAssessment.prediction.outcome.text
RiskAssessment.prediction.qualitativeRisk	Risikowahrscheinlichkeit (qualitativ, codiert)	Begründung des Must-Support-Support-Flag (MS): Die Risikowahrscheinlichkeit ist eine Kerninformation der Risikobeurteilung. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt.
RiskAssessment.prediction.qualitativeRisk.coding
RiskAssessment.prediction.qualitativeRisk.coding.system
RiskAssessment.prediction.qualitativeRisk.coding.code
RiskAssessment.prediction.qualitativeRisk.coding.display
RiskAssessment.prediction.qualitativeRisk.text
RiskAssessment.mitigation	Hinweis zur Risikovermeidung	Begründung des Must-Support-Support-Flag (MS): Hinweise zur Risikovermeidung sind eine Kerninformation der Risikobeurteilung. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt.
RiskAssessment.note	Anmerkung zur Risikobewertung	Begründung des Must-Support-Support-Flag (MS): freitextliche Anmerkungen sind fachlich üblich und gewünscht. Hintergrund: Das MS wurde im Rahmen der Ausarbeitung zur Stufe 4 des ISiK Moduls Medikation hinzugefügt und mit den Stakeholdern abgestimmt.

Interaktionen

(Reverse-)Include

Command 'pagelink' could not render: Page not found.

Interaktionen

Für die Ressource Medication MÜSSEN die REST-Interaktionen "READ", "CREATE" und "UPDATE" implementiert werden.

Folgende Suchparameter sind für das Bestätigungsverfahren relevant, auch in Kombination:

Der Suchparameter "_id" MUSS unterstützt werden:

Beispiele:

GET [base]/RiskAssessment?_id=103270

Anwendungshinweise: Weitere Informationen zur Suche nach "_id" finden sich in der FHIR-Basisspezifikation - Abschnitt "Parameters for all resources".
Der verkettete Suchparameter "condition.code" MUSS unterstützt werden:

Beispiele:

GET [base]/RiskAssessment?condition.code=http://fhir.de/CodeSystem/bfarm/icd-10-gm|F71.0

Anwendungshinweise: Weitere Informationen zur Suche nach Token-type Parametern finden sich in der FHIR-Basisspezifikation - Abschnitt "Token Search".

Weitere Informationen zur Suche nach verketteten Parametern finden sich in der FHIR-Basisspezifikation - Abschnitt "Chained Parameters".
Der Suchparameter "date" MUSS unterstützt werden:

Beispiele:

GET [base]/RiskAssessment.date=2022-03-21

Anwendungshinweise: Weitere Informationen zur Suche nach Date-type Parametern finden sich in der FHIR-Basisspezifikation - Abschnitt "Date".
Der Suchparameter "encounter" MUSS unterstützt werden:

Beispiele:

GET [base]/RiskAssessment?encounter=Encounter/123

Anwendungshinweise: Weitere Informationen zur Suche nach Reference-type Parametern finden sich in der FHIR-Basisspezifikation - Abschnitt "Reference Search".
Der verkettete Suchparameter "encounter.identifier" MUSS unterstützt werden:

Beispiele:

GET [base]/RiskAssessment?encounter.identifier=http://mein-krankenhaus.example/fhir/sid/fallnummern|7567867

GET [base]/RiskAssessment?encounter.identifier=7567867

Anwendungshinweise: Weitere Informationen zur Suche nach Reference-type Parametern finden sich in der FHIR-Basisspezifikation - Abschnitt "Reference Search".

Weitere Informationen zur Suche nach verketteten Parametern finden sich in der FHIR-Basisspezifikation - Abschnitt "Chained Parameters".
Der Suchparameter "patient" MUSS unterstützt werden:

Beispiele:

GET [base]/RiskAssessment?patient=Patient/123

Anwendungshinweise: Weitere Informationen zur Suche nach Reference-type Parametern finden sich in der FHIR-Basisspezifikation - Abschnitt "Reference Search".
Der verkettete Suchparameter "patient.identifier" MUSS unterstützt werden:

Beispiele:

GET [base]/RiskAssessment?patient.identifier=http://mein-krankenhaus.example/fhir/sid/patienten|1032702

GET [base]/RiskAssessment?patient.identifier=1032702

Anwendungshinweise: Weitere Informationen zur Suche nach Token-type Parametern finden sich in der FHIR-Basisspezifikation - Abschnitt "Token Search".

Weitere Informationen zur Suche nach verketteten Parametern finden sich in der FHIR-Basisspezifikation - Abschnitt "Chained Parameters".
Der Suchparameter "risk" MUSS unterstützt werden:

Beispiele:

GET [base]/RiskAssessment.risk=http://terminology.hl7.org/CodeSystem/risk-probability|high

Anwendungshinweise: Weitere Informationen zur Suche nach Token-type Parametern finden sich in der FHIR-Basisspezifikation - Abschnitt "Token Search".

Beispiele

RiskAssessment

id : ExampleISiKAMTSBewertung1

meta

profile : https://gematik.de/fhir/isik/StructureDefinition/ISiKAMTSBewertung

status : final

code

text : AMTS Risikobewertung

subject

reference : Patient/PatientinMusterfrau

encounter

reference : Encounter/Fachabteilungskontakt

occurrence : 2024-02-20T13:14:32+01:00

condition

reference : Condition/BehandlungsDiagnoseFreitext

reasonReference

reference : DocumentReference/AnamnesebogenScan123456

basis

reference : Observation/Koerpergewicht7777

prediction

outcome

text : Niereninsuffizienz

qualitativeRisk

coding

system : http://terminology.hl7.org/CodeSystem/risk-probability

code : high

mitigation : Substitution der Stalevo Dauermedikation

note

text : Abklärung in der Frühbesprechung am 21.02.2024

<RiskAssessment xmlns="http://hl7.org/fhir">
    <id value="ExampleISiKAMTSBewertung1" />
    <meta>
        <profile value="https://gematik.de/fhir/isik/StructureDefinition/ISiKAMTSBewertung" />
    </meta>
    <status value="final" />
    <code>
        <text value="AMTS Risikobewertung" />
    </code>
    <subject>
        <reference value="Patient/PatientinMusterfrau" />
    </subject>
    <encounter>
        <reference value="Encounter/Fachabteilungskontakt" />
    </encounter>
    <occurrenceDateTime value="2024-02-20T13:14:32+01:00" />
    <condition>
        <reference value="Condition/BehandlungsDiagnoseFreitext" />
    </condition>
    <reasonReference>
        <reference value="DocumentReference/AnamnesebogenScan123456" />
    </reasonReference>
    <basis>
        <reference value="Observation/Koerpergewicht7777" />
    </basis>
    <prediction>
        <outcome>
            <text value="Niereninsuffizienz" />
        </outcome>
        <qualitativeRisk>
            <coding>
                <system value="http://terminology.hl7.org/CodeSystem/risk-probability" />
                <code value="high" />
            </coding>
        </qualitativeRisk>
    </prediction>
    <mitigation value="Substitution der Stalevo Dauermedikation" />
    <note>
        <text value="Abkl&#228;rung in der Fr&#252;hbesprechung am 21.02.2024" />
    </note>
</RiskAssessment>

{
    "resourceType": "RiskAssessment",
    "id": "ExampleISiKAMTSBewertung1",
    "meta": {
        "profile":  [
            "https://gematik.de/fhir/isik/StructureDefinition/ISiKAMTSBewertung"
        ]
    },
    "status": "final",
    "code": {
        "text": "AMTS Risikobewertung"
    },
    "subject": {
        "reference": "Patient/PatientinMusterfrau"
    },
    "encounter": {
        "reference": "Encounter/Fachabteilungskontakt"
    },
    "occurrenceDateTime": "02/20/2024 12:14:32",
    "condition": {
        "reference": "Condition/BehandlungsDiagnoseFreitext"
    },
    "reasonReference":  [
        {
            "reference": "DocumentReference/AnamnesebogenScan123456"
        }
    ],
    "basis":  [
        {
            "reference": "Observation/Koerpergewicht7777"
        }
    ],
    "prediction":  [
        {
            "outcome": {
                "text": "Niereninsuffizienz"
            },
            "qualitativeRisk": {
                "coding":  [
                    {
                        "code": "high",
                        "system": "http://terminology.hl7.org/CodeSystem/risk-probability"
                    }
                ]
            }
        }
    ],
    "mitigation": "Substitution der Stalevo Dauermedikation",
    "note":  [
        {
            "text": "Abklärung in der Frühbesprechung am 21.02.2024"
        }
    ]
}

RiskAssessment for Patient/PatientinMusterfrau