PrescribeIT® Specification and Guide Version 5.0


v5.0 of this specification has been superseded by v5.3. v5.3 is compatible but adds additional features for Quebec.

The version (Bundle.meta.tag:version) that is sent in the message will remain PrescribeIT5.0

 

Definitions for the ext-medicationorder-dispense-first-fill Extension

1. Extension
Definition

Provides specific instructions as to how the first fill of a prescription should be dispensed.

Usage Note: This is typically provided when the prescriber wants the patient to try a medication for short period of time in order to determine if the patient can tolerate the medication without issues or to determine whether the medication is effective prior to the patient receiving a larger supply that would be wasted if not tolerated or not effective. The first fill information should only be specified in the case of additional refills, where the quantity or expected supply duration of the refills differs from the first fill. If the first fill information is not provided, it means that the general dispenseRequest instructions related to the quantity or expected supply duration apply to all fills.

Control0..1
Comments

Conformance Rule: If entry of the first fill information is supported within the EMR as discrete information, this must be populated. For the first fill instructions to be meaningful, the first fill quantity or the first fill expected supply duration must be provided. Both can be provided if available but at minimum one of these must be provided.

2. Extension.id
Definition

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

Control0..1
Typeid
3. Extension.extension
Definition

An Extension

Control0..*
TypeExtension
Must Supporttrue
SlicingThis element introduces a set of slices on Extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
  • value @ url
4. Extension.extension:date
SliceNamedate
Definition

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.

Control0..1
TypeExtension
Must Supporttrue
Comments

Conformance Rules: If the first fill expiry date concept is supported within the EMR as a discrete data element, this must be populated.

5. Extension.extension:date.id
Definition

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

Control0..1
Typeid
6. Extension.extension:date.extension
Definition

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.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

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.

7. Extension.extension:date.url
Definition

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

Control1..1
Typeuri
Must Supporttrue
Comments

Fixed value: expiry

Fixed Valueexpiry
8. Extension.extension:date.value[x]
Definition

First fill expiry date value.

Control1..1
Typedate
[x] NoteSee Choice of Data Types for further information about how to use [x]
Must Supporttrue
Comments

Conformance Rule: Must be a full date value, time is not required unless it can be specified in EMR by the user.

9. Extension.extension:quantity
SliceNamequantity
Definition

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

Control0..1
TypeExtension
Must Supporttrue
Requirements

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.

Comments

Conformance Rule: The first fill quantity or the first fill expected supply duration must be provided. Both can be provided if available but at minimum one of these needs to be provided.

10. Extension.extension:quantity.id
Definition

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

Control0..1
Typeid
11. Extension.extension:quantity.extension
Definition

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.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

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.

12. Extension.extension:quantity.url
Definition

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

Control1..1
Typeuri
Must Supporttrue
Comments

Fixed value: quantity

Fixed Valuequantity
13. Extension.extension:quantity.value[x]
Definition

A measured or counted amount of a medication expressed as a value and human-readable string with optional coded units expressed in a local coding system

Control1..1
BindingThe codes SHALL be taken from PrescribedQuantityUnit (20210308); other codes may be used where these codes are not suitable
TypeQuantity(PrescribeIT® Drug Quantity)
[x] NoteSee Choice of Data Types for further information about how to use [x]
Must Supporttrue
Comments

Usage Note: Quantity is used throughout the messages. It may be a drug form (e.g. TAB) an administrable drug (e.g. PUFF) form or a unit of measure (e.g. mg).

Max Length0
InvariantsDefined on this element
qty-3: If a code for the unit is present, the system SHALL also be present (: code.empty() or system.exists())
sqty-1: The comparator is not used on a SimpleQuantity (: comparator.empty())
14. Extension.extension:expectedSupplyDuration
SliceNameexpectedSupplyDuration
Definition

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

Control0..1
TypeExtension
Must Supporttrue
Requirements

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.

Comments

Conformance Rules: The first fill quantity or the first fill expected supply duration must be provided. Both can be provided if available but at minimum one of these needs to be provided.

Conformance Rule: When providing the first fill expected supply duration it must be expressed as a duration of time in days'.

15. Extension.extension:expectedSupplyDuration.id
Definition

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

Control0..1
Typeid
16. Extension.extension:expectedSupplyDuration.extension
Definition

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.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

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.

17. Extension.extension:expectedSupplyDuration.url
Definition

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

Control1..1
Typeuri
Must Supporttrue
Comments

Fixed value: expectedSupplyDuration

Fixed ValueexpectedSupplyDuration
18. Extension.extension:expectedSupplyDuration.value[x]
Definition

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.

Control1..1
TypeQuantity(Duration)
[x] NoteSee Choice of Data Types for further information about how to use [x]
Must Supporttrue
Comments

Conformance Rule: The duration must be expressed as a ‘day(s)’ value and must be coded in the following way; code must be 'd' and system must be 'http://unitsofmeasure.org'.

Max Length0
InvariantsDefined on this element
drt-1: 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. (: (code.exists() or value.empty()) and (system.empty() or system = %ucum))
qty-3: If a code for the unit is present, the system SHALL also be present (: code.empty() or system.exists())
19. Extension.url
Definition

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

Control1..1
Typeuri
Must Supporttrue
Comments

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

Fixed Valuehttp://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-first-fill
20. Extension.value[x]
Definition

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

Control0..0
TypeChoice of: boolean, integer, decimal, base64Binary, instant, string, uri, date, dateTime, time, code, oid, id, unsignedInt, positiveInt, markdown, Annotation, Attachment, Identifier, CodeableConcept, Coding, Quantity, Range, Period, Ratio, SampledData, Signature, HumanName, Address, ContactPoint, Timing, Reference, Meta
[x] NoteSee Choice of Data Types for further information about how to use [x]