PrescribeIT™ Specification and Guide Version 2.0 Revision F

Provides instructions specific to how the first fill of a prescription should be processed (if different from other fills)

Conformance Rule: If this is supported within the EMR as a discrete data element, this must be populated. (e.g. this could map to 'Must be filled within').

First fill is only populated if required; if not populated, the general dispenseRequest instructions apply to all fills. You only specify an initial fill quantity if you have refills.

unique id for the element within a resource (for internal references).

An Extension

Indicates the date by which the initial fill of the prescription must be made. If not dispensed on or before this date, no subsequent fills are permitted.

Conformance Rules: If this is supported within the EMR as a discrete data element, this must be populated. (e.g. this could map to 'Must be filled within') Conformance Rule First fill is only populated if required; if not populated, the general dispenseRequest instructions apply to all fills

unique id for the element within a resource (for internal references).

May be used to represent additional information that is not part of the basic definition of the element. In order 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.

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.

Fixed value: expiry

Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

Indicates the quantity that should be provided as part of the first dispense against the prescription.

Allows a more limited quantity to be dispensed on the initial dispense to confirm the medication is tolerated and providing the desired effect before incurring the costs of a full fill.

Conformance Rule: If this is supported within the EMR as a discrete data element, this must be populated. If days supply is NOT present, this MUST be populated.

Conformance Rule: First fill is only populated if required; if not populated, the FILL_QUANTITY applies to all

unique id for the element within a resource (for internal references).

May be used to represent additional information that is not part of the basic definition of the element. In order 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.

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.

Fixed value: quantity

Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

Conformance Rule: If this is supported within the EMR as a discrete data element, this must be populated. If FIRSTFILLQUANTITY is not populated, this MUST be included.

Conformance Rule: First fill is only populated if required; if not populated, the DAYS_SUPPLY applies to all fills

Indicates the number of days supply of the medication that should be provided as part of the first dispense against the prescription.

Allows a more limited quantity to be dispensed on the initial dispense to confirm the medication is tolerated and providing the desired effect before incurring the costs of a full fill.

Conformance Rules: If this is supported within the EMR as a discrete data element, this must be populated. If FIRSTFILLQUANTITY is not populated, this MUST be included.

Conformance Rule: First fill is only populated if required; if not populated, the DAYS_SUPPLY applies to all fills. Code must be 'd' and system must be 'http://unitsofmeasure.org'.

unique id for the element within a resource (for internal references).

May be used to represent additional information that is not part of the basic definition of the element. In order 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.

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.

Fixed value: expectedSupplyDuration

There SHALL be a code if there is a value and it SHALL be an expression of time. If system is present, it SHALL be UCUM.

The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.

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

Fixed value: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-first-fill

Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).