Logical model for representing one line/medication in medication overview.

Unique business identifier(s) for the medication treatment line

Medicinal product for which the treatment line refers to. Identification or sufficient description of the product.

Status of the record, not the status of the treatment.

Business version of the treatment line

Timestamp of the version of the treatment line

The state of the actual treatment - taking, not taken...

The reason - coded - for the treatment status - i.e. adverse events, refusal...

The reason - free text - for the treatment status - i.e. adverse events, refusal...

The period of time the treatment is in effect

Verification of medication line. The overview is verified as a whole, but each line is equipped with the information. The actual functional meaning and impact of this validation depends on the implementation.

HCP (or device, if authorized) verifying the treatments/overview

The date and time when this medication treatment line was verified

Whatever category for the treatment line. Categorisation of treatment lines is implementation-specific.

Reference or identifier of the group of lines that belong together

Reason why the product has been prescribed to the patient, or why the patient claims to be taking it

Textual explanation for why the medication has been prescribed or why the patient is taking it. This might not be allowed by some implementations.

Intended Use of the medication - prophylaxis, therapy...

Instructions about requested or actual administration of the product. This is repeatable to support complex or concurrent dosage instructions. e.g. take 1 per day for 3 weeks; 2x PRN

Additional instructions about preparation or dispense

Comment on the individual line

Author of the comment (Pharmacist, doctor, social carer, patient, device, related person)

time of comment

content of the comment

Whether and which type of substitution is allowed for this medication treatment line

The type of substitution that is allowed.

Coded reason for the substitution requirement

Textual reason for the substitution requirement

Metadata about reporting/authoring of the treatment line

Person entering the statement by initiating a treatment or documenting a statement by a patient or another professional. The recorder may be different from the author.

Time of creation of the treatment line

The treatment line has been documented according to patient's statement

HCP who takes the clinical decision for the medication treatment line. If an author is not present, the responsibility of the medication line is with the recorder.

The time the clinical decision was made by the responsibleAuthor. Normally, the same time as recording time when it's the same person.

Any data object that this treatment line is derived from

Prescriptions that have been the source for creating the unverified treatment line

Medication-related statements from patients, pharmacists, or other HCPs, that are the source for creating the unverified treatment line

Related dispensations that are not necessarily related to existing prescriptions/requests/statements.

Related administrations that are not necessarily related to existing prescriptions/requests/statements.

Other related sources of information - CarePlan, Immunizations, Documents (e.g. Discharge letters)...

Logical model for representing one line/medication in medication overview.

Unique business identifier(s) for the medication treatment line

Medicinal product for which the treatment line refers to. Identification or sufficient description of the product.

Status of the record, not the status of the treatment.

Business version of the treatment line

Timestamp of the version of the treatment line

The state of the actual treatment - taking, not taken...

The reason - coded - for the treatment status - i.e. adverse events, refusal...

The reason - free text - for the treatment status - i.e. adverse events, refusal...

The period of time the treatment is in effect

Verification of medication line. The overview is verified as a whole, but each line is equipped with the information. The actual functional meaning and impact of this validation depends on the implementation.

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 managable, 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.

HCP (or device, if authorized) verifying the treatments/overview

The date and time when this medication treatment line was verified

Whatever category for the treatment line. Categorisation of treatment lines is implementation-specific.

Reference or identifier of the group of lines that belong together

Reason why the product has been prescribed to the patient, or why the patient claims to be taking it

Textual explanation for why the medication has been prescribed or why the patient is taking it. This might not be allowed by some implementations.

Intended Use of the medication - prophylaxis, therapy...

Instructions about requested or actual administration of the product. This is repeatable to support complex or concurrent dosage instructions. e.g. take 1 per day for 3 weeks; 2x PRN

Additional instructions about preparation or dispense

Comment on the individual line

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 managable, 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.

Author of the comment (Pharmacist, doctor, social carer, patient, device, related person)

time of comment

content of the comment

Whether and which type of substitution is allowed for this medication treatment line

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 managable, 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.

The type of substitution that is allowed.

Coded reason for the substitution requirement

Textual reason for the substitution requirement

Metadata about reporting/authoring of the treatment line

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 managable, 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.

Person entering the statement by initiating a treatment or documenting a statement by a patient or another professional. The recorder may be different from the author.

Time of creation of the treatment line

The treatment line has been documented according to patient's statement

HCP who takes the clinical decision for the medication treatment line. If an author is not present, the responsibility of the medication line is with the recorder.

The time the clinical decision was made by the responsibleAuthor. Normally, the same time as recording time when it's the same person.

Any data object that this treatment line is derived from

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 managable, 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.

Prescriptions that have been the source for creating the unverified treatment line

Medication-related statements from patients, pharmacists, or other HCPs, that are the source for creating the unverified treatment line

Related dispensations that are not necessarily related to existing prescriptions/requests/statements.

Related administrations that are not necessarily related to existing prescriptions/requests/statements.

Other related sources of information - CarePlan, Immunizations, Documents (e.g. Discharge letters)...

Logical model for representing one line/medication in medication overview.

Unique business identifier(s) for the medication treatment line

Medicinal product for which the treatment line refers to. Identification or sufficient description of the product.

Status of the record, not the status of the treatment.

Business version of the treatment line

Timestamp of the version of the treatment line

The state of the actual treatment - taking, not taken...

The reason - coded - for the treatment status - i.e. adverse events, refusal...

The reason - free text - for the treatment status - i.e. adverse events, refusal...

The period of time the treatment is in effect

Verification of medication line. The overview is verified as a whole, but each line is equipped with the information. The actual functional meaning and impact of this validation depends on the implementation.

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 managable, 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.

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 managable, 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.

HCP (or device, if authorized) verifying the treatments/overview

The date and time when this medication treatment line was verified

Whatever category for the treatment line. Categorisation of treatment lines is implementation-specific.

Reference or identifier of the group of lines that belong together

Reason why the product has been prescribed to the patient, or why the patient claims to be taking it

Textual explanation for why the medication has been prescribed or why the patient is taking it. This might not be allowed by some implementations.

Intended Use of the medication - prophylaxis, therapy...

Instructions about requested or actual administration of the product. This is repeatable to support complex or concurrent dosage instructions. e.g. take 1 per day for 3 weeks; 2x PRN

Additional instructions about preparation or dispense

Comment on the individual line

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 managable, 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.

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 managable, 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.

Author of the comment (Pharmacist, doctor, social carer, patient, device, related person)

time of comment

content of the comment

Whether and which type of substitution is allowed for this medication treatment line

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 managable, 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.

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 managable, 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.

The type of substitution that is allowed.

Coded reason for the substitution requirement

Textual reason for the substitution requirement

Metadata about reporting/authoring of the treatment line

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 managable, 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.

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 managable, 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.

Person entering the statement by initiating a treatment or documenting a statement by a patient or another professional. The recorder may be different from the author.

Time of creation of the treatment line

The treatment line has been documented according to patient's statement

HCP who takes the clinical decision for the medication treatment line. If an author is not present, the responsibility of the medication line is with the recorder.

The time the clinical decision was made by the responsibleAuthor. Normally, the same time as recording time when it's the same person.

Any data object that this treatment line is derived from

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 managable, 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.

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 managable, 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.

Prescriptions that have been the source for creating the unverified treatment line

Medication-related statements from patients, pharmacists, or other HCPs, that are the source for creating the unverified treatment line

Related dispensations that are not necessarily related to existing prescriptions/requests/statements.

Related administrations that are not necessarily related to existing prescriptions/requests/statements.

Other related sources of information - CarePlan, Immunizations, Documents (e.g. Discharge letters)...