Logical model for medication prescription. A prescription contains one or more prescription items.

Business identifier(s) for the prescription

No change

Question: would we want to add basic Practicioner model?

No change

Time of issuing (signing) the prescription by health care practicioner

No change

Question: would we want to add basic Patient model?

No change (Patient model will be common for all use cases)

Category or categories of prescription. For example type of reimbursement, or type of prescription (e.g. hospital, private, etc).

Added.

Effective date of the prescription. The prescription is not dispensable before this date. In most cases this information repeats issueDate

Added. Often the same as IssueDate (A 1.2.2) or Start of therapy (A 1.5.6)

The validity period end date. The prescription is not dispensable after this date.

No change (A.1.5.8)

The recorder of the prescription/draft in the information system

Added. Not relevant for crossborder.

Time of authoring the prescription/draft in the information system

Added. Not relevant for crossborder.

Status of the prescription, this should not be status of treatment

Added.

Reason for the current status of prescription, for example the reason why the prescription was made invalid

Added.

Textual reason for the current status of prescription

Added.

Additional information or comments

Presription line for one medication. In many countries, only one line is allowed. In case multiple medications are allowed, all lines need to be authored together.

Identifier for a single line on prescription, if exists. In case of single-line prescription, this identifier is typically the same as prescription identifier.

Prescribed product, branded, generic, virtual, extemporal, etc

Medication model changed - described within that model

Reason for the prescription (typically diagnosis, or a procedure)

No change (A.1.5.10)

shall we have a preferred binding here?

Reason for the prescription in textual form. This might not be allowed by some implementations.

No change (code not required) A1.5.10

Period over which the medication is to be taken (in case of multiple dosaging schemes, this would be the overall period of all dosages.)

Starting Date of Therapy A1.5.6. End date added.

Overall quantity of prescribed product (e.g number of packages or number of tablets).

No change

Dosaging and administration instructions

Dosage model significantly changed towards more granularity. A.1.5.3-A.1.5.7

Additional instructions about preparation or dispense

Added.

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

No change but subelements added. A 1.5.11

Whether substitution is allowed or not.

The type of substitution that is allowed.

Reason for the substitution requirement

Status of the prescription, this should not be status of treatment

Added.

Reason for the current status of prescription, for example the reason why the prescription was made invalid

Added.

Textual reason for the current status of prescription

Added.

Additional information or comments

Added. Still missing A.1.5.9 Repeats and A.1.5.2 Quantity of prescribed product

Logical model for medication prescription. A prescription contains one or more prescription items.

Business identifier(s) for the prescription

No change

Question: would we want to add basic Practicioner model?

No change

Time of issuing (signing) the prescription by health care practicioner

No change

Question: would we want to add basic Patient model?

No change (Patient model will be common for all use cases)

Category or categories of prescription. For example type of reimbursement, or type of prescription (e.g. hospital, private, etc).

Added.

Effective date of the prescription. The prescription is not dispensable before this date. In most cases this information repeats issueDate

Added. Often the same as IssueDate (A 1.2.2) or Start of therapy (A 1.5.6)

The validity period end date. The prescription is not dispensable after this date.

No change (A.1.5.8)

The recorder of the prescription/draft in the information system

Added. Not relevant for crossborder.

Time of authoring the prescription/draft in the information system

Added. Not relevant for crossborder.

Status of the prescription, this should not be status of treatment

Added.

Reason for the current status of prescription, for example the reason why the prescription was made invalid

Added.

Textual reason for the current status of prescription

Added.

Additional information or comments

Presription line for one medication. In many countries, only one line is allowed. In case multiple medications are allowed, all lines need to be authored together.

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.

Identifier for a single line on prescription, if exists. In case of single-line prescription, this identifier is typically the same as prescription identifier.

Prescribed product, branded, generic, virtual, extemporal, etc

Medication model changed - described within that model

Reason for the prescription (typically diagnosis, or a procedure)

No change (A.1.5.10)

shall we have a preferred binding here?

Reason for the prescription in textual form. This might not be allowed by some implementations.

No change (code not required) A1.5.10

Period over which the medication is to be taken (in case of multiple dosaging schemes, this would be the overall period of all dosages.)

Starting Date of Therapy A1.5.6. End date added.

Overall quantity of prescribed product (e.g number of packages or number of tablets).

No change

Dosaging and administration instructions

Dosage model significantly changed towards more granularity. A.1.5.3-A.1.5.7

Additional instructions about preparation or dispense

Added.

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

No change but subelements added. A 1.5.11

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.

Whether substitution is allowed or not.

The type of substitution that is allowed.

Reason for the substitution requirement

Status of the prescription, this should not be status of treatment

Added.

Reason for the current status of prescription, for example the reason why the prescription was made invalid

Added.

Textual reason for the current status of prescription

Added.

Additional information or comments

Added. Still missing A.1.5.9 Repeats and A.1.5.2 Quantity of prescribed product

Logical model for medication prescription. A prescription contains one or more prescription items.

Business identifier(s) for the prescription

No change

Question: would we want to add basic Practicioner model?

No change

Time of issuing (signing) the prescription by health care practicioner

No change

Question: would we want to add basic Patient model?

No change (Patient model will be common for all use cases)

Category or categories of prescription. For example type of reimbursement, or type of prescription (e.g. hospital, private, etc).

Added.

Effective date of the prescription. The prescription is not dispensable before this date. In most cases this information repeats issueDate

Added. Often the same as IssueDate (A 1.2.2) or Start of therapy (A 1.5.6)

The validity period end date. The prescription is not dispensable after this date.

No change (A.1.5.8)

The recorder of the prescription/draft in the information system

Added. Not relevant for crossborder.

Time of authoring the prescription/draft in the information system

Added. Not relevant for crossborder.

Status of the prescription, this should not be status of treatment

Added.

Reason for the current status of prescription, for example the reason why the prescription was made invalid

Added.

Textual reason for the current status of prescription

Added.

Additional information or comments

Presription line for one medication. In many countries, only one line is allowed. In case multiple medications are allowed, all lines need to be authored together.

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.

Identifier for a single line on prescription, if exists. In case of single-line prescription, this identifier is typically the same as prescription identifier.

Prescribed product, branded, generic, virtual, extemporal, etc

Medication model changed - described within that model

Reason for the prescription (typically diagnosis, or a procedure)

No change (A.1.5.10)

shall we have a preferred binding here?

Reason for the prescription in textual form. This might not be allowed by some implementations.

No change (code not required) A1.5.10

Period over which the medication is to be taken (in case of multiple dosaging schemes, this would be the overall period of all dosages.)

Starting Date of Therapy A1.5.6. End date added.

Overall quantity of prescribed product (e.g number of packages or number of tablets).

No change

Dosaging and administration instructions

Dosage model significantly changed towards more granularity. A.1.5.3-A.1.5.7

Additional instructions about preparation or dispense

Added.

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

No change but subelements added. A 1.5.11

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.

Whether substitution is allowed or not.

The type of substitution that is allowed.

Reason for the substitution requirement

Status of the prescription, this should not be status of treatment

Added.

Reason for the current status of prescription, for example the reason why the prescription was made invalid

Added.

Textual reason for the current status of prescription

Added.

Additional information or comments

Added. Still missing A.1.5.9 Repeats and A.1.5.2 Quantity of prescribed product