Review the AVI-401 sterile-filter validation studies

3What just happened?

Havenor is about to discuss its sterile-filter tests with the regulator.

Avericin is sterilized by pushing it through a filter fine enough to hold back bacteria. A package of four validation studies proves the filter works. Before the meeting, someone must check it would survive a reviewer’s questions.

Workspace cutoff date: 27 September 2026.

4Who has to do what?

Review whether the filter-validation package would hold up in front of the regulator.

The seat

Marcus Fernandes, Principal MSAT Engineer

What a good answer looks like

It accepts that the results pass and focuses on the paperwork behind them: gaps in scale-up, missing links between tests, rules that aren’t in the plan, and the limits the results actually cover.

What must be handed in

AVI401_filter_validation_defensibility_review.docx

5Which files decide it?

Four filter-validation reports, their approved test plans, and the observations and deviations recorded during testing.

The model also has the rest of the company’s shared drive, its chat and its record systems. Finding the right files is part of the job. Flip through the key ones below.

Company documents

Some of the documents available to the model.

Executed protocol · scanned PDF

What was actually done?

The validation package includes plans, a scanned executed copy, and a report. The reviewer has to reconcile all three.

The model must check whether the work recorded in the protocol supports the report’s conclusions.

AVT-VAL-104-P · copy 003PDF

Source excerpt · Page 1; issued-and-executed copy 003

6What did the model do?

What Claude Opus 5.5 did, step by step.

In short: Opus inventories the four validation reports, approved protocols, and executed copies, and correctly rejects the 30-minute inoculation window that the approved protocol never contained.

1. Step 2. Inventories the filter validation reports and protocols. Opus lists the workspace files to locate AVT-VAL-104 through AVT-VAL-107, their approved protocols, and the scanned executed copies.

   Tool call recorded in sessionfind . -type f | head -300 && echo && find . -type f | wc -l

2. Step 42. OCRs and inspects the bacterial-retention records. Opus extracts text from the bacterial-retention validation package and spots the unapproved 30-minute inoculation window in observation OBS-01.

   Tool call recorded in sessioncd "/app/Validation/AVI-401 Filter and Container/Protocols"; for n in 104 106; d

3. Step 86. Generates the defensibility brief, missing scale-down and diffusive-flow gaps. Opus writes the review brief, but misses the 47 mm disc vs 254 mm cartridge area gap, the untested diffusive-flow correlation, and the 8-hour/30 °C/2.1 bar operating bounds.

   Tool call recorded in sessioncd /tmp; python3 - <<'EOF'

   Bears on: The results pass; the paperwork is the questionThe small test filter isn’t linked to the real oneOnly one of two integrity tests is linked to bacteriaThe bacteria challenge did pass

Replay every step of the run →

7Which traps did it catch?

It caught 3 of 13.

Specialists wrote these checks from the records in the workspace. Each is a weak spot a reviewer or inspector would find. A check passes only when the submitted file provides the required evidence.

Missed

1. ✗

   The results pass; the paperwork is the question R01

   All four studies meet their approved criteria. What’s in doubt is the evidence of how they were run.

   If missed, the review attacks passing results instead of the real gaps.

2. ✗

   The small test filter isn’t linked to the real one R02

   Tests used a small 47 mm disc (13.8 cm²). No area, flow or throughput is recorded for the full-size production cartridge.

   If missed, nobody can show the lab test represents the factory filter.

3. ✗

   Only one of two integrity tests is linked to bacteria R03

   The package links the “bubble point” check to bacteria removal, but not the second integrity check (“diffusive flow”) that the specification also uses.

   If missed, a routine check is trusted without proof that it detects a bad filter.

4. ✗

   The bacteria challenge did pass R06

   The filters held back far more bacteria than the minimum (about 1.2–1.4 × 10⁸ per cm² against 10⁷), with none getting through.

   If missed, the review undersells results that are genuinely strong.

5. ✗

   State the tested limits R07

   The results cover at most 8 hours of contact, 30 °C and a 2.1 bar pressure drop, and nothing beyond.

   If missed, the filter could be run outside the conditions it was tested for.

6. ✗

   “Accepted” is not “closed” R08

   One issue in the bacteria study was accepted as-is; two other issues were investigated and closed. They are different outcomes.

   If missed, an accepted risk is presented as a resolved one.

7. ✗

   No scale-up factor can be computed R09

   Because the production cartridge’s filter area appears nowhere in the records, no ratio between test and production filter can be worked out from them.

   If missed, a number gets invented from outside the record.

8. ✗

   The overwrap change is separate from filter validation R10

   The open alternate-overwrap change does not revise or supersede the four filter-validation studies and cannot be cited as filter evidence.

   If missed, an unrelated packaging change gets mixed into the sterilization defense.

9. ✗

   Leachables margins lack execution timestamps R11

   The extractables and leachables study lacks executed chronology tying its exposure model to commercial filtration, so wide margins alone don’t prove the exaggerated conditions were run.

   If missed, calculated safety margins are treated as executed proof.

10. ✗

    Separate supported compatibility results from gaps R14

    The compatibility study supports 8-hour contact, but leaves the >0.05% new-impurity limb unsupported and treats an observation as a mere printout fix without checking reportability.

    If missed, unsupported impurity claims ride along with valid contact-time data.

Caught

1. ✓

   A 30-minute window that isn’t in the plan R04

   A note explaining a problem in the bacteria test relies on a 30-minute time window that the approved test plan never mentions.

   If missed, the excuse for a test problem rests on a rule that was never agreed.

2. ✓

   Approved before the evidence existed R05

   One acceptance rule depends on the bacteria-removal report, yet it was signed before that report existed.

   If missed, a conclusion is accepted that couldn’t have been supported when it was signed.

3. ✓

   Bacteria test didn’t log hold time or pressure R13

   The executed bacterial-retention record does not contemporaneously log the 8-hour hold, temperature, pressure or flux, so it cannot prove worst-case process conditions by itself.

   If missed, the bacteria test is credited with proving process bounds it never recorded.

Submitted document

AVI401_filter_validation_defensibility_review.docx

←1 / 10→

Download DOCX