Radiology Information System

Key Features

New ORM models (`models.Model`) for radiology order, exam/study, modality, room, and acquisition protocol with enforced Many2one/One2many relational integrity

Study lifecycle as a `Selection` state field: requested → scheduled → in-progress → acquired → reported → verified, with guarded transitions

Modality worklist as list + kanban views, filterable by modality, room, technologist, and date, backed by search-view filters and grouping

Protocol enforcement — a scan cannot start until an acquisition protocol is assigned, driven by an automated action / server logic

Multi-format study file storage via `ir.attachment` fields for DICOM exports, JPEG/PNG key images, PDF reports, and structured measurement files, each bound to one study

Compute fields with `@api.depends` for report turnaround time, SLA-breach flags, and modality utilization

Structured radiologist reporting (findings / impression / recommendation) rendered to a branded QWeb PDF report ready to sign

Role-based access via `ir.model.access.csv` plus record rules separating front desk, technologist, radiologist, and referring-physician visibility

Scheduling through a calendar view with room and modality resource assignment and double-booking checks

Automated actions (`base.automation`) for SLA-breach alerts, referrer notification on report verification, and pending-report reminders

Referring-physician and patient linkage to Odoo contacts (`res.partner`) so orders, studies, and reports roll up per referrer and patient

XML-RPC / JSON-RPC API surface for PACS gateways, modality worklist brokers, and external portals to create orders and post results

Sequenced accession/study numbering via `ir.sequence` for unique, human-readable study identifiers

Targeted to Odoo 17.0 / 18.0 / 19.0 and your Community or Enterprise edition, packaged with a clean `__manifest__.py` and declared dependencies

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Radiology departments live and die by the order-to-report loop: a referral arrives, a study is scheduled against the right modality, the technologist runs the correct protocol, images and reports stay bound to the patient and exam, and a signed report reaches the referrer. Odoo out of the box has no concept of a radiology order, a modality worklist, an acquisition protocol, or a study file that must stay attached to one specific exam. Teams bolt this onto Calendar, Projects, or Documents and then discover that a generic scheduler cannot enforce protocol selection, a document folder cannot guarantee an image belongs to the right study, and a to-do board cannot represent the states a radiology exam actually passes through. A typical off-the-shelf apps.odoo.com module hands you a fixed data model you cannot bend to your referral sources, report layouts, or local compliance rules — and no one to change it when your workflow changes.

ECOSIRE builds a Radiology Information System as a proper Odoo module for your instance. At its core are new ORM models (models.Model) for the radiology order, the exam/study, the modality, the room, and the acquisition protocol, wired with real relational integrity — a study carries a Many2one to its order, patient, and referring physician, images are One2many study files, and a Selection state field drives each exam through requested → scheduled → in-progress → acquired → reported → verified. Compute fields with @api.depends derive turnaround time, report-due flags, and modality utilization so no one recalculates them by hand. Multi-format file storage is handled with binary/attachment fields (ir.attachment) so DICOM exports, JPEG/PNG key images, PDF reports, and structured measurements can all be stored, versioned, and retrieved against the exact study they belong to, with size and mimetype recorded.

The department sees the workflow through purpose-built views: a modality worklist (list + kanban) filtered by room and date, a study form with protocol picker and technologist assignment, and a calendar for scheduling. Radiologist reporting uses a structured findings/impression layout that renders to a branded QWeb PDF report, ready to sign and send. Automated actions (base.automation) handle the repetitive edges — flagging studies breaching turnaround SLA, notifying referrers when a report is verified, and prompting protocol assignment before a scan can start. Everything is permission-boundaried through ir.model.access.csv plus record rules so front-desk staff, technologists, radiologists, and referrers each see only what their role allows, and the whole model is reachable over the XML-RPC/JSON-RPC API for integration with PACS gateways, modality worklist brokers, or an external portal. We build against your edition — Community or Enterprise — and target Odoo 17.0, 18.0, or 19.0 to match your running version, noting where an Enterprise-only feature (such as advanced approvals or studio-style layouts) shapes the design.

Delivery is build-to-order: it starts with a scoping call where we map your referral sources, modalities, protocols, report templates, and roles, then confirm the exact data model and states before a line of code is written. You receive the installable module source, installation and configuration on your instance, UAT on a staging database with a rollback plan, technical documentation, a user guide and training session, and a post-go-live support window. Typical delivery is 2–4 weeks from confirmed scope, depending on integration and report complexity. Pricing starts from $299 (indicative, single-company base scope); multi-company or multi-site operation, PACS/DICOM and modality-worklist integrations, localized report formats and regulatory fields, and migrating historical studies each increase the quoted scope.

What you get

Installable module source code for your version, built against your Odoo edition and version (17.0/18.0/19.0)

Installation and configuration on your Odoo instance, including access rights, sequences, and report templates

UAT on a staging database with an agreed test script and a documented rollback plan

Technical documentation: data model, security matrix, automated actions, and API integration points

End-user guide plus a live training session for front desk, technologists, and radiologists

Post-go-live support window for defect fixes and configuration adjustments

Git repository handover with full commit history and tagged release

Branded QWeb report template(s) and sample outputs delivered with the module

Who this is for

Radiology / Imaging Department Manager

Runs the daily worklist across modalities and rooms, needs enforced protocols, turnaround-time visibility, and SLA alerts so no study stalls between acquisition and a signed report.

Odoo Administrator / IT Lead at a clinic or hospital

Owns the running Odoo instance and wants imaging handled as a first-class module with clean access rights, sequences, and an XML-RPC/JSON-RPC surface for PACS integration — not a fragile bolt-on to Calendar or Documents.

Reporting Radiologist

Reads studies and signs reports; needs structured findings/impression capture, reliable image-to-study binding, and a clean branded PDF that reaches the referrer without manual re-keying.

Clinic Operations Owner

Wants imaging orders, referrers, and revenue to live inside the same Odoo their contacts and invoicing already use, and prefers a scoped fixed quote with local support over an unsupported marketplace download.

How Radiology Information System Compares

Criterion	ECOSIRE	Custom Build	Competitor
Data model fit	Purpose-built order/study/modality/protocol models matched to your workflow	Whatever you specify and build in-house	Fixed generic schema you cannot reshape
Protocol & modality worklist	Enforced protocol selection and a filtered modality worklist	Possible but you design and maintain it	Basic worklist, limited enforcement
Multi-format study storage	DICOM/JPEG/PNG/PDF/measurements bound per study via ir.attachment	Build attachment handling yourself	Often limited file types or loose binding
Ownership & source	Full source and git repo handed over, no lock-in	You own it but carry all build cost	Licensed code, vendor-controlled roadmap
Fit to Odoo version/edition	Built for your exact 17.0/18.0/19.0 and Community/Enterprise	Depends on your team's Odoo depth	Version support varies, upgrades lag
Support & changes	Scoped support window plus paid maintenance and upgrades	Your team, or nobody, when it breaks	Ticket queue, no workflow-specific changes
Integration (PACS/API)	XML-RPC/JSON-RPC surface, scoped PACS/DICOM/HL7 bridges	Buildable at full cost	Rarely offered or extra-cost
Time to value	2–4 weeks from confirmed scope, installed and trained	Months, plus hiring/spec risk	Fast install, slow/none to fit your process

Frequently Asked Questions about Radiology Information System

Is this an existing app I can download and install today?

No. This is a build-to-order Odoo module. ECOSIRE scopes it with you, then builds, installs, and supports it on your instance. There is no instant download — you receive a module built for your workflow, edition, and Odoo version.

How long does delivery take?

Typical delivery is 2–4 weeks from confirmed scope. The exact timeline depends on integration complexity (PACS/DICOM, modality worklist brokers), the number of report templates, and any historical-study data migration. We agree the schedule in writing after the scoping call.

How does pricing and scoping work?

Pricing starts from $299 as an indicative figure for a single-company base scope. After a short scoping call we send a fixed written quote. Drivers such as multi-company/multi-site operation, PACS/DICOM integration, localized regulatory report formats, and data migration volume increase the quoted scope.

What about support and future Odoo updates?

Every build includes a post-go-live support window for defect fixes and configuration tweaks. Because you receive the full source and git repository, you are never locked in. We also offer paid maintenance and version-upgrade work if you later move from Odoo 17.0 to 18.0 or 19.0.

Does it work with Odoo Community or Enterprise?

Both. We build against your edition and target Odoo 17.0, 18.0, or 19.0 to match your running version. During scoping we flag any capability that depends on an Enterprise-only feature so the design and quote reflect your edition accurately.

Can it integrate with our PACS or imaging modalities?

Yes, as scoped work. The module exposes an XML-RPC/JSON-RPC surface and can store DICOM exports and key images as attachments bound to each study. Direct PACS gateways, DICOM modality-worklist (MWL) feeds, and HL7 bridges are integration options that we size during scoping.

Do you migrate our existing studies and reports?

We can, as a scoped add-on. Migration volume and source-format cleanliness drive the effort, so we assess a sample during scoping and quote the migration separately from the base build if you need it.