Specialty Medication Enrollment, published by HL7 International - Pharmacy. This is not an authorized publication; it is the continuous build for version 2.1.0). This version is based on the current content of https://github.com/HL7/fhir-specialty-rx/ and changes regularly. See the Directory of published versions
This FHIR implementation Guide describes the exchange of patient demographic, clinical, consent and coverage data to support fulfillment of specialty medication prescriptions by pharmacies, and enrollment of patients into related support programs offered by parties such as Hub vendors and pharmaceutical manufacturers.
This guide is the result of collaboration between HL7 and the National Council for Prescription Drug Programs (NCPDP).
Specialty medications are generally defined as those of high cost or requiring special handling. The use of these medications may be constrained based on indication for use, risks to patient health vs. potential benefits, cost, etc.
There can be different settings for administration as well as limitations on where they can be dispensed. Additional steps in the prescribing and dispensing process may exist, including the need to share consent information. Consent may be needed to authorize contact by patient support programs, sharing of patient clinical and other information to support steps to obtain insurance coverage or other financial support, etc.
The current process for exchanging information to support specialty medication fulfillment is complex and manual, often resulting in delays of days to weeks before patients can begin their therapy. This is caused largely by the absence of an industry standard for exchanging clinical data needed to dispense specialty medications and enroll the patient into associated support and savings programs.
NCPDP created a task group to focus on the exchange of this data, with the goal of reducing the time to therapy for a patient who has been prescribed a specialty medication. The group identified demographic, clinical and coverage information needed to support the process, and defined data exchange workflows between the clinic, pharmacy and other fulfilling parties to efficiently deliver the data to the parties that need it.
This information is outside of the scope of the NCPDP e-prescription standard that conveys specialty orders to pharmacies in the US today. After an extensive analysis of the types of information required beyond what is carried in the prescription, the task group determined that developing an implementation guide using HL7 FHIR would be the best approach for meeting this need. Exchange of that information is the focus of this guide.
This guide addresses the exchange of information to support specialty medication fulfillment functions, including:
The guide does not address transmission of the original prescription from the prescriber to dispensing pharmacy, which is typically accomplished in the US using the NewRx message defined in the NCPDP SCRIPT standard.
Further, the exchanges described in the guide are not intended to be used to request a change to a received prescription or to propose a particular clarification; these functions are supported by the NCPDP SCRIPT RxChangeRequest and RxChangeResponse messages.
This implementation guide is intended be used in the United States. It reflects US pharmacy processes and conventions.
The guide is organized into the following sections:
For those new to FHIR, the material below describes basic FHIR principles and gives guidance for reading FHIR specifications.
HL7 Pharmacy Workgroup | |
NCPDP Workgroup 18 - Specialty Requirements for ePrescribing Taskgroup | |
NCPDP Workgroup 10 / 11 - Patient Consent Taskgroup | |
Frank McKinney | frank.mckinney@pocp.com |
IG | Package | FHIR | Comment |
---|---|---|---|
Specialty Medication Enrollment | hl7.fhir.us.specialty-rx#2.1.0 | R4 | |
HL7 Terminology (THO) | hl7.terminology.r4#5.0.0 | R4 | Automatically added as a dependency - all IGs depend on HL7 Terminology |
US Core | hl7.fhir.us.core#3.1.1 | R4 |
Package hl7.fhir.us.core#3.1.1 |
This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (hl7.fhir.us.specialty-rx.r4) and R4B (hl7.fhir.us.specialty-rx.r4b) are available.
There are no Global profiles defined
This publication includes IP covered under the following statements.