Regulatory Record
FDA Form 483
FDA investigators Lillian S. Wu and Youkeun Kim, working out of the Seattle District Office, closed a ten-day inspection of Cascade Specialty Pharmacy, LLC in Poulsbo, Washington on July 17, 2026, documenting…
Cascade Specialty Pharmacy FDA 483: 6 Observations at Poulsbo, Washington and the Quality Management System Pattern Every Compounding Pharmacy Should Assess
Source Context
On this recordRecord overview
Regulatory Event
FDA investigators Lillian S. Wu and Youkeun Kim, working out of the Seattle District Office, closed a ten-day inspection of Cascade Specialty Pharmacy, LLC in Poulsbo, Washington on July 17, 2026, documenting six observations issued to Pharmacist in Charge and General Manager Chad R. Tinnes. The Form 483 records what investigators observed during the inspection — it is not a finding that Cascade violated any regulation, and the company has 15 business days to respond before FDA determines whether the response is adequate. What makes this 483 worth a closer read is its breadth: across six observations, investigators touched quality-unit oversight, batch-record completeness, cleaning-validation evidence, finished-product release testing, incoming-component identity testing, and the facility’s stability program — six of the load-bearing systems a compounding pharmacy’s Corrective and Preventive Action (CAPA) program is supposed to hold up. No single technical process failed here; the 483 reads as a quality management system that has gaps at nearly every checkpoint a batch passes through, from raw material receipt to finished-product release.
Observation 1, which maps to the quality-unit responsibilities and procedures requirement at 21 CFR 211.22(d), found that the pharmacist-verification role defined in Cascade’s own written procedure was not being applied with enough rigor to catch an incomplete compounding record. The example cited — a Gabapentin 100 mg/mL suspension stock solution whose compounding record described the container only as “Bottle with Insert and Dosing Syringe,” without specifying material or type — is a small-looking gap with a real consequence: without knowing the actual container-closure system, there is no basis for confirming it resists leaching, permeability, or seal failure over the solution’s assigned storage period. Observation 2, under the batch-record completeness requirement at 21 CFR 211.188, extends the same pattern to production instructions themselves: an Amoxicillin/Clavulanate suspension record did not specify tablet-pulverization duration or quantity, and a Methimazole cream record did not describe how product should be transferred into its dispensing syringe. Records this thin do not just risk documentation citations — they mean the process itself cannot be reliably reproduced by a different operator on a different day, which is the practical definition of a validation gap hiding inside a paperwork gap.
What the Record Documents
Observation 3, cited under the equipment cleaning and maintenance procedure requirement at 21 CFR 211.67(b), is the observation with the clearest patient-safety signal. Cascade compounds beta-lactam drug substances in a non-dedicated work area alongside other non-sterile hazardous drugs, and relies solely on the deactivating-agent manufacturer’s claims — not an in-house efficacy study — to establish that beta-lactam residue is actually being deactivated and that the contact time used is sufficient. Beta-lactam cross-contamination is a well-documented sensitization and allergic-reaction risk in compounding settings precisely because trace residue in a shared, non-dedicated space can carry into an unrelated patient’s medication; a facility that has not verified its own deactivation chemistry under its own operating conditions is relying on an assumption where verification is the standard practitioners in this space are expected to meet.
Observation 4, under the testing-and-release requirement at 21 CFR 211.165(a), documents that Cascade performs routine potency testing only on in-process materials for its Levothyroxine Sodium and Liothyronine Sodium lines and does not perform finished-product identity or strength testing more broadly. The two examples in the 483 — a Trilostane 58 mg capsule and a Gabapentin 100 mg/mL suspension — were both released based on theoretical potency calculated from the quantities of components used in production, with no analytical confirmation that the finished product actually met its labeled strength. Observation 5, addressing component testing at 21 CFR 211.84(d)(2), shows the same reliance-on-paper pattern moved upstream: Trilostane powder, Methimazole powder, and Itraconazole powder were each accepted into production based solely on the supplier’s certificate of analysis, with no in-house identity testing and no program demonstrating that those suppliers’ CoAs are themselves reliable over time. Observation 6, under the stability-testing requirement at 21 CFR 211.166(a), completes the pattern: Cascade has no written stability testing program of its own and assigns beyond-use dates based on stability data generated by other entities or on general assumptions tied to dosage form and storage condition, rather than data generated for its own formulations and processes.
Technical and Quality Context
Individually, several of these observations resemble findings common at small and mid-size compounding pharmacies still building out a full Current Good Manufacturing Practice (CGMP)-equivalent quality infrastructure. Read together, though, they describe a facility where verification — of container suitability, of process reproducibility, of cleaning efficacy, of finished-product identity and strength, of incoming-material identity, and of shelf life — has been substituted with assumption or reliance on a third party’s word at nearly every stage. The International Council for Harmonisation’s (ICH) Q10 Pharmaceutical Quality System model treats this kind of pattern as a management-review and CAPA-effectiveness signal rather than six unrelated technical gaps: a functioning quality system is expected to have already surfaced and corrected at least some of these six gaps through routine internal review, long before an FDA investigator found all of them in the same ten-day inspection.
This inspection also has site history worth noting as context, not as part of the new findings. FDA’s public Warning Letter archive shows that this same Poulsbo, Washington address — then operating as Poulsbo Compounding Pharmacy LLC, dba Cascade Specialty Pharmacy — received a Warning Letter dated October 9, 2020, following a Form 483 issued April 17, 2019, which cited insanitary-conditions concerns including inadequate aseptic smoke studies. That 2020 enforcement action addressed different specific citations than this 2026 483, and none of the six new observations references the earlier inspection or any prior corrective action as unimplemented. But a site with a documented Warning Letter in its history returning six years later with six new observations spanning most of its core quality system is a pattern worth watching for a Warning Letter response standard: FDA’s evaluation of the forthcoming 483 response will likely weigh this site’s compliance trajectory, not just the technical adequacy of each individual corrective action.
Decision Relevance
Quality directors at compounding pharmacies — particularly 503A and hazardous-drug-handling operations reading this before their own inspection — should treat this 483 as a prompt to check three things independently of their next scheduled audit: whether every finished non-sterile product batch has a documented identity and strength release test rather than a theoretical-potency calculation; whether cleaning and deactivation procedures for hazardous or beta-lactam production areas are supported by an in-house efficacy study rather than a supplier’s general claim; and whether beyond-use dating is backed by the facility’s own stability data rather than borrowed data from another entity’s process.
XGene Consulting helps compounding pharmacies and hazardous-drug manufacturers build finished-product release testing programs, design and document cleaning-validation studies for shared non-dedicated production areas, and establish CAPA effectiveness-check processes that demonstrate — with evidence, not just a closed ticket — that corrective actions actually changed practice on the floor. If your site is preparing for its next FDA inspection, the question worth asking now is not whether your quality unit has procedures on paper, but whether those procedures are actually being followed at the point of production.
Primary regulatory references
Connected intelligence
Continue through the evidence graph.
Article
OOS Root Cause Analysis — Moving Beyond ‘Analyst Error’
"Analyst error" is not a root cause — it is a conclusion in search of evidence, and FDA’s May 2022 Level 2 revised OOS guidance is…Article
Chiral Drug Substances: Stereospecific Synthesis, Enantiomeric Purity, and the ICH Q6A Specification Strategy
More than half of the small molecule drugs approved by FDA in any given year contain at least one stereocenter. For most of those programs, the…Article
CAPA Effectiveness Verification — Closing the Loop FDA Actually Closes
An FDA investigator reviewing your CAPA system is not interested in how many CAPAs you have opened — they are interested in how many you have…Article
CareFusion 213, LLC (BD) Class I Recall — ChloraPrep Sterile Antiseptic Applicators: The Sterile Manufacturing System Failure Behind the Recall and What Every Aseptic Processing Director Must Address
CareFusion 213, LLC, a subsidiary of Becton, Dickinson and Company (BD), has recalled two configurations of its BD ChloraPrep One-Step and FREPP Clear sterile antiseptic applicators…From record to action
Use the evidence in context.
Continue into related XGene analysis or discuss the technical implication when the issue needs action.
