USP Chapters 795, 797 and 800, the FDA Distinction Between Section 503A and 503B, State Board Compounding Rules and DSCSA Tracing for Outsourcing Facilities: Compliance for US Compounding Software

A Compendium, a Statute, Fifty Boards and a Supply Chain Law

Compounding compliance arrives from four distinct sources that bind in different ways, and separating them is the first step toward specifying compounding compliance software that fits the operation.

Compendial chapters set standards for practice, acquiring force through state board adoption, federal reference and professional expectation, and they have been revised with their official status changing over time.

A federal statute distinguishes traditional compounding from outsourcing facility operation, and that distinction determines which body of federal requirements applies.

State boards regulate compounding within their jurisdictions, with rules that differ and in a number of states exceed compendial baselines. And supply chain tracing law applies to outsourcing facilities in their role within distribution.

A platform built against one of these and reviewed against the others afterwards will need substantial rework, which is why compounding compliance software is specified before design rather than after it.

This is educational content, not legal advice, and requirements change. Compliance is the architectural layer of the full custom software development guide to custom compounding platform development, expressed through web application development in the records staff actually keep.

The FDA Distinction Between Section 503A and 503B

What Section 503A Covers

Compounding by a licensed pharmacist or physician, generally pursuant to a prescription for an identified individual patient, with exemptions from certain federal requirements where the section’s conditions are met.

Regulation falls principally to state boards of pharmacy. The conditions and their scope belong with counsel.

What an Outsourcing Facility Takes On

Registration with FDA, the ability to compound without patient-specific prescriptions, compliance with current good manufacturing practice, inspection by FDA, adverse event reporting, product reporting, and additional obligations.

This is a substantially heavier regime and the step into it is a strategic decision rather than an operational one.

Why This Determines Architecture

Batch production records under a quality system, release by a quality unit distinct from production, formal deviation and investigation processes, change control, supplier qualification and stability programs belong to the second regime and not the first.

A platform built for one and adapted for the other produces something that satisfies neither, which is why the question comes before requirements rather than during them.

USP Chapters 795, 797 and 800

The standards that define practice, addressed here structurally since their criteria belong in the current chapters rather than in an article.

The nonsterile chapter addresses compounding of nonsterile preparations, covering personnel training and evaluation, facilities and equipment, components, master formulation and compounding records, beyond-use dating, quality assurance and documentation.

The sterile chapter addresses sterile compounding with a considerably heavier apparatus: personnel training, garbing and competency including media fill and gloved fingertip testing, facility design and engineering controls, air quality classification, environmental monitoring, cleaning and disinfection, sterilization and depyrogenation where applicable, dating criteria that differ by preparation category, and quality assurance.

The hazardous drugs chapter addresses handling throughout receipt, storage, compounding, administration and disposal, with containment, engineering controls, personal protective equipment, personnel training and an assessment of risk in defined circumstances.

These chapters have been revised and their official status has shifted over time, which makes working from current versions essential rather than advisable, and several state boards incorporate them with their own variations.

For the platform: records, monitoring, training, dating inputs and documentation structured to what the current chapters require for the operation’s scope.

Work from the current chapters and the state board, and never publish criteria. Settling the regime question is what early consulting does, covered in Rebuilding Twice Is the Default.

State Board Compounding Rules

The layer that makes a single national answer impossible and that organizations shipping across state lines underestimate.

State boards of pharmacy regulate compounding within their jurisdictions through licensure, inspection and rules that address sterile and nonsterile compounding, facility requirements, personnel, record-keeping, dating, labeling and in many cases specific restrictions on what may be compounded.

Several states adopt compendial chapters by reference, sometimes a specific version, sometimes with amendments. Several impose requirements exceeding compendial baselines. Several have adopted rules in response to compounding incidents that are stricter than federal or compendial expectations.

Non-resident licensure matters particularly: a pharmacy shipping a compounded preparation into another state generally requires licensure there, with that state’s inspection and rules potentially applying.

Which means an organization serving multiple states is meeting multiple rule sets, and an inspection from any of them may examine the records.

For the platform: records sufficient for the strictest applicable jurisdiction rather than the most convenient, licensure held per state with expiry, and configuration where genuine differences require different handling.

Verify with each board of pharmacy where you are licensed, and never publish rules.

DSCSA Tracing for Outsourcing Facilities

The supply chain obligation that applies in the outsourcing facility context and that a 503A pharmacy generally encounters from the other side as a dispenser.

Federal drug supply chain security requirements establish a system for identifying and tracing certain prescription drugs through distribution, with obligations covering product identification at package level, transaction information exchange between trading partners, verification of product identifiers, response to suspect and illegitimate product, and authorized trading partner requirements.

Requirements have phased in over time with enhanced interoperable obligations and associated timelines that have been subject to stabilization and exemption periods, which makes current status something to confirm rather than assume.

An outsourcing facility’s position within the chain determines which obligations attach and in what capacity.

For the platform: product identifiers applied and recorded where required, transaction information captured and exchangeable with trading partners, verification capability, suspect product handling as a defined process, and records retained for the required period.

Trading partner status verification where obligations apply. And the connection to the traceability chain already built, since internal lot traceability and external supply chain tracing are related but not identical and both are needed.

Confirm current requirements and timelines, and never publish obligations.

Other Obligations

Controlled substance requirements where applicable, with their own record-keeping, security and reporting. Labeling requirements, which differ between patient-specific and office use and between regimes.

Adverse event reporting obligations. Occupational safety requirements for personnel, including hazardous drug exposure. Waste handling for hazardous drug and chemical waste.

Patient privacy obligations where patient information is held. Accreditation where sought, including compounding-specific programs.

Payer and contract requirements where preparations are billed. Veterinary compounding requirements where applicable, which have their own framework.

Equipment calibration and qualification requirements. And record retention across formulation, compounding, monitoring and distribution records, which is long.

What This Means for the Build

Five positions follow, and the first precedes architecture entirely, which is what separates compounding compliance software from a compliance review.

The regime settled before design, since the obligations differ in kind and a shared record with a flag is the architecture that gets rebuilt.

Lot-level traceability in the first data model, because retrofitting a chain onto records that did not capture component lots is close to a rewrite.

Dating as a recorded determination with its inputs and basis, never as a computed output.

Compounding records captured as work happens with no pre-population, no back-filling and corrections under documented practice.

And records built to the strictest applicable jurisdiction rather than the most convenient, since a non-resident license means another state’s board may examine them.

The first two are the ones that produce the rebuild, which is why the final article in this cluster is about exactly that. Which obligations become concrete product structure is mapped in Compounding Pharmacy Software Features.

Conclusion

Settle the regime before design, since the two sets of obligations differ in kind rather than degree.

Build lot traceability into the first data model because it cannot be added later. Record dating as a determination with its basis. Build records to the strictest state you are licensed in.

And work from current chapter versions rather than remembered ones, since this material has been revised. This is educational content, not legal advice. Obtain regulatory counsel and confirm with your boards of pharmacy, then brief the software companies in the United States quoting you on where the platform’s job stops.

FAQ