Skip to Content

Hosting and deployment options for Ventrecs

Where Ventrecs runs, which services sit beside it, and how the hosting model and data location are agreed for each deployment.

What a deployment looks like

Ventrecs is a suite of modules that run together on one database. The hosting model, the software it depends on and any third-party licences are listed in the proposal before you commit, and agreed for each deployment.

Ventrecs is a suite of modules that extends Odoo Enterprise applications and does not modify Odoo core. It deploys on Odoo.sh or on infrastructure you operate, and it requires a licensed Odoo Enterprise deployment. Odoo is a trademark of Odoo S.A., and Ventrecs is not an Odoo S.A. product.

Clinical records, audit events and the integration outbox are stored in the PostgreSQL database. A few things deliberately run as separate services, so each can be secured, scaled and replaced on its own.

At a glance
Deployment
On Odoo.sh or on your own infrastructure, agreed per deployment
Separate services
The PACS, the integration layer and the identity provider
Database
PostgreSQL
Data location
Discussed and agreed for each deployment
Commitments
No hosting or uptime figure is published
Hosting and deployment

Who decides what

Your IT and information-security leads, who choose the hosting model and the network design.
Your privacy lead, who documents data-controller and processor roles and approved data-transfer routes.
Ventrecs delivery, who agree the architecture, the environments and the test plan with you.
Hosting and deployment

The pieces

The platform

The clinical, operational and administrative modules run together on one database.

  • Care, Lab, Imaging, Pharmacy, Connect, Operations and the specialist modules
  • Server-side access rules and an audit trail
  • English and Arabic side by side on documents and patient-facing screens

Separate services

Some services stay outside the platform on purpose.

  • Orthanc PACS, synchronised over DICOMweb, with studies opened in a viewer
  • The integration layer that carries messages to partners
  • The identity provider for single sign-on and multi-factor sign-in

Environments

A deployment has more than one.

  • Development and test environments that never receive production patient data without documented approval and de-identification
  • A production environment with backups and a restore exercise
  • Sandbox and production separation for every partner connection
Hosting and deployment

What we agree with you

Hosting model and locationWhere the system runs and where backups are kept, written down for the facility and its legal entities.
Backup and recoveryBackup encryption, restore exercises and recovery targets signed before go-live.
Network and certificatesSegmentation, endpoint certificates and their renewal, owned by named people.
MonitoringInterface and platform monitoring with a named owner and a downtime procedure.
What we do not claim

Ventrecs does not claim ISO 27001, SOC 2, HIPAA or any other security certification, and makes no data-residency, uptime or response-time promise on this page. Hosting, security review and service levels are discussed and agreed for each deployment and written into the contract.

Hosting and deployment

Questions we are asked

Where is my data hosted?

The hosting location and model are discussed and agreed for each deployment. We do not make a data-residency promise in advance.

Do we need other software licences?

Yes. Ventrecs requires a licensed Odoo Enterprise deployment. Odoo is a trademark of Odoo S.A., and Ventrecs is not an Odoo S.A. product. Any other licences are listed in the proposal before you commit.

Is the PACS part of the platform?

No. Orthanc PACS stays a separate service. Study records synchronise over DICOMweb and studies open in a viewer.

Do you publish an uptime figure?

No. Availability targets for hosted deployments are agreed per deployment and written into the contract.

Talk to us about your setup

Tell us about your facility and current systems. We will reply within one working day.