Most clinics that start offering remote consultations end up stitching the workflow together by hand: a video link pasted into an email, a payment chased after the call, prescriptions typed into a separate document, and no clean record of what happened landing back in the patient file. Odoo's native calendar and appointment tools can book a slot and even attach a videoconference URL, but they treat a telemedicine visit like any other meeting — there is no concept of paying before the link goes live, no structured intake completed ahead of time, no waiting-room signal to the doctor, and no clinical encounter or prescription tied to the patient's EMR. The result is revenue leakage from unpaid no-shows, compliance gaps as consent and records scatter across tools, and a patchy experience for both clinician and patient.

Clinical Telemedicine is a build-to-order Odoo application we design and develop for your practice on top of base, calendar, portal, payment, mail, and our clinical-core-his-emr foundation. We introduce a dedicated telemedicine appointment type whose confirmation triggers a secure, auto-generated meeting link — wired through integration hooks so it can drive Odoo Discuss WebRTC, a self-hosted Jitsi room, or an external meeting URL depending on your infrastructure. A new telemedicine.encounter model (extending our clinical encounter) carries the whole visit: it is created in a draft state, moves to waiting when the patient joins, in_progress when the clinician opens the room, and done when the note is signed — each transition driven by ORM methods and surfaced through @api.depends computed fields on the doctor's kanban.

Technically, the flow is enforced rather than assumed. The portal payment step uses Odoo's payment provider stack; a payment.transaction reaching done is what flips a boolean like is_call_unlocked and renders the join button in the QWeb portal template — no payment, no link. Before the call, the patient completes an intake form built as an OWL/website form persisting to the encounter, so the clinician opens the room already briefed. During the session the doctor writes the encounter note and creates an e-prescription (prescription.line records with drug, dose, duration), and on sign-off an ir.actions.report QWeb PDF of the prescription and visit summary is emailed via mail.template. Recording-consent capture is a required checkbox logged with a timestamp before the room can start, and a follow-up appointment can be scheduled straight from the encounter. Access is governed by ir.model.access.csv plus record rules so a patient sees only their own encounters through the portal, and every state change is auditable in the mail.thread chatter. Automated actions handle reminders and stale-draft cleanup, and the whole surface is reachable over XML-RPC/JSON-RPC if you integrate an external booking site or mobile app.

Because this is build-to-order, nothing ships until we agree scope. After a short scoping call we produce a fixed-scope statement, build your version against Odoo 17.0, 18.0, or 19.0 (Community or Enterprise — we confirm which fields, like the Enterprise appointment engine, are available on your edition), and deliver it on a staging environment for UAT before go-live. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); additional integrations such as a specific video provider, e-prescription regulatory formatting, multi-company or multi-branch setup, and depth of EMR data migration increase the quoted scope.