Identify the REMS program requirements for the target drug via the FDA REMS database (accessdata.fda.gov/scripts/rems); confirm which transaction model applies—some REMS programs require prescriber enrollment, patient enrollment, or pharmacy certification
Implement the NCPDP SCRIPT 2017071 REMSInitiationRequest transaction: populate with prescriber NPI, patient demographics, drug NDC, and REMS program identifier; transmit to the REMS data hub or registry endpoint designated by the drug manufacturer
Receive the REMSInitiationResponse: parse REMSStatus (Compliant, NonCompliant, PendingCertification) and required compliance actions; if NonCompliant, surface the specific REMS requirement gap to the prescriber (e.g., prescriber not enrolled, required lab not on file)
For programs requiring patient enrollment (e.g., iPLEDGE for isotretinoin), integrate with the REMS program's own patient registry API or portal; NCPDP SCRIPT REMS transactions may complement but not fully replace program-specific registry interactions
Transmit the NewRx only after REMSInitiationResponse confirms Compliant status; do not transmit prescriptions for REMS-restricted drugs without confirmed REMS compliance status
At the pharmacy, verify REMS compliance again before dispensing: some REMS programs require a pharmacy-level dispense authorization check with the REMS registry on the day of dispensing
Known gotchas
REMS programs vary significantly in their technical implementation; not all REMS programs support NCPDP SCRIPT REMS transactions—some rely entirely on proprietary manufacturer web portals or phone hotlines, making electronic integration partial or unavailable
REMS requirements and authorized dispensing pharmacies can change when FDA approves REMS modifications; integrate periodic checks against the FDA REMS database to detect program changes that may affect your workflow
Dispensing a REMS drug without documented REMS compliance verification is a serious regulatory violation that can result in FDA enforcement action against the pharmacy; never bypass REMS status checks even when the REMS system is slow or unresponsive
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp