The weight of a patient under 12 years of age Sic! notation The reason for the Sic! notation Additional information on the Sic! notation Dosage instructions only as text

An Extension

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

Information of the patient's weight and weight unit. The information is mandatory for patients under 12 years of age. It may also be recorded for older patients when it is necessary for prescribing the 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.

Information of the patient's weight and weight unit. The information is mandatory for patients under 12 years of age. It may also be recorded for older patients when it is necessary for prescribing the drug.

Weight of a patient under 12 years of age, e.g., 35.

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.

How the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues; e.g. if the comparator is "<" , then the real value is < stated value.

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.

Unit of weight of a patient under 12 years of age, e.g., kg.

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

Information as to whether the prescription is intentionally prescribed in the written manner and should not be questioned (in Latin 'sic erat scriptum', in English 'as it had been written'). Primarily the 'Sic!' notation is used to indicate that the dosage of the prescribed drug stated in the prescription differs from normal dosage of the drug, but it may also be used if the drug is prescribed in a way that differs from standard treatment practices.

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.

Information as to whether the prescription is intentionally prescribed in the written manner and should not be questioned (in Latin 'sic erat scriptum', in English 'as it had been written'). Primarily the 'Sic!' notation is used to indicate that the dosage of the prescribed drug stated in the prescription differs from normal dosage of the drug, but it may also be used if the drug is prescribed in a way that differs from standard treatment practices.

Classified justification for using the Sic! notation According to the Kanta code system 'THL - Sic!-merkinnän syy' Repeated information, there may be several reasons for justifying the use of the Sic! notation.

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.

Classified justification for using the sic! According to the Kanta code system 'THL - Sic!-merkinnän syy' Repeated information, there may be several reasons for justifying the use of the Sic! notation.

OID of the Kanta code system 'THL - Sic!-merkinnän 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 'THL - Sic!-merkinnän syy'

Need to refer to a particular code in the system.

If necessary, freely formatted additional information for using the Sic! notation on the prescription.

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.

If necessary, freely formatted additional information for using the Sic! notation on the prescription.

Information as to whether the dosage instructions for the prescribed medicine are recorded in free text by the author and structured dosage information has not been stored. If the value is False, the text-based dosage instructions are automatically formed on the basis of structured dosage information.

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.

Information as to whether the dosage instructions for the prescribed medicine are recorded in free text by the author and structured dosage information has not been stored. If the value is False, the text-based dosage instructions are automatically formed on the basis of structured dosage information.

Information on whether the prescriber allows a nurse or pharmacist to make changes to the dosage instructions on the prescription, in accordance with the treatment plan and section 5c of the Act on Electronic Prescriptions, by issuing a new prescription.

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.

Information on whether the prescriber allows a nurse or pharmacist to make changes to the dosage instructions on the prescription, in accordance with the treatment plan and section 5c of the Act on Electronic Prescriptions, by issuing a new prescription.

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

The weight of a patient under 12 years of age Sic! notation The reason for the Sic! notation Additional information on the Sic! notation Dosage instructions only as text

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

Information of the patient's weight and weight unit. The information is mandatory for patients under 12 years of age. It may also be recorded for older patients when it is necessary for prescribing the drug.

Information of the patient's weight and weight unit. The information is mandatory for patients under 12 years of age. It may also be recorded for older patients when it is necessary for prescribing the drug.

Weight of a patient under 12 years of age, e.g., 35.

Unit of weight of a patient under 12 years of age, e.g., kg.

Information as to whether the prescription is intentionally prescribed in the written manner and should not be questioned (in Latin 'sic erat scriptum', in English 'as it had been written'). Primarily the 'Sic!' notation is used to indicate that the dosage of the prescribed drug stated in the prescription differs from normal dosage of the drug, but it may also be used if the drug is prescribed in a way that differs from standard treatment practices.

Information as to whether the prescription is intentionally prescribed in the written manner and should not be questioned (in Latin 'sic erat scriptum', in English 'as it had been written'). Primarily the 'Sic!' notation is used to indicate that the dosage of the prescribed drug stated in the prescription differs from normal dosage of the drug, but it may also be used if the drug is prescribed in a way that differs from standard treatment practices.

Classified justification for using the Sic! notation According to the Kanta code system 'THL - Sic!-merkinnän syy' Repeated information, there may be several reasons for justifying the use of the Sic! notation.

Classified justification for using the sic! According to the Kanta code system 'THL - Sic!-merkinnän syy' Repeated information, there may be several reasons for justifying the use of the Sic! notation.

OID of the Kanta code system 'THL - Sic!-merkinnän syy'

Code of the Kanta code system 'THL - Sic!-merkinnän syy'

If necessary, freely formatted additional information for using the Sic! notation on the prescription.

If necessary, freely formatted additional information for using the Sic! notation on the prescription.

Information as to whether the dosage instructions for the prescribed medicine are recorded in free text by the author and structured dosage information has not been stored. If the value is False, the text-based dosage instructions are automatically formed on the basis of structured dosage information.

Information as to whether the dosage instructions for the prescribed medicine are recorded in free text by the author and structured dosage information has not been stored. If the value is False, the text-based dosage instructions are automatically formed on the basis of structured dosage information.

Information on whether the prescriber allows a nurse or pharmacist to make changes to the dosage instructions on the prescription, in accordance with the treatment plan and section 5c of the Act on Electronic Prescriptions, by issuing a new prescription.

Information on whether the prescriber allows a nurse or pharmacist to make changes to the dosage instructions on the prescription, in accordance with the treatment plan and section 5c of the Act on Electronic Prescriptions, by issuing a new prescription.

The weight of a patient under 12 years of age Sic! notation The reason for the Sic! notation Additional information on the Sic! notation Dosage instructions only as text

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

An Extension

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

Information of the patient's weight and weight unit. The information is mandatory for patients under 12 years of age. It may also be recorded for older patients when it is necessary for prescribing the drug.

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.

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.

Information of the patient's weight and weight unit. The information is mandatory for patients under 12 years of age. It may also be recorded for older patients when it is necessary for prescribing the drug.

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.

Weight of a patient under 12 years of age, e.g., 35.

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.

How the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues; e.g. if the comparator is "<" , then the real value is < stated value.

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.

Unit of weight of a patient under 12 years of age, e.g., kg.

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

The identification of the system that provides the coded form of the unit.

Need to know the system that defines the coded form of the unit.

A computer processable form of the unit in some unit representation system.

The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.

Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest.

Information as to whether the prescription is intentionally prescribed in the written manner and should not be questioned (in Latin 'sic erat scriptum', in English 'as it had been written'). Primarily the 'Sic!' notation is used to indicate that the dosage of the prescribed drug stated in the prescription differs from normal dosage of the drug, but it may also be used if the drug is prescribed in a way that differs from standard treatment practices.

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.

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.

Information as to whether the prescription is intentionally prescribed in the written manner and should not be questioned (in Latin 'sic erat scriptum', in English 'as it had been written'). Primarily the 'Sic!' notation is used to indicate that the dosage of the prescribed drug stated in the prescription differs from normal dosage of the drug, but it may also be used if the drug is prescribed in a way that differs from standard treatment practices.

Classified justification for using the Sic! notation According to the Kanta code system 'THL - Sic!-merkinnän syy' Repeated information, there may be several reasons for justifying the use of the Sic! notation.

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.

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.

Classified justification for using the sic! According to the Kanta code system 'THL - Sic!-merkinnän syy' Repeated information, there may be several reasons for justifying the use of the Sic! notation.

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.

OID of the Kanta code system 'THL - Sic!-merkinnän 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.

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.

Code of the Kanta code system 'THL - Sic!-merkinnän syy'

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

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

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

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

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

If necessary, freely formatted additional information for using the Sic! notation on the prescription.

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.

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.

If necessary, freely formatted additional information for using the Sic! notation on the prescription.

Information as to whether the dosage instructions for the prescribed medicine are recorded in free text by the author and structured dosage information has not been stored. If the value is False, the text-based dosage instructions are automatically formed on the basis of structured dosage information.

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.

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.

Information as to whether the dosage instructions for the prescribed medicine are recorded in free text by the author and structured dosage information has not been stored. If the value is False, the text-based dosage instructions are automatically formed on the basis of structured dosage information.

Information on whether the prescriber allows a nurse or pharmacist to make changes to the dosage instructions on the prescription, in accordance with the treatment plan and section 5c of the Act on Electronic Prescriptions, by issuing a new prescription.

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.

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.

Information on whether the prescriber allows a nurse or pharmacist to make changes to the dosage instructions on the prescription, in accordance with the treatment plan and section 5c of the Act on Electronic Prescriptions, by issuing a new prescription.

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