Purpose of this summary
This summary describes the intended arrangements for handling data during Verrion Systems Ltd walkthroughs and early hosted pilots. It is not a substitute for a customer-specific data processing agreement, security review, supplier qualification or validation assessment.
Private walkthroughs
- Initial walkthroughs should use synthetic or non-confidential example material.
- Do not send live deviation packs, patient data, confidential SOPs, batch records or proprietary regulated records through ordinary email or public website enquiries.
- If a deeper evaluation requires customer-approved material, agree the scope and data route first.
Hosted pilot arrangements
Hosted pilots are intended to be fixed-scope, controlled evaluations with limited users, defined scenarios, guided onboarding, agreed review responsibilities and an explicit export, deletion or retention path at pilot end.
AI support and sanitisation
- AI support is decision support, not automatic root-cause determination, CAPA approval or quality disposition.
- Customer users remain responsible for reviewing, accepting, editing or rejecting AI-supported suggestions.
- Hosted pilot design uses sanitisation before AI support so direct identifiers and sensitive operational references can be reduced before model processing.
- The exact configuration, permitted data and residual risk must be agreed before customer-approved material is used.
Hosting and suppliers
The configured and intended Pharma Compliance Suite AI route uses AWS Bedrock in eu-west-2. Each customer pilot must separately confirm its applicable hosting region, model route, subprocessors, access controls, retention, backup, support, export, deletion and incident-handling expectations. This public summary is not deployment evidence for a particular environment.
Access control and review
- Access should be limited to agreed pilot users.
- Outputs should remain reviewable, editable and rejectable by authorised customer users.
- Audit trail and e-signature design support review and validation assessment but do not replace customer validation responsibilities.
Customer validation responsibility
Verrion Systems software can support structured quality work and evidence handling. The customer remains responsible for intended use, required GxP validation, supplier qualification, procedural controls, data protection review, training and release governance before production use.
Pilot end
Pilot exit should include a clear decision on export, deletion, retention or transition to another agreed arrangement. Timing and required evidence should be recorded in the pilot terms.
Contact
Data handling questions can be sent to hello@verrionsystems.com.