Skip to Content
Solutions

Start from the kind of provider you are.

Each solution combines the products and integrations that type of organisation actually needs, deployed in phases.

01

Medical centres & polyclinics

Run outpatient care, results and billing from one place.

Typical challenges
  • Appointments, records and billing in separate systems
  • Results arriving by phone, paper or email
  • Payer rules handled manually at the front desk
Integrations commonly required
  • Payer eligibility & claims
  • Reference laboratories
  • Health information exchange
Typical challenges
  • Specimens lost between collection and analysis
  • Manual result transcription from instruments
  • Patients and doctors chasing results by phone
Integrations commonly required
  • Laboratory analysers & middleware
  • Label printers
  • Referring clinics and corporate accounts
Typical challenges
  • Studies landing on the wrong patient
  • Radiologists switching between RIS and PACS
  • Slow, unsigned or untracked reports
Integrations commonly required
  • PACS over DICOMweb
  • Modality worklist
  • Referrer result delivery
04

Pharmacy groups

Control dispensing, stock and POS across every branch.

Typical challenges
  • Stock and expiry tracked per branch, not per group
  • Prescriptions re-keyed at the counter
  • No traceability for recalled batches
Integrations commonly required
  • Medicine traceability services
  • Payer and corporate accounts
  • Payment gateways
05

Hospital groups

Modernise department by department, without a big-bang replacement.

Typical challenges
  • Legacy HIS that departments work around
  • Lab, imaging and pharmacy on separate vendors
  • Bed, theatre and billing data that don’t reconcile
Integrations commonly required
  • Existing HIS and departmental systems
  • Payers and claims
  • PACS and laboratory instruments
Typical challenges
  • Each site configured differently
  • No group-level view of throughput or revenue
  • Patients re-registered at every location
Integrations commonly required
  • Group finance and ERP
  • Payers across sites
  • Shared laboratory and imaging services
Technology

What Ventrecs is built on.

Ventrecs is a suite of add-on modules for Odoo 20 Enterprise.

Platform

Odoo 20 Enterprise

Ventrecs adds clinical modules to Odoo's applications: Contacts, Calendar, Inventory, Accounting, Sales, Purchase, Point of Sale and Documents. It is an extension suite, not a fork.

Language

Python

Server-side logic runs on Odoo's ORM. Beyond the Python standard library, the modules use requests for outbound connectors and pylibdmtx for DataMatrix labels.

Database

PostgreSQL

Odoo's database. Clinical records, audit events and the integration outbox are stored there.

Interface

JavaScript and OWL

Odoo's web framework drives the live clinical dashboard, the operating room timeline and the imaging viewer launcher.

Imaging

Orthanc and DICOMweb

Your Orthanc PACS stays a separate service. Ventrecs syncs study records over DICOMweb (QIDO-RS) and opens studies in browser viewers: OHIF for images, ecg-dicom-web-viewer for ECG waveforms.

Exchange

FHIR R4 and REST

A durable outbox produces FHIR R4-shaped resources for an integration service. Payer eligibility connectors use generic REST or FHIR R4. Other transports, such as HL7 v2, run in a separate integration layer scoped per project.

Labels

ZPL and DataMatrix

Specimen labels and patient wristbands print as ZPL to Zebra network printers, with a PDF fallback. Pharmacy labels carry DataMatrix codes.

Hosting

Odoo.sh or your servers

Deploy on an Odoo.sh project or on your own infrastructure. The PACS, integration layer and identity provider run as separate services.

Versions are those of the current build. Odoo is a trademark of Odoo S.A. Ventrecs is built by Al Jawad Software House and is not an Odoo S.A. product. It requires a licensed Odoo Enterprise deployment.