US Medication Risk Evaluation and Mitigation Strategies (REMS) FHIR IG
2.0.0-ballot - STU 2 Ballot

US Medication Risk Evaluation and Mitigation Strategies (REMS) FHIR IG, published by HL7 International / Pharmacy. This guide is not an authorized publication; it is the continuous build for version 2.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-medication-rems-ig/ and changes regularly. See the Directory of published versions

Plain Language Summary goes here

## REMS IG Home Page

### Overview

A Risk Evaluation and Mitigation Strategy (REMS) is a drug safety program that the United States Food and Drug Administration (FDA) requires for medications with serious safety concerns. REMS are designed to reinforce medication use behaviors and actions that support the safe use of the medication. While all medications have labeling that informs health care stakeholders about medication risks, only a small number of medications require REMS programs.

This implementation guide focuses on provider workflows during the ordering of REMS medications and associated patient encounters. It defines information exchanges to support those events, including interactions between…

- the provider and the REMS Administrator that manages the associated program
- the provider and the pharmacy to which the prescription is sent for dispensing
- the pharmacist or other involved party and the REMS Administrator, to learn the status of REMS steps associated with a patient prescription and/or additional REMS requirements for which they are responsible (discuss)
- new or existing intermediaries in place to facilitate easier communication between the various parties including the provider, REMS Administrator, and pharmacist

The guide describes the use of FHIR features including CDS Hooks and SMART App Launch to exchange REMS-related information between providers and REMS Administrators during patient care, and it provides guidance for including REMS-related information in the resulting prescription sent to the pharmacy in an NCPDP SCRIPT transaction.

The goal of this guide is to establish information exchange conventions that support…

- notifying providers and patients of REMS requirements early in the ordering process
- satisfying REMS information needs using data from the patient's electronic record where possible–minimizing manual data entry
- capturing information about a specific patient's participation in a REMS program–including identifiers or other information assigned by the REMS Administrator–in the Provider System
- reducing prescription fulfillment delays by completing up-front REMS steps before the order is sent to the pharmacy and including relevant REMS information in the prescription
- enabling those involved in fulfilling the prescription to learn of their responsibilities and the status of other REMS requirements
- enabling an approach that is congruent with the Da Vinci prior authorization (PA) related IGs, CRD and DTR, mitigating implementation burden as often both PA and REMS are applicable

… with the aim of ensuring safe use in a way that gets the medication to the patient quicker.

### Content and organization

The implementation guide is organized into the following sections:

- REMS Steps and Terminology provides the high-level set of steps and timeframes the IG uses as the context for its guidance. It also describes how REMS steps fit within e-prescribing workflows and provides guidance for integrating related FHIR and NCPDP SCRIPT exchanges
- Participant Roles and Needs identifies the REMS program participants, the systems they use, and their needs addressed by this implementation guide
- Use Cases introduces the REMS workflows, identifies the participants and scenarios covered by the guide, and describes how the associated systems interact to support the process goals
- REMS Interaction Events and Triggers provides guidance for initiating interactions between the Provider System (e.g., an EHR) and REMS Administrator System at appropriate points in the patient's care
- Future Directions discusses REMS flows and features that are not covered in this version of the IG, but are the focus of continued efforts
- Technical Background describes the specifications this implementation guide relies on and indicates what developers should read and understand prior to implementing this specification, including US Core profiles used in this IG.. It also provides background and rationale for key aspects of the IG's approach, and describes how approaches used in this guide relate to those employed in the Da Vinci "Burden Reduction" guides
- Formal Specification provides detailed implementation requirements and conformance expectations related to:
  - this IG's use of CDS Hooks conventions for triggering exchanges and exchanging information in different scenarios
  - guidance related to the SMART on FHIR app launch process and associated workflows
  - REMS-specific and general FHIR requirements related to security and patient privacy
- CDS Hooks Card Profiles formally defines content for CDS Hooks cards and system actions returned in REMS flows
- Artifacts introduces and provides links to the FHIR resource profiles and other FHIR artifacts defined in this implementation guide
- Downloads allows download of this and other specifications as well as other useful files
- Credits identifies the individuals and organizations involved in developing this implementation guide

### Dependencies

This implementation guide relies on the following other specifications:

- CDS Hooks 2.0 - The official standard for trial use publication of CDS Hooks that defines the CDS Hooks protocol and interfaces used by this implementation guide
- SMART on FHIR 2.2 - The specification provides a reliable, secure authorization protocol for SMART apps launched from a clinical system or standalone application to support REMS information capture and data exchange
- FHIR R4 - The current official version of FHIR as of the time this implementation guide was published
- US Core 3.1.1 - The current published version of US Core profiles based on FHIR R4

### Sponsoring HL7 Workgroup

Pharmacy

### Co-Sponsors

Clinical Decision Support Biomedical Research & Regulation

### Authors

HL7 Pharmacy Work Group
Frank McKinney | fm@frankmckinney.com
Robert Dingwell | bobd@mitre.com
Patrick LaRocque | plarocque@mitre.com
Lauren DiCristofaro | laurend@mitre.org

### Dependencies

IG | Package | FHIR | Comment
--- | --- | --- | ---
US Medication Risk Evaluation and Mitigation Strategies (REMS) FHIR IG | hl7.fhir.us.medication-rems#2.0.0-ballot | R4 |
HL7 Terminology (THO) | hl7.terminology.r4#6.5.0 | R4 | Automatically added as a dependency - all IGs depend on HL7 Terminology
FHIR Extensions Pack | hl7.fhir.uv.extensions.r4#5.2.0 | R4 | Automatically added as a dependency - all IGs depend on the HL7 Extension Pack
US Core | hl7.fhir.us.core#3.1.1 | R4 | Defines U.S. EHR expectations on a range of resources that will be passed to and/or queried by REMS CDS servers
SMART App Launch | hl7.fhir.uv.smart-app-launch#2.2.0 | R4 | Defines base expectations and profiles for SMART app launch requirements
CDS Hooks | hl7.fhir.uv.cds-hooks#2.0.1 | R4 | Defines cds hooks protocol
FHIR Tooling Extensions IG | hl7.fhir.uv.tools.r4#0.8.0 | R4 | for example references

### Cross Version Analysis

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.medication-rems.r4) and R4B (hl7.fhir.us.medication-rems.r4b) are available.

### Global Profiles

There are no Global profiles defined

### IP Statements

This publication includes IP covered under the following statements.

- ISO maintains the copyright on the country codes, and controls its use carefully. For further details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
  Show Usage
  - ISO 3166-1 Codes for the representation of names of countries and their subdivisions — Part 1: Country code: MedicationRemsCapabilityStatementProviderSystem, MedicationRemsCapabilityStatementRemsAdministratorSystem, MedicationRemsTaskSmartLaunch and REMS
- This material contains content from LOINC. LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.
  Show Usage
  - LOINC: DocumentReference/example-rems-docref-1
- Using RxNorm codes of type SAB=RXNORM as this specification describes does not require a UMLS license. Access to the full set of RxNorm definitions, and/or additional use of other RxNorm structures and information requires a UMLS license. The use of RxNorm in this specification is pursuant to HL7's status as a licensee of the NLM UMLS. HL7's license does not convey the right to use RxNorm to any users of this specification; implementers must acquire a license to use RxNorm in their own right.
  Show Usage
  - RxNorm: Parameters/parameters-rems-etasu-input