PrescribeIT™ Specification and Guide Version 2.0 Revision F

 

3.54 StructureDefinition: PrescribeIT Prescription

The official URL for this profile is: 

http://prescribeit.ca/fhir/StructureDefinition/profile-medicationorder

3.54.1 Scope and Usage

This profile is used in the following tasks:

An Excel spreadsheet providing guidance on how to populate dosage instructions can be found here.

3.54.2 Formal Views of Profile Content

Download Excel representation

Description of Profiles, Differentials, Snapshots and how the different presentations work.

>

This structure is derived from MedicationOrder

NameCard.TypeConstraints and Usage
.  MedicationOrder 0..*Definition:
An order for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationOrder" rather than "MedicationPrescription" to generalize the use across inpatient and outpatient settings as well as for care plans, etc.


Comments:
For Task e110-m - New RX Fill Request, this conveys the details of a single medication order.

For Task p160-m - RX Renewal Create Request, this conveys the details of a single medication order for which the renewal is being requested.

For Task e120-m - Renewal RX Fill Request, this conveys the medication order for which a fill is being requested.

..  id 1..1idDefinition:
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.


Comments:
Usage Note: This will usually be a GUID and is assigned by the sending application.

..  contained 1..*ResourceDefinition:
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.


Comments:
Conformance Rule: This will be used to contain the Medication resource. No other resources should be 'contained'.

..  extension 0..*ExtensionSlice: Unordered, Open by value:url
Definition:
An Extension

..  extension
     (category) 		0..1Medication Order CategoryDefinition:
Sub-categorizes medication prescriptions into drugs, devices, compounds, etc. May be used to apply sub-type-specific constraints


Comments:
Conformance Rule: If no appropriate code exists, provide details using the 'text' component.

..  extension
     (renderedDosageInstruction) 		1..1Medication Rendered Dosage InstructionDefinition:
A free form textual specification generated from the input specifications as created by the provider.This is made up of either an 'Ad-hoc instruction' or 'Textual rendition of the structured dosage lines', plus route, dosage unit, and other pertinent administration information specified by the provider.


Comments:
Usage Note: This is intended to provide all dosage instructions to the Pharmacist in a clear human-readable format. This field will be displayed to the Pharmacist upon receipt of the prescription. Note: This must be as clear as possible and must include all instructions because the EMR may not provide individual/structured dosage instructions. When the Prescription cannot be delivered electronically, the rendered dosage instruction will be printed on the fax and will be the only source of dosage information.

It is recognized that very complex instructions may be conveyed as text only (not as structured data). Example: take 500 mg twice a day at breakfast and at lunch AND 250 mg once a day at bedtime - THEN (new dosage line)). If the EMR submits structured dosage instructions, this must be consistent with the textual instructions provided here. The PMS may ignore the structured frequency, or override it to align with the textual instructions.

Example: the EMR may enter frequency (multiplier of the dose) in their system like this (2 qam and 3 qhs ), in the structured frequency. The textual instructions could say Take 2 tablets in the morning and 3 at bedtime.

Conformance Rule: The rendered dosage instruction MUST contain ALL dosage instructions. This includes ALL child elements of dosage instruction, such as dosage quantity, dosage unit, frequency, etc) in human readable form and must be able to stand on its own. This field will include all of the information contained in the structured dosage as well as patient instructions (eg take with food, starting one day before dental appointment), assembled into one field and formatted as human-readable. Coded values codes should not be used (e.g. 'days' should be used instead of 'd', the code of PO as 'oral' )

Conformance Rule: MUST allow all printable characters and carriage return/line feeds. 5000 character max.

Conformance Rule: If an EMR has discrete field for Pharmacy Notes (Dispenser Instructions), they should not be included here. If EMR's have both concepts combined into one field, they can both be included here.

..  extension
     (protocol) 		0..10Medication Order ProtocolDefinition:
Identifies the Protocol, Order set, Guideline or other definition that guided the creation of this prescription


Comments:
Conformance Rule: If EMR's support as a discrete data element, this should be populated; else it will be part of the Dispenser Instructions (MedicationOrder.note.text). If it is present, it must be displayed to the Pharmacist. Usage Note: To date, the only known use case is for LU codes. If sent as an identifier, no guidance yet exists on appropriate values for the 'system' component.

..  extension
     (treatmentType) 		0..1Medication Order Treatment TypeDefinition:
Identifies whether this drug is for acute or chronic use


Comments:
Conformance Rule: Must be populated if known

..  extension
     (supportingInformation) 		0..*Medication Order Supporting InformationDefinition:
Additional information that relevant to the order. E.g. observations, allergies, etc.


Comments:
Cardinality must be 0..1 for Shared Health List-Allergies and 0..2 for Shared Health Pharmacy-related Observation (i.e. 1 for height and 1 for weight).

Conformance Rule: All known patient allergies must be included in the Medication Order.

..  extension
     (detectedIssue) 		0..*Request-related Detected IssuesDefinition:
A set of managed and relevant detected issues that should be transmitted along with a prescription or order to provide context during the execution of that order.


Comments:
Usage Note: This is a reference to the resource which is used to convey Managed Detected Issues (DUR)

..  extension
     (coverage) 		0..1Request-related Coverage (NOT SUPPORTED)Definition:
Identifies insurance coverage that may be relevant to fulfilling an order

..  extension
     (pharmacyInstructions) 		0..1Request Dispenser InstructionsDefinition:
Provides additional instructions from the prescriber to the pharmacy or other dispenser


Comments:
Usage Note: To convey explicit instructions to the Pharmacist/dispenser related to this medication order.

Usage Note: If the PMS solution is unable to display the entire instructions, then it is expected that the current solution has a fail-over process and will create a printout of the prescription.

Conformance Rule: PMS solution must be able to print out the entire prescription with ALL dispensing instructions included on the printout. Minimum data elements can be based on the eFax model

Conformance Rule: When 'compliance pack' is indicated on the prescription within the EMR, populate the pharmacist instruction/dispenser instructions with 'COMPLIANCE PACK REQUESTED'

Usage Note: In the case where the prescriber indicates the concept of ‘do not adapt’ (meaning that the pharmacist should not alter the prescription based on the patient's weight as an example), this direction to the pharmacist should be conveyed in human language in this field.

Conformance Rule: If a prescriber wishes to indicate that there is no substitution it must be included as part of the pharmacy instructions.

Conformance Rule: LU Codes must be clearly conveyed as part of the Pharmacists Instructions. If vendors are programmitically mapping into this field, they should use a prefix of LU Code before the identifier.

..  extension
     (over25dur) 		0..1Medication Order - Over 25 DURDefinition:
Indicates that the total number of managed DURs associated with the prescription exceeds the reporting limit of 25


Comments:
Conformance Rule: Set value = true when there are more than 25 warnings returned in the EMR DUR system

..  extension
     (monitoreddrug) 		0..1Medication Order - Monitored DrugDefinition:
Allows prescribers to indicate that the prescription is for a 'Monitored Drug' (e.g. compound) value in the prescription message to the pharmacies


Comments:
Conformance Rule: The prescriber should have the ability to set this flag when the medication is a compound. The absence of this extension means (i.e. value=”false”) that this is not a monitored substance.

Usage Note: Provinces may require prescribers to enter this value when a compound contains a monitored substance (e.g. narcotic) to support Prescription Drug Monitoring Programs (e.g. the Alberta Triplicate Prescription Program).

..  extension
     (norenewals) 		0..1Medication Order - No Prescription RenewalsDefinition:
Indicates that the prescriber will not support renewals for this prescription


Comments:
Conformance Rule: The PMS should present a warning to the dispenser if they create a renewal request for a prescription that has this flag set to indicate 'no renewals'. The PMS should allow the renewal to be submitted along with an explanation as there may be exceptional circumstances.

..  identifier 1..3Shared Health IdentifierSlice: Unordered, Open by value:type
Definition:
A technical identifier - identifies some entity uniquely and unambiguously.


Comments:
These are the identifiers assigned by the EMR and, in some cases, by the DIS.

..  identifier
     (emr-id) 		1..1PrescribeIT™ Prescriber Prescription IdentifierDefinition:
A technical identifier - identifies some entity uniquely and unambiguously.


Comments:
In the context of a net new prescription (e110, e120, e162, or e163), this identifier is generated by the EMR. The prescription number should be sent in the value element and should be an OID of the form [vendor root].[application instance node].2 expressed as a urn (e.g. urn:oid:2.16.840.1.113883.3.368.1234.2).

In the context of a Renewal Request (p160), the prescription number for the prescription that is being requested to be renewed should be used for this element. In most cases, this will be a value that was originally generated by an EMR. However, in some cases (such as the renewal of a paper/fax prescription), there will be no EMR generated prescription number, and in this case, the PMS should generate a number.

In the context of an Rx Response - Denied (e161), or an Rx Response - Under Review (e164), this element should be populated with the MedicationOrder.identifier(emr-id) provided in the Renewal Request (p160).

In the context of a Cancel Rx Fill Request (e140), this element should be populated with the same Rx that was included in the original net new prescription message (e110, e120, e162, or e163).

...  type 1..1Shared Health CodeableConcept CodeBinding: Identifier Type Codes (extensible)
Required Pattern: {"coding":[{"system":"http://hl7.org/fhir/identifier-type","code":"PLAC"}]}
Definition:
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.


Comments:
....  coding 1..*CodingSlice: Unordered, Open by value:system, value:code
Definition:
A reference to a code defined by a terminology system.


Comments:
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labelled as UserSelected = true.

.....  system 1..1uriDefinition:
The identification of the code system that defines the meaning of the symbol in the code.


Comments:
.....  code 1..1codeDefinition:
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

....  coding
         (placer) 		1..*CodingDefinition:
A reference to a code defined by a terminology system.


Comments:
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labelled as UserSelected = true.

.....  system 1..1uriFixed Value: http://hl7.org/fhir/identifier-type
Definition:
The identification of the code system that defines the meaning of the symbol in the code.


Comments:
Fixed value: http://hl7.org/fhir/identifier-type

.....  code 1..1codeFixed Value: PLAC
Definition:
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).


Comments:
Fixed value: PLAC

...  system 1..1uriExample' General': http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri
Definition:
Establishes the namespace in which set of possible id values is unique.

...  value 1..1string​Example' General': 123456
Definition:
The portion of the identifier typically relevant to the user and which is unique within the context of the system.


Comments:
If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension.

..  identifier
     (dis-id) 		0..2IdentifierDefinition:
External identifier - one that would be used by another non-FHIR system - for example a re-imbursement system might issue its own id for each prescription that is created. This is particularly important where FHIR only provides part of an entire workflow process where records have to be tracked through an entire system.


Comments:
Usage Note: When an e110-m, e120-m, e162-m or e163-m passes through the PrescribeIT™ Switch in a jurisdiction which has a Drug Information System (DIS), the PrescribeIT™ Switch will add the DIS's identifier to the MedicationOrder. PMS are to use this identifier to record the dispense event against the correct DIS Prescription identifier. This element will not be present in the message transmitted from the EMR to the PrescribeIT™ Switch.

There should only be 2 identifiers in the case of a border town such as Lloydminster where the DIS identifier in both provinces needs to be stored.

...  type 1..1Shared Health CodeableConcept CodeBinding: Identifier Type Codes (extensible)
Required Pattern: {"coding":[{"system":"http://hl7.org/fhir/v2/0203","code":"RRI"}]}
Definition:
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.


Comments:
...  system 0..1uriExample' General': http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri
Definition:
Establishes the namespace in which set of possible id values is unique.

...  value 1..1string​Example' General': 123456
Definition:
The portion of the identifier typically relevant to the user and which is unique within the context of the system.


Comments:
If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension.

..  status 1..1codeBinding: MedicationOrderStatus (required)
Fixed Value: active
Definition:
A code specifying the state of the order. Generally this will be active or completed state.


Comments:
Fixed value: active

..  medicationReference 1..1Reference(PrescribeIT Medication) {c}Definition:
A reference from one resource to another.


Comments:
Usage Note: this is populated with the reference to the Medication resource pertaining to this Medication Order. It will point to the 'contained' Medication resource. E.g. <reference value='#med'/>

..  patient 1..1Reference(Shared Health Patient) {b}Definition:
A reference from one resource to another.


Comments:
Usage Note: This must point to the patient associated with the message.

..  dateWritten 0..1dateTimecreated-full: Must be at least a full date. i.e. yyyy-mm-dd
Definition:
The date (and perhaps time) when the prescription was written.


Comments:
Conformance Rule: Must be either equal to or earlier then the MedicationOrder.dispenseRequest.valididityPeriod.start element.

Must be a full date and time with timezone (i.e. yyyy-mm-dd-HH:mm:ss.SSS-ZZZZZ).

..  prescriber 1..1Reference(Shared Health Practitioner) {b}Definition:
A reference from one resource to another.


Comments:
Conformance Rule: When requesting that a prescription be filled or responding to a renewal request, this SHALL be the practitioner initiating the message.

..  reasonCode 0..5Shared Health CodeableConcept Required Text with optional code​Binding: PrescriptionIndicationForUse (extensible)
Definition:
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.


Comments:
Conformance Rule: In the case where the prescriber wants to send an Indication for Use that is not included in the value set the prescriber must be able to send a text value without a code.

...  text 1..1stringMax Length: 2500
Definition:
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.


Comments:
Usage Note: When conveying the reason, this must be populated

..  note 0..1AnnotationMax Length: 2500
Definition:
Extra information about the prescription that could not be conveyed by the other attributes.

...  text 1..1stringDefinition:
The text of the annotation.


Comments:
Usage Note: This is used as an additional pharmacy note that is unrelated to the dispensing instructions. Eg. Do not fill immediately, Patient is coming in on July 12th for Booster shot.

Conformance Rule: PMS Vendors MUST display this to the pharmacist as it may contain important information. There could be Patient Instructions in here, inadvertently due to current prescribing behaviours.

..  dosageInstruction 0..*BackboneElementDefinition:
Indicates how the medication is to be used by the patient.


Comments:
Conformance Rule: For EMRs that can support structured dosage instruction, this element must be populated when the prescriber specifies any of structured dosage information. Anything that is populated as part of the structured dosage information must also be part of the RENDERED_DOSAGE_INSTRUCTION element.

Usage Note: An Excel spreadsheet providing guidance on how to populate dosage instructions can be found under 'Scope and Usage'.

When the dose or rate is intended to change over the entire administration period, e.g. Tapering dose prescriptions, multiple instances of dosage instructions will need to be supplied to convey the different doses/rates. Another common example in institutional settings is 'titration' of an IV medication dose to maintain a specific stated hemodynamic value or range e.g. drug x to be administered to maintain AM (arterial mean) greater than 65.

...  extension 0..*ExtensionSlice: Unordered, Open by value:url
Definition:
An Extension

...  extension
       (sequence) 		1..1Medication Dosage Line SequenceDefinition:
Optional Extensions Element - found in all resources.


Comments:
Conformance Rule: This must match the positional sequence of the dosageInstruction repetition. I.e. The first dosageInstruction repetition must have a 'sequence' value of 1, the second a 'sequence' value of 2, etc.

...  extension
       (instructionRelationship) 		0..1Medication Order Dosage Instruction RelationshipDefinition:
Optional Extensions Element - found in all resources.


Comments:
Conformance Rule: As this will establish the relationship to the previous dosage lines (example: first and second dosage line, the second and third dosage line, etc.) this must be present for all dosage lines except for the FIRST dosage line.

Conformance Rule: ANDs and THENs should not be mixed due to ambiguity of meaning.

...  text 0..1stringDefinition:
Free text dosage instructions can be used for cases where the instructions are too complex to code. The content of this attribute does not include the name or description of the medication. When coded instructions are present, the free text instructions may still be present for display to humans taking or administering the medication. It is expected that the text instructions will always be populated. If the dosage.timing attribute is also populated, then the dosage.text should reflect the same information as the timing.


Comments:
Conformance Rule: When providing multiple dosage lines can be expressed individually. All dosage lines (full text content) must be concatenated into the RENDERED_DOSAGE_INSTRUCTION as PMS will not be forced to support the receipt of individual lines.

Usage Note: This is a string that is typically composed of the route, duration, dose, frequency, per line

Example: Prednisone; variable dosage instruction, or concurrent instructions (1 pill morning and 1 pill before bed) or sequential dosages (1 pill for 2 days, then 2 pills).

...  additionalInstructions 0..1Shared Health CodeableConcept TextBinding: (unbound) (example)
inv-1: Must have coding or text but not both
Definition:
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.


Comments:
Conformance Rule: When providing an additional instruction at the dosage line level (complex), this should be populated when appropriate.

Usage Note: It may be necessary for the EMR to parse instructions such as QHS (take at bedtime), into two data elements DOSAGE_TIMING_FREQUENCY = once a day and 'at bedtime' would be placed into this field.

Usage Note: 'Coding' is not available, so 'Text' is expected to be used

Usage Note: At this time there is no known coding system. Therefore ‘text’ will be used.

....  coding 0..*CodingDefinition:
A reference to a code defined by a terminology system.


Comments:
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labelled as UserSelected = true.

.....  system 1..1uriDefinition:
The identification of the code system that defines the meaning of the symbol in the code.


Comments:
.....  code 1..1codeDefinition:
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

....  text 1..1stringMax Length: 5000
Definition:
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.


Comments:
Very often the text is the same as a displayName of one of the codings.

...  timing 0..1TimingDefinition:
The timing schedule on how the patient is to take the medication. The timing schedules allows many different expressions to be expressed. For example: Every 8 hours, Three times a day, 1/2 an hour before breakfast for 10 days from 17 Oct 2017 to 27 Oct 2017


Comments:
Conformance Rule: For EMRs that can support structured dosage instruction, this must be populated if prescriber specifies any of structured timing information. Anything that is populated as part of the structured timing information must also be part of the RENDERED_DOSAGE_INSTRUCTION.

Usage Note: An Excel spreadsheet providing guidance on how to populate dosage instructions can be found under 'Scope and Usage'.

....  repeat 0..1Elementtim-3: Either frequency or when can exist, not both
tim-1: if there's a duration, there needs to be duration units
tim-2: if there's a period, there needs to be period units
tim-9: If there's an offset, there must be a when
tim-6: If there's a periodMax, there must be a period
tim-8: If there's a countMax, there must be a count
tim-7: If there's a durationMax, there must be a duration
tim-4: duration SHALL be a non-negative value
Definition:
A set of rules that describe when the event should occur.


Comments:
Conformance Rule: If an EMR cannot send discrete elements in all cases for timing.repeat element, this is acceptable as long as RENDERED_DOSAGE_INSTRUCTION captures the timing.

.....  boundsPeriod 0..1PeriodDefinition:
boundsPeriod defines the start and/or end date of the period over which all the periods should take place for a given dosage line. For example, if the prescriber wants to a patient to take one pill daily for 10 days, but the prescriber only wants the patient to start taking the pills one week from now, the start date for bounds period would be 10 days from now (if the script was being written on Feb 1st, 2018, the start date within bounds period would be Feb 10th).

.....  count 0..1integerDefinition:
count defines how many time the dosing activities should be repeated across all periods. For example, if a prescriber wants a patient to take 1 pill morning and night every day for 10 days, the dose is 1 pill, the frequency is 2 per day, the period is one day, and the count is 20 doses (corresponding to 10 days times 2 doses per day).


Comments:
If you have both bounds and count, then this should be understood as within the bounds period, until count times happens.

.....  countMax 0..1integerDefinition:
countMax defines the max number of doses that should be taken across all periods within a dosage line. countMax is only used when the count is expressed as a range of values. For example, if a prescriber wants a patient to take a dose of 2 pills per day for 7-10 days, the dose is 2 pills, the frequency is 1 dose per day, the period is 1 days, the count is 7 doses, and the countMax is 10 doses.

.....  duration 0..1decimalDefinition:
duration defines the amount of time it takes to provide a SINGLE dose of a medication to a patient. For most medications, duration is not relevant. However, one example that uses duration would be the application of a patch. The prescriber may instruct the patient to apply a patch for 10 hours each day for 10 days. In this case, the dose would be 1 patch, the duration would be 10 hours, the period would be 1 day, and the count would be 10 doses.


Comments:
For some events the duration is part of the definition of the event (e.g. IV infusions, where the duration is implicit in the specified quantity and rate). For others, it's part of the timing specification (e.g. exercise).

.....  durationMax 0..1decimalDefinition:
durationMax defines the maximum amount of time CAN/SHOULD take to provide a SINGLE dose of a medication to a patient. durationMax implies the usage of a range of values for the duration. For most medications, duration and durationMax is not relevant. However, one example that uses duration and durationMax would be the application of a patch for a range of time each day. The prescriber may instruct the patient to apply a patch for 10-12 hours each day for 10 days. In this case, the dose would be 1 patch, the duration would be 10 hours, the durationMax would be 12 hours, the period would be 1 day, and the count would be 10 doses.


Comments:
For some events the duration is part of the definition of the event (e.g. IV infusions, where the duration is implicit in the specified quantity and rate). For others, it's part of the timing specification (e.g. exercise).

.....  durationUnit 0..1codeBinding: UnitsOfTime (required)
Definition:
The units of time for the duration, in UCUM units.


Comments:
Codes are from http://unitsofmeasure.org (h | d | wk | etc.)

.....  frequency 0..1integerDefinition:
frequency defines the number of times to apply a single dose of a medication within a particular period. For example, the prescriber may instruct the patient to take 1 tablet 3 times per day for 10 days. In this cases, the dose would be 1 tablet, the frequency would be 3 times, the period would be 1 day, and the count would be 30 doses.

.....  frequencyMax 0..1integerDefinition:
frequencyMax defines the maximum number of times to apply a single dose of a medication within a particular period. Using frequencyMax implies that the frequency is a range of values. For example, the prescriber may instruct the patient to take 1 tablet 3-4 times per day for 10 days. In this cases, the dose would be 1 tablet, the frequency would be 3 times, the frequencyMax would be 4 times, the period would be 1 day, and the count would be 30 doses.

.....  period 0..1decimalDefinition:
The period defines the amount of time over which the frequency of doses should occur. For example, the prescriber may instruct the patient to take 1 tablet every day for 10 days. In this case, the period is 1 day.

.....  periodMax 0..1decimalDefinition:
The periodMax defines the maximum amount of time over which the frequency of doses should occur. For example, the prescriber may instruct the patient to apply one patch every 48 to 72 hours and leave the patch on for 12 hour and do this for 1 month. In this case, the dose would be one patch, the frequency would be 1, the duration would be 12 hours, the period would be 48 hours, the periodMax would be 72 hours, and the boundPeriod would be a start day of today and an end date of 2 months from now.

.....  periodUnit 0..1codeBinding: UnitsOfTime (required)
Definition:
The units of time for the period in UCUM units.


Comments:
Codes are from http://unitsofmeasure.org (h | d | wk | etc.)

...  asNeeded[x] 0..1boolean, CodeableConceptBinding: (unbound) (example)
Definition:
Indicates whether the Medication is only taken when needed within a specific dosing schedule (Boolean option), or it indicates the precondition for taking the Medication (CodeableConcept).


Comments:
Conformance Rule: This is ONLY populated when the medication is prescribed on an as needed (i.e. PRN) basis.

Conformance Rule: Set value = true

Conformance Rule: When this is specified, it is not acceptable to express the quantity exclusively as a duration/DAYS_SUPPLY. The DOSAGE_QUANTITY must be provided.

The CodeableConcept should not be used at this time. If it is present, treat it as though the boolean value is set to true.

...  siteCodeableConcept 0..1Shared Health CodeableConcept Required Text with optional code​Binding: PrescriptionAdministrationSite (extensible)
Definition:
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.


Comments:
Conformance Rule: When providing a structured SIG, this should be populated when appropriate. If not structured, this should be part of the SIG (RENDERED_DOSAGE_INSTRUCTION)

...  route 0..1Shared Health CodeableConcept Required Text with optional code​Binding: PrescriptionRouteOfAdministration (extensible)
Definition:
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.


Comments:
Conformance Rule: Coding should be populated if a code is available. However, text is always required.

Also specified for Multi-dosage lines.

...  dose[x] 0..1PrescribeIT Drug Quantity for Administration, PrescribeIT Drug RangeDefinition:
The amount of therapeutic or other substance given at one administration event.


Comments:
Conformance Rule: Could be sent as part of the dosage instruction. OR for those EMRs that can support it, this should be specified.

...  rate[x] 0..1RatioDefinition:
Identifies the speed with which the medication was or will be introduced into the patient. Typically the rate for an infusion e.g. 100 ml per 1 hour or 100 ml/hr. May also be expressed as a rate per unit of time e.g. 500 ml per 2 hours. Currently we do not specify a default of '1' in the denominator, but this is being discussed. Other examples: 200 mcg/min or 200 mcg/1 minute; 1 liter/8 hours.


Comments:
It is possible to supply both a rate and a doseQuantity to provide full details about how the medication is to be administered and supplied. If the rate is intended to change over time, depending on local rules/regulations, each change should be captured as a new version of the MedicationOrder with an updated rate, or captured with a new MedicationOrder with the new rate.

....  numerator 1..1PrescribeIT Drug Quantity for Administrationqty-3: If a code for the unit is present, the system SHALL also be present
sqty-1: The comparator is not used on a SimpleQuantity
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


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

....  denominator 1..1Shared Health Quantityqty-3: If a code for the unit is present, the system SHALL also be present
Definition:
A measured amount (or an amount that can potentially be measured). Note that measured amounts include amounts that are not precisely quantified, including amounts involving arbitrary units and floating currencies.


Comments:
This indicates the unit of time (e.g. per day, every 4 weeks, etc.)

...  maxDosePerPeriod 0..1RatioDefinition:
The maximum total quantity of a therapeutic substance that may be administered to a subject over the period of time. For example, 1000mg in 24 hours.


Comments:
Conformance Rule: When providing a structured SIG, this should be populated when appropriate.

....  numerator 1..1PrescribeIT Drug Quantity for Administrationqty-3: If a code for the unit is present, the system SHALL also be present
sqty-1: The comparator is not used on a SimpleQuantity
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


Comments:
Conformance Rule: Quantity is used throughout the messages. It may be a drug form (e.g. TAB) an adminstratable drug (e.g. PUFF) for or a unit of measure (e.g. mg). If this is provided it is mandatory to send a value from the PrescribeIT™ Drug Quantity.

....  denominator 1..1Shared Health Quantityqty-3: If a code for the unit is present, the system SHALL also be present
Definition:
A measured amount (or an amount that can potentially be measured). Note that measured amounts include amounts that are not precisely quantified, including amounts involving arbitrary units and floating currencies.


Comments:
This indicates the unit of time (e.g. per day, every 4 weeks, etc.)

..  dispenseRequest 1..1BackboneElement1: Must have at least one of quantity and expectedSupplyDuration
3: Must have at least one of total prescribed quantity and total days supply
Definition:
Indicates the specific details for the dispense or medication supply part of a medication order (also known as a Medication Prescription). Note that this information is NOT always sent with the order. There may be in some settings (e.g. hospitals) institutional or system support for completing the dispense details in the pharmacy department.

...  extension 0..*ExtensionSlice: Unordered, Open by value:url
Definition:
An Extension

...  extension
       (dispenseInterval) 		0..1Medication Order Dispense IntervalDefinition:
Optional Extensions Element - found in all resources.


Comments:
Indicates the minimum period of time that must pass between dispensing events.

Conformance Rule: Only days are currently support as a measurement of dispenseInterval.

Example: A prescriber instructs a patient to take 3 Tylenol 3 tablets every day as needed for pain for 90 days. However, the prescriber does not wish the patient to have more than 30 days supply at any given time so the prescriber instructs the pharmacist that the dispenseInterval is 30 days. The pharmacist then does 3 partial fills of 90 tablets (or 30 days supply) over the 90 day period.

...  extension
       (trialEligibility) 		0..1Medication Order Trial Dispense EligibilityDefinition:
Optional Extensions Element - found in all resources.


Comments:
Conformance Rule: If eligible for trial, this must be set to 'true' and presented to the Pharmacist.

Conformance Rule: This is ONLY populated if it is for trial, else it is assumed not to be eligble.

Note: Prescribers may include this information in notes.

...  extension
       (firstFillInstructions) 		0..1Medication Order Dispense First Fill Instructions2: At least one of first fill quantity or first fill days supply must be specified
Definition:
Optional Extensions Element - found in all resources.


Comments:
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')

Conformance Rule: 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.

Usage Note: There are times when a patient's drug plan limits what can be dispensed (i.e. 7 days initially as a trial). In this situation, the patient is informed that their drug plan only pays for 7 days. The pharmacist will ask the patient to sign the Rx that they have been informed are ok with changing the quantity to 7 days and then dispense the 7 days. The patient's file is updated to note that 7 days was dispensed as a trial period. After the initial 7 days, the patient will still have 353 tablets to be used. (90 tabs x 4 authorized fills = 360 tabs - 7 tabs dispensed as trial.

...  extension
       (maxDispense) 		0..1Medication Order Max DispenseDefinition:
Identifies the maximum quantity authorized to be dispensed at one time.


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

Example: A prescriber instructs a patient to take 3 Tylenol 3 tablets every day as needed for pain for 90 days. However, the prescriber does not wish the patient to have more than 30 days supply at any given time so the prescriber instructs the pharmacist that the maxDispense is 90 tablets. The pharmacist then does 3 partial fills of 90 tablets (or 30 days supply) over the 90 day period.

...  extension
       (totalPrescribedQuantity) 		0..1Medication Order Total Prescribed QuantityDefinition:
Optional Extensions Element - found in all resources.


Comments:
Conformance Rule: The Total Prescribed Quantity is not mandatory but must be supplied if the value is entered by the user or can be calculated by the system.

...  extension
       (totalDaysSupply) 		0..1Medication Order Total Prescribed Days SupplyDefinition:
Optional Extensions Element - found in all resources.


Comments:
Conformance Rule: Must be populated when the Total Days Supply is entered by the user or when the Total Days Supply can be calculated by the system.

Conformance Rule: Code must be 'd' and system must be 'http://unitsofmeasure.org'.

...  validityPeriod 1..1PeriodDefinition:
This indicates the validity period of a prescription (stale dating the Prescription).


Comments:
Conformance Rule: Must be either equal to or later then the MedicationOrder.dateWritten element.

....  start 1..1dateTimeDefinition:
The start of the period. The boundary is inclusive.


Comments:
Must be a full date and time with timezone (i.e. yyyy-mm-dd-HH:mm:ss.SSS-ZZZZZ).

....  end 0..1dateTimeDefinition:
The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.


Comments:
Must be a full date and time with timezone (i.e. yyyy-mm-dd-HH:mm:ss.SSS-ZZZZZ).

...  numberOfRepeatsAllowed 0..1positiveIntDefinition:
An integer indicating the number of additional times (aka refills or repeats) the patient can receive the prescribed medication. Usage Notes: This integer does NOT include the original order dispense. This means that if an order indicates dispense 30 tablets plus "3 repeats", then the order can be dispensed a total of 4 times and the patient can receive a total of 120 tablets.


Comments:
Conformance Rule: This must be populated when the number of repeats is 1 or more. As this field only allows a positive integer, this is not populated if there are no refills allowed.

Guidance: For narcotics, if this is incorrectly populated, the PMS could choose not to reject the message; rather they can adjust for the dispense.

...  quantity 0..1PrescribeIT Drug Quantityqty-3: If a code for the unit is present, the system SHALL also be present
sqty-1: The comparator is not used on a SimpleQuantity
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


Comments:
Conformance Rule: If days supply is NOT present, this MUST be populated.

...  expectedSupplyDuration 0..1DurationDefinition:
Identifies the period time over which the supplied product is expected to be used, or the length of time the dispense is expected to last.


Comments:
Conformance Rule: This maps to 'duration' in some EMR's. Must be populated when this is a discrete data element in the EMR; else this is sent as part of the textual description.

Conformance Rule: If Fill Quantity is NOT populated, this must be present.

....  value 1..1decimalDefinition:
The value of the measured amount. The value includes an implicit precision in the presentation of the value.


Comments:
The implicit precision in the value should always be honored.

....  system 1..1uriFixed Value: http://unitsofmeasure.org
Definition:
The identification of the system that provides the coded form of the unit.


Comments:
Fixed value: http://unitsofmeasure.org

....  code 1..1codeFixed Value: d
Definition:
A computer processable form of the unit in some unit representation system.


Comments:
Fixed value: d

..  priorPrescription 0..1Reference(PrescribeIT Prescription) {r}Definition:
A link to a resource representing an earlier order or prescription that this order supersedes.


Comments:
When present with a prescription number, this must be in the same form as was present on the original prescription - generally with a system of OID of the form [vendor root].[application instance node].2 expressed as a urn (e.g. urn:oid:1.2.3.4).

The 'value' element will contain the actual RX Number. Note that the system value must refer to the namespace of the system that created the original prescription, which may not always be the system performing the renewal.

In the context of Task e120-m:

Conformance Rule: This is mandatory and MUST be populated with the EMR generated eRX number (PRESCRIPTION_NUMBER) of the medication used as the basis for the new prescription for the same therapy. Its purpose is to identify the original prescription that drove the creation of this Renewal Fill Request. Note: This identifier may not be recognized by the PMS receiving this as it could have been a paper prescription or an ePrescription that was originally sent to another pharmacy.

For transition period, from paper to electronic, there would not be an EMR-assigned number. In this case, EMR MUST populate with a value of 'NA' in the Identifier.value and omit the system.

In the context of Task e140-m: This should include any prior prescription information that was included in the original prescription request from the EMR that is being cancelled. If the original EMR prescription request has this segment empty, then it should be empty for the e140-m.

In the context Tasks e162-m and e163-m:

Conformance Rule: This is mandatory and MUST be populated with the MedicationOrder.identifier as specified in the p160 being responded to.

In the context of Task p160-m:

Conformance Rule: The MedicationOrder transmitted in a p160 is the prior order that is being asked to be renewed. If this came in as an e110, priorPrescription will be absent. If this came in as an e120, priorPrescription will be present. If it was entered into the PMS as a paper or fax prescription, priorPrescription may not be known (in which case it will be absent), or may be set to 'NA' if the prescription was known to be a renewal, but the prescription identifier of the prior request is unknown).

...  extension 0..*ExtensionSlice: Unordered, Open by value:url
Definition:
An Extension

...  extension
       (identifier) 		0..1Referenced Requisition identifierDefinition:
Allows a reference to identify the target prescription, dispense or task by business identifier rather than URL


Comments:
When this is present, the reference is typically omitted

Usage Note: The URL for this extension does not refer to an existing web-page as is a pre-adoption extension. Refer to the Shared Health implementation Guide for more information.

....  url 1..1uri"http://hl7.org/fhir/StructureDefinition/extension-Reference.identifier"
....  valueIdentifier 1..1PrescribeIT™ Prescriber Prescription IdentifierDefinition:
A technical identifier - identifies some entity uniquely and unambiguously.


Comments:
When this is present, the reference is typically omitted

...  display 0..1stringDefinition:
Plain text narrative that identifies the resource in addition to the resource reference.


Comments:
This can be populated with the prescription number as a human-readable hint for downstream systems that don't recognize the extension. However, there is no known need for this element at present.

This structure is derived from MedicationOrder

Summary

Mandatory: 12 elements (12 nested mandatory elements)
Must-Support: 82 elements
Fixed Value: 3 elements
Prohibited: 3 elements

Structures

This structure refers to these other structures:

Extensions

This structure refers to these extensions:

Slices

This structure defines the following Slices:

  • The element MedicationOrder.identifier is sliced based on the value of value:type

This structure is derived from MedicationOrder

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationOrder S0..*
... id S1..1id
... contained S1..*Resource
... extension S0..*ExtensionSlice: Unordered, Open by value:url
... ext-medicationorder-category S0..1Shared Health CodeableConcept Text​Medication Order Category
URL: http://hl7.org/fhir/StructureDefinition/extension-MedicationRequest.category profiled by http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-category
Binding: PrescriptionType (extensible)
... ext-medication-rendered-dosage S1..1stringRendered Dosage Instruction
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medication-rendered-dosage
... ext-medicationorder-protocol S0..10string, uri, Shared Health IdentifierProtocol, order set, guideline, etc.
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-protocol
... ext-medicationorder-treatment-type S0..1code​ACU | CHRON
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-treatment-type
Binding: PrescriptionTreatmentCategory (required)
... ext-medicationorder-supportinginfo S0..*Reference(PrescribeIT List - Allergies | PrescribeIT Pharmacy-related Observation) {b}Allergies, height, weight, etc.
URL: http://hl7.org/fhir/StructureDefinition/extension-MedicationRequest.supportingInfo profiled by http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-supportinginfo
... ext-request-detectedissue S0..*Reference(PrescribeIT DUR) {b}Managed DUR and other issues
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-request-detectedissue
... ext-request-coverage S0..1Reference(PrescribeIT Coverage (NOT SUPPORTED)) {b}Insurance coverage
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-request-coverage
... ext-request-dispenser-instructions S0..1stringDispenser Instructions
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-request-dispenser-instructions
... ext-medicationorder-over-25-dur S0..1booleanMore than 25 DURs?
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-over-25-dur
... ext-medicationorder-monitored-drug S0..1booleanMonitored Drug?
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-monitored-drug
... ext-medicationorder-no-renewals S0..1booleanNo Prescription Renewals?
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-no-renewals
... identifier SShared Health IdentifierSlice: Unordered, Open by value:type
... identifier S1..1PrescribeIT™ Prescriber Prescription IdentifierEMR Prescription ID
.... type S1..1Shared Health CodeableConcept CodeRequired Pattern: {"coding":[{"system":"http://hl7.org/fhir/identifier-type","code":"PLAC"}]}
... identifier S0..2IdentifierDrug Information System's order number
.... type S1..1Shared Health CodeableConcept CodeRequired Pattern: {"coding":[{"system":"http://hl7.org/fhir/v2/0203","code":"RRI"}]}
.... system S0..1uri
.... value S1..1string
... status S1..1codeFixed Value: active
... medicationReference S1..1Reference(PrescribeIT Medication) {c}
... patient S1..1Reference(Shared Health Patient) {b}
... dateWritten SI0..1dateTimecreated-full: Must be at least a full date. i.e. yyyy-mm-dd
... prescriber S1..1Reference(Shared Health Practitioner) {b}
... reasonCode S0..5Shared Health CodeableConcept Required Text with optional code​Binding: PrescriptionIndicationForUse (extensible)
.... coding 0..*Coding
.... text S1..1string
... note S0..1AnnotationMax Length: 2500
.... text S1..1string
... dosageInstruction S0..*BackboneElement
.... extension S0..*ExtensionSlice: Unordered, Open by value:url
.... ext-medication-dosageinstruction-sequence S1..1positiveIntSequence of dosage instruction
URL: http://hl7.org/fhir/StructureDefinition/extension-Dosage.sequence profiled by http://prescribeit.ca/fhir/StructureDefinition/ext-medication-dosageinstruction-sequence
.... ext-medicationorder-dosageinstruction-relationship S0..1code​AND | THEN
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dosageinstruction-relationship
Binding: PrescriptionDosageInstructionLineRelationship (required)
.... text S0..1string
.... additionalInstructions S0..1Shared Health CodeableConcept Text
..... text S1..1stringMax Length: 5000
.... timing S0..1Timing
..... repeat S0..1Element
...... boundsPeriod S0..1Period
...... count S0..1integer
...... countMax S0..1integer
...... duration S0..1decimal
...... durationMax S0..1decimal
...... durationUnit S0..1code
...... frequency S0..1integer
...... frequencyMax S0..1integer
...... period S0..1decimal
...... periodMax S0..1decimal
...... periodUnit S0..1code
...... when 0..0
...... offset 0..0
.... asNeeded[x] S0..1boolean, CodeableConcept
.... siteCodeableConcept S0..1Shared Health CodeableConcept Required Text with optional code​Binding: PrescriptionAdministrationSite (extensible)
.... route S0..1Shared Health CodeableConcept Required Text with optional code​Binding: PrescriptionRouteOfAdministration (extensible)
.... doseQuantity S0..1PrescribeIT Drug Quantity for Administration, PrescribeIT Drug Range
.... rateRatio S0..1Ratio
..... numerator S1..1PrescribeIT Drug Quantity for Administration
..... denominator S1..1Shared Health Quantity
.... maxDosePerPeriod S0..1Ratio
..... numerator S1..1PrescribeIT Drug Quantity for Administration
..... denominator S1..1Shared Health Quantity
... dispenseRequest SI1..1BackboneElement1: Must have at least one of quantity and expectedSupplyDuration
3: Must have at least one of total prescribed quantity and total days supply
.... extension S0..*ExtensionSlice: Unordered, Open by value:url
.... ext-medicationorder-dispense-interval S0..1DurationDispense interval
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-interval
.... ext-medicationorder-dispense-trial S0..1booleanTrial fill authorized?
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-trial
.... ext-medicationorder-dispense-first-fill SI0..1(Complex)First fill instructions
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-first-fill
2: At least one of first fill quantity or first fill days supply must be specified
.... ext-medicationorder-dispense-max S0..1PrescribeIT Drug QuantityMaximum prescribed quantity
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-max
.... ext-medicationorder-total-quantity S0..1PrescribeIT Drug QuantityTotal prescribed quantity
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-total-quantity
.... ext-medicationorder-total-days-supply S0..1DurationTotal prescribed days supply
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-total-days-supply
.... medicationCodeableConcept 0..1Shared Health CodeableConcept Required Text with optional code​Binding: PrescriptionMedicinalProduct (extensible)
.... validityPeriod S1..1Period
..... start S1..1dateTime
..... end S0..1dateTime
.... numberOfRepeatsAllowed S0..1positiveInt
.... quantity SI0..1PrescribeIT Drug Quantity
.... expectedSupplyDuration SI0..1Duration
..... value S1..1decimal
..... comparator 0..0
..... unit 0..1string
..... system S1..1uriFixed Value: http://unitsofmeasure.org
..... code S1..1codeFixed Value: d
... priorPrescription S0..1Reference(PrescribeIT Prescription) {r}
.... extension S0..*ExtensionSlice: Unordered, Open by value:url
.... ext-reference-identifier S0..1Shared Health IdentifierReferenced identifier
URL: http://hl7.org/fhir/StructureDefinition/extension-Reference.identifier profiled by http://sharedhealth.exchange/fhir/StructureDefinition/ext-reference-identifier
..... valueIdentifier S1..1PrescribeIT™ Prescriber Prescription Identifier
.... reference 0..1string
.... display S0..1string

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationOrder SΣ0..*Prescription of medication to for patient
... id SΣ1..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: http://tools.ietf.org/html/bcp47 (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained S1..*ResourceContained, inline Resources
... extension S0..*ExtensionExtension
Slice: Unordered, Open by value:url
... ext-medicationorder-category S0..1Shared Health CodeableConcept Text​Medication Order Category
URL: http://hl7.org/fhir/StructureDefinition/extension-MedicationRequest.category profiled by http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-category
Binding: PrescriptionType (extensible)
... ext-medication-rendered-dosage S1..1stringRendered Dosage Instruction
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medication-rendered-dosage
... ext-medicationorder-protocol S0..10string, uri, Shared Health IdentifierProtocol, order set, guideline, etc.
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-protocol
... ext-medicationorder-treatment-type S0..1code​ACU | CHRON
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-treatment-type
Binding: PrescriptionTreatmentCategory (required)
... ext-medicationorder-supportinginfo S0..*Reference(PrescribeIT List - Allergies | PrescribeIT Pharmacy-related Observation) {b}Allergies, height, weight, etc.
URL: http://hl7.org/fhir/StructureDefinition/extension-MedicationRequest.supportingInfo profiled by http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-supportinginfo
... ext-request-detectedissue S0..*Reference(PrescribeIT DUR) {b}Managed DUR and other issues
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-request-detectedissue
... ext-request-coverage S0..1Reference(PrescribeIT Coverage (NOT SUPPORTED)) {b}Insurance coverage
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-request-coverage
... ext-request-dispenser-instructions S0..1stringDispenser Instructions
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-request-dispenser-instructions
... ext-medicationorder-over-25-dur S0..1booleanMore than 25 DURs?
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-over-25-dur
... ext-medicationorder-monitored-drug S0..1booleanMonitored Drug?
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-monitored-drug
... ext-medicationorder-no-renewals S0..1booleanNo Prescription Renewals?
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-no-renewals
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier SΣShared Health IdentifierAn identifier intended for computation
Slice: Unordered, Open by value:type
... identifier S1..1PrescribeIT™ Prescriber Prescription IdentifierEMR Prescription ID
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?!Σ0..1codeusual | official | temp | secondary (If known)
Binding: IdentifierUse (required)
.... type S1..1Shared Health CodeableConcept CodeConcept - reference to a terminology or just text
Binding: Identifier Type Codes (extensible)
Required Pattern: {"coding":[{"system":"http://hl7.org/fhir/identifier-type","code":"PLAC"}]}
..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... coding SΣCodingCode defined by a terminology system
Slice: Unordered, Open by value:system, value:code
...... id 0..1idxml:id (or equivalent in JSON)
...... extension 0..*ExtensionAdditional Content defined by implementations
...... system SΣ1..1uriIdentity of the terminology system
...... version Σ0..1stringVersion of the system - if relevant
...... code SΣ1..1codeSymbol in syntax defined by the system
...... display Σ0..1stringRepresentation defined by the system
...... userSelected Σ0..1booleanIf this coding was chosen directly by the user
..... coding SΣ1..*CodingCode defined by a terminology system
...... id 0..1idxml:id (or equivalent in JSON)
...... extension 0..*ExtensionAdditional Content defined by implementations
...... system SΣ1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/identifier-type
...... version Σ0..1stringVersion of the system - if relevant
...... code SΣ1..1codeSymbol in syntax defined by the system
Fixed Value: PLAC
...... display Σ0..1stringRepresentation defined by the system
...... userSelected Σ0..1booleanIf this coding was chosen directly by the user
..... text Σ0..1stringPlain text representation of the concept
.... system SΣ1..1uriThe namespace for the identifier
Example General': http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri
.... value SΣ1..1stringThe value that is unique
Example General': 123456
.... period Σ0..1PeriodTime period when id is/was valid for use
.... assigner Σ0..1Reference(Organization)Organization that issued id (may be just text)
... identifier SΣ0..2IdentifierDrug Information System's order number
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?!Σ0..1codeusual | official | temp | secondary (If known)
Binding: IdentifierUse (required)
.... type S1..1Shared Health CodeableConcept CodeConcept - reference to a terminology or just text
Binding: Identifier Type Codes (extensible)
Required Pattern: {"coding":[{"system":"http://hl7.org/fhir/v2/0203","code":"RRI"}]}
.... system SΣ0..1uriThe namespace for the identifier
Example General': http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri
.... value SΣ1..1stringThe value that is unique
Example General': 123456
.... period Σ0..1PeriodTime period when id is/was valid for use
.... assigner Σ0..1Reference(Organization)Organization that issued id (may be just text)
... status ?!SΣ1..1codeactive | on-hold | completed | entered-in-error | stopped | draft
Binding: MedicationOrderStatus (required)
Fixed Value: active
... medicationReference SΣ1..1Reference(PrescribeIT Medication) {c}A reference from one resource to another
... patient SΣ1..1Reference(Shared Health Patient) {b}A reference from one resource to another
... encounter Σ0..1Reference(Encounter)Created during encounter/admission/stay
... dateWritten SΣI0..1dateTimeWhen prescription was authorized
created-full: Must be at least a full date. i.e. yyyy-mm-dd
... prescriber SΣ1..1Reference(Shared Health Practitioner) {b}A reference from one resource to another
... reasonCode S0..5Shared Health CodeableConcept Required Text with optional code​Concept - reference to a terminology or just text
Binding: PrescriptionIndicationForUse (extensible)
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... coding Σ0..*CodingCode defined by a terminology system
..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... system SΣ1..1uriIdentity of the terminology system
..... version Σ0..1stringVersion of the system - if relevant
..... code SΣ1..1codeSymbol in syntax defined by the system
..... display Σ0..1stringRepresentation defined by the system
..... userSelected Σ0..1booleanIf this coding was chosen directly by the user
.... text SΣ1..1stringPlain text representation of the concept
Max Length: 2500
... reasonReference Σ0..*Reference(Condition)Condition that supports why the prescription is being written
... dateEnded Σ0..1dateTimeWhen prescription was stopped
... reasonEnded Σ0..1CodeableConceptWhy prescription was stopped
Binding: (unbound) (example)
... note SΣ0..1AnnotationInformation about the prescription

Max Length: 2500
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... author[x] Σ0..1Reference(Practitioner | Patient | RelatedPerson), stringIndividual responsible for the annotation
.... time Σ0..1dateTimeWhen the annotation was made
.... text S1..1stringThe annotation - text content
... dosageInstruction SΣ0..*BackboneElementHow medication should be taken
.... id 0..1idxml:id (or equivalent in JSON)
.... extension S0..*ExtensionExtension
Slice: Unordered, Open by value:url
.... ext-medication-dosageinstruction-sequence S1..1positiveIntSequence of dosage instruction
URL: http://hl7.org/fhir/StructureDefinition/extension-Dosage.sequence profiled by http://prescribeit.ca/fhir/StructureDefinition/ext-medication-dosageinstruction-sequence
.... ext-medicationorder-dosageinstruction-relationship S0..1code​AND | THEN
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dosageinstruction-relationship
Binding: PrescriptionDosageInstructionLineRelationship (required)
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... text SΣ0..1stringFree text dosage instructions e.g. SIG
.... additionalInstructions SI0..1Shared Health CodeableConcept TextConcept - reference to a terminology or just text
Binding: (unbound) (example)
..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... coding SΣ0..*CodingCode defined by a terminology system
...... id 0..1idxml:id (or equivalent in JSON)
...... extension 0..*ExtensionAdditional Content defined by implementations
...... system SΣ1..1uriIdentity of the terminology system
...... version Σ0..1stringVersion of the system - if relevant
...... code SΣ1..1codeSymbol in syntax defined by the system
...... display Σ0..1stringRepresentation defined by the system
...... userSelected Σ0..1booleanIf this coding was chosen directly by the user
..... text SΣ1..1stringPlain text representation of the concept
Max Length: 5000
.... timing SΣ0..1TimingWhen medication should be administered
..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... event Σ0..*dateTimeWhen the event occurs
..... repeat SΣI0..1ElementWhen the event is to occur
...... id 0..1idxml:id (or equivalent in JSON)
...... extension 0..*ExtensionAdditional Content defined by implementations
...... boundsPeriod SΣ0..1PeriodLength/Range of lengths, or (Start and/or end) limits
...... count SΣ0..1integerNumber of times to repeat
...... countMax SΣ0..1integerMaximum number of times to repeat
...... duration SΣ0..1decimalHow long when it happens
...... durationMax SΣ0..1decimalHow long when it happens (Max)
...... durationUnit SΣ0..1codes | min | h | d | wk | mo | a - unit of time (UCUM)
Binding: UnitsOfTime (required)
...... frequency SΣ0..1integerEvent occurs frequency times per period
...... frequencyMax SΣ0..1integerEvent occurs up to frequencyMax times per period
...... period SΣ0..1decimalEvent occurs frequency times per period
...... periodMax SΣ0..1decimalUpper limit of period (3-4 hours)
...... periodUnit SΣ0..1codes | min | h | d | wk | mo | a - unit of time (UCUM)
Binding: UnitsOfTime (required)
..... code Σ0..1CodeableConceptQD | QOD | Q4H | Q6H | BID | TID | QID | AM | PM +
Binding: TimingAbbreviation (preferred)
.... asNeeded[x] SΣ0..1boolean, CodeableConceptTake "as needed" (for x)
Binding: (unbound) (example)
.... siteCodeableConcept S0..1Shared Health CodeableConcept Required Text with optional code​Concept - reference to a terminology or just text
Binding: PrescriptionAdministrationSite (extensible)
.... route S0..1Shared Health CodeableConcept Required Text with optional code​Concept - reference to a terminology or just text
Binding: PrescriptionRouteOfAdministration (extensible)
.... method Σ0..1CodeableConceptTechnique for administering medication
Binding: (unbound) (example)
.... dose[x] SΣ0..1PrescribeIT Drug Quantity for Administration, PrescribeIT Drug RangeAmount of medication per dose
.... rate[x] SΣ0..1RatioAmount of medication per unit of time
..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... numerator SI1..1PrescribeIT Drug Quantity for AdministrationQuantity of a medication
..... denominator SI1..1Shared Health QuantityA measured or measurable amount
.... maxDosePerPeriod SΣ0..1RatioUpper limit on medication per unit of time
..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... numerator SI1..1PrescribeIT Drug Quantity for AdministrationQuantity of a medication
..... denominator SI1..1Shared Health QuantityA measured or measurable amount
... dispenseRequest SΣI1..1BackboneElementMedication supply authorization
1: Must have at least one of quantity and expectedSupplyDuration
3: Must have at least one of total prescribed quantity and total days supply
.... id 0..1idxml:id (or equivalent in JSON)
.... extension S0..*ExtensionExtension
Slice: Unordered, Open by value:url
.... ext-medicationorder-dispense-interval S0..1DurationDispense interval
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-interval
.... ext-medicationorder-dispense-trial S0..1booleanTrial fill authorized?
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-trial
.... ext-medicationorder-dispense-first-fill SI0..1(Complex)First fill instructions
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-first-fill
2: At least one of first fill quantity or first fill days supply must be specified
.... ext-medicationorder-dispense-max S0..1PrescribeIT Drug QuantityMaximum prescribed quantity
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-max
.... ext-medicationorder-total-quantity S0..1PrescribeIT Drug QuantityTotal prescribed quantity
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-total-quantity
.... ext-medicationorder-total-days-supply S0..1DurationTotal prescribed days supply
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-total-days-supply
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... medicationCodeableConcept 0..1Shared Health CodeableConcept Required Text with optional code​Concept - reference to a terminology or just text
Binding: PrescriptionMedicinalProduct (extensible)
.... validityPeriod SΣ1..1PeriodTime period supply is authorized for
..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... start SΣI1..1dateTimeStarting time with inclusive boundary
..... end SΣI0..1dateTimeEnd time with inclusive boundary, if not ongoing
.... numberOfRepeatsAllowed SΣ0..1positiveIntNumber of refills authorized
.... quantity SI0..1PrescribeIT Drug QuantityQuantity of a medication
.... expectedSupplyDuration SΣ0..1DurationNumber of days supply per dispense
..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... value SΣ1..1decimalNumerical value (with implicit precision)
..... unit Σ0..1stringUnit representation
..... system SΣI1..1uriSystem that defines coded unit form
Fixed Value: http://unitsofmeasure.org
..... code SΣ1..1codeCoded form of the unit
Fixed Value: d
... substitution Σ0..1BackboneElementAny restrictions on medication substitution
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... type Σ1..1CodeableConceptgeneric | formulary +
Binding: ActSubstanceAdminSubstitutionCode (example)
.... reason Σ0..1CodeableConceptWhy should (not) substitution be made
Binding: SubstanceAdminSubstitutionReason (example)
... priorPrescription SΣ0..1Reference(PrescribeIT Prescription) {r}An order/prescription that this supersedes
.... id 0..1idxml:id (or equivalent in JSON)
.... extension S0..*ExtensionExtension
Slice: Unordered, Open by value:url
.... ext-reference-identifier S0..1Shared Health IdentifierReferenced identifier
URL: http://hl7.org/fhir/StructureDefinition/extension-Reference.identifier profiled by http://sharedhealth.exchange/fhir/StructureDefinition/ext-reference-identifier
..... id 0..1idxml:id (or equivalent in JSON)
..... url S1..1uri"http://hl7.org/fhir/StructureDefinition/extension-Reference.identifier"
..... valueIdentifier S1..1PrescribeIT™ Prescriber Prescription IdentifierAn identifier intended for computation
.... reference ΣI0..1stringRelative, internal or absolute URL reference
.... display SΣ0..1stringText alternative for the resource

doco Documentation for this format

Grid View

This structure is derived from MedicationOrder

NameCard.TypeConstraints and Usage
.  MedicationOrder 0..*Definition:
An order for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationOrder" rather than "MedicationPrescription" to generalize the use across inpatient and outpatient settings as well as for care plans, etc.


Comments:
For Task e110-m - New RX Fill Request, this conveys the details of a single medication order.

For Task p160-m - RX Renewal Create Request, this conveys the details of a single medication order for which the renewal is being requested.

For Task e120-m - Renewal RX Fill Request, this conveys the medication order for which a fill is being requested.

..  id 1..1idDefinition:
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.


Comments:
Usage Note: This will usually be a GUID and is assigned by the sending application.

..  contained 1..*ResourceDefinition:
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.


Comments:
Conformance Rule: This will be used to contain the Medication resource. No other resources should be 'contained'.

..  extension 0..*ExtensionSlice: Unordered, Open by value:url
Definition:
An Extension

..  extension
     (category) 		0..1Medication Order CategoryDefinition:
Sub-categorizes medication prescriptions into drugs, devices, compounds, etc. May be used to apply sub-type-specific constraints


Comments:
Conformance Rule: If no appropriate code exists, provide details using the 'text' component.

..  extension
     (renderedDosageInstruction) 		1..1Medication Rendered Dosage InstructionDefinition:
A free form textual specification generated from the input specifications as created by the provider.This is made up of either an 'Ad-hoc instruction' or 'Textual rendition of the structured dosage lines', plus route, dosage unit, and other pertinent administration information specified by the provider.


Comments:
Usage Note: This is intended to provide all dosage instructions to the Pharmacist in a clear human-readable format. This field will be displayed to the Pharmacist upon receipt of the prescription. Note: This must be as clear as possible and must include all instructions because the EMR may not provide individual/structured dosage instructions. When the Prescription cannot be delivered electronically, the rendered dosage instruction will be printed on the fax and will be the only source of dosage information.

It is recognized that very complex instructions may be conveyed as text only (not as structured data). Example: take 500 mg twice a day at breakfast and at lunch AND 250 mg once a day at bedtime - THEN (new dosage line)). If the EMR submits structured dosage instructions, this must be consistent with the textual instructions provided here. The PMS may ignore the structured frequency, or override it to align with the textual instructions.

Example: the EMR may enter frequency (multiplier of the dose) in their system like this (2 qam and 3 qhs ), in the structured frequency. The textual instructions could say Take 2 tablets in the morning and 3 at bedtime.

Conformance Rule: The rendered dosage instruction MUST contain ALL dosage instructions. This includes ALL child elements of dosage instruction, such as dosage quantity, dosage unit, frequency, etc) in human readable form and must be able to stand on its own. This field will include all of the information contained in the structured dosage as well as patient instructions (eg take with food, starting one day before dental appointment), assembled into one field and formatted as human-readable. Coded values codes should not be used (e.g. 'days' should be used instead of 'd', the code of PO as 'oral' )

Conformance Rule: MUST allow all printable characters and carriage return/line feeds. 5000 character max.

Conformance Rule: If an EMR has discrete field for Pharmacy Notes (Dispenser Instructions), they should not be included here. If EMR's have both concepts combined into one field, they can both be included here.

..  extension
     (protocol) 		0..10Medication Order ProtocolDefinition:
Identifies the Protocol, Order set, Guideline or other definition that guided the creation of this prescription


Comments:
Conformance Rule: If EMR's support as a discrete data element, this should be populated; else it will be part of the Dispenser Instructions (MedicationOrder.note.text). If it is present, it must be displayed to the Pharmacist. Usage Note: To date, the only known use case is for LU codes. If sent as an identifier, no guidance yet exists on appropriate values for the 'system' component.

..  extension
     (treatmentType) 		0..1Medication Order Treatment TypeDefinition:
Identifies whether this drug is for acute or chronic use


Comments:
Conformance Rule: Must be populated if known

..  extension
     (supportingInformation) 		0..*Medication Order Supporting InformationDefinition:
Additional information that relevant to the order. E.g. observations, allergies, etc.


Comments:
Cardinality must be 0..1 for Shared Health List-Allergies and 0..2 for Shared Health Pharmacy-related Observation (i.e. 1 for height and 1 for weight).

Conformance Rule: All known patient allergies must be included in the Medication Order.

..  extension
     (detectedIssue) 		0..*Request-related Detected IssuesDefinition:
A set of managed and relevant detected issues that should be transmitted along with a prescription or order to provide context during the execution of that order.


Comments:
Usage Note: This is a reference to the resource which is used to convey Managed Detected Issues (DUR)

..  extension
     (coverage) 		0..1Request-related Coverage (NOT SUPPORTED)Definition:
Identifies insurance coverage that may be relevant to fulfilling an order

..  extension
     (pharmacyInstructions) 		0..1Request Dispenser InstructionsDefinition:
Provides additional instructions from the prescriber to the pharmacy or other dispenser


Comments:
Usage Note: To convey explicit instructions to the Pharmacist/dispenser related to this medication order.

Usage Note: If the PMS solution is unable to display the entire instructions, then it is expected that the current solution has a fail-over process and will create a printout of the prescription.

Conformance Rule: PMS solution must be able to print out the entire prescription with ALL dispensing instructions included on the printout. Minimum data elements can be based on the eFax model

Conformance Rule: When 'compliance pack' is indicated on the prescription within the EMR, populate the pharmacist instruction/dispenser instructions with 'COMPLIANCE PACK REQUESTED'

Usage Note: In the case where the prescriber indicates the concept of ‘do not adapt’ (meaning that the pharmacist should not alter the prescription based on the patient's weight as an example), this direction to the pharmacist should be conveyed in human language in this field.

Conformance Rule: If a prescriber wishes to indicate that there is no substitution it must be included as part of the pharmacy instructions.

Conformance Rule: LU Codes must be clearly conveyed as part of the Pharmacists Instructions. If vendors are programmitically mapping into this field, they should use a prefix of LU Code before the identifier.

..  extension
     (over25dur) 		0..1Medication Order - Over 25 DURDefinition:
Indicates that the total number of managed DURs associated with the prescription exceeds the reporting limit of 25


Comments:
Conformance Rule: Set value = true when there are more than 25 warnings returned in the EMR DUR system

..  extension
     (monitoreddrug) 		0..1Medication Order - Monitored DrugDefinition:
Allows prescribers to indicate that the prescription is for a 'Monitored Drug' (e.g. compound) value in the prescription message to the pharmacies


Comments:
Conformance Rule: The prescriber should have the ability to set this flag when the medication is a compound. The absence of this extension means (i.e. value=”false”) that this is not a monitored substance.

Usage Note: Provinces may require prescribers to enter this value when a compound contains a monitored substance (e.g. narcotic) to support Prescription Drug Monitoring Programs (e.g. the Alberta Triplicate Prescription Program).

..  extension
     (norenewals) 		0..1Medication Order - No Prescription RenewalsDefinition:
Indicates that the prescriber will not support renewals for this prescription


Comments:
Conformance Rule: The PMS should present a warning to the dispenser if they create a renewal request for a prescription that has this flag set to indicate 'no renewals'. The PMS should allow the renewal to be submitted along with an explanation as there may be exceptional circumstances.

..  identifier 1..3Shared Health IdentifierSlice: Unordered, Open by value:type
Definition:
A technical identifier - identifies some entity uniquely and unambiguously.


Comments:
These are the identifiers assigned by the EMR and, in some cases, by the DIS.

..  identifier
     (emr-id) 		1..1PrescribeIT™ Prescriber Prescription IdentifierDefinition:
A technical identifier - identifies some entity uniquely and unambiguously.


Comments:
In the context of a net new prescription (e110, e120, e162, or e163), this identifier is generated by the EMR. The prescription number should be sent in the value element and should be an OID of the form [vendor root].[application instance node].2 expressed as a urn (e.g. urn:oid:2.16.840.1.113883.3.368.1234.2).

In the context of a Renewal Request (p160), the prescription number for the prescription that is being requested to be renewed should be used for this element. In most cases, this will be a value that was originally generated by an EMR. However, in some cases (such as the renewal of a paper/fax prescription), there will be no EMR generated prescription number, and in this case, the PMS should generate a number.

In the context of an Rx Response - Denied (e161), or an Rx Response - Under Review (e164), this element should be populated with the MedicationOrder.identifier(emr-id) provided in the Renewal Request (p160).

In the context of a Cancel Rx Fill Request (e140), this element should be populated with the same Rx that was included in the original net new prescription message (e110, e120, e162, or e163).

...  type 1..1Shared Health CodeableConcept CodeBinding: Identifier Type Codes (extensible)
Required Pattern: {"coding":[{"system":"http://hl7.org/fhir/identifier-type","code":"PLAC"}]}
Definition:
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.


Comments:
....  coding 1..*CodingSlice: Unordered, Open by value:system, value:code
Definition:
A reference to a code defined by a terminology system.


Comments:
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labelled as UserSelected = true.

.....  system 1..1uriDefinition:
The identification of the code system that defines the meaning of the symbol in the code.


Comments:
.....  code 1..1codeDefinition:
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

....  coding
         (placer) 		1..*CodingDefinition:
A reference to a code defined by a terminology system.


Comments:
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labelled as UserSelected = true.

.....  system 1..1uriFixed Value: http://hl7.org/fhir/identifier-type
Definition:
The identification of the code system that defines the meaning of the symbol in the code.


Comments:
Fixed value: http://hl7.org/fhir/identifier-type

.....  code 1..1codeFixed Value: PLAC
Definition:
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).


Comments:
Fixed value: PLAC

...  system 1..1uriExample' General': http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri
Definition:
Establishes the namespace in which set of possible id values is unique.

...  value 1..1string​Example' General': 123456
Definition:
The portion of the identifier typically relevant to the user and which is unique within the context of the system.


Comments:
If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension.

..  identifier
     (dis-id) 		0..2IdentifierDefinition:
External identifier - one that would be used by another non-FHIR system - for example a re-imbursement system might issue its own id for each prescription that is created. This is particularly important where FHIR only provides part of an entire workflow process where records have to be tracked through an entire system.


Comments:
Usage Note: When an e110-m, e120-m, e162-m or e163-m passes through the PrescribeIT™ Switch in a jurisdiction which has a Drug Information System (DIS), the PrescribeIT™ Switch will add the DIS's identifier to the MedicationOrder. PMS are to use this identifier to record the dispense event against the correct DIS Prescription identifier. This element will not be present in the message transmitted from the EMR to the PrescribeIT™ Switch.

There should only be 2 identifiers in the case of a border town such as Lloydminster where the DIS identifier in both provinces needs to be stored.

...  type 1..1Shared Health CodeableConcept CodeBinding: Identifier Type Codes (extensible)
Required Pattern: {"coding":[{"system":"http://hl7.org/fhir/v2/0203","code":"RRI"}]}
Definition:
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.


Comments:
...  system 0..1uriExample' General': http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri
Definition:
Establishes the namespace in which set of possible id values is unique.

...  value 1..1string​Example' General': 123456
Definition:
The portion of the identifier typically relevant to the user and which is unique within the context of the system.


Comments:
If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension.

..  status 1..1codeBinding: MedicationOrderStatus (required)
Fixed Value: active
Definition:
A code specifying the state of the order. Generally this will be active or completed state.


Comments:
Fixed value: active

..  medicationReference 1..1Reference(PrescribeIT Medication) {c}Definition:
A reference from one resource to another.


Comments:
Usage Note: this is populated with the reference to the Medication resource pertaining to this Medication Order. It will point to the 'contained' Medication resource. E.g. <reference value='#med'/>

..  patient 1..1Reference(Shared Health Patient) {b}Definition:
A reference from one resource to another.


Comments:
Usage Note: This must point to the patient associated with the message.

..  dateWritten 0..1dateTimecreated-full: Must be at least a full date. i.e. yyyy-mm-dd
Definition:
The date (and perhaps time) when the prescription was written.


Comments:
Conformance Rule: Must be either equal to or earlier then the MedicationOrder.dispenseRequest.valididityPeriod.start element.

Must be a full date and time with timezone (i.e. yyyy-mm-dd-HH:mm:ss.SSS-ZZZZZ).

..  prescriber 1..1Reference(Shared Health Practitioner) {b}Definition:
A reference from one resource to another.


Comments:
Conformance Rule: When requesting that a prescription be filled or responding to a renewal request, this SHALL be the practitioner initiating the message.

..  reasonCode 0..5Shared Health CodeableConcept Required Text with optional code​Binding: PrescriptionIndicationForUse (extensible)
Definition:
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.


Comments:
Conformance Rule: In the case where the prescriber wants to send an Indication for Use that is not included in the value set the prescriber must be able to send a text value without a code.

...  text 1..1stringMax Length: 2500
Definition:
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.


Comments:
Usage Note: When conveying the reason, this must be populated

..  note 0..1AnnotationMax Length: 2500
Definition:
Extra information about the prescription that could not be conveyed by the other attributes.

...  text 1..1stringDefinition:
The text of the annotation.


Comments:
Usage Note: This is used as an additional pharmacy note that is unrelated to the dispensing instructions. Eg. Do not fill immediately, Patient is coming in on July 12th for Booster shot.

Conformance Rule: PMS Vendors MUST display this to the pharmacist as it may contain important information. There could be Patient Instructions in here, inadvertently due to current prescribing behaviours.

..  dosageInstruction 0..*BackboneElementDefinition:
Indicates how the medication is to be used by the patient.


Comments:
Conformance Rule: For EMRs that can support structured dosage instruction, this element must be populated when the prescriber specifies any of structured dosage information. Anything that is populated as part of the structured dosage information must also be part of the RENDERED_DOSAGE_INSTRUCTION element.

Usage Note: An Excel spreadsheet providing guidance on how to populate dosage instructions can be found under 'Scope and Usage'.

When the dose or rate is intended to change over the entire administration period, e.g. Tapering dose prescriptions, multiple instances of dosage instructions will need to be supplied to convey the different doses/rates. Another common example in institutional settings is 'titration' of an IV medication dose to maintain a specific stated hemodynamic value or range e.g. drug x to be administered to maintain AM (arterial mean) greater than 65.

...  extension 0..*ExtensionSlice: Unordered, Open by value:url
Definition:
An Extension

...  extension
       (sequence) 		1..1Medication Dosage Line SequenceDefinition:
Optional Extensions Element - found in all resources.


Comments:
Conformance Rule: This must match the positional sequence of the dosageInstruction repetition. I.e. The first dosageInstruction repetition must have a 'sequence' value of 1, the second a 'sequence' value of 2, etc.

...  extension
       (instructionRelationship) 		0..1Medication Order Dosage Instruction RelationshipDefinition:
Optional Extensions Element - found in all resources.


Comments:
Conformance Rule: As this will establish the relationship to the previous dosage lines (example: first and second dosage line, the second and third dosage line, etc.) this must be present for all dosage lines except for the FIRST dosage line.

Conformance Rule: ANDs and THENs should not be mixed due to ambiguity of meaning.

...  text 0..1stringDefinition:
Free text dosage instructions can be used for cases where the instructions are too complex to code. The content of this attribute does not include the name or description of the medication. When coded instructions are present, the free text instructions may still be present for display to humans taking or administering the medication. It is expected that the text instructions will always be populated. If the dosage.timing attribute is also populated, then the dosage.text should reflect the same information as the timing.


Comments:
Conformance Rule: When providing multiple dosage lines can be expressed individually. All dosage lines (full text content) must be concatenated into the RENDERED_DOSAGE_INSTRUCTION as PMS will not be forced to support the receipt of individual lines.

Usage Note: This is a string that is typically composed of the route, duration, dose, frequency, per line

Example: Prednisone; variable dosage instruction, or concurrent instructions (1 pill morning and 1 pill before bed) or sequential dosages (1 pill for 2 days, then 2 pills).

...  additionalInstructions 0..1Shared Health CodeableConcept TextBinding: (unbound) (example)
inv-1: Must have coding or text but not both
Definition:
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.


Comments:
Conformance Rule: When providing an additional instruction at the dosage line level (complex), this should be populated when appropriate.

Usage Note: It may be necessary for the EMR to parse instructions such as QHS (take at bedtime), into two data elements DOSAGE_TIMING_FREQUENCY = once a day and 'at bedtime' would be placed into this field.

Usage Note: 'Coding' is not available, so 'Text' is expected to be used

Usage Note: At this time there is no known coding system. Therefore ‘text’ will be used.

....  coding 0..*CodingDefinition:
A reference to a code defined by a terminology system.


Comments:
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labelled as UserSelected = true.

.....  system 1..1uriDefinition:
The identification of the code system that defines the meaning of the symbol in the code.


Comments:
.....  code 1..1codeDefinition:
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

....  text 1..1stringMax Length: 5000
Definition:
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.


Comments:
Very often the text is the same as a displayName of one of the codings.

...  timing 0..1TimingDefinition:
The timing schedule on how the patient is to take the medication. The timing schedules allows many different expressions to be expressed. For example: Every 8 hours, Three times a day, 1/2 an hour before breakfast for 10 days from 17 Oct 2017 to 27 Oct 2017


Comments:
Conformance Rule: For EMRs that can support structured dosage instruction, this must be populated if prescriber specifies any of structured timing information. Anything that is populated as part of the structured timing information must also be part of the RENDERED_DOSAGE_INSTRUCTION.

Usage Note: An Excel spreadsheet providing guidance on how to populate dosage instructions can be found under 'Scope and Usage'.

....  repeat 0..1Elementtim-3: Either frequency or when can exist, not both
tim-1: if there's a duration, there needs to be duration units
tim-2: if there's a period, there needs to be period units
tim-9: If there's an offset, there must be a when
tim-6: If there's a periodMax, there must be a period
tim-8: If there's a countMax, there must be a count
tim-7: If there's a durationMax, there must be a duration
tim-4: duration SHALL be a non-negative value
Definition:
A set of rules that describe when the event should occur.


Comments:
Conformance Rule: If an EMR cannot send discrete elements in all cases for timing.repeat element, this is acceptable as long as RENDERED_DOSAGE_INSTRUCTION captures the timing.

.....  boundsPeriod 0..1PeriodDefinition:
boundsPeriod defines the start and/or end date of the period over which all the periods should take place for a given dosage line. For example, if the prescriber wants to a patient to take one pill daily for 10 days, but the prescriber only wants the patient to start taking the pills one week from now, the start date for bounds period would be 10 days from now (if the script was being written on Feb 1st, 2018, the start date within bounds period would be Feb 10th).

.....  count 0..1integerDefinition:
count defines how many time the dosing activities should be repeated across all periods. For example, if a prescriber wants a patient to take 1 pill morning and night every day for 10 days, the dose is 1 pill, the frequency is 2 per day, the period is one day, and the count is 20 doses (corresponding to 10 days times 2 doses per day).


Comments:
If you have both bounds and count, then this should be understood as within the bounds period, until count times happens.

.....  countMax 0..1integerDefinition:
countMax defines the max number of doses that should be taken across all periods within a dosage line. countMax is only used when the count is expressed as a range of values. For example, if a prescriber wants a patient to take a dose of 2 pills per day for 7-10 days, the dose is 2 pills, the frequency is 1 dose per day, the period is 1 days, the count is 7 doses, and the countMax is 10 doses.

.....  duration 0..1decimalDefinition:
duration defines the amount of time it takes to provide a SINGLE dose of a medication to a patient. For most medications, duration is not relevant. However, one example that uses duration would be the application of a patch. The prescriber may instruct the patient to apply a patch for 10 hours each day for 10 days. In this case, the dose would be 1 patch, the duration would be 10 hours, the period would be 1 day, and the count would be 10 doses.


Comments:
For some events the duration is part of the definition of the event (e.g. IV infusions, where the duration is implicit in the specified quantity and rate). For others, it's part of the timing specification (e.g. exercise).

.....  durationMax 0..1decimalDefinition:
durationMax defines the maximum amount of time CAN/SHOULD take to provide a SINGLE dose of a medication to a patient. durationMax implies the usage of a range of values for the duration. For most medications, duration and durationMax is not relevant. However, one example that uses duration and durationMax would be the application of a patch for a range of time each day. The prescriber may instruct the patient to apply a patch for 10-12 hours each day for 10 days. In this case, the dose would be 1 patch, the duration would be 10 hours, the durationMax would be 12 hours, the period would be 1 day, and the count would be 10 doses.


Comments:
For some events the duration is part of the definition of the event (e.g. IV infusions, where the duration is implicit in the specified quantity and rate). For others, it's part of the timing specification (e.g. exercise).

.....  durationUnit 0..1codeBinding: UnitsOfTime (required)
Definition:
The units of time for the duration, in UCUM units.


Comments:
Codes are from http://unitsofmeasure.org (h | d | wk | etc.)

.....  frequency 0..1integerDefinition:
frequency defines the number of times to apply a single dose of a medication within a particular period. For example, the prescriber may instruct the patient to take 1 tablet 3 times per day for 10 days. In this cases, the dose would be 1 tablet, the frequency would be 3 times, the period would be 1 day, and the count would be 30 doses.

.....  frequencyMax 0..1integerDefinition:
frequencyMax defines the maximum number of times to apply a single dose of a medication within a particular period. Using frequencyMax implies that the frequency is a range of values. For example, the prescriber may instruct the patient to take 1 tablet 3-4 times per day for 10 days. In this cases, the dose would be 1 tablet, the frequency would be 3 times, the frequencyMax would be 4 times, the period would be 1 day, and the count would be 30 doses.

.....  period 0..1decimalDefinition:
The period defines the amount of time over which the frequency of doses should occur. For example, the prescriber may instruct the patient to take 1 tablet every day for 10 days. In this case, the period is 1 day.

.....  periodMax 0..1decimalDefinition:
The periodMax defines the maximum amount of time over which the frequency of doses should occur. For example, the prescriber may instruct the patient to apply one patch every 48 to 72 hours and leave the patch on for 12 hour and do this for 1 month. In this case, the dose would be one patch, the frequency would be 1, the duration would be 12 hours, the period would be 48 hours, the periodMax would be 72 hours, and the boundPeriod would be a start day of today and an end date of 2 months from now.

.....  periodUnit 0..1codeBinding: UnitsOfTime (required)
Definition:
The units of time for the period in UCUM units.


Comments:
Codes are from http://unitsofmeasure.org (h | d | wk | etc.)

...  asNeeded[x] 0..1boolean, CodeableConceptBinding: (unbound) (example)
Definition:
Indicates whether the Medication is only taken when needed within a specific dosing schedule (Boolean option), or it indicates the precondition for taking the Medication (CodeableConcept).


Comments:
Conformance Rule: This is ONLY populated when the medication is prescribed on an as needed (i.e. PRN) basis.

Conformance Rule: Set value = true

Conformance Rule: When this is specified, it is not acceptable to express the quantity exclusively as a duration/DAYS_SUPPLY. The DOSAGE_QUANTITY must be provided.

The CodeableConcept should not be used at this time. If it is present, treat it as though the boolean value is set to true.

...  siteCodeableConcept 0..1Shared Health CodeableConcept Required Text with optional code​Binding: PrescriptionAdministrationSite (extensible)
Definition:
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.


Comments:
Conformance Rule: When providing a structured SIG, this should be populated when appropriate. If not structured, this should be part of the SIG (RENDERED_DOSAGE_INSTRUCTION)

...  route 0..1Shared Health CodeableConcept Required Text with optional code​Binding: PrescriptionRouteOfAdministration (extensible)
Definition:
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.


Comments:
Conformance Rule: Coding should be populated if a code is available. However, text is always required.

Also specified for Multi-dosage lines.

...  dose[x] 0..1PrescribeIT Drug Quantity for Administration, PrescribeIT Drug RangeDefinition:
The amount of therapeutic or other substance given at one administration event.


Comments:
Conformance Rule: Could be sent as part of the dosage instruction. OR for those EMRs that can support it, this should be specified.

...  rate[x] 0..1RatioDefinition:
Identifies the speed with which the medication was or will be introduced into the patient. Typically the rate for an infusion e.g. 100 ml per 1 hour or 100 ml/hr. May also be expressed as a rate per unit of time e.g. 500 ml per 2 hours. Currently we do not specify a default of '1' in the denominator, but this is being discussed. Other examples: 200 mcg/min or 200 mcg/1 minute; 1 liter/8 hours.


Comments:
It is possible to supply both a rate and a doseQuantity to provide full details about how the medication is to be administered and supplied. If the rate is intended to change over time, depending on local rules/regulations, each change should be captured as a new version of the MedicationOrder with an updated rate, or captured with a new MedicationOrder with the new rate.

....  numerator 1..1PrescribeIT Drug Quantity for Administrationqty-3: If a code for the unit is present, the system SHALL also be present
sqty-1: The comparator is not used on a SimpleQuantity
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


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

....  denominator 1..1Shared Health Quantityqty-3: If a code for the unit is present, the system SHALL also be present
Definition:
A measured amount (or an amount that can potentially be measured). Note that measured amounts include amounts that are not precisely quantified, including amounts involving arbitrary units and floating currencies.


Comments:
This indicates the unit of time (e.g. per day, every 4 weeks, etc.)

...  maxDosePerPeriod 0..1RatioDefinition:
The maximum total quantity of a therapeutic substance that may be administered to a subject over the period of time. For example, 1000mg in 24 hours.


Comments:
Conformance Rule: When providing a structured SIG, this should be populated when appropriate.

....  numerator 1..1PrescribeIT Drug Quantity for Administrationqty-3: If a code for the unit is present, the system SHALL also be present
sqty-1: The comparator is not used on a SimpleQuantity
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


Comments:
Conformance Rule: Quantity is used throughout the messages. It may be a drug form (e.g. TAB) an adminstratable drug (e.g. PUFF) for or a unit of measure (e.g. mg). If this is provided it is mandatory to send a value from the PrescribeIT™ Drug Quantity.

....  denominator 1..1Shared Health Quantityqty-3: If a code for the unit is present, the system SHALL also be present
Definition:
A measured amount (or an amount that can potentially be measured). Note that measured amounts include amounts that are not precisely quantified, including amounts involving arbitrary units and floating currencies.


Comments:
This indicates the unit of time (e.g. per day, every 4 weeks, etc.)

..  dispenseRequest 1..1BackboneElement1: Must have at least one of quantity and expectedSupplyDuration
3: Must have at least one of total prescribed quantity and total days supply
Definition:
Indicates the specific details for the dispense or medication supply part of a medication order (also known as a Medication Prescription). Note that this information is NOT always sent with the order. There may be in some settings (e.g. hospitals) institutional or system support for completing the dispense details in the pharmacy department.

...  extension 0..*ExtensionSlice: Unordered, Open by value:url
Definition:
An Extension

...  extension
       (dispenseInterval) 		0..1Medication Order Dispense IntervalDefinition:
Optional Extensions Element - found in all resources.


Comments:
Indicates the minimum period of time that must pass between dispensing events.

Conformance Rule: Only days are currently support as a measurement of dispenseInterval.

Example: A prescriber instructs a patient to take 3 Tylenol 3 tablets every day as needed for pain for 90 days. However, the prescriber does not wish the patient to have more than 30 days supply at any given time so the prescriber instructs the pharmacist that the dispenseInterval is 30 days. The pharmacist then does 3 partial fills of 90 tablets (or 30 days supply) over the 90 day period.

...  extension
       (trialEligibility) 		0..1Medication Order Trial Dispense EligibilityDefinition:
Optional Extensions Element - found in all resources.


Comments:
Conformance Rule: If eligible for trial, this must be set to 'true' and presented to the Pharmacist.

Conformance Rule: This is ONLY populated if it is for trial, else it is assumed not to be eligble.

Note: Prescribers may include this information in notes.

...  extension
       (firstFillInstructions) 		0..1Medication Order Dispense First Fill Instructions2: At least one of first fill quantity or first fill days supply must be specified
Definition:
Optional Extensions Element - found in all resources.


Comments:
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')

Conformance Rule: 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.

Usage Note: There are times when a patient's drug plan limits what can be dispensed (i.e. 7 days initially as a trial). In this situation, the patient is informed that their drug plan only pays for 7 days. The pharmacist will ask the patient to sign the Rx that they have been informed are ok with changing the quantity to 7 days and then dispense the 7 days. The patient's file is updated to note that 7 days was dispensed as a trial period. After the initial 7 days, the patient will still have 353 tablets to be used. (90 tabs x 4 authorized fills = 360 tabs - 7 tabs dispensed as trial.

...  extension
       (maxDispense) 		0..1Medication Order Max DispenseDefinition:
Identifies the maximum quantity authorized to be dispensed at one time.


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

Example: A prescriber instructs a patient to take 3 Tylenol 3 tablets every day as needed for pain for 90 days. However, the prescriber does not wish the patient to have more than 30 days supply at any given time so the prescriber instructs the pharmacist that the maxDispense is 90 tablets. The pharmacist then does 3 partial fills of 90 tablets (or 30 days supply) over the 90 day period.

...  extension
       (totalPrescribedQuantity) 		0..1Medication Order Total Prescribed QuantityDefinition:
Optional Extensions Element - found in all resources.


Comments:
Conformance Rule: The Total Prescribed Quantity is not mandatory but must be supplied if the value is entered by the user or can be calculated by the system.

...  extension
       (totalDaysSupply) 		0..1Medication Order Total Prescribed Days SupplyDefinition:
Optional Extensions Element - found in all resources.


Comments:
Conformance Rule: Must be populated when the Total Days Supply is entered by the user or when the Total Days Supply can be calculated by the system.

Conformance Rule: Code must be 'd' and system must be 'http://unitsofmeasure.org'.

...  validityPeriod 1..1PeriodDefinition:
This indicates the validity period of a prescription (stale dating the Prescription).


Comments:
Conformance Rule: Must be either equal to or later then the MedicationOrder.dateWritten element.

....  start 1..1dateTimeDefinition:
The start of the period. The boundary is inclusive.


Comments:
Must be a full date and time with timezone (i.e. yyyy-mm-dd-HH:mm:ss.SSS-ZZZZZ).

....  end 0..1dateTimeDefinition:
The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.


Comments:
Must be a full date and time with timezone (i.e. yyyy-mm-dd-HH:mm:ss.SSS-ZZZZZ).

...  numberOfRepeatsAllowed 0..1positiveIntDefinition:
An integer indicating the number of additional times (aka refills or repeats) the patient can receive the prescribed medication. Usage Notes: This integer does NOT include the original order dispense. This means that if an order indicates dispense 30 tablets plus "3 repeats", then the order can be dispensed a total of 4 times and the patient can receive a total of 120 tablets.


Comments:
Conformance Rule: This must be populated when the number of repeats is 1 or more. As this field only allows a positive integer, this is not populated if there are no refills allowed.

Guidance: For narcotics, if this is incorrectly populated, the PMS could choose not to reject the message; rather they can adjust for the dispense.

...  quantity 0..1PrescribeIT Drug Quantityqty-3: If a code for the unit is present, the system SHALL also be present
sqty-1: The comparator is not used on a SimpleQuantity
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


Comments:
Conformance Rule: If days supply is NOT present, this MUST be populated.

...  expectedSupplyDuration 0..1DurationDefinition:
Identifies the period time over which the supplied product is expected to be used, or the length of time the dispense is expected to last.


Comments:
Conformance Rule: This maps to 'duration' in some EMR's. Must be populated when this is a discrete data element in the EMR; else this is sent as part of the textual description.

Conformance Rule: If Fill Quantity is NOT populated, this must be present.

....  value 1..1decimalDefinition:
The value of the measured amount. The value includes an implicit precision in the presentation of the value.


Comments:
The implicit precision in the value should always be honored.

....  system 1..1uriFixed Value: http://unitsofmeasure.org
Definition:
The identification of the system that provides the coded form of the unit.


Comments:
Fixed value: http://unitsofmeasure.org

....  code 1..1codeFixed Value: d
Definition:
A computer processable form of the unit in some unit representation system.


Comments:
Fixed value: d

..  priorPrescription 0..1Reference(PrescribeIT Prescription) {r}Definition:
A link to a resource representing an earlier order or prescription that this order supersedes.


Comments:
When present with a prescription number, this must be in the same form as was present on the original prescription - generally with a system of OID of the form [vendor root].[application instance node].2 expressed as a urn (e.g. urn:oid:1.2.3.4).

The 'value' element will contain the actual RX Number. Note that the system value must refer to the namespace of the system that created the original prescription, which may not always be the system performing the renewal.

In the context of Task e120-m:

Conformance Rule: This is mandatory and MUST be populated with the EMR generated eRX number (PRESCRIPTION_NUMBER) of the medication used as the basis for the new prescription for the same therapy. Its purpose is to identify the original prescription that drove the creation of this Renewal Fill Request. Note: This identifier may not be recognized by the PMS receiving this as it could have been a paper prescription or an ePrescription that was originally sent to another pharmacy.

For transition period, from paper to electronic, there would not be an EMR-assigned number. In this case, EMR MUST populate with a value of 'NA' in the Identifier.value and omit the system.

In the context of Task e140-m: This should include any prior prescription information that was included in the original prescription request from the EMR that is being cancelled. If the original EMR prescription request has this segment empty, then it should be empty for the e140-m.

In the context Tasks e162-m and e163-m:

Conformance Rule: This is mandatory and MUST be populated with the MedicationOrder.identifier as specified in the p160 being responded to.

In the context of Task p160-m:

Conformance Rule: The MedicationOrder transmitted in a p160 is the prior order that is being asked to be renewed. If this came in as an e110, priorPrescription will be absent. If this came in as an e120, priorPrescription will be present. If it was entered into the PMS as a paper or fax prescription, priorPrescription may not be known (in which case it will be absent), or may be set to 'NA' if the prescription was known to be a renewal, but the prescription identifier of the prior request is unknown).

...  extension 0..*ExtensionSlice: Unordered, Open by value:url
Definition:
An Extension

...  extension
       (identifier) 		0..1Referenced Requisition identifierDefinition:
Allows a reference to identify the target prescription, dispense or task by business identifier rather than URL


Comments:
When this is present, the reference is typically omitted

Usage Note: The URL for this extension does not refer to an existing web-page as is a pre-adoption extension. Refer to the Shared Health implementation Guide for more information.

....  url 1..1uri"http://hl7.org/fhir/StructureDefinition/extension-Reference.identifier"
....  valueIdentifier 1..1PrescribeIT™ Prescriber Prescription IdentifierDefinition:
A technical identifier - identifies some entity uniquely and unambiguously.


Comments:
When this is present, the reference is typically omitted

...  display 0..1stringDefinition:
Plain text narrative that identifies the resource in addition to the resource reference.


Comments:
This can be populated with the prescription number as a human-readable hint for downstream systems that don't recognize the extension. However, there is no known need for this element at present.

This structure is derived from MedicationOrder

Summary

Mandatory: 12 elements (12 nested mandatory elements)
Must-Support: 82 elements
Fixed Value: 3 elements
Prohibited: 3 elements

Structures

This structure refers to these other structures:

Extensions

This structure refers to these extensions:

Slices

This structure defines the following Slices:

  • The element MedicationOrder.identifier is sliced based on the value of value:type

Differential View

This structure is derived from MedicationOrder

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationOrder S0..*
... id S1..1id
... contained S1..*Resource
... extension S0..*ExtensionSlice: Unordered, Open by value:url
... ext-medicationorder-category S0..1Shared Health CodeableConcept Text​Medication Order Category
URL: http://hl7.org/fhir/StructureDefinition/extension-MedicationRequest.category profiled by http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-category
Binding: PrescriptionType (extensible)
... ext-medication-rendered-dosage S1..1stringRendered Dosage Instruction
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medication-rendered-dosage
... ext-medicationorder-protocol S0..10string, uri, Shared Health IdentifierProtocol, order set, guideline, etc.
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-protocol
... ext-medicationorder-treatment-type S0..1code​ACU | CHRON
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-treatment-type
Binding: PrescriptionTreatmentCategory (required)
... ext-medicationorder-supportinginfo S0..*Reference(PrescribeIT List - Allergies | PrescribeIT Pharmacy-related Observation) {b}Allergies, height, weight, etc.
URL: http://hl7.org/fhir/StructureDefinition/extension-MedicationRequest.supportingInfo profiled by http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-supportinginfo
... ext-request-detectedissue S0..*Reference(PrescribeIT DUR) {b}Managed DUR and other issues
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-request-detectedissue
... ext-request-coverage S0..1Reference(PrescribeIT Coverage (NOT SUPPORTED)) {b}Insurance coverage
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-request-coverage
... ext-request-dispenser-instructions S0..1stringDispenser Instructions
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-request-dispenser-instructions
... ext-medicationorder-over-25-dur S0..1booleanMore than 25 DURs?
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-over-25-dur
... ext-medicationorder-monitored-drug S0..1booleanMonitored Drug?
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-monitored-drug
... ext-medicationorder-no-renewals S0..1booleanNo Prescription Renewals?
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-no-renewals
... identifier SShared Health IdentifierSlice: Unordered, Open by value:type
... identifier S1..1PrescribeIT™ Prescriber Prescription IdentifierEMR Prescription ID
.... type S1..1Shared Health CodeableConcept CodeRequired Pattern: {"coding":[{"system":"http://hl7.org/fhir/identifier-type","code":"PLAC"}]}
... identifier S0..2IdentifierDrug Information System's order number
.... type S1..1Shared Health CodeableConcept CodeRequired Pattern: {"coding":[{"system":"http://hl7.org/fhir/v2/0203","code":"RRI"}]}
.... system S0..1uri
.... value S1..1string
... status S1..1codeFixed Value: active
... medicationReference S1..1Reference(PrescribeIT Medication) {c}
... patient S1..1Reference(Shared Health Patient) {b}
... dateWritten SI0..1dateTimecreated-full: Must be at least a full date. i.e. yyyy-mm-dd
... prescriber S1..1Reference(Shared Health Practitioner) {b}
... reasonCode S0..5Shared Health CodeableConcept Required Text with optional code​Binding: PrescriptionIndicationForUse (extensible)
.... coding 0..*Coding
.... text S1..1string
... note S0..1AnnotationMax Length: 2500
.... text S1..1string
... dosageInstruction S0..*BackboneElement
.... extension S0..*ExtensionSlice: Unordered, Open by value:url
.... ext-medication-dosageinstruction-sequence S1..1positiveIntSequence of dosage instruction
URL: http://hl7.org/fhir/StructureDefinition/extension-Dosage.sequence profiled by http://prescribeit.ca/fhir/StructureDefinition/ext-medication-dosageinstruction-sequence
.... ext-medicationorder-dosageinstruction-relationship S0..1code​AND | THEN
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dosageinstruction-relationship
Binding: PrescriptionDosageInstructionLineRelationship (required)
.... text S0..1string
.... additionalInstructions S0..1Shared Health CodeableConcept Text
..... text S1..1stringMax Length: 5000
.... timing S0..1Timing
..... repeat S0..1Element
...... boundsPeriod S0..1Period
...... count S0..1integer
...... countMax S0..1integer
...... duration S0..1decimal
...... durationMax S0..1decimal
...... durationUnit S0..1code
...... frequency S0..1integer
...... frequencyMax S0..1integer
...... period S0..1decimal
...... periodMax S0..1decimal
...... periodUnit S0..1code
...... when 0..0
...... offset 0..0
.... asNeeded[x] S0..1boolean, CodeableConcept
.... siteCodeableConcept S0..1Shared Health CodeableConcept Required Text with optional code​Binding: PrescriptionAdministrationSite (extensible)
.... route S0..1Shared Health CodeableConcept Required Text with optional code​Binding: PrescriptionRouteOfAdministration (extensible)
.... doseQuantity S0..1PrescribeIT Drug Quantity for Administration, PrescribeIT Drug Range
.... rateRatio S0..1Ratio
..... numerator S1..1PrescribeIT Drug Quantity for Administration
..... denominator S1..1Shared Health Quantity
.... maxDosePerPeriod S0..1Ratio
..... numerator S1..1PrescribeIT Drug Quantity for Administration
..... denominator S1..1Shared Health Quantity
... dispenseRequest SI1..1BackboneElement1: Must have at least one of quantity and expectedSupplyDuration
3: Must have at least one of total prescribed quantity and total days supply
.... extension S0..*ExtensionSlice: Unordered, Open by value:url
.... ext-medicationorder-dispense-interval S0..1DurationDispense interval
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-interval
.... ext-medicationorder-dispense-trial S0..1booleanTrial fill authorized?
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-trial
.... ext-medicationorder-dispense-first-fill SI0..1(Complex)First fill instructions
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-first-fill
2: At least one of first fill quantity or first fill days supply must be specified
.... ext-medicationorder-dispense-max S0..1PrescribeIT Drug QuantityMaximum prescribed quantity
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-max
.... ext-medicationorder-total-quantity S0..1PrescribeIT Drug QuantityTotal prescribed quantity
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-total-quantity
.... ext-medicationorder-total-days-supply S0..1DurationTotal prescribed days supply
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-total-days-supply
.... medicationCodeableConcept 0..1Shared Health CodeableConcept Required Text with optional code​Binding: PrescriptionMedicinalProduct (extensible)
.... validityPeriod S1..1Period
..... start S1..1dateTime
..... end S0..1dateTime
.... numberOfRepeatsAllowed S0..1positiveInt
.... quantity SI0..1PrescribeIT Drug Quantity
.... expectedSupplyDuration SI0..1Duration
..... value S1..1decimal
..... comparator 0..0
..... unit 0..1string
..... system S1..1uriFixed Value: http://unitsofmeasure.org
..... code S1..1codeFixed Value: d
... priorPrescription S0..1Reference(PrescribeIT Prescription) {r}
.... extension S0..*ExtensionSlice: Unordered, Open by value:url
.... ext-reference-identifier S0..1Shared Health IdentifierReferenced identifier
URL: http://hl7.org/fhir/StructureDefinition/extension-Reference.identifier profiled by http://sharedhealth.exchange/fhir/StructureDefinition/ext-reference-identifier
..... valueIdentifier S1..1PrescribeIT™ Prescriber Prescription Identifier
.... reference 0..1string
.... display S0..1string

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationOrder SΣ0..*Prescription of medication to for patient
... id SΣ1..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: http://tools.ietf.org/html/bcp47 (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained S1..*ResourceContained, inline Resources
... extension S0..*ExtensionExtension
Slice: Unordered, Open by value:url
... ext-medicationorder-category S0..1Shared Health CodeableConcept Text​Medication Order Category
URL: http://hl7.org/fhir/StructureDefinition/extension-MedicationRequest.category profiled by http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-category
Binding: PrescriptionType (extensible)
... ext-medication-rendered-dosage S1..1stringRendered Dosage Instruction
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medication-rendered-dosage
... ext-medicationorder-protocol S0..10string, uri, Shared Health IdentifierProtocol, order set, guideline, etc.
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-protocol
... ext-medicationorder-treatment-type S0..1code​ACU | CHRON
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-treatment-type
Binding: PrescriptionTreatmentCategory (required)
... ext-medicationorder-supportinginfo S0..*Reference(PrescribeIT List - Allergies | PrescribeIT Pharmacy-related Observation) {b}Allergies, height, weight, etc.
URL: http://hl7.org/fhir/StructureDefinition/extension-MedicationRequest.supportingInfo profiled by http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-supportinginfo
... ext-request-detectedissue S0..*Reference(PrescribeIT DUR) {b}Managed DUR and other issues
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-request-detectedissue
... ext-request-coverage S0..1Reference(PrescribeIT Coverage (NOT SUPPORTED)) {b}Insurance coverage
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-request-coverage
... ext-request-dispenser-instructions S0..1stringDispenser Instructions
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-request-dispenser-instructions
... ext-medicationorder-over-25-dur S0..1booleanMore than 25 DURs?
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-over-25-dur
... ext-medicationorder-monitored-drug S0..1booleanMonitored Drug?
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-monitored-drug
... ext-medicationorder-no-renewals S0..1booleanNo Prescription Renewals?
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-no-renewals
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier SΣShared Health IdentifierAn identifier intended for computation
Slice: Unordered, Open by value:type
... identifier S1..1PrescribeIT™ Prescriber Prescription IdentifierEMR Prescription ID
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?!Σ0..1codeusual | official | temp | secondary (If known)
Binding: IdentifierUse (required)
.... type S1..1Shared Health CodeableConcept CodeConcept - reference to a terminology or just text
Binding: Identifier Type Codes (extensible)
Required Pattern: {"coding":[{"system":"http://hl7.org/fhir/identifier-type","code":"PLAC"}]}
..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... coding SΣCodingCode defined by a terminology system
Slice: Unordered, Open by value:system, value:code
...... id 0..1idxml:id (or equivalent in JSON)
...... extension 0..*ExtensionAdditional Content defined by implementations
...... system SΣ1..1uriIdentity of the terminology system
...... version Σ0..1stringVersion of the system - if relevant
...... code SΣ1..1codeSymbol in syntax defined by the system
...... display Σ0..1stringRepresentation defined by the system
...... userSelected Σ0..1booleanIf this coding was chosen directly by the user
..... coding SΣ1..*CodingCode defined by a terminology system
...... id 0..1idxml:id (or equivalent in JSON)
...... extension 0..*ExtensionAdditional Content defined by implementations
...... system SΣ1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/identifier-type
...... version Σ0..1stringVersion of the system - if relevant
...... code SΣ1..1codeSymbol in syntax defined by the system
Fixed Value: PLAC
...... display Σ0..1stringRepresentation defined by the system
...... userSelected Σ0..1booleanIf this coding was chosen directly by the user
..... text Σ0..1stringPlain text representation of the concept
.... system SΣ1..1uriThe namespace for the identifier
Example General': http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri
.... value SΣ1..1stringThe value that is unique
Example General': 123456
.... period Σ0..1PeriodTime period when id is/was valid for use
.... assigner Σ0..1Reference(Organization)Organization that issued id (may be just text)
... identifier SΣ0..2IdentifierDrug Information System's order number
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?!Σ0..1codeusual | official | temp | secondary (If known)
Binding: IdentifierUse (required)
.... type S1..1Shared Health CodeableConcept CodeConcept - reference to a terminology or just text
Binding: Identifier Type Codes (extensible)
Required Pattern: {"coding":[{"system":"http://hl7.org/fhir/v2/0203","code":"RRI"}]}
.... system SΣ0..1uriThe namespace for the identifier
Example General': http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri
.... value SΣ1..1stringThe value that is unique
Example General': 123456
.... period Σ0..1PeriodTime period when id is/was valid for use
.... assigner Σ0..1Reference(Organization)Organization that issued id (may be just text)
... status ?!SΣ1..1codeactive | on-hold | completed | entered-in-error | stopped | draft
Binding: MedicationOrderStatus (required)
Fixed Value: active
... medicationReference SΣ1..1Reference(PrescribeIT Medication) {c}A reference from one resource to another
... patient SΣ1..1Reference(Shared Health Patient) {b}A reference from one resource to another
... encounter Σ0..1Reference(Encounter)Created during encounter/admission/stay
... dateWritten SΣI0..1dateTimeWhen prescription was authorized
created-full: Must be at least a full date. i.e. yyyy-mm-dd
... prescriber SΣ1..1Reference(Shared Health Practitioner) {b}A reference from one resource to another
... reasonCode S0..5Shared Health CodeableConcept Required Text with optional code​Concept - reference to a terminology or just text
Binding: PrescriptionIndicationForUse (extensible)
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... coding Σ0..*CodingCode defined by a terminology system
..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... system SΣ1..1uriIdentity of the terminology system
..... version Σ0..1stringVersion of the system - if relevant
..... code SΣ1..1codeSymbol in syntax defined by the system
..... display Σ0..1stringRepresentation defined by the system
..... userSelected Σ0..1booleanIf this coding was chosen directly by the user
.... text SΣ1..1stringPlain text representation of the concept
Max Length: 2500
... reasonReference Σ0..*Reference(Condition)Condition that supports why the prescription is being written
... dateEnded Σ0..1dateTimeWhen prescription was stopped
... reasonEnded Σ0..1CodeableConceptWhy prescription was stopped
Binding: (unbound) (example)
... note SΣ0..1AnnotationInformation about the prescription

Max Length: 2500
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... author[x] Σ0..1Reference(Practitioner | Patient | RelatedPerson), stringIndividual responsible for the annotation
.... time Σ0..1dateTimeWhen the annotation was made
.... text S1..1stringThe annotation - text content
... dosageInstruction SΣ0..*BackboneElementHow medication should be taken
.... id 0..1idxml:id (or equivalent in JSON)
.... extension S0..*ExtensionExtension
Slice: Unordered, Open by value:url
.... ext-medication-dosageinstruction-sequence S1..1positiveIntSequence of dosage instruction
URL: http://hl7.org/fhir/StructureDefinition/extension-Dosage.sequence profiled by http://prescribeit.ca/fhir/StructureDefinition/ext-medication-dosageinstruction-sequence
.... ext-medicationorder-dosageinstruction-relationship S0..1code​AND | THEN
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dosageinstruction-relationship
Binding: PrescriptionDosageInstructionLineRelationship (required)
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... text SΣ0..1stringFree text dosage instructions e.g. SIG
.... additionalInstructions SI0..1Shared Health CodeableConcept TextConcept - reference to a terminology or just text
Binding: (unbound) (example)
..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... coding SΣ0..*CodingCode defined by a terminology system
...... id 0..1idxml:id (or equivalent in JSON)
...... extension 0..*ExtensionAdditional Content defined by implementations
...... system SΣ1..1uriIdentity of the terminology system
...... version Σ0..1stringVersion of the system - if relevant
...... code SΣ1..1codeSymbol in syntax defined by the system
...... display Σ0..1stringRepresentation defined by the system
...... userSelected Σ0..1booleanIf this coding was chosen directly by the user
..... text SΣ1..1stringPlain text representation of the concept
Max Length: 5000
.... timing SΣ0..1TimingWhen medication should be administered
..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... event Σ0..*dateTimeWhen the event occurs
..... repeat SΣI0..1ElementWhen the event is to occur
...... id 0..1idxml:id (or equivalent in JSON)
...... extension 0..*ExtensionAdditional Content defined by implementations
...... boundsPeriod SΣ0..1PeriodLength/Range of lengths, or (Start and/or end) limits
...... count SΣ0..1integerNumber of times to repeat
...... countMax SΣ0..1integerMaximum number of times to repeat
...... duration SΣ0..1decimalHow long when it happens
...... durationMax SΣ0..1decimalHow long when it happens (Max)
...... durationUnit SΣ0..1codes | min | h | d | wk | mo | a - unit of time (UCUM)
Binding: UnitsOfTime (required)
...... frequency SΣ0..1integerEvent occurs frequency times per period
...... frequencyMax SΣ0..1integerEvent occurs up to frequencyMax times per period
...... period SΣ0..1decimalEvent occurs frequency times per period
...... periodMax SΣ0..1decimalUpper limit of period (3-4 hours)
...... periodUnit SΣ0..1codes | min | h | d | wk | mo | a - unit of time (UCUM)
Binding: UnitsOfTime (required)
..... code Σ0..1CodeableConceptQD | QOD | Q4H | Q6H | BID | TID | QID | AM | PM +
Binding: TimingAbbreviation (preferred)
.... asNeeded[x] SΣ0..1boolean, CodeableConceptTake "as needed" (for x)
Binding: (unbound) (example)
.... siteCodeableConcept S0..1Shared Health CodeableConcept Required Text with optional code​Concept - reference to a terminology or just text
Binding: PrescriptionAdministrationSite (extensible)
.... route S0..1Shared Health CodeableConcept Required Text with optional code​Concept - reference to a terminology or just text
Binding: PrescriptionRouteOfAdministration (extensible)
.... method Σ0..1CodeableConceptTechnique for administering medication
Binding: (unbound) (example)
.... dose[x] SΣ0..1PrescribeIT Drug Quantity for Administration, PrescribeIT Drug RangeAmount of medication per dose
.... rate[x] SΣ0..1RatioAmount of medication per unit of time
..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... numerator SI1..1PrescribeIT Drug Quantity for AdministrationQuantity of a medication
..... denominator SI1..1Shared Health QuantityA measured or measurable amount
.... maxDosePerPeriod SΣ0..1RatioUpper limit on medication per unit of time
..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... numerator SI1..1PrescribeIT Drug Quantity for AdministrationQuantity of a medication
..... denominator SI1..1Shared Health QuantityA measured or measurable amount
... dispenseRequest SΣI1..1BackboneElementMedication supply authorization
1: Must have at least one of quantity and expectedSupplyDuration
3: Must have at least one of total prescribed quantity and total days supply
.... id 0..1idxml:id (or equivalent in JSON)
.... extension S0..*ExtensionExtension
Slice: Unordered, Open by value:url
.... ext-medicationorder-dispense-interval S0..1DurationDispense interval
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-interval
.... ext-medicationorder-dispense-trial S0..1booleanTrial fill authorized?
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-trial
.... ext-medicationorder-dispense-first-fill SI0..1(Complex)First fill instructions
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-first-fill
2: At least one of first fill quantity or first fill days supply must be specified
.... ext-medicationorder-dispense-max S0..1PrescribeIT Drug QuantityMaximum prescribed quantity
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-dispense-max
.... ext-medicationorder-total-quantity S0..1PrescribeIT Drug QuantityTotal prescribed quantity
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-total-quantity
.... ext-medicationorder-total-days-supply S0..1DurationTotal prescribed days supply
URL: http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-total-days-supply
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... medicationCodeableConcept 0..1Shared Health CodeableConcept Required Text with optional code​Concept - reference to a terminology or just text
Binding: PrescriptionMedicinalProduct (extensible)
.... validityPeriod SΣ1..1PeriodTime period supply is authorized for
..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... start SΣI1..1dateTimeStarting time with inclusive boundary
..... end SΣI0..1dateTimeEnd time with inclusive boundary, if not ongoing
.... numberOfRepeatsAllowed SΣ0..1positiveIntNumber of refills authorized
.... quantity SI0..1PrescribeIT Drug QuantityQuantity of a medication
.... expectedSupplyDuration SΣ0..1DurationNumber of days supply per dispense
..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... value SΣ1..1decimalNumerical value (with implicit precision)
..... unit Σ0..1stringUnit representation
..... system SΣI1..1uriSystem that defines coded unit form
Fixed Value: http://unitsofmeasure.org
..... code SΣ1..1codeCoded form of the unit
Fixed Value: d
... substitution Σ0..1BackboneElementAny restrictions on medication substitution
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... type Σ1..1CodeableConceptgeneric | formulary +
Binding: ActSubstanceAdminSubstitutionCode (example)
.... reason Σ0..1CodeableConceptWhy should (not) substitution be made
Binding: SubstanceAdminSubstitutionReason (example)
... priorPrescription SΣ0..1Reference(PrescribeIT Prescription) {r}An order/prescription that this supersedes
.... id 0..1idxml:id (or equivalent in JSON)
.... extension S0..*ExtensionExtension
Slice: Unordered, Open by value:url
.... ext-reference-identifier S0..1Shared Health IdentifierReferenced identifier
URL: http://hl7.org/fhir/StructureDefinition/extension-Reference.identifier profiled by http://sharedhealth.exchange/fhir/StructureDefinition/ext-reference-identifier
..... id 0..1idxml:id (or equivalent in JSON)
..... url S1..1uri"http://hl7.org/fhir/StructureDefinition/extension-Reference.identifier"
..... valueIdentifier S1..1PrescribeIT™ Prescriber Prescription IdentifierAn identifier intended for computation
.... reference ΣI0..1stringRelative, internal or absolute URL reference
.... display SΣ0..1stringText alternative for the resource

doco Documentation for this format

 

Other representations of profile: Schematron

3.54.3 Terminology Bindings

Terminology Bindings

PathNameConformanceValueSet
MedicationOrder.language?extrequiredhttp://tools.ietf.org/html/bcp47
MedicationOrder.identifier.useIdentifierUserequiredIdentifierUse
MedicationOrder.identifier.typeIdentifier Type CodesextensibleIdentifier Type Codes
MedicationOrder.identifier.useIdentifierUserequiredIdentifierUse
MedicationOrder.identifier.typeIdentifier Type CodesextensibleIdentifier Type Codes
MedicationOrder.statusMedicationOrderStatusrequiredMedicationOrderStatus
MedicationOrder.reasonCodePrescriptionIndicationForUseextensible​PrescriptionIndicationForUse
MedicationOrder.reasonEnded?extexample
MedicationOrder.dosageInstruction.additionalInstructions?extexample
MedicationOrder.dosageInstruction.timing.repeat.durationUnitUnitsOfTimerequiredUnitsOfTime
MedicationOrder.dosageInstruction.timing.repeat.periodUnitUnitsOfTimerequiredUnitsOfTime
MedicationOrder.dosageInstruction.timing.codeTimingAbbreviationpreferredTimingAbbreviation
MedicationOrder.dosageInstruction.asNeeded[x]?extexample
MedicationOrder.dosageInstruction.siteCodeableConceptPrescriptionAdministrationSiteextensible​PrescriptionAdministrationSite
MedicationOrder.dosageInstruction.routePrescriptionRouteOfAdministrationextensible​PrescriptionRouteOfAdministration
MedicationOrder.dosageInstruction.method?extexample
MedicationOrder.dispenseRequest.medicationCodeableConceptPrescriptionMedicinalProductextensible​PrescriptionMedicinalProduct
MedicationOrder.substitution.typeActSubstanceAdminSubstitutionCodeexampleActSubstanceAdminSubstitutionCode
MedicationOrder.substitution.reasonSubstanceAdminSubstitutionReasonexampleSubstanceAdminSubstitutionReason

3.54.4 Constraints

Constraints

IdPathDetailsRequirements
created-fullMedicationOrder.dateWrittenMust be at least a full date. i.e. yyyy-mm-dd
: length()>=10
inv-1MedicationOrder.dosageInstruction.additionalInstructionsMust have coding or text but not both
: coding.exists() xor text.exists()
tim-3MedicationOrder.dosageInstruction.timing.repeatEither frequency or when can exist, not both
: ((period or frequency) and when).not()
tim-1MedicationOrder.dosageInstruction.timing.repeatif there's a duration, there needs to be duration units
: duration.empty() or durationUnit.exists()
tim-2MedicationOrder.dosageInstruction.timing.repeatif there's a period, there needs to be period units
: period.empty() or periodUnit.exists()
tim-9MedicationOrder.dosageInstruction.timing.repeatIf there's an offset, there must be a when
: offset.empty() or when.exists()
tim-6MedicationOrder.dosageInstruction.timing.repeatIf there's a periodMax, there must be a period
: periodMax.empty() or period.exists()
tim-8MedicationOrder.dosageInstruction.timing.repeatIf there's a countMax, there must be a count
: countMax.empty() or count.exists()
tim-7MedicationOrder.dosageInstruction.timing.repeatIf there's a durationMax, there must be a duration
: durationMax.empty() or duration.exists()
tim-4MedicationOrder.dosageInstruction.timing.repeatduration SHALL be a non-negative value
: duration.exists() implies duration >= 0
qty-3MedicationOrder.dosageInstruction.rate[x].numeratorIf a code for the unit is present, the system SHALL also be present
: code.empty() or system.exists()
sqty-1MedicationOrder.dosageInstruction.rate[x].numeratorThe comparator is not used on a SimpleQuantity
: comparator.empty()
qty-3MedicationOrder.dosageInstruction.rate[x].denominatorIf a code for the unit is present, the system SHALL also be present
: code.empty() or system.exists()
qty-3MedicationOrder.dosageInstruction.maxDosePerPeriod.numeratorIf a code for the unit is present, the system SHALL also be present
: code.empty() or system.exists()
sqty-1MedicationOrder.dosageInstruction.maxDosePerPeriod.numeratorThe comparator is not used on a SimpleQuantity
: comparator.empty()
qty-3MedicationOrder.dosageInstruction.maxDosePerPeriod.denominatorIf a code for the unit is present, the system SHALL also be present
: code.empty() or system.exists()
1MedicationOrder.dispenseRequestMust have at least one of quantity and expectedSupplyDuration
: (quantity.empty() and expectedSupplyDuration.empty()).not()
3MedicationOrder.dispenseRequestMust have at least one of total prescribed quantity and total days supply
: extension.where(url='http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-total-days-supply').exists() or extension.where(url='http://prescribeit.ca/fhir/StructureDefinition/ext-medicationorder-total-quantity').exists()
qty-3MedicationOrder.dispenseRequest.quantityIf a code for the unit is present, the system SHALL also be present
: code.empty() or system.exists()
sqty-1MedicationOrder.dispenseRequest.quantityThe comparator is not used on a SimpleQuantity
: comparator.empty()