This page provides a list of the FHIR artifacts defined as part of this implementation guide.
• You can download a list of CSVs for the profiles here.
• A zip of formatted Excel files for profiles is here.
Extensions
The set of 'extra' elements that have been defined to supplement the capabilities of the base FHIR resources to meet the implementation guide requirements.
- Medication Code is Representative
- Medication Dispense Quantity Remaining
- Medication Dosage Instruction Sequence
- Medication Rendered Dosage Instruction
- Medication Order Category
- Medication Order Monitored Drug
- Medication Order No Renewals
- Medication Order Dispense First Fill Instructions
- Medication Order Dispense Interval
- Medication Order Dosage Instruction Relationship
- Medication Order Indication Priority
- Medication Order Max Dispense Quantity
- Medication Order - Over 25 DUR
- Medication Order Protocol
- Medication Order Supporting Information
- Medication Order Total Prescribed Days Supply
- Medication Order Total Prescribed Quantity
- Medication Order Treatment Type
- Medication Order Trial Dispense Eligibility
- Medication Strength Description
- Request-related Coverage (NOT SUPPORTED)
- Request-related Detected Issues
- Request Dispenser Instructions
- Task Based On
- Task DIS Notification
- Task Do Not Autofill
- Task Effective Date/Time
- Task Message
- Task Reason
- Task Request Reason
- Task Requisition Id
Data Type Profiles
Constraints and extensions on the FHIR data types used throughout the implementation guide
Abstract Profiles
High-level, shared constraints and extensions on FHIR resources used by the implementation guide. These profiles are not used directly in the specification but serve as a foundation for other profiles that are used within the tasks and interactions.
Payload Resource Profiles
General constraints and extensions on FHIR resources used by the implementation guide. These profiles are referenced by Tasks and Interactions or by resources that are referenced by Tasks or Interactions
- PrescribeIT™ Communication - Task message
- PrescribeIT™ Communication
- PrescribeIT™ Coverage (NOT SUPPORTED)
- PrescribeIT™ Detected Issue - DUR
- PrescribeIT™ Dispense
- PrescribeIT™ Formulary Operation Output
- PrescribeIT™ List - Allergies
- PrescribeIT™ Observation - Pharmacy-related
- PrescribeIT™ Prescribable Item
- PrescribeIT™ Prescription
- PrescribeIT™ New Prescription
- PrescribeIT™ Renewal Prescription
Task Profiles - Current
Profiles for all of the Tasks defined as part of this implementation guide and the constraints associated with each
- Task e110-m - New RX Fill Request
- Task e120-m - Renewal RX Fill Request
- Task e140-m - Cancel RX Fill Request
- Task e161-m - RX Response - Denied
- Task e162-m - RX Response - Approved
- Task e163-m - RX Response - Approved with Changes
- Task e164-m - RX Response - Under Review
- Task e180-m - Deferred RX Fill Request
- Task p141-m - Cancel RX Request Denied
- Task p142-m - Cancel RX Request Approved
- Task p143-m - Cancel RX Remaining Fills Revoked
- Task p160-m - RX Renewal Create Request
- Task p200-m - RX Dispense Notification
- Task p210-m - RX Dispense Cancel Notification
Interaction Profiles
Profiles used to define communication interactions for this implementation guide. Two types of profiles are defined. The 'Bundle' profiles define the root set of content allowed to be shared. For messaging interactions, the 'MessageHeader' profiles define the messaging events and the focal ''data'' resources for each message.
- Interaction Message Header 101 - Execute tasks from an EMR
- Interaction Message Header 201 - Execute tasks from a PMS
- Interaction Message Header 305 - Send Clinician Communication
- Interaction Message Header 401 - Execute Deferred Prescription from an EMR
- Interaction Bundle 101 - Execute Tasks from an EMR
- Interaction Bundle 201 - Execute Tasks from a PMS
- Interaction Bundle 305 - Send Clinician Communication
- Interaction Bundle 401 - Send Deferred Tasks from an EMR
- Interaction Bundle - Non-authoritative Deferred Message Queue Response
Conformance Statements
Descriptions of the types of systems that can participate in PrescribeIT™ and what the expectations of each of those systems are.
Examples
Examples of the different interactions supported by this specification.
- A1 - 401 Simple new medication request (e180-Ventolin)
- A2 - 201 RX Dispense Notification (p200-Ventolin)
- A3 - 201 RX Dispense Cancel Notification (p210-Ventolin)
- A5 - 201 Cancel RX Request Accepted (p210-Ventolin)
- B1 - 101 Narcotic new medication request (e110-Metadol)
- B2 - 101 Cancel Rx Request (e140-Nicoderm)
- B3 - 201 Cancel refusal (p141-Metadol)
- C1 - 101 Multiple new medication and device requests (e110s-Prednisone, Nicoderm and Strips)
- C2 - 101 Cancel RX Fill Request (e140-Nicoderm)
- C3 - 201 RX Dispense Notification (p200-Ventolin) and Cancel RX Remaining Fills Revoked (p143-Ventolin)
- D1 - 101 Multiple medication requests (e110s-Dimenhydrinate and Cloxacillin)
- E1 - 201 Multiple Renewal requests (p160s-Prednisone, Nicoderm, Strips, and Compound)
- E3 - 101 Multiple Renewal responses and new renewal (e120-Ventolin, e161-Nicoderm, e162-Strips, e163-Prednisone, and e164-Compound)
- F1- 305 Clinician Communication - Locum to Organization
- F1 - 305 Clinician Communication - Organization to Practitioner
- F1 - 305 Clinician Communication - Practitioner to Organization
- Formulary Response
- Undirected retrieval query response