WorkflowQuality Control Laboratory

Analytical Data Review by Exception

Analytical data review for drug-substance QC labs: agents re-perform each second-person check of a chromatography sequence from the raw records. Each check settles under its injection with the record behind it, and the reviewer rules on and signs only the exceptions.

Follow one HPLC sequence from 1,204 checks to four ↓
Watch with transcript →
The problem

A reviewer reads chromatogram after chromatogram and misses the run before it

Before a result is reported, a second person owes the raw data, each calculation, system suitability, the standards, each integration and the audit trail. In most labs that means opening chromatograms one by one, re-keying a few sums, filtering the audit trail and signing a checklist in LIMS. The balance printout sits in a scanner tray while the typed weight sits in LIMS, and the two are rarely on the same screen.

Attention spreads thin across dozens of injections a sequence and a full queue a day. A swapped digit in a standard weight, or a single injection run under a sample's name before the sequence started and never processed, is exactly what a tired eye passes and an inspector reading the audit trail asks about.

Built forQC data reviewersQC laboratory headsQC analystsQA data integrity leads

The Problem Today

A second person owes every raw record and every sum, so reviewers read each chromatogram by eye.

Checked by eye, one at a time

  • Peaks
  • Weights
  • Sums
  • Audit trail
  • Typed weights slip throughThe printout and the LIMS entry seldom sit side by side
  • Unreported runs stay hiddenAn injection outside the sequence never reaches the results

The Solution

  1. Each check under its injectionSix check rows re-performed from raw data, each mark citing its record
  2. Challenged as an inspector wouldEach exception and each agent draft asked which record proves it
  3. Unknown injections fingerprintedCompared with each solution in the run before anyone concludes
  4. People rule and countersignThe reviewer rules, the analyst corrects, the lab head countersigns

Built-in controls

  • No check passes without its record
  • Nobody reviews a sequence they ran
  • A ruling that lets results stand waits for a second person

What You Get

Review moves from reading each chromatogram to ruling on the few things the records cannot settle.

  • Each check shows its recordClients and inspectors follow any mark to the data behind it
  • New reviewers rule like veteransPast rulings quoted, approved rules applied to the method
  • Clients get the summary they were promisedEach finding and what was done, after the review is signed
Features

Analytical data review of one HPLC sequence, exception by exception

A 42-injection HPLC sequence with release and stability samples: the reviewer rules, the analyst corrects, and the head of the QC laboratory countersigns before the review is signed.

demoThe lab, its clients and people, the sequences and each result shown are sample data.

  1. 01Sequence strip

    Review by exception for HPLC: every check settled under its injection

    • Six check rows per injection. System suitability, standards, integration, calculations, identity and audit trail each settle as a mark the reviewer can open to its record.
    • An injection outside the sequence shown first. A run made before the sequence started gets its own tile, so an unreported injection is in front of the reviewer instead of deep in the trail.
    • Only what the records could not settle. The reviewer works four exceptions in run order and can steer the agents to the release samples first.
  2. 02Fingerprint

    Unreported injection identified by impurity fingerprint, not by its name

    • Compared with every solution in the run. Impurity levels and vial position say what was in the vial, so nobody concludes from a sample name typed into a template.
    • The overlay on the run. The reviewer sees the injection laid over the solution it matches and the sample it was named for.
  3. 03Ruling

    Audit trail rows behind a data integrity ruling, then a countersignature

    • Audit trail read from before the run. The look-back starts ahead of the sequence, so a run made before it starts is read with the data it touches.
    • Facts given, intent never stated. The agents report what was injected, when and under which name; the reviewer rules and nobody's motive goes on the record.
    • A ruling that lets results stand waits. The head of the QC laboratory countersigns after opening the same records, and the review cannot be signed before then.
  4. 04Inspector's read

    A challenger that catches the agents' own label and their own rounding

    • Which record proves this. Each exception is questioned the way an inspector reading the audit trail would question it, before the reviewer opens it.
    • The agents' drafts are challenged too. A label taken from a sample name is withdrawn and a sum of rounded values is corrected before either reaches the reviewer.
  5. 05Weight

    Balance printout against the LIMS entry, calculations re-performed both ways

    • Printout and typed value side by side. A transposed standard weight is caught against the scanned printout, which is the additional check a hand-typed entry needs.
    • Every reported value recomputed. The reviewer sees whether the error changes a result before deciding how to send it back.
  6. 06Manual integration

    Manual integration checked against the method's own rule and past rulings

    • Both integrations computed. Skim and drop line results sit next to the method text, so the ruling rests on the rule and not on a feel for the peak.
    • Earlier rulings quoted. The reviewer sees how the lab ruled on the same exception last time, including the send-backs.
  7. 07Method edit

    Processing method edits after acquisition re-run in both versions

    • Version history with the analyst's reason. An edit made after acquisition is laid out line by line, with the inhibit window highlighted.
    • Results kept from both versions. Reprocessed results stay on the record for review, and the reviewer sees that no reported peak moved.
  8. 08Correction

    The analyst corrects the LIMS entry; the reviewer cannot

    • Correction by the person who made the entry. The analyst types the printed weight, gives the reason and signs, and the original stays readable in LIMS.
    • Rechecked before it is confirmed. The agents re-run the calculation, and the reviewer confirms only after opening the corrected entry.
  9. 09Sign-off

    Second person review sign-off blocked until the lab head countersigns

    • Coverage by check row. The sign-off lists how many checks each row holds, how many settled and how each exception closed.
    • Blockers named on screen. The reviewer's signature stays off while any exception is open, and the screen says which one.

The reviewer rules, the analyst corrects, the lab head countersigns

The people who buy and run second-person review in a QC laboratory.

QC data reviewers

Second-person review of each sequence before results are reported

  • Four exceptions to read, each with its record
  • Past rulings quoted on the same exception
  • Clean sequences signed in bulk after a sampled look
QC laboratory heads

Countersign data integrity rulings and approve CAPAs, rules and settings

  • The same records the reviewer opened
  • Rules that apply only after approval
  • A lab incident path when nothing explains a run
QC analysts

Run the sequences and correct their own entries when sent back

  • The printout beside the entry to fix
  • Corrections that keep the original readable
  • No review of their own sequences
QA data integrity leads

Re-read a monthly sample of completed reviews and each data integrity ruling

  • Each settled check with its record
  • Disagreement that reopens the review
  • One audit trail of people and agents
More screens

Three agreeing rulings on the same skim become a rule the lab head can approve

Past the sequence: the lab's rules, the signed review, the day's queue, the trail, the client's summary and QA's sample.

A review rule proposed from the reviewers' own rulingsTwo rules are active; a third, for the same manual skim, is ready once three rulings agree, and it applies only after the head of the QC laboratory approves it.
The signed review, with a different person at each stepAll six check rows settled; the ruling, the send-back, the correction, the countersignature and the CAPA approval each carry their own signer, time and reason.
The day's queue, release tests firstEighteen sequences with clocks: two already reviewed, one waiting for a scanned printout, and eleven read clean that can be signed in bulk after a sampled look.
People and agents on one audit trailEach ruling, send-back, correction and countersignature with its signer, reason and meaning, beside the agents' own steps, exportable as CSV.
The client's quality reviewer sees a signed summary of findingsAfter the review is signed, the client reads what was found and what was done for its release tests, under its quality agreement; a question goes to a person.
QA re-reads a sample of signed reviewsThe QA data integrity lead opens each sampled review record before agreeing; a disagreement clears the reviewer's signature and sends it to the lab head.

demoSample data, from the working solution.

A data integrity ruling needs two signatures before the review gets one

Each person signs as themself, after opening what they sign.

QC data reviewer
Sees
The exception, its records and the inspector's questions
Signs
Each ruling, send-back and confirmation, then the review
QC analyst
Sees
The printout beside the entry that was sent back
Signs
The correction of their own entry, with a reason
Head of the QC laboratory
Sees
The overlay, the audit trail and the chromatogram
Signs
The countersignature, the CAPA and each new review rule
QA data integrity lead
Sees
Each sampled review record
Signs
Agreement, or a disagreement that reopens the review

No agent edits a LIMS value or says why an injection was made

Correcting a recordThe analyst corrects their own entry with a reason; the reviewer has no edit control, and the agents never write to the data system or LIMS.
Judging intentThe agents state what was injected, when and under which name; the reviewer rules and the lab head countersigns.
Passing a check without its recordA missing printout stays not checked, never passed, until a person opens the scan.
Making a ruling a standing ruleA proposed rule applies only after the head of the QC laboratory approves it, and the proposer cannot approve.
Releasing a batchThe review covers the laboratory records; the plant QA head dispositions the batch, and the client's quality person releases it to market.

The data system's raw files, the balance printout and the signed method

Chromatography data systemSequences, raw data, processing method versions and the audit trail, read only.
LIMSSamples, standards, typed weights and results; review status is written only after sign-off.
Balance printoutsThe scans of what the balance printed, against which every weight is checked.
Signed test methods and SOPsSystem suitability criteria and integration rules, only from the signed version.
Past rulings and approved rulesHow the lab ruled before, quoted to the reviewer on the same exception.

What QC labs ask about analytical data review

What is analytical data review?

Analytical data review is the second-person check of laboratory records before a result is reported: raw data, calculations, system suitability, standards, integrations and the audit trail. Here agents re-perform each check from the raw records and the reviewer rules only on the exceptions they could not settle.

How does review by exception work for chromatography?

Each check settles as a mark under its injection, citing the record it was checked against. What cannot be settled, such as a typed weight that differs from its printout or an injection outside the sequence, stays open for a person, and a missing record is never a pass.

Does it replace the second person review?

No. The QC data reviewer still signs the review, after every exception is settled, and a ruling that lets results stand waits for the head of the QC laboratory to countersign. The agents do the reading and the arithmetic.

What happens to an injection that was never reported?

It appears on the strip before the sequence. The agents compare it with each solution in the run by impurity pattern and vial, the reviewer rules from those facts, and the lab head countersigns or opens a lab incident.

How do rulings become rules?

When reviewers rule the same way on the same kind of exception for the same method, the agents propose a rule. It applies to later sequences on that method only after the head of the QC laboratory approves it, and QA samples what it settles.

What does the client receive after the review?

Only the summary its quality agreement promises, after the review is signed: each finding and what was done about it. A question from the client goes to a person, unread by the agents.

Bring one sequence
and its balance printouts.

Send a chromatography sequence with its audit trail, LIMS entries and printouts; we re-perform the review and show you the exceptions.