Small-to-mid private hospitals and multi-doctor clinics usually run their front desk, their doctors, and their billing on three disconnected systems: a spreadsheet for patients, a paper file for the chart, and Odoo Accounting for invoices that nobody reconciles back to the visit. Odoo core gives you contacts, calendar, product, and account — genuinely strong foundations — but it has no concept of a Medical Record Number, no OPD queue, no admission/transfer/discharge cycle, no vitals or ICD-10 diagnosis, and no encounter that ties a consultation to a prescription to an invoice. You end up bolting a generic off-the-shelf apps.odoo.com module onto your database and inheriting its GPL/AGPL licensing baggage, its opinionated data model, and features you will never use. Clinical Core is the alternative: a purpose-built HIS that ECOSIRE designs, builds, and hands to you as clean, permissively-licensed source code you own.

Technically, Clinical Core is a set of Odoo addons layered on base, mail, contacts, calendar, product, account, hr, uom, and web. The patient master extends the partner model with an auto-generated MRN (via an ir.sequence and a @api.model create override), demographics, next-of-kin links, and a merge-duplicates tool for the inevitable double-registrations. OPD is a real workflow — check-in, triage, doctor queue, encounter form, disposition — modelled as models.Model state machines with computed fields (@api.depends) driving the kanban and list views (XML today, OWL where interactivity earns it). IPD is a full ADT cycle: admissions, ward/room/bed occupancy on a kanban board, transfers, and a QWeb discharge summary. The EMR captures vitals, chief complaint, ICD-10-coded diagnoses, clinical notes, and a running problem list; prescriptions record drug, dosage, frequency, and duration and print a QWeb PDF Rx report. Appointments sit on native calendar.event with per-practitioner availability and slots, and reminder emails fire from scheduled/automated actions. Every consultation and procedure maps a service product.product to price, so a finished encounter generates a patient account.move invoice automatically. Access is governed by real ir.model.access.csv groups plus record rules — receptionist, doctor, nurse, billing, admin — and multi-company scoping keeps each branch's patients and billing isolated. Because it is native Odoo, the whole system is reachable over the XML-RPC/JSON-RPC API for labs, insurance, or a patient portal, and it targets Odoo 17.0, 18.0, and 19.0 on Community or Enterprise.

Clinical Core is built to order, not downloaded. We start with a short scoping call to pin down your bed count, departments, billing rules, localization, and which integrations matter, then we build against a confirmed scope, deliver on a staging environment for UAT, and install on your production Odoo. Typical delivery is one working week from confirmed scope. You receive the full source, documentation, a user guide, a training session, and a post-go-live support window — and you own the git repository. Pricing starts from $999 (indicative, single-company base scope); multi-clinic scoping, deeper localization, lab/insurance integrations, and volume of legacy patient-data migration increase the quoted scope. The firm number comes in a fixed quote after the scoping call, never as a surprise later.