This page is part of the Specialty Medication Enrollment (v2.0.0-ballot: STU2 Ballot 1) based on FHIR R4. . For a full list of available versions, see the Directory of published versions

IG Home Page

This version of the IG includes new content to support requesting and sharing consents that are frequently needed when fulfilling specialty product prescriptions.

Additions in version 2.0.0 (STU2 ballot)

• Consent workflows gives an overview of consent scenarios supported by the guide.
• Requested consent profile conveying the appropriate blank consent form
• Consent profile for completed specialty consents
• Task profile used to request consent.. This profile is used in an exchange process based on the FHIR workflow management option POST of Task to fulfiller's system.
• Terminology:
  • New value in the specialty-rx-task-type code system and value set
  • New value in the specialty-rx-task-input-type code system and value set
  • New specialty-rx-task-output-type code system and value set
• New examples:
• Requested Consent resource (containing a blank consent form)
• Completed Consent resource
• Task illustrating a consent request
• Completed Task after consent is obtained

Overview

This FHIR implementation Guide describes the exchange of patient demographic, clinical 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).

Background

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.

Scope of This Guide

This guide addresses the exchange of information to support specialty medication fulfillment functions, including:

• medication dispensing and billing
• specialty enrollment for programs or services
• facilitation of clinical care management, education, and training.

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.

Content and Organization

The guide is organized into the following sections:

• Use Cases and Roles gives an overview of the guide’s goals and participants.
• Systematic Query Workflows describes the exchanges that retrieve information systematically from the patient’s records.
• Information Flows Requiring Human Interaction describes a process enabling the prescriber or staff to provide information through a SMART application launched from the EHR.
• Consent Workflows gives an overview of consent scenarios supported by the guide.
• Search Conventions defines required and recommended searches and conventions for specifying searches in Specialty Rx messages.
• Patient Matching describes methods for identifying the patient for whom information is being exchanged.
• Message Structures and Message Submission give details related to the Specialty Rx messaging options.
• Error Handling defines expectations for handling exception situations.
• Conformance Expectations defines use of Must Support elements and also describes conventions for situations where information is not available.
• Intermediary Facilitation describes how an intermediary can enable exchange between implementers of the guide’s RESTful and messaging options.
• Security provides information for implementers related to security and privacy.
• Specialty Rx Profiles, Terminology and Examples lists all profiles and terminology defined in this guide. It also provides examples instances that conform to the guide’s profiles.
• Applicable US Core Profiles defines expectations for the use of US Core profiles in the guide’s searches.
• Capability Statements defines sets of guide functionality that can be implemented individually or in combination.

FHIR Basics

For those new to FHIR, the material below describes basic FHIR principles and gives guidance for reading FHIR specifications.

• FHIR overview
• Developer’s introduction (or Clinical introduction)
• FHIR data types
• Using codes
• References between resources
• How to read resource & profile definitions
• Base resource

Authors

HL7 Pharmacy Workgroup
NCPDP Workgroup 18 - Specialty Requirements for ePrescribing Taskgroup
Frank McKinney	frank.mckinney@pocp.com