503A vs 503B: what changes for the software
Sections 503A and 503B of the Federal Food, Drug, and Cosmetic Act draw the line between two kinds of compounding operations, and the line runs straight through the software each one needs. A system built for one side of the line does not satisfy the other.
The legal frame, in brief
A 503A compounding pharmacy compounds for an identified individual patient on a prescription. Its primary regulator is the state Board of Pharmacy, and its practice standards arrive largely through USP General Chapters: <795> for nonsterile preparations, <797> for sterile preparations, <800> where hazardous drugs are handled. Compounding under 503A is exempt from certain federal requirements, including full current Good Manufacturing Practice, provided the section's conditions are met.
A 503B outsourcing facility registers with FDA, may compound without patient-specific prescriptions, may distribute across state lines at scale, and is held to current Good Manufacturing Practice under 21 CFR Parts 210 and 211. It is inspected by FDA, reports adverse events, and reports its products to FDA twice a year.
What that means for the record
| Dimension | 503A pharmacy | 503B outsourcing facility |
|---|---|---|
| Unit of record | The prescription and the dispensing event | The batch and its electronic batch record |
| Primary oversight | State Board of Pharmacy | FDA, under cGMP (21 CFR 210/211) |
| Dating | Beyond-Use Date under USP <795>/<797> | Expiration dating supported by stability under cGMP, with BUD provisions where applicable |
| Traceability | Prescription to patient; component lots supporting recall | Bidirectional lot genealogy: component lot to unit shipped, unit to every input |
| Release | Pharmacist final verification under the pharmacy's permit | Quality-unit release discipline with documented signatures and segregation of duties |
Where software projects go wrong
The recurring failure is carrying a 503A mental model into a 503B build. A dispensing system tracks prescriptions; an outsourcing facility needs a manufacturing record: a Master Formulation Record under change control, an electronic batch record whose phases gate on the checks each phase prescribes, environmental monitoring bound to the session it covers, and an audit trail that satisfies 21 CFR Part 11. None of that is a feature you add to a pharmacy system in a later sprint. It is the data model.
The reverse error also costs money: imposing full cGMP recordkeeping on a 503A pharmacy that the law does not require it of. The pharmacy drowns in ceremony, and the staff route around the system, which is worse than having no system, because the record now disagrees with the work.
Questions to ask a software vendor
- Which section does the data model assume, 503A or 503B, and where is that visible in the record structure?
- For 503B: where does the electronic batch record live, and what stops a phase from advancing on an open requirement?
- For 503A: how is the Beyond-Use Date assigned, surfaced at the point of pick, and escalated as it approaches?
- For either: when a recall question arrives, is the answer a query or a reconstruction from paper?