Indicates that a medication product is to be or has been dispensed for a named person/patient. This includes a description of the medication product (supply) provided and the instructions for administering the medication. The medication dispense is the result of a pharmacy system responding to a medication order.

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.

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

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

CDA R2 header specification templateId (specification package version)

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

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

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

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

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

CDA R2 header specification templateId (specification package version).

Need to refer to a particular code in the system.

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

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

An Extension

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them

Lääkitysasiakirjan versiointinumero.

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

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

Lääkitysasiakirjan versiointinumero.

The creation time of a document

Information about whether the drug was dispensed with dose dispensing.

Information on whether the medicine has been fully dispensed.

Identifiers of medicine continuum: The identifier of the medicine in use and part identifier of medicine continuum.

An Extension

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them

Automatically produced by an information system, a technical OID identifier that combines the entries of the same prescribed drug.

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

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

Automatically produced by an information system, a technical OID identifier that combines the entries of the same prescribed drug.

The purpose of this identifier.

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

Identifies the purpose for this identifier, if known .

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

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

Identifier.system is always case sensitive.

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

Automatically produced by an information system, a technical OID identifier that combines the entries of the same prescribed drug.

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

Automatically produced by the information system. Separates the different continuums of the same drug (that is, simultaneously used prescriptions for the same drug). As a rule, the drug used has only one medicine continuum at a time (only one active prescription). When it is necessary to have two or more active prescriptions for a drug, for example, when the patient uses two different strengths of the drug, the medicine continuums are separated by the part identifier of the medicine continuum.

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

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

Automatically produced by the information system. Separates the different continuums of the same drug (that is, simultaneously used prescriptions for the same drug). As a rule, the drug used has only one medicine continuum at a time (only one active prescription). When it is necessary to have two or more active prescriptions for a drug, for example, when the patient uses two different strengths of the drug, the medicine continuums are separated by the part identifier of the medicine continuum.

Information maintained by the Kanta Prescription Centre on what is the latest prescription in the medicine continuum. The value True says that the prescription is the latest prescription in the continuum.

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

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

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

Further clarification of the drug dispensation to Kela.

Dispensation price in euros.

Number of dispensed drug packages.

Different packages have been dispensed in the dispense.

Toimituksen kauppanimen muutospäivä, kauppanimen muutospäivänä toimitetun valmisteen kauppanimi, kauppanimen muutospäivänä toimitetun valmisteen VNR-numero, kauppanimen muutospäivänä toimitetun valmisteen vahvuus, kauppanimen muutospäivänä toimitetun valmisteen lääkemuoto.

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

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

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

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

Identifiers associated with this Medication Dispense that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server.

This is a business identifier, not a resource identifier.

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them

Unique identifier of the dispensation document. For example, the identifier may be an identifier that identifies a particular version of the dispensation document.

This is a business identifier, not a resource identifier.

The purpose of this identifier.

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

Identifies the purpose for this identifier, if known .

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

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

Note. Here a separate namespace was created, another option would have been to put urn:ietf:rfc:3986 as system and encode the identifiers with the type element (own codes for id and setId).

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

An unique OID identifier of the dispensation document

Note. Here a separate namespace was created, another option would have been to put urn:ietf:rfc:3986 as system and encode the identifiers with the type element (own codes for id and setId). (If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986.)

Identifier of the original drug dispensation document that connects different versions of the document.

This is a business identifier, not a resource identifier.

The purpose of this identifier.

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

Identifies the purpose for this identifier, if known .

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

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

Note. Here a separate namespace was created, another option would have been to put urn:ietf:rfc:3986 as system and encode the identifiers with the type element (own codes for id and setId). (If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986.)

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

Identifier of the original drug dispensation document that connects different versions of the document.

Note. Here a separate namespace was created, another option would have been to put urn:ietf:rfc:3986 as system and encode the identifiers with the type element (own codes for id and setId). (If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986.)

The procedure that trigger the dispense.

A standard value is used: Completed

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

A coded concept specifying the state of the dispense event.

This information tells whether information from the drug dispensation or its different versions (i.e., correction of dispensation) is returned. This is represented as a code from the Kanta code system 'Sähköinen lääkemääräys - Reseptisanoman tyyppi', depending on the dispensation document: 10 = Prescription dispensation or 12 = Correction of prescription dispensation

A code describing why a dispense was not performed.

Kanta code system 'Sähköinen lääkemääräys - Reseptisanoman tyyppi'.

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

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

OID of the Kanta code system 'Sähköinen lääkemääräys - Reseptisanoman tyyppi'.

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

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

Code of the Kanta code system 'Sähköinen lääkemääräys - Reseptisanoman tyyppi': 10 = Prescription dispensation 11 = Invalidation of prescription dispensation 12 = Correction of prescription dispensation

Need to refer to a particular code in the system.

Indicates the type of medication dispense (for example, where the medication is expected to be consumed or administered (i.e. inpatient or outpatient)).

The category can be used to include where the medication is expected to be consumed or other types of dispenses. Invariants can be used to bind to different value sets when profiling to bind.

A code describing where the dispensed medication is expected to be consumed or administered.

Identifies the medication being administered. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code that identifies the medication from a known list of medications.

If only a code is specified, then it needs to be a code for a specific product. If more information is required, then the use of the medication resource is recommended. For example, if you require form or lot number, then you must reference the Medication resource.

A link to a resource representing the person or the group to whom the medication will be given.

SubstanceAdministration->subject->Patient.

The encounter or episode of care that establishes the context for this event.

Additional information that supports the medication being dispensed.

The principal physical location where the dispense was performed.

Reference to the unique identifier of the MedicationRequest resource to which the MedicationDispense resource is linked (MedicationRequest.id).

Maps to basedOn in Event logical model.

An Extension

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them

setId, the original identifier of the prescription document, with which the drug dispensation is associated

Unique identifier of the MedicationRequest resource to which the MedicationDispense resource is linked

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

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

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

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

The purpose of this identifier.

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

Identifies the purpose for this identifier, if known .

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

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

Identifier.system is always case sensitive.

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

The unique OID identifier of the prescription.

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

Indicates the type of dispensing event that is performed. For example, Trial Fill, Completion of Trial, Partial Fill, Emergency Fill, Samples, etc.

Indicates the type of dispensing event that is performed. For example, Trial Fill, Completion of Trial, Partial Fill, Emergency Fill, Samples, etc.

The amount of the drug provided by the prescription at that dispensation. The amount of the drug supplied as a numerical value (e.g., 100) and the unit (e.g., tab).

An Extension

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them

The dispensed amount of drug as a calculation formula.

The dispensed amount of the drug as text (e.g., 1 suppository + 20 g ointment). The unit is also recorded in the text.

Kyseisen lääkemääräyksen kaikilla toimituskerroilla yhteensä toimitettu lääkkeen määrä. Jos kyseessä on lääkemääräyksen ensimmäinen toimitus, arvo on sama kuin kyseisellä toimituskerralla toimitettu määrä. Voi palautua yhdellä vaihtoehtoisella tavalla: lääkkeen kokonaismäärä ja määrän yksikkö, lääkkeen määrä laskukaavana tai lääkkeen määrä tekstinä.

The amount of the drug remaining (to be dispensed) in the prescription. Can be returned in the following ways: the total amount of the drug and the unit, the amount of the drug as a calculation formula or the amount of the drug as text. This information is not returned by the basic medication list search or in the search for discontinued medications if the dispensation is not related to the latest prescription in the continuum.

The dispensed amount of the medicine as a numerical value (e.g., 100).

The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).

Precision is handled implicitly in almost all cases of measurement.

Not allowed to be used in this context

How the Quantity should be understood and represented.

Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology.

The dispensed amount of drug as a numerical value, unit (e.g., tab).

There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms.

The amount of medication expressed as a timing amount.

The time when the dispensed product was packaged and reviewed.

Dispensation date of the drug.

Identification of the facility/location where the medication was shipped to, as part of the dispense event.

Identifies the person who picked up the medication. This will usually be a patient or their caregiver, but some cases exist where it can be a healthcare professional.

Extra information about the dispense that could not be conveyed in the other attributes.

Pharmacy's note on drug dispensing. The name of the pharmacist who prepared the drug for dispensing is recorded in the field dedicated for notes. This information is mandatory when, in addition to receiving the prescription and dispensing the drug, another pharmacist has been required for the preparation of the drug for dispensing.

Indicates whether or not substitution was made as part of the dispense. In some cases, substitution will be expected but does not happen, in other cases substitution is not expected but does happen. This block explains what substitution did or did not happen and why. If nothing is specified, substitution was not done.

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

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

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

Information about whether the drug has been substituted in dispensing.

Information of a forbidden drug change or the reason for dispensing a drug outside the reference pricing system. According to the Kanta code system 'Sähköinen lääkemääräys - Lääkevaihtokielto tai lääkevaihdon syy'. Also, provide the additional information for dispensing a drug outside the reference pricing system.

A coded concept describing the reason that a different medication should (or should not) be substituted from what was prescribed.

Information of a forbidden drug change or the reason for dispensing a drug outside the reference pricing system. According to the Kanta code system 'Sähköinen lääkemääräys - Lääkevaihtokielto tai lääkevaihdon syy'.

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

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

OID of the Kanta code system 'Sähköinen lääkemääräys - Lääkevaihtokielto tai lääkevaihdon syy'.

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

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

Code of the Kanta code system 'Sähköinen lääkemääräys - Lääkevaihtokielto tai lääkevaihdon syy'.

Need to refer to a particular code in the system.

Further clarification on the dispensing of a drug outside of the reference pricing system. Always returned if the reason for the dispensation outside of the reference pricing system is M (other reason).

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

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

Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. drug-drug interaction, duplicate therapy, dosage alert etc.

This element can include a detected issue that has been identified either by a decision support system or by a clinician and may include information on the steps that were taken to address the issue.

A summary of the events of interest that have occurred, such as when the dispense was verified.

This might not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.).

CDA R2 header specification templateId (specification package version)

CDA R2 header specification templateId (specification package version).

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them

Identifiers of medicine continuum: The identifier of the medicine in use and part identifier of medicine continuum.

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them

Dispensation price in euros.

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them

Unique identifier of the dispensation document. For example, the identifier may be an identifier that identifies a particular version of the dispensation document.

Note. Here a separate namespace was created, another option would have been to put urn:ietf:rfc:3986 as system and encode the identifiers with the type element (own codes for id and setId).

An unique OID identifier of the dispensation document

Note. Here a separate namespace was created, another option would have been to put urn:ietf:rfc:3986 as system and encode the identifiers with the type element (own codes for id and setId). (If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986.)

Identifier of the original drug dispensation document that connects different versions of the document.

Note. Here a separate namespace was created, another option would have been to put urn:ietf:rfc:3986 as system and encode the identifiers with the type element (own codes for id and setId). (If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986.)

Identifier of the original drug dispensation document that connects different versions of the document.

Note. Here a separate namespace was created, another option would have been to put urn:ietf:rfc:3986 as system and encode the identifiers with the type element (own codes for id and setId). (If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986.)

A standard value is used: Completed

This information tells whether information from the drug dispensation or its different versions (i.e., correction of dispensation) is returned. This is represented as a code from the Kanta code system 'Sähköinen lääkemääräys - Reseptisanoman tyyppi', depending on the dispensation document: 10 = Prescription dispensation or 12 = Correction of prescription dispensation

Kanta code system 'Sähköinen lääkemääräys - Reseptisanoman tyyppi'.

OID of the Kanta code system 'Sähköinen lääkemääräys - Reseptisanoman tyyppi'.

Code of the Kanta code system 'Sähköinen lääkemääräys - Reseptisanoman tyyppi': 10 = Prescription dispensation 11 = Invalidation of prescription dispensation 12 = Correction of prescription dispensation

Reference to the unique identifier of the MedicationRequest resource to which the MedicationDispense resource is linked (MedicationRequest.id).

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them

setId, the original identifier of the prescription document, with which the drug dispensation is associated

Unique identifier of the MedicationRequest resource to which the MedicationDispense resource is linked

The unique OID identifier of the prescription.

The amount of the drug provided by the prescription at that dispensation. The amount of the drug supplied as a numerical value (e.g., 100) and the unit (e.g., tab).

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them

The dispensed amount of drug as a calculation formula.

The amount of the drug remaining (to be dispensed) in the prescription. Can be returned in the following ways: the total amount of the drug and the unit, the amount of the drug as a calculation formula or the amount of the drug as text. This information is not returned by the basic medication list search or in the search for discontinued medications if the dispensation is not related to the latest prescription in the continuum.

The dispensed amount of the medicine as a numerical value (e.g., 100).

The dispensed amount of drug as a numerical value, unit (e.g., tab).

Dispensation date of the drug.

Pharmacy's note on drug dispensing. The name of the pharmacist who prepared the drug for dispensing is recorded in the field dedicated for notes. This information is mandatory when, in addition to receiving the prescription and dispensing the drug, another pharmacist has been required for the preparation of the drug for dispensing.

The intended use of the drug written during dispensation if the intended use written on the prescription is unclear.

Dispensation instruction printed on a dispensation information sticker if the dosage instructions written on the prescription are unclear. If the dosage information is given in structured format, the dosage instructions provided for the prescription by the system may not be changed.

Information about whether the drug has been substituted in dispensing.

Information of a forbidden drug change or the reason for dispensing a drug outside the reference pricing system. According to the Kanta code system 'Sähköinen lääkemääräys - Lääkevaihtokielto tai lääkevaihdon syy'. Also, provide the additional information for dispensing a drug outside the reference pricing system.

Information of a forbidden drug change or the reason for dispensing a drug outside the reference pricing system. According to the Kanta code system 'Sähköinen lääkemääräys - Lääkevaihtokielto tai lääkevaihdon syy'.

OID of the Kanta code system 'Sähköinen lääkemääräys - Lääkevaihtokielto tai lääkevaihdon syy'.

Code of the Kanta code system 'Sähköinen lääkemääräys - Lääkevaihtokielto tai lääkevaihdon syy'.

Further clarification on the dispensing of a drug outside of the reference pricing system. Always returned if the reason for the dispensation outside of the reference pricing system is M (other reason).

Indicates that a medication product is to be or has been dispensed for a named person/patient. This includes a description of the medication product (supply) provided and the instructions for administering the medication. The medication dispense is the result of a pharmacy system responding to a medication order.

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

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

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

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

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

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

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

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

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

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

A uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc.

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

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

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

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

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

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

Security Labels from the Healthcare Privacy and Security Classification System.

CDA R2 header specification templateId (specification package version)

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

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

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

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

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

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

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

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

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

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

CDA R2 header specification templateId (specification package version).

Need to refer to a particular code in the system.