Each active's assessment, the plant map, holds and supplier questionnaires
- Change controls screened as they arrive
- A potency score with each rule shown
- Holds placed when a crossing turns credible
A nitrosamine risk assessment solution for multi-product drug substance plants. It draws each product's route and each shared solvent, vessel and water line on one map, then works the limit wherever an amine can meet a nitrosating source.
Follow the toluene path from map to client letter ↓Assessments are written one active at a time, from the route as filed and a stack of supplier questionnaires. In a multi-product API plant the toluene, the filter-dryer and the purified water are shared, and a solvent recovered from one product's mother liquors can end up washing another product's cake. Neither product's assessment owns that path.
Then a change control lets recovered solvent into a wash step. Its risk section checks purity and water, calls the nitrosamine question same solvent, and passes as minor. Batches are made and shipped for months while the old assessment still says no nitrosating agent, until a periodic review, the client's own testing or an inspector asks where the solvent came from.
Built forNitrosamine risk assessorsPlant QA headsQC laboratory headsRegulatory CMC leads
Every active gets its own assessment, so a solvent recovered from one product and reused in another belongs to none of them.
Stitched together by hand
Built-in controls
The client hears from its API maker first, with each limit, its source and the test plan in one signed letter.
The assessor runs the read and confirms the score; QC and QA sign the test plan; the QA head reads both holds, then signs the letter.
demoThe plant, its clients, suppliers, people, batches and change controls are sample data, as is each figure on these screens.
Four people share one assessment; nobody approves their own part.
Each active's assessment, the plant map, holds and supplier questionnaires
Approve test plans and assessments, read holds, sign what goes to clients
Method needs, contract-lab requests and the certificate when it returns
The drug master file and what it says the plant does
Eight agents read, trace, score and draft; people confirm, approve and sign.
Reads each master production instruction and marks the amines and nitrosating sources on each stage.
Reads the recovered-solvent, equipment and water records and draws who shares what.
Screens each change control since each product's last assessment and reopens a crossing it touches.
Scores each possible drug-related nitrosamine feature by feature from the published tables.
Divides each acceptable intake by the daily dose and works the tenths, totals and what-if doses.
Chooses batches and analytes, checks each LOQ and drafts the contract-lab request.
Drafts supplier questionnaires, the client letter and the master-file hand-off.
Attacks the score and draft as an inspecting agency's assessor would.
Past the crossing: the record that started it, the suppliers, the waiting draft, the changes left for a person, the client's view and the trail.
demoSample data, from the working solution.
A nitrosamine risk assessment is the first of FDA's three steps for nitrosamine impurities: find where an amine and a nitrosating source can meet in the route, the materials and the shared plant, then decide what to test and change. Here agents draw that across the whole plant and keep it open as change controls arrive.
The potency category comes from the categorization approach in FDA's guidance on acceptable intake limits for drug substance-related impurities. The scorer shows each feature and rule, a person confirms the category, and the limit in parts per million is the acceptable intake divided by the client's maximum daily dose.
FDA recommends reusing recovered material only in the same or an earlier step of the process it came from. The shared-asset tracer reads the solvent log, so a solvent recovered from one product and used in another opens a crossing on both.
Under FDA's guidance, a nitrosamine found above one tenth of its acceptable intake limit is tested on release. The limits screen puts that tenth beside each planned LOQ before the plan is signed.
The plant's QA head signs it, after opening the quality agreement and only once the potency category is confirmed and the test plan approved. Batches already at the client's drug product maker, and release to market, are for the client's own quality and regulatory people; the letter says so.
A template is filled in once and filed. Here the assessment is drafted in FDA's three steps from the map, the sums and the signed test plan, and any change control touching a solvent, reagent, vessel or water reopens it.
Investigations that start from the chemistry, with a rising unknown caught before a limit.
1-min demoAPI Batch Production Record ReviewQA decides exceptions instead of reading pages, and a hand adjustment in a logbook reaches the investigation before the next batch runs.
1-min demoDrug Master File (DMF) & CEP AuthoringThe holder finds its own gap and tells the client first, so each client's filing rests on a file that matches the plant.
1-min demoSend one product's production instructions, its recovered-solvent log and the change controls since its last assessment; we will draw its crossings and work the limits.