Chatten Sie auf WhatsApp

Produktdetails werden auf Englisch angezeigt. Übersetzungen folgen in Kürze.

Preis: $299.00 USD
Odoo-Versionen: 17, 18, 19
Rüstzeit: 30 Min
Lizenz: Einmalig und unbefristet
Sprachen: 11 Sprachen

Einmalkauf

Patient Follow-up

Name: Patient Follow-up
Brand: ECOSIRE
SKU: patient-follow-up

A made-to-order Odoo module that embeds recurring follow-up scheduling, automatic no-show detection, and protocol-driven care recalls directly into your patient and appointment records. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19 instance.

$299.00USD

Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.

Hauptfunktionen

Dedicated `patient.followup` model linked to the patient record (`res.partner`/patient) and the originating `calendar.event`, giving follow-ups a first-class object rather than free-text notes

Reusable `patient.followup.protocol` records encoding cadence interval, day-offset rule, channel, owning care team, and escalation steps

Computed `next_due_date`, `days_overdue`, and lifecycle `state` (`scheduled → reminded → completed → missed`) via `@api.depends` compute methods

Daily `ir.cron` scheduled action that sweeps for due and overdue follow-ups and generates coordinator activities

No-show detection through `base.automation` automated actions reconciling appointment attendance and auto-transitioning records to `missed` with a rebooking task

QWeb-templated reminder messages sent over Odoo's native mail and SMS layer, with per-protocol template selection

Kanban, list, form, calendar, and pivot views (XML/OWL) delivering a single 'Follow-ups Due' coordinator cockpit

Access control via `ir.model.access.csv` plus record rules scoping follow-ups to the correct care team and clinic

Multi-company record rules that isolate follow-up data across separate clinics or legal entities

Pivot/graph analytics for no-show rate, on-time recall rate, and overdue backlog by protocol, team, or period

QWeb PDF recall summary report per patient or per due-list batch for front-desk and clinical handoff

XML-RPC/JSON-RPC endpoints so external portals, telephony, or reminder gateways can read and write follow-up records

Configurable escalation ladder (reminder → second reminder → coordinator activity → supervisor alert) driven by protocol rules

Clean `__manifest__.py` with pinned dependencies and version-branch parity across Odoo 17.0, 18.0, and 19.0

Über dieses Produkt

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."

Warum Patient Follow-up wählen

Dedicated `patient.followup` model linked to the patient record (`res.partner`/patient) and the originating `calendar.event`, giving follow-ups a first-class object rather than free-text notes

Reusable `patient.followup.protocol` records encoding cadence interval, day-offset rule, channel, owning care team, and escalation steps

Computed `next_due_date`, `days_overdue`, and lifecycle `state` (`scheduled → reminded → completed → missed`) via `@api.depends` compute methods

Daily `ir.cron` scheduled action that sweeps for due and overdue follow-ups and generates coordinator activities

No-show detection through `base.automation` automated actions reconciling appointment attendance and auto-transitioning records to `missed` with a rebooking task

QWeb-templated reminder messages sent over Odoo's native mail and SMS layer, with per-protocol template selection

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 2 to 4 weeks from confirmed scope, ending in UAT on staging, a supervised go-live, and a support window. Pricing starts from $299 (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.

Was Sie bekommen

Installable module source code for your confirmed Odoo version (17.0/18.0/19.0), Community or Enterprise
Installation and configuration on your instance, including protocol setup and security-group wiring
Technical documentation: data model, `ir.cron`/automation logic, security rules, and API surface
End-user guide plus a live training session for coordinators and front-desk staff
Post-go-live support window for defect fixes and configuration adjustments
UAT on a staging copy of your database with a documented rollback plan before go-live
Git repository handover with full commit history and tagged release
Configured follow-up protocols and reminder templates matching the cadences you actually run

Für wen das ist

Clinic Operations Manager

Runs day-to-day scheduling and needs a reliable recall backlog and no-show visibility instead of spreadsheets, so overdue patients stop slipping through the appointment pipeline.

Care Coordinator / Front Desk Lead

Works the daily due list, sends reminders, and rebooks no-shows. Needs one cockpit inside Odoo that shows exactly who is due, who missed, and what action each protocol requires.

Odoo Administrator / Internal IT

Owns the Odoo instance and wants a clean, well-documented module with proper `ir.model.access.csv`, record rules, and a git handover — not an opaque add-on that breaks on the next upgrade.

Practice Owner / Medical Director

Accountable for continuity of care and recall compliance. Needs protocol-driven follow-up cadences and KPI reporting (no-show rate, on-time recall rate) to demonstrate the clinic follows through on care plans.

Installationsübersicht

Von ECOSIRE herunterladen
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei des Patient Follow-up-Moduls von Ihrem Konto-Dashboard herunter.
Auf Odoo hochladen
Extrahieren Sie die ZIP-Datei in Ihren Odoo-Ordner für benutzerdefinierte Add-ons auf dem Server (oder laden Sie sie über „Apps“ > „Aus Datei installieren“ auf Odoo.sh/Runbot hoch).
Installieren Sie das Modul
Aktivieren Sie den Entwicklermodus, öffnen Sie „Apps“, klicken Sie auf „Apps-Liste aktualisieren“, suchen Sie nach „Patient Follow-up“ und klicken Sie auf „Installieren“.
Einstellungen konfigurieren
Öffnen Sie das neue Menü, fügen Sie Ihren ECOSIRE-Lizenzschlüssel ein, verbinden Sie alle externen Anmeldeinformationen (Shopify, Amazon, Stripe usw.) und speichern Sie.
Verifizieren und live gehen
Führen Sie den integrierten Verbindungstest aus, synchronisieren Sie Ihre ersten 10 Datensätze und planen Sie den wiederkehrenden Cron. Wenden Sie sich an den Support, wenn etwas fehlschlägt.

Wie Patient Follow-up im Vergleich abschneidet

Kriterium	ECOSIRE	Benutzerdefinierter Build	Konkurrent
Follow-up scheduling model	Dedicated `patient.followup` object with protocol-driven cadences	Possible, but you design and maintain the model yourself	Generic follow-up fields, rarely protocol-aware
No-show detection	Automated attendance reconciliation transitions record to `missed` + rebooking task	Must be built and tested from scratch	Often manual status change, no auto-escalation
Protocol automation	Reusable cadence protocols with escalation ladder via `ir.cron` + automations	Feasible but adds significant build and QA time	Fixed reminder rules, limited configurability
Fit to your workflow	Built against your data model, Odoo version, and real protocols	Fully bespoke, but you own all design risk	Generic; you adapt your process to the app
Security & multi-company	`ir.model.access.csv` + record rules + multi-company isolation as scoped	You implement and verify all access rules	Basic access groups, multi-company varies
Delivery & responsibility	Build-to-order, 2-4 weeks, UAT + rollback + support window	Depends on your internal team's capacity	Instant download, self-support, upgrade-at-your-risk
Reporting & KPIs	Pivot/graph on no-show rate, on-time recall, overdue backlog	Build your own reports	Limited or no follow-up analytics
Code ownership	Full git repo handover; you own the code	You own it, but also built it	Vendor-locked, obfuscation possible

Häufig gestellte Fragen zu Patient Follow-up

Is this an app I can download and install today?

No. Patient Follow-up is build-to-order. ECOSIRE builds the module against your specific Odoo version and patient data model, then installs and supports it. It is not an existing apps.odoo.com download, so there is no instant-download or self-serve install.

How long does delivery take?

Typical delivery is 2 to 4 weeks from confirmed scope. The timeline starts once we have agreed the protocols, your Odoo version and edition, and the data model on a scoping call, and it includes UAT on staging before go-live. Larger multi-company or migration-heavy builds sit at the upper end.

How does pricing and scoping work?

Pricing starts from $299 as an indicative single-company base scope. It is not a fixed price — after a short scoping call we send a fixed quote based on your confirmed requirements. Multi-company clinic groups, extra reminder or telephony integrations, deeper localization, and historical data migration increase the quoted scope.

Which Odoo versions and editions do you support?

We build for Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. The module runs on Community; where your instance has Enterprise we use Enterprise-native widgets and features rather than duplicating them. We confirm your exact version and edition before building.

What about support and future updates?

Every build includes a post-go-live support window for defects and configuration tweaks. Because you receive the full git repository, you own the code. We can also provide ongoing maintenance or version-upgrade work (for example moving from 17.0 to 18.0/19.0) under a separate agreement.

How does no-show detection actually work?

Automated actions (`base.automation`) reconcile appointment attendance against the linked `calendar.event`. When a patient does not attend, the follow-up record transitions to `missed` and a rebooking task or activity is created for the assigned coordinator, so missed visits become actionable rather than invisible.

Can it integrate with our external systems?

Yes. Follow-up records are exposed over Odoo's XML-RPC/JSON-RPC API, so an external patient portal, telephony platform, or reminder gateway can read and write them. Specific third-party integrations are scoped and quoted as part of the build.

Angebot anfordern