Clinics running Odoo quickly discover that native calendar.event and Appointments cover booking, but say nothing about what happens after a visit ends. There is no first-class concept of a follow-up cadence, no automatic flag when a patient never shows, and no way to trigger a protocol-specific recall (post-op check at 7 days, chronic-care review every 90 days, lab re-test in 6 weeks). Care coordinators end up tracking recalls in spreadsheets, reminders fire manually, and no-shows silently fall out of the pipeline — which is exactly the population most at clinical and revenue risk. Odoo out of the box has no model that answers "who is due, who slipped, and what should happen next."

ECOSIRE builds a dedicated Patient Follow-up module that lives inside your existing patient workflow. At its core is a patient.followup model (linked to res.partner/your patient record and to the source calendar.event) with a companion patient.followup.protocol model that encodes reusable cadences — interval, offset rule, channel, assigned team, and escalation steps. Computed fields using @api.depends derive next_due_date, days_overdue, and a state progressing through scheduled → reminded → completed → missed. A scheduled action (ir.cron) sweeps daily for due and overdue follow-ups; base.automation automated actions detect no-shows by reconciling appointment status against attendance and transition the record to missed, spawning a rebooking task or activity for the assigned coordinator. Reminders go out through Odoo's native mail/SMS layer using QWeb-rendered templates, and everything is exposed via list, form, kanban, calendar, and pivot views built in XML/OWL so coordinators work a single "Follow-ups Due" cockpit.

Security is enforced through ir.model.access.csv plus record rules so that follow-up data is scoped to the right care team, and — where you separate clinics or legal entities — multi-company rules keep records isolated. We can wire a QWeb PDF recall summary, surface follow-up KPIs (no-show rate, on-time recall rate, overdue backlog) in pivot/graph views, and expose the follow-up records over the XML-RPC/JSON-RPC API so an external portal, telephony system, or reminder gateway can read and write them. The build respects Community vs Enterprise boundaries: it runs on Community, and where your instance has Enterprise we can lean on Enterprise-only widgets and studio-adjacent features rather than reinventing them.

Because this is build-to-order, nothing is shipped as an instant download. After a short scoping call we confirm your Odoo version (17.0/18.0/19.0), Community vs Enterprise, your patient data model, and the protocols you actually run, then build against a staging copy of your database. Typical delivery is one working week from confirmed scope, ending in UAT on staging, a supervised go-live, and a support window. Pricing starts from $999 (indicative, single-company base scope); multi-company clinic groups, deeper localization, extra reminder-channel or telephony integrations, and migration of historical recall data increase the quoted scope.