Run the assessment program across plants and keep the evidence pack ready
- Paths drawn from SOPs, exports and the bench walk-through
- The riskiest process assessed first
- A program view for any auditor
A data integrity assessment that draws each GxP process as the path its data really takes, scores every hop on the nine ALCOA+ letters with evidence, reconciles what instruments hold against what was reported, and closes each gap only on signed proof.
See one lab process assessed screen by screen ↓Data integrity is usually assessed one computerized system at a time, with a questionnaire. A standalone instrument plus a paper worksheet is a hybrid process that rarely makes the system list, and the questionnaire's answer to whether it has an audit trail is that the printout is the original record. The analyst prints the run they are happy with, types the number into LIMS, and a second person checks the printout against LIMS.
Nobody compares what the instrument still holds in memory with what was reported, so a run that never reached LIMS stays invisible until the memory overwrites it. Remediation sits in a tracker with no link to the attribute it repairs, closure is a memo from the owner, and the path is not looked at again until the next cycle or the next inspector.
Built forData integrity leadsQC lab headsPlant QA headsSystem ownersHeads of quality
A lab process passes its system questionnaire while the instrument still holds results nobody reported.
Assessed from paper today
Built-in controls
Data integrity becomes a standing program with proof instead of a push before each inspection.
The data integrity lead, the QC lab head and the plant QA head each work their part, from the first run of the agents to a signed plan with its interim controls.
demoPlants, clients, people, instruments, batches and results shown here are sample data.
One person runs the program across plants; each lab owns its paths; the quality unit decides what is fixed.
Run the assessment program across plants and keep the evidence pack ready
Own their lab's data paths, raise lab events and own the fixes
Sign assessments, remediation plans, closures and the plant's rules
Own LIMS and instrument interfaces and supply the proof of a fix
Seven agents read records and propose; the people named on each screen decide.
Draws each hop from SOPs, the system inventory, configuration exports and the walk-through note.
Lights or breaks the nine letters on each hop, each with its passage.
Lays instrument memory and local copies beside LIMS and the logbooks, and counts what a record explains.
Plays the inspector against the SOP, the path and the agents' own work.
Proposes interim controls and fixes with the letters each repairs, an owner, a date and the proof that closes it.
Sends structured requests to instrument suppliers and reads the returned fields.
Checks that submitted proof matches what the item asked for, and re-scores the path after a person signs.
Beyond one process: the open items across plants, the inventory ranked by data risk, the program, the rules and the trail.
demoSample data, from the working solution.
A data integrity assessment checks whether a GxP process's records stay attributable, legible, contemporaneous, original and accurate, and complete, consistent, enduring and available, from where the data is created to where it is used. Here agents draw the real data path, score each hop with evidence and reconcile what instruments hold against what was reported.
By data criticality and vulnerability, as PIC/S guidance describes. The inventory ranks each system, hybrid process and simple instrument on both, so the riskiest process, such as a standalone instrument with hand transcription, is assessed first.
Only for very simple instruments that do not store data, in PIC/S terms, and FDA accepts a printout only when it is the original or a true copy. An instrument that keeps its own results has an electronic original, which is why the printout hop stays broken until that result is kept and reviewed.
If no logbook, reagent log or incident record explains it, the QC lab head raises a possible data integrity event inside the quality system and QA is notified. The agents never suggest a reason, and each affected client is told its own rows under its quality agreement.
Each item names the letters it repairs, an owner, a date and the proof that closes it. The owner submits the proof, a second person opens it and signs, and the path is scored again the same day.
Yes. A standalone instrument with a paper worksheet is assessed by the path its data takes, hop by hop, which is where a system-by-system questionnaire usually stops.
Each removal comes with the export that proves it, and every action in a GxP system stays tied to one person.
1-min demoGxP AI Validation & MonitoringA model goes live only on the inputs where it proved itself, and quality teams can read and sign its evidence.
1-min demoGxP IT Change & Patch Impact AssessmentSecurity fixes go in on their clock, and each function a patch reaches is tested with a reason an auditor can follow.
1-min demoSend its SOP, a memory export and the matching LIMS results; we draw its path and reconcile what it holds.