Skip to Content

AminiTech HMS PACS / DICOM Bridge

by
Odoo

$ 186.99

v 18.0 Third Party
Live Preview
You bought this module and need support? Click here!
For Odoo 18.0 · Community & Enterprise · AminiTech HMS

PACS / DICOM Bridge (Radiology Imaging)

$289 $199 ★ 30% LAUNCH OFFER

Connect your hospital to any PACS — from Orthanc and dcm4chee to AWS HealthImaging. A DICOM-aware bridge that mirrors the full Study / Series / Instance hierarchy inside Odoo, drives the Modality Worklist, and carries every exam from ordered to a signed radiology report. Launch studies straight into the OHIF viewer without leaving the patient record.

✅ Multi-vendor PACS✅ DICOM MWL✅ OHIF viewer launch✅ Signed reports ⭐ 90 days free support
💻 Try the LIVE demo — login demo / demo 📚 Documentation
PACS / DICOM Bridge (Radiology Imaging) for Odoo 18 - AminiTech HMS
Speak your patients' language

Works in your language

Every screen, label and report is translated — switch a user's language in Odoo and the whole system follows.

EnglishFrançaisEspañolPortuguêsKiswahiliDeutsch中文العربية
6

PACS vendors supported out of the box: Orthanc, dcm4chee, Conquest, Dicoogle, Google Healthcare API and AWS HealthImaging.

8

Dedicated models — server registry, modality dictionary, study, series, instance, modality worklist, Q/R audit log and radiology report.

3

Automated crons keep you honest: study sync, stale-study flagging and modality-worklist purge run on schedule.

📸 Live screens Features ★ All features Setup in 4 steps ★ Live demo ↗ HMS family FAQ Support & Contact
RADIOLOGY IMAGING

What you get

Every feature below is live on the public demo — open hms.aminitechsolutions.com (login demo / demo) and walk it yourself.

Register any PACS server, or several
01 · PACS REGISTRY

Register any PACS server, or several

A multi-vendor server registry connects Odoo to Orthanc, dcm4chee, Conquest, Dicoogle, Google Healthcare API or AWS HealthImaging. Each study, series and instance records which server it lives on, so multi-site and cloud-archive setups stay traceable.

Studies flow ordered → acquired → reported → finalized
02 · STUDY PIPELINE

Studies flow ordered → acquired → reported → finalized

Each study carries accession number, Study Instance UID, patient, modality, anatomic region, body part, referring and performing physician, priority and size in MB — with a kanban board grouped by state and a statusbar on the form so nothing stalls unnoticed.

Structured radiology reports with sign-off
03 · REPORTING BENCH

Structured radiology reports with sign-off

Reports capture clinical history, technique, findings, impression and recommendation, plus RSNA-style structured findings JSON. Critical-finding and peer-review flags are tracked in the chatter, and one click signs the report — stamping who signed, when, and moving it to Final. Addenda supported.

DICOM MWL keeps machines in sync
04 · MODALITY WORKLIST

DICOM MWL keeps machines in sync

Scheduled exams publish to a Modality Worklist so CT, MR, US, XR, MG and other modalities pull patient demographics instead of retyping them. A cron purges stale worklist entries automatically.

OHIF viewer launch and Q/R audit log
05 · VIEW & AUDIT

OHIF viewer launch and Q/R audit log

Open any study in the embedded OHIF viewer iframe, and query the archive via DICOMweb QIDO-RS endpoints. Every query/retrieve is written to an audit log you can review from Configuration.

Radiologist, Technologist, Admin
06 · ROLE-BASED ACCESS

Radiologist, Technologist, Admin

Three security groups split the department cleanly: technologists work the worklist and acquisitions, radiologists own reporting and sign-off, admins configure servers, modalities and crons.

Real screens — not mockups

See it running on the live demo

Every screen below is a real screenshot from the working system at hms.aminitechsolutions.com — log in with demo / demo and try it yourself.

PACS / DICOM Bridge (Radiology Imaging) running live
Live screen recording — captured from the running demo.
PACS / DICOM Bridge (Radiology Imaging) live screen
PACS / DICOM Bridge (Radiology Imaging) live screen
PACS / DICOM Bridge (Radiology Imaging) live screen
PACS / DICOM Bridge (Radiology Imaging) live screen
PACS / DICOM Bridge (Radiology Imaging) live screen
PACS / DICOM Bridge (Radiology Imaging) live screen
Everything included

All 62 features — nothing held back

The complete capability list for PACS / DICOM Bridge (Radiology Imaging), straight from the module. Every one of these is live on the demo at hms.aminitechsolutions.com.

PACS / DICOM Bridge (Radiology Imaging) feature tour
PACS Server Registry10 features
✓
Multi-Vendor PACS Server Registry — Register any number of PACS archives with unique code, AE title, host, DICOM port, country code, status and notes.
✓
Six Supported Server Types — Choose Orthanc, dcm4chee, Conquest, Dicoogle, Google Healthcare API or AWS HealthImaging per server.
✓
DICOMweb & WADO Endpoint Config — Store separate base URL, DICOMweb URL and WADO-URI URL for each archive to route queries and image retrieval.
✓
Four Authentication Modes — Configure None, Basic Auth, OAuth 2.0 or API Token credentials per server, with password/token fields masked in the form.
✓
Live Connection Test Button — One-click 'Test Connection' pings Orthanc /system or DICOMweb /studies over REST and posts the HTTP result to the chatter.
✓
Server Status Tracking — Each server carries an Active/Disabled/Error status badge that auto-flips to Error on failed pings or syncs.
✓
Study Count Telemetry — Stores a per-server study count and last-sync timestamp so admins see archive volume at a glance.
✓
Unique Server Code Constraint — Database constraint guarantees each PACS server code is unique across the registry.
✓
Seeded Demo Servers — Ships a local on-prem Orthanc and a regional dcm4chee cloud server as ready-to-edit demo configurations.
✓
Server List, Kanban & Search — Browse servers as a list or kanban with filters for Active/Disabled and grouping by server type or status.
Study / Series / Instance Hierarchy14 features
✓
Three-Level DICOM Hierarchy — Model studies, their series and individual image instances as a linked Study to Series to Instance tree.
✓
DICOM Study Records — Capture Study Instance UID, accession number, study date, description, anatomic region and body part examined per exam.
✓
Patient Linkage — Link each study and worklist entry to the shared hms.patient record for a unified patient imaging history.
✓
Study Lifecycle State Machine — Track studies through Ordered, Acquired, Reported, Finalized and Cancelled states on a status bar.
✓
Secondary Study Status — Additional Scheduled/In Progress/Completed/Reported/Finalized/Cancelled status captures the clinical workflow stage.
✓
Priority Triage — Flag studies STAT, Urgent, Routine or Research for radiology triage and a dedicated STAT filter.
✓
Series Records — Store Series Instance UID, series number, description, protocol name, contrast agent, image count and size per series.
✓
Image Instance Records — Store SOP Instance UID plus rows, columns, bits allocated, photometric interpretation, transfer syntax and file size per image.
✓
WADO Image & Thumbnail URLs — Each instance holds its WADO-URI image URL and thumbnail URL for direct image retrieval.
✓
Referring & Performing Physicians — Record referring physician (user) and free-text performing physician on every study.
✓
Study Size & Image Counters — Aggregate series count, image count and study size in MB for capacity and reporting.
✓
UID Uniqueness Constraints — Database constraints enforce unique Study, Series and SOP Instance UIDs to prevent duplicate imports.
✓
Study Kanban, Pivot & Graph — Analyse studies via kanban by state plus pivot and graph views measuring image counts by modality and state.
✓
Computed Study Reference — Auto-derives a human-readable study reference from accession number or Study Instance UID.
Radiology Reporting10 features
✓
Structured Radiology Report — Author reports with distinct clinical history, technique, findings, impression and recommendation sections.
✓
Report Lifecycle States — Move reports through Draft, Preliminary, Final, Addended and Cancelled statuses on a status bar.
✓
Sign & Finalize Button — One click stamps the signer, signed timestamp and flips the report to Final state.
✓
Critical Finding Flag — Mark reports as critical findings, trackable and filterable for urgent communication follow-up.
✓
RSNA Structured Findings — Store machine-readable structured findings as RSNA-style JSON alongside the narrative report.
✓
Addendum Support — Append addendum text to signed reports and move them to an Addended state.
✓
Peer Review Flag — Mark reports as requiring peer review for quality-assurance workflows.
✓
Dictation Method Tracking — Record whether a report was authored Manual, Voice Recognition, Template or Ambient AI.
✓
Reports Embedded on Study — View and open a study's reports directly from a dedicated Report tab on the study form.
✓
Report Analytics Views — Kanban, pivot and graph views break reports down by radiologist and state with critical-finding and signed filters.
Modality Worklist (MWL)7 features
✓
DICOM Modality Worklist — Schedule imaging procedures the modality can query, with scheduled datetime, station AE title and procedure codes.
✓
Auto-Generated Accession Numbers — New worklist entries receive an ACC-prefixed sequence accession number when none is supplied.
✓
MWL Status Workflow — Track entries through Scheduled, Arrived, In Progress, Completed, Discontinued and Cancelled statuses.
✓
Pre-Exam Safety Checklist — Capture allergies, isolation-required, contrast-required, GFR-check-done and pregnancy-check-done flags before imaging.
✓
Requesting Physician & Reason — Record the requesting physician and clinical reason for each scheduled procedure.
✓
Unique Accession Constraint — Database constraint keeps worklist accession numbers unique.
✓
Worklist Analytics — Kanban by status plus pivot and graph views and filters for Scheduled/Arrived/Cancelled and grouping by modality.
DICOMweb & Viewer Integration5 features
✓
QIDO-RS Studies Endpoint — Exposes /pacs/dicomweb/studies returning studies as DICOM+JSON, filterable by PatientID, AccessionNumber and modality.
✓
Study Metadata Endpoint — Exposes /pacs/dicomweb/studies/<uid>/metadata returning study and per-series metadata in DICOM+JSON.
✓
OHIF Viewer Launcher — /pacs/study/<id>/viewer renders an OHIF viewer page embedding the study by UID against its server's DICOMweb URL.
✓
Q/R Query Audit Log — Records every patient/study/series/image query with level, criteria, result count, status, user and error message.
✓
Q/R Audit Analytics — Kanban, pivot and graph views with Failed/Completed filters and grouping by server and status for query auditing.
Modality Dictionary4 features
✓
20 Seeded Imaging Modalities — Ships CT, MR, US, XR, CR, DX, MG, NM, PT, RF, XA, IO, IVUS, DG, OPT, OCT, GM, BMD, ES and OT out of the box.
✓
Modality Metadata — Each modality carries DICOM code, full name, SOP Class UID, category, typical size in MB and an IV-contrast flag.
✓
Modality Categorization — Group modalities into Radiography, CT, MRI, Ultrasound, Nuclear Medicine, Mammography, Fluoroscopy or Other.
✓
Unique Modality Code — Database constraint enforces unique DICOM modality codes.
Automation & Scheduled Jobs4 features
✓
Daily Study-Count Sync Cron — Daily job pulls live study counts from each active Orthanc/DICOMweb server, falling back to local counts on failure.
✓
Hourly Stale-Study Flagger — Hourly job posts a chatter warning on acquired studies older than 7 days that still have no report.
✓
Weekly MWL Purge — Weekly job deletes worklist entries cancelled more than 90 days ago to keep the worklist clean.
✓
Accession Number Sequence — Provides an ACC-prefixed, 8-digit padded sequence for automatic worklist accession numbering.
Security & Access Control4 features
✓
Three-Tier RBAC Roles — Ships PACS Technologist, PACS Radiologist and PACS Admin groups with implied-inheritance escalation.
✓
Model Access Rules — ir.model.access.csv grants per-role create/read/write/unlink rights across all PACS models.
✓
Auto-Grant Admin on Install — Post-init hook adds the superuser to all three PACS groups so the app is usable immediately after install.
✓
Mail Thread & Activities — Servers, studies, reports and worklist entries carry chatter tracking and scheduled activities via mail mixins.
Navigation & Integration4 features
✓
PACS / Radiology Menu Suite — Adds a PACS/Radiology section under HMS Integration with Studies, Worklist, Reports, Series, Instances menus.
✓
Configuration Menus — Dedicated configuration submenus for PACS Servers, Modalities and the Q/R Audit Log.
✓
HMS Base & Patient Integration — Depends on aminitech_hms_base and the concept dictionary, reusing the shared patient master and HMS menu tree.
✓
Phase Gate Marker — Includes a phase-4 gate data record tying the module into the AminiTech HMS suite build sequence.
Setup in 4 steps

From install to first live workflow

Install
1 · Install    2 · Register your PACS

Install AminiTech HMS: PACS / DICOM Bridge from Apps. Required HMS apps (HMS Base, Concept Dictionary) are added automatically at checkout and install with it. Under PACS / Radiology > Configuration > PACS Servers, add your archive — Orthanc, dcm4chee, Conquest, Dicoogle, Google Healthcare API or AWS HealthImaging. Demo data ships to explore first.

Run your first study
3 · Run your first study    4 · Go live

Create a study with accession number, patient and modality, publish it to the Modality Worklist, then move it through acquired to reported and sign the radiology report. Enable the sync, stale-study and MWL-purge crons, assign Radiologist / Technologist / Admin groups to your staff, and launch studies in the OHIF viewer from day one.

Save with a suite

Buy this app on its own, or get it in a suite

Buying more than a couple of apps? The Complete Suite gives you 170 modules for $3,999 in one purchase — usually less than the apps bought separately, and everything is installed and updated together.

Clinic Suite
$499
49 modules — a full outpatient clinic
—
View the Clinic Suite ↗
Hospital Suite
$1,499
78 modules — a full hospital
—
View the Hospital Suite ↗
BEST FIT FOR THIS APP
Complete Suite
$3,999
170 modules — the entire HMS catalogue
✓ includes this app
View the Complete Suite ↗
What's in your download

PACS / DICOM Bridge installs with everything it needs

This app builds on the apps below. Odoo adds them to your cart automatically and delivers everything in one download — you are only charged for apps you don't already own.

Adds these apps to your cart automatically
+Patient Management
✓ Plus 9 more modules included free — the code that powers every feature, delivered in the same download.

Fitting out a whole facility? The Complete Suite includes this app and its whole family in one purchase.

FAQ

Common questions

What other apps does this module require?
It depends on AminiTech HMS Base and the HMS Concept Dictionary (plus standard mail). Required apps are added to your cart automatically at checkout — no manual dependency hunting.
Does it work on Odoo Community and Enterprise?
Yes, both Community and Enterprise editions of Odoo 18 are fully supported. It does not run on Odoo Online (SaaS), since custom modules cannot be installed there.
Do I need a specific PACS vendor?
No. The server registry supports Orthanc, dcm4chee, Conquest, Dicoogle, Google Healthcare API and AWS HealthImaging, and the DICOM data model (Study / Series / Instance, MWL, QIDO-RS) is vendor-neutral.
Does it replace my PACS or viewer?
No — it is a bridge. Your PACS keeps storing the pixels; Odoo mirrors the study hierarchy, runs the worklist and reporting workflow, and launches the OHIF viewer in an iframe for reading.
What support do you provide?
Every purchase includes a 90-day bug-fix guarantee. Reach us any time at reach@aminitechsolutions.com — we respond fast and ship fixes, not workarounds.
Support & Contact

Talk to us today

🏆
90 days of free support included with your purchase
Real people, business hours, typical first reply under 4 hours — including installation help and configuration for your hospital.
⭐ Included — no extra cost
✉️
Email
reach@aminitechsolutions.com
📞
Phone / WhatsApp
+254 746 883 809
💻
Live demo
hms.aminitechsolutions.com
📚
Documentation
aminitechsolutions.com/docs
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Calendar (calendar)
• Contacts (contacts)
• Discuss (mail)
• Employees (hr)
Community Apps Dependencies
Lines of code 35618
Technical Name aminitech_hms_app_pacs
LicenseOPL-1
Websitehttps://aminitechsolutions.com 
Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.