BRENNEN

Industries / Health / Healthcare / Pharmacy / Specialty pharmacy

Data for drug makers

Specialty pharmacies report to the makers of the drugs they dispense: what was shipped and to how many patients, how much stock is on hand, why a patient paused or stopped, and, for drugs under an FDA safety program, proof that each fill met the program's conditions.

7

Milestones achieved, from 1998 to 2026.

1

To watch for: announced, not yet confirmed outside.

2

Open deliverables. Nobody has shipped them.

The road

AchievedWatch forOpen

Achieved

  1. 1998

    Pharmacies register to dispense

    When the FDA approved thalidomide in July 1998 for a complication of leprosy, its maker, Celgene, put it under a program called S.T.E.P.S. (System for Thalidomide Education and Prescribing Safety). Prescribers, pharmacies and patients all had to register; pharmacies agreed to check patient identity and monitoring before dispensing; and women who could become pregnant needed a negative pregnancy test before treatment and at set times during it. A 2006 review by FDA and Celgene staff counted about 124,000 patients registered from September 1998 to December 2004; one woman was found pregnant while taking the drug, and two others were already pregnant before they started. The designers drew on earlier controls for isotretinoin and clozapine and wrote that the program "may provide a model" for other drugs with grave risks.

    europepmc.orgeuropepmc.org

    Credit

    J. B. Zeldis and colleagues at Celgene; K. Uhl and colleagues at the FDA

  2. 2007

    FDA can require REMS

    The Food and Drug Administration Amendments Act of 2007 let the FDA require a drug maker to run a Risk Evaluation and Mitigation Strategy (REMS), a safety program for a drug with a serious risk. The strictest REMS carry "elements to assure safe use", which typically require clinicians or health care settings, and for some drugs pharmacies, to be certified before they prescribe or dispense. FDA counts more than 300 REMS approved since 2008; 68 are in force now, 56 (82%) of them with such elements, and they include specialty drugs from lenalidomide for myeloma to Tysabri for multiple sclerosis.

    accessdata.fda.govaccessdata.fda.govfda.gov

    Credit

    US Congress; FDA

  3. 2011

    Court protects prescriber data sales

    Pharmacies record which doctor prescribed which drug and sell the records to "data miners", who produce reports on prescriber behaviour that drug makers use to target sales visits. Vermont barred pharmacies from selling these records without the prescriber's consent and barred drug makers from using them for marketing. On 23 June 2011 the US Supreme Court, 6 to 3 in an opinion by Justice Anthony Kennedy, struck the law down as a content- and speaker-based burden on protected expression. Data companies and the brand-name drug makers' trade group had brought the suit.

    LessonIn the US a state may not single out drug marketing among the uses of prescription records.

    law.cornell.edu

    Credit

    US Supreme Court, Sorrell v. IMS Health Inc

  4. 2013

    Selling patient data needs consent

    HIPAA is the US health privacy law. Since a HIPAA rule of 25 January 2013, a pharmacy or other covered entity may not take payment for a patient's protected health information without the patient's written authorization. Some disclosures are exempt, such as those for treatment and payment, and for research when the only payment is a reasonable cost-based fee. Data de-identified under HIPAA's rules, either by removing 18 kinds of identifiers (names, all date elements except the year, most of the ZIP code and others) or by an expert's finding that the risk of identifying anyone is very small, falls outside the rule.

    ecfr.govecfr.gov

    Credit

    US Department of Health and Human Services

  5. 2016

    REMS checks enter pharmacy messages

    Pharmacies carry much of the REMS work, confirming forms and enrollments before each fill; one estimate quoted in 2016 put setting up a REMS in a hospital at 160 hours of pharmacy work. For some drugs the check runs inside the insurance claim: for fast-acting fentanyl products under the TIRF REMS, claims pass through a switching company, RelayHealth, which rejects the claim back to the pharmacy if the prescriber has not met the requirements. In 2016 NCPDP reported that it had finished REMS transactions for SCRIPT. REMS fields such as patient and prescriber enrollment numbers and an authorization number are carried in the new-prescription message of SCRIPT version 2017071, the version Medicare adopted, though the current HL7 guide for these fields only encourages sending them and says its guidance was not tested with pharmacists.

    pmc.ncbi.nlm.nih.govhl7.org

    Credit

    NCPDP; FDA; RelayHealth

  6. 2018

    A framework for real-world evidence

    Section 3022 of the 21st Century Cures Act of 2016 required the FDA to build a program for using real-world evidence, evidence drawn from data collected in ordinary care, to help support approval of new uses for approved drugs and to meet post-approval study requirements. FDA's framework of December 2018 defines real-world data as data on patients' health or care "routinely collected from a variety of sources", such as health records, claims and billing data and registries. Its main tool for drug safety, the Sentinel System, already ran on medical claims and pharmacy dispensing data covering more than 100 million people through 18 data partners as of August 2018.

    fda.gov

    Credit

    US Congress; FDA

  7. 2026

    Paid for data never sent

    In Medicaid's drug rebate rules a bona fide service fee is a fee a drug maker pays at fair market value "for a bona fide, itemized service actually performed on behalf of the manufacturer". On 10 August 2026 Veloxis Pharmaceuticals, maker of the kidney transplant drug Envarsus XR, agreed to pay more than $46 million to resolve criminal and civil kickback allegations, by the US Justice Department's account. In the civil settlement Veloxis admitted that from 2017 to 2023 it paid specialty pharmacies per patient and per month to buy Envarsus instead of competing drugs, including a cheaper generic, that its contracts falsely described the payments as being for "enhanced services" such as data collection or adherence services, and that it paid "regardless of whether they provided any data". The civil settlement comes to $34.45 million for the United States and certain states. A deferred prosecution agreement with a $10.04 million criminal penalty covers kickbacks to transplant doctors and staff, and a $1.55 million penalty covers payments to physicians that were not reported to CMS.

    LessonA data fee paid whether or not data arrives pays for the prescription, not the data.

    ecfr.govjustice.gov

    Credit

    US Attorney's Office for the District of Massachusetts; HHS-OIG; FBI Boston

Watch for

  1. REMS checks by machine

    CodeX, a member-driven HL7 community, is building with MITRE a way for prescriber and pharmacy systems to check REMS conditions automatically. The prescriber's record system asks the REMS administrator what is needed through FHIR, and a mock pharmacy system checks the safe-use conditions before releasing a prescription, exchanging NCPDP SCRIPT messages. HL7's US Medication REMS FHIR guide is at version 2.0.0, built on 17 November 2025, and the open-source prototype, produced for the US government, was still being updated in November 2026. It runs on made-up data and encodes three programs: iPLEDGE, the TIRF fentanyl program and Turalio.

    Achieved whenAt least one live REMS program accepts these checks from a real pharmacy system and publishes counts of fills checked and delays avoided.

    hl7.orggithub.com

    Claimed by

    HL7 CodeX and MITRE, November 2025 and November 2026

Open

  1. 01

    Every REMS, coded for pharmacies

    A public, machine-readable table of what a pharmacy must do under each current REMS: whether it must be certified, what it must check before each fill (prescriber and patient enrollment, an authorization number, a lab or pregnancy test and its time window), limits on days' supply or refills, counseling, what it must report back to the program, and how the check is made (web, phone or claims switch). Each cell links to the sentence in the FDA-approved REMS document. Then encode programs in the HL7 REMS format and run them in the open prototype on made-up patients.

    The brief
    Credit · unclaimed
  2. 02

    An open patient-status feed

    An open, documented schema for the data specialty pharmacies send drug makers (dispenses and shipments, stock on hand, and patient status such as waiting for approval, on hold or stopped, with the reason), mapped to X12's public 852 and 867 transactions and to the FHIR MedicationDispense resource. Publish synthetic sample files for made-up patients, a validator that checks files against the schema and finds planted errors, and a privacy check that reports how many records are unique on the fields HIPAA's Safe Harbor method leaves in.

    The brief
    Credit · unclaimed

Open 01 · the brief

Every REMS, coded for pharmacies

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

A public, machine-readable table of what a pharmacy must do under each current REMS: whether it must be certified, what it must check before each fill (prescriber and patient enrollment, an authorization number, a lab or pregnancy test and its time window), limits on days' supply or refills, counseling, what it must report back to the program, and how the check is made (web, phone or claims switch). Each cell links to the sentence in the FDA-approved REMS document. Then encode programs in the HL7 REMS format and run them in the open prototype on made-up patients.

Why it is still open

FDA's REMS data files flag, for each version of each program, whether dispensers must be certified, but not what a pharmacy must check, in what time window, or how. By this research's count about 60 current program versions in FDA's November 2026 file carry the dispenser flag, though FDA warns that the file's active and inactive marks are not accurate. MITRE's open prototype encodes only iPLEDGE, the TIRF fentanyl program and Turalio.

accessdata.fda.govgithub.com

Built with what exists

FDA's four REMS data files (programs, versions, products and materials, as CSV) and the REMS documents they point to; MITRE's open-source rems-admin and its mock pharmacy system, PIMS (Apache-2.0); the HL7 US Medication REMS FHIR guide; a low-cost AI model for repeated extraction, such as Meta's Muse Ember (see the Note "The jobs agents repeat"), drafting rows that a pharmacist checks.

  1. First step

    Download the four FDA files, list current versions with the dispenser flag, and hand-code the lenalidomide, pomalidomide and thalidomide programs as the template.

  2. Done looks like

    Every program whose current version carries the dispenser flag coded, each duty linked to its source sentence; two pharmacists code 20 programs independently and their agreement is reported; at least 10 programs encoded in the prototype and run on five made-up patients each, with the expected dispense-or-hold result for every patient; the table refreshed within a month of each FDA change to a program.

Open 02 · the brief

An open patient-status feed

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

An open, documented schema for the data specialty pharmacies send drug makers (dispenses and shipments, stock on hand, and patient status such as waiting for approval, on hold or stopped, with the reason), mapped to X12's public 852 and 867 transactions and to the FHIR MedicationDispense resource. Publish synthetic sample files for made-up patients, a validator that checks files against the schema and finds planted errors, and a privacy check that reports how many records are unique on the fields HIPAA's Safe Harbor method leaves in.

Why it is still open

NCPDP publishes a Specialty Pharmacy Data Reporting standard that "provides a standardized format for the data submitted by specialty pharmacy to drug manufacturers", but "Membership in NCPDP is required for access to standards", so outsiders cannot read it or test against it. A GitHub search in November 2026 found an EDI 852-to-CSV converter and a synthetic analytics project modelled on commercial claims and specialty pharmacy data, but no open feed schema, sample files or validator. In the 2026 Veloxis settlement, a drug maker admitted paying pharmacies "data collection" fees whether or not any data arrived.

standards.ncpdp.orgjustice.gov

Built with what exists

Synthea (Apache-2.0) for made-up patients; X12's public descriptions of the 852 Product Activity Data and 867 Product Transfer and Resale Report transactions; HL7 FHIR R4 MedicationDispense; JSON Schema and a Python validator, with Frictionless Data or Great Expectations for checks; the Safe Harbor identifier list in 45 CFR 164.514; a coding agent such as Claude Code to write and test the validator.

x12.org

  1. First step

    Draft the field list from the public X12 and FHIR descriptions, generate 1,000 Synthea patients on two invented drugs, and write the first 20 planted error types.

  2. Done looks like

    A documented schema of at least 40 fields; synthetic files for 10,000 made-up patients across 10 invented drugs; a validator that finds at least 95% of 500 planted errors of 20 types, with its false-alarm rate on clean files reported; a table showing, for cohorts of 50, 500 and 5,000 patients, the share of records unique on year of birth, the first three ZIP digits, sex and drug; everything under an open licence, with the field list reviewed by at least one specialty pharmacy data team.