Radiology departments live in the gap between a hospital's clinical systems and its business ERP. Imaging orders arrive by phone, referral, or paper; modality slots are juggled on whiteboards or spreadsheets; report turnaround is invisible until a clinician complains; and none of it reconciles cleanly with the invoicing, insurance, and inventory sides of Odoo. Out of the box, Odoo has no concept of a radiology order, a modality, an accession number, a reading worklist, or a structured radiology report — so teams end up bolting the workflow onto generic project tasks or helpdesk tickets that were never designed for imaging throughput or turnaround-time governance.

We build a dedicated Radiology Management module on top of your Odoo. At its core are new ORM models — a radiology order (radiology.order) linked to res.partner (patient) and the referring physician, a modality registry (radiology.modality) for CT/MRI/X-ray/ultrasound rooms, an examination catalogue (radiology.exam) carrying body-part and protocol metadata, and a report record (radiology.report) that holds findings, impression, sign-off, and an addendum trail. Each order is stamped with a sequenced accession number via ir.sequence, moved through a documented state machine (draft → scheduled → acquired → preliminary → final) built with fields.Selection and guarded transition methods, and its turnaround time is a stored @api.depends compute so you can report on it rather than guess. Reading worklists are ordinary filtered/grouped views, so radiologists see their queue by modality, priority (STAT vs routine), and status without leaving Odoo.

Technically, the module ships as a proper addon with its own __manifest__.py, migration-safe data files, and clean separation of concerns. Access is locked down with ir.model.access.csv for role groups (front-desk, technologist, radiologist, department manager) plus record rules so a technologist sees the acquisition worklist while a radiologist owns sign-off — and, where you run multi-site, record rules scope each site's orders. Views are XML (list, form, kanban worklist, calendar for modality scheduling) with OWL widgets where an interaction genuinely needs them; a QWeb PDF template produces the signed radiology report on your letterhead; and Odoo automated actions / scheduled crons handle escalations such as flagging STAT studies breaching their turnaround SLA. Because everything is native ORM, your PACS, RIS, or HL7 middleware can push and pull orders and results over the standard XML-RPC / JSON-RPC API rather than a bespoke bridge. We target Odoo 17.0, 18.0, and 19.0, and we tell you honestly where a capability leans on Enterprise features (e.g., advanced dashboards) versus what runs on Community.

This is a build-to-order engagement, not an existing apps.odoo.com download. After a short scoping call we confirm your exact workflow, roles, integrations, and Odoo version, then engineer, install, and support the module — typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $299 (indicative, single-company base scope); PACS/RIS/HL7 integration depth, DICOM-adjacent worklist requirements, multi-site record-rule scoping, and historical data migration volume increase the quoted scope. You receive a fixed quote after the scoping call, never a surprise invoice.