Vanguard Biotech Systems

Collaborate with VBS

VBS is open to evaluating collaborations around NextGenAMR. These are concrete modalities and an invitation to study fit — not services already deployed in every context, and not a licence. Each project is defined by a specific agreement.

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.

Propose a collaboration Research & surveillance →

Collaboration modalities

Research & validation

Scientific & methodological research

Study reproducibility, configuration comparison and methodological questions with a controlled workflow.

What VBS contributes: The NextGenAMR workflow within its published scope, run provenance, component and database versioning, parameter records, and structured, reviewable outputs.
Who fits: Research groups, bioinformatics teams and university labs with a defined scientific or methodological question about genomic AMR analysis.
Preconditions: Depending on the project: a defined question, a scientific and technical contact, and legitimately accessible data with known provenance.
Possible outcomes: A reproducible analysis, a provenance package, or a methodological comparison — defined per project, not guaranteed results.

Start this conversation →See the evidence →

Datasets & data collaboration

Explore authorised, purpose-limited use or characterisation of datasets under agreed conditions.

What VBS contributes: A controlled workflow to characterise and analyse data within scope, with provenance and versioning. Your data stays under your control and the conditions you agree.
Who fits: Teams holding legitimately accessible datasets who want a reproducible, documented analysis — not a data sale.
Preconditions: A legitimate basis to share data, information on its provenance and quality, and the applicable approvals and transfer conditions.
Possible outcomes: A dataset characterisation, a reproducible analysis, or a feasibility assessment — under the agreed, purpose-limited terms.

Start this conversation →

Validation

Discuss a controlled, retrospective validation design — the specifics depend on the study.

What VBS contributes: Experience defining controlled evaluations, structured outputs, abstention handling and provenance to support a validation protocol.
Who fits: Reference laboratories and clinical/scientific teams able to define a protocol and provide a reference standard where applicable.
Preconditions: The final design depends on population, organisms, panel, reference standard, endpoints, discordances, abstentions, inclusion criteria and authorisations.
Possible outcomes: A defined protocol, a feasibility assessment, or a methodological result — not a clinical validation claim.

Start this conversation →See the evidence →

Surveillance & data

Public-health surveillance workflows

Explore structuring a reproducible surveillance workflow, comparison and reporting within scope.

What VBS contributes: Reproducible, versioned execution, provenance and structured reporting that can help organise a surveillance workflow within the published scope.
Who fits: Public-health bodies, surveillance networks and reference centres studying how to structure genomic AMR workflows.
Preconditions: A defined workflow question, legitimately accessible data, and the applicable approvals. This is not an operational surveillance service.
Possible outcomes: A reproducible analysis, a provenance package, or a reporting template to evaluate — not a deployed surveillance system.

Start this conversation →

Technical integration

Sequencing & systems integration

Study input compatibility and handoff with sequencing platforms, storage, APIs or LIMS — by state.

What VBS contributes: A defined workflow with structured inputs and outputs. Specific integrations are assessed per project and labelled by their real state — not offered as ready connectors.
Who fits: Sequencing centres and technical teams evaluating input compatibility, handoff and integration feasibility.
Preconditions: Information about the systems involved, data formats, and the transfer or interface conditions that apply.
Possible outcomes: An integration feasibility assessment or a defined next phase — not a delivered integration.

Start this conversation →

Interoperability & standards

Discuss structured, documented outputs and how they could fit interoperable reporting.

What VBS contributes: Structured JSON and reporting outputs with provenance and versioning that can be examined for interoperability within scope.
Who fits: Teams working on data standards, interoperable reporting or bioinformatics infrastructure.
Preconditions: A defined interoperability goal and the standards or systems in scope.
Possible outcomes: A technical assessment or a mapping to evaluate — subject to project scope.

Start this conversation →

Partnerships & consortia

Consortia & grants

Evaluate a VBS technical or scientific contribution to a work package or funding call.

What VBS contributes: A technical or scientific contribution around bioinformatics, provenance, interoperability or AMR analysis to a collaborative work package.
Who fits: Consortia, coordinators and applicants building a proposal that needs a bioinformatics/AMR contribution.
Preconditions: A defined work package or call, timelines, and the role expected of VBS. Participation is subject to fit and agreement.
Possible outcomes: A defined technical contribution to a consortium or a proposal — subject to evaluation and agreement.

Start this conversation →

Strategic / technology partnership

Explore a technology, diagnostics, sequencing, infrastructure or bioinformatics partnership.

What VBS contributes: The NextGenAMR platform and its technical capabilities as a basis to explore a partnership — before any commitment.
Who fits: Technology companies, diagnostics, sequencing, infrastructure or bioinformatics organisations exploring a fit.
Preconditions: A described interest and objective. No exclusivity, distribution or partnership is implied before an evaluation.
Possible outcomes: A defined next step toward evaluating a partnership — not a partnership itself.

Start this conversation →

Collaboration principles

These are initial working principles — orientations to structure a conversation, discussed case by case and subject to appropriate written agreements for each collaboration. They are not contractual terms, guarantees, an automatic grant of rights or approved legal policy; how they apply depends on the nature of the collaboration.

Pre-existing technology stays with its owner

As an initial working principle, each party keeps its pre-existing technologies, know-how, data, software and materials. Unless a specific written agreement says otherwise, VBS retains ownership of NextGenAMR, its code, architecture, orchestration, scope control, aggregation, abstention, provenance, versioning and reporting.

New results are defined up front

Ownership and use of anything developed jointly is discussed case by case and defined for each project in a specific written agreement, before the work begins.

Your data stays yours

A collaborator's data stays under their control and the conditions they agree. Use is limited to the agreed purpose and depends on the applicable authorisations, legal bases, security measures and agreements. VBS does not acquire ownership of datasets and does not reuse them beyond the agreed purpose.

Data moves only through secure, authorised channels

No data or materials are exchanged through this website or ordinary email. Any exchange happens only after a secure, explicitly authorised channel is agreed.

Confidentiality when it is needed

VBS can work under confidentiality agreements when the nature of the collaboration requires it. A confidentiality agreement is not a requirement to send a first inquiry.

Responsible scientific publication

VBS favours reproducibility, methodological transparency and responsible communication when a project allows it. Authorship and acknowledgements depend on real contribution and a specific agreement. A prior review may protect confidential information, intellectual property and scientific accuracy.

Recognition follows contribution

Recognition of a collaboration is based on the real contribution of each party and a specific agreement.

No names or logos without authorisation

The name, identity, logo, results or collaborator status of an organisation are not made public without its authorisation.

Propose a collaboration

Tell us who you are and how you would like to collaborate. This starts a conversation to evaluate fit — it requests no sensitive data, sequences or files.

Full name

Professional email

Organisation

Country

Your role

Type of collaboration

Do not submit patient data, clinical information, sample identifiers, genomic files, sequences, or any other confidential or sensitive information through this form.

Add optional context (helps us prepare)

Area of interest

Project objective

General type of data available (no sensitive detail)

Organisms or scope envisaged

Sequencing platform

Funding or consortium status

Approximate time horizon

Message

I understand this form starts a conversation to evaluate fit, that it is not a licence or an agreement, and I have read the privacy policy. Privacy policy.

Reminder: do not include patient data, sample identifiers, sequences, genomic files or credentials.

Understand the product

Research & surveillance →How it works →Evidence & validation →Security & deployment →