Clinics running Odoo quickly discover that patient intake and clinical assessment fall through the cracks. Vitals get typed into free-text notes on a contact or a helpdesk ticket, triage priority lives in someone's head, and there is no structured record you can audit, report on, or hand to the next clinician. Odoo core has no clinical model at all — there is no hr.hospital.patient, no encounter object, no vitals table — so teams end up bending Contacts, CRM, or Appointments into shapes they were never designed for. The moment you need computed values (BMI, MAP), a triage acuity score, or a nurse-vs-doctor access boundary, native fields and generic modules run out of road.

We build a dedicated Patient Evaluation module for your Odoo database. At its core is a new ecosire.patient.evaluation model (models.Model) linked to the patient record, with typed fields for every vital sign — temperature, pulse, respiratory rate, blood pressure (systolic/diastolic), SpO₂, height, weight and pain score. Derived clinical values such as BMI and Mean Arterial Pressure are @api.depends compute fields so they recalculate the instant an input changes and are never entered by hand. A configurable triage step maps the captured vitals to an acuity level (for example a 5-level ESI-style scale) via a compute method plus editable threshold configuration, and out-of-range readings are flagged with @api.constrains validation so a clinically impossible entry can't be saved silently.

The workflow is a proper state machine — draft → in_triage → assessed → closed — surfaced through purpose-built views: an OWL/XML form for bedside data entry, a kanban triage board colour-coded by acuity, and filtered list/search views for the waiting queue. Role separation is enforced with ir.model.access.csv plus record rules so front-desk, nursing and clinician groups see and edit only what their role permits. Each completed evaluation renders a clean QWeb PDF assessment summary for the chart or referral, automated actions (base.automation) can escalate a high-acuity case or notify the on-call clinician, and everything is reachable over the XML-RPC/JSON-RPC API so labs, devices or a patient portal can push and pull readings programmatically. It ships against Odoo 17.0, 18.0 and 19.0 and runs on Community or Enterprise — we flag any capability (such as Studio-style tweaks or advanced portal features) that depends on Enterprise before we build.

Because this is build-to-order, nothing is downloaded from a marketplace and switched on. We start with a scoping call, agree the exact vitals set, triage rules, roles and reports for your practice, then build, test on a staging copy of your database, run UAT with your team, and deploy with a rollback plan. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); additional clinics or multi-company setups, deeper localization of clinical terminology, device/lab integrations, and migration of historical patient data increase the quoted scope.