NextGenAMR — a product by Vanguard Biotech Systems
The NextGenAMR pilot process
A pilot is a controlled institutional evaluation — initially retrospective and non-interventional — run in parallel to your laboratory's usual workflow, to study whether NextGenAMR fits technically and operationally. Submitting this form starts a fit review; it is not a commitment.
NextGenAMR is a functional platform in controlled preview. Validation is ongoing, and the product is not presented as an autonomous diagnostic or treatment-decision system.
What a pilot studies
Technical and operational fit, data processability, run traceability, report completeness and utility, reproducibility, the frequency and causes of abstention or failure, processing time, professional-review time, and fit to your local workflow. Pilot results do not replace your reference method and are not used autonomously to diagnose, report susceptibility, select treatment or change care decisions.
How the evaluation works
A real sequence of work. No data or files are requested until a controlled environment is prepared and approved.
- 01Initial discoveryNo data or files requested
- What happens
- VBS and the institution identify the objective, the laboratory, the current workflow, the scientific scope, the people involved, general constraints and the question you want to answer.
- Who takes part
- Laboratory / innovation lead and VBS.
- What is decided
- Whether there is enough mutual interest to move to a fit review.
- 02Fit reviewNo data or files requested
- What happens
- Organism, panel, input, approximate volume, reference method, product maturity, institutional requirements and general compatibility are checked against the published scope.
- Who takes part
- Microbiology / bioinformatics and VBS.
- What is decided
- Advance, request additional non-sensitive information, or conclude that the product does not currently fit.
- 03Data & requirements evaluationNo data or files requested
- What happens
- The nature of the dataset is characterised: provenance, format, expected quality, governance, sensitivity, volume, transfer mechanism and conditions of use. No dataset is sent through the form or by ordinary email.
- Who takes part
- Data governance / privacy, laboratory and VBS.
- What is decided
- Whether a suitable, legitimately usable dataset can be defined — prioritising retrospective de-identified data.
- 04Protocol definitionNo data or files requested
- What happens
- Objective, population or dataset, inclusion/exclusion criteria, reference standard, endpoints, repetitions, failure handling, abstention handling, discordances, analysis, reporting and decision criteria are agreed before any execution.
- Who takes part
- Scientific + technical leads and VBS.
- What is decided
- A written, agreed protocol with success criteria fixed in advance.
- 05Controlled deployment preparationNo data or files requested
- What happens
- Architecture, access, responsibilities, secure transfer, retention, deletion, support, versioning, traceability, readiness and the conditions to start are confirmed. Not every institution follows exactly the same deployment.
- Who takes part
- IT / security / privacy, laboratory and VBS.
- What is decided
- Readiness sign-off: data reception and processing do not begin until the applicable conditions are met.
- 06ExecutionApproved dataset processed
- What happens
- The approved dataset is processed; versions and provenance are preserved; incidents are documented; the defined criteria are applied; the protocol is never silently changed to favour results.
- Who takes part
- Laboratory and VBS, under the agreed protocol.
- What is decided
- A documented set of runs with preserved versions, provenance and incidents.
- 07AnalysisNo data or files requested
- What happens
- Favourable and unfavourable runs, failures, exclusions, abstentions, discordances, limitations and operational observations are all included. No cherry-picking; denominators are not changed without documented justification.
- Who takes part
- Scientific + technical leads and VBS.
- What is decided
- An honest, complete analysis against the pre-agreed criteria.
- 08DecisionNo data or files requested
- What happens
- The institution and VBS may advance, advance with conditions, expand or repeat the evaluation, study a later integration, pause the work, or conclude that there is no current fit.
- Who takes part
- Institution leadership and VBS.
- What is decided
- A joint, non-obligatory decision — the journey is not designed to force every inquiry into contracting.
What a protocol can measure
These are evaluation objectives — dimensions a protocol may measure — not benefits already demonstrated. Success thresholds are agreed per protocol before execution, and abstentions, failures and exclusions are never hidden.
- Data eligibility & processability
How much of the dataset meets the input and scope conditions.
- Completed runs
Runs that finish and produce the expected output.
- Technical failures & causes
Runs that fail technically, with their causes.
- Abstentions & causes
Cases where the system abstains, and why.
- Repeatability & consistency
Consistency of results across repetitions.
- Per-stage & total runtime
Bioinformatic processing time — a technical measure, not a clinical turnaround or an operational saving.
- Report completeness & provenance
Whether the report and its provenance are complete and available.
- Professional-review time
Time a professional needs to review an output.
- Discordances vs the reference
Where applicable, differences against the reference standard.
- Fit to the local workflow
How well the process fits the laboratory's routine.
No clinical performance metrics (sensitivity, specificity, categorical agreement, VME/ME, accuracy) have been published. Performance evaluation is in progress.
Who contributes what
VBS provides
- The platform in a controlled managed-cloud environment.
- Configuration of the agreed scope.
- Technical onboarding and data-preparation documentation.
- Support during the evaluation.
- Version registry and run provenance.
- Failure investigation and result generation.
- An aggregate closing report.
The institution provides
- Scientific and technical leads.
- Compatible, legitimately usable data (agreed separately, never via the form).
- A reference method, where applicable.Scope-dependent
- Context on the current workflow.
- The applicable internal approvals.
- Participation in the kickoff, monitoring and closing reviews.
Deployment for an evaluation
NextGenAMR can be evaluated through a VBS-operated, controlled managed-cloud environment, subject to technical, contractual, scientific, privacy and security review. The architecture, region, isolation, transfer, persistence, retention, deletion and controls are agreed before any institutional data is received.
Assessed during the fit review
- · Certain deployment requirements can be assessed during the fit review.
- · Dataset, secure transfer, retention and deletion are agreed per evaluation.
- · A reference-standard comparison is defined where applicable.
Not offered as current capabilities
- — On-premise, hybrid or in-hospital installation, and single-tenant or configurable regional residency, are not currently available.
- — LIMS or direct sequencer integration, service-level guarantees, always-on support and certified deletion are not offered as current capabilities.
What this evaluation does not mean
- Submitting the form does not mean a pilot has been accepted.
- An initial call does not mean technical approval.
- Defining a protocol does not mean purchase or implementation.
- Running an evaluation does not mean general validation.
- A favourable result does not remove the scientific, legal, regulatory, technical, privacy, security, leadership or procurement approvals that may apply.
Timeframe
We do not publish a fixed duration. The timeframe is defined after reviewing the scope, the data, the approvals, the deployment, the volume and the dependencies.
Assess fit for your laboratory
Tell us about your institution and what you would like to evaluate. This qualifies fit and prepares a conversation — it requests no sensitive data.