Trinity Reporting Engine by SOMATIQ

Most conversations about better radiology reporting end in the same place: "We would need to integrate it with our RIS and PACS." Then, quite often, nothing happens for months. Integration is real work. Someone has to talk to the PACS vendor, someone has to map fields, someone has to test it, and the centre has to accept some risk to a system that is already running. For a large hospital that might be worth it. For a radiologist who reports for four centres on four different systems, it is never going to happen.

So the radiologist keeps typing reports in Word and pasting them into the RIS or HIS, or into whatever text box the PACS provides. Every impression is written from scratch and every structure is done by hand. The Trinity Reporting Engine by SOMATIQ (Trinity, for short) is our answer to that situation. Let's go over what it is, how it works, what you give up by not integrating, and who it suits.

What we learned at IRIA 2026

We showed the first version of this product, under its earlier name, at IRIA 2026 in Hyderabad, alongside our full RIS-PACS platform. It crossed 100 sign-ups at the conference.

That number told us something specific. A lot of radiologists are not waiting for their centre to replace its PACS. They want fast, intuitive reporting now, without complex integrations. Trinity is built for exactly that. (We wrote up the wider conversations from that week in What radiologists told us at IRIA 2026.)

What Trinity is

That sounds almost too simple, and it is deliberate. Because Trinity does not need to connect to anything, it works with any RIS or PACS, and a radiologist can start using it the same day. The disadvantage, which we come to below, is that it also cannot see anything in those systems unless you bring it in.

How it works

The workflow is characterised as follows.

The shift we are aiming for is small but important. In a traditional editor, you type and the system records; structure is done manually, every time, and impressions are written from scratch. In Trinity, you describe what you see, and the structuring and drafting happen around you. If your centre is moving towards templates, this matters, because it removes most of the time cost that makes radiologists abandon them (see Structured reporting for where templates earn their place). Dictation itself is not new to our radiologists either; on the full platform they already talk to the worklist to move between cases.

An assistant, not a chatbot

Trinity's assistant is built for questions in the middle of a report. You ask, in the context of what you have written. For example:

• "What are the differentials for this appearance?"
• "Is this finding consistent with the clinical history?"
• "Make this impression more concise."
• "Are there any critical findings I should flag?"

The aim is a knowledgeable colleague sitting next to you, not a general-purpose chat window. It works from your findings rather than from a generic search, and it is designed to rewrite without changing clinical meaning; the radiologist still checks every rewritten finding and impression before signing.

It does not read the images, and it does not sign anything. The observations are the radiologist's, and so is the final report. Trinity helps with the writing and the thinking around it.

What you give up by not integrating

We would rather be clear about the trade-offs than have someone discover them later. There are three.

1. There is a copy-paste step. The report has to be moved into your RIS or PACS by hand. For most radiologists today this is no change at all, because they already paste from Word, but it is a step.
2. Trinity on its own does not pull data from your systems. It does not see your worklist, your priors or the patient's previous reports unless you bring that information in yourself.
3. It does not manage workflow. Assignment, turnaround tracking, multi-centre worklists and report delivery belong to a RIS-PACS.

If workflow is what your centre needs, our full platform, the SOMATIQ Unified RIS-PACS, runs the whole cycle in one system: registration, scheduling, billing, acquisition, reporting and report delivery. Inside the platform, reporting also has built-in speech-to-text, LLM-assisted report drafting with impression checks and inconsistency detection, and live co-reporting between radiologists and transcriptionists, because the reporting tool can see the study, the priors and the order. (For the difference between the two kinds of system, see RIS, PACS or RIS-PACS, and for what to ask when choosing one, our PACS checklist.) Standalone Trinity is for when you want better reporting without changing anything else.

Who it suits

• Radiologists who report for several centres, each with a different PACS. One reporting tool across all of them.
• Teleradiologists and home readers who work in whatever system each client provides.
• Centres not ready to change their PACS, but whose radiologists want better reporting now.
• Individual radiologists who simply want to stop writing every impression from scratch.

What this means for a centre

If your radiologists are typing reports in Word, or wrestling with a PACS editor that was never built for thinking, Trinity is a low-risk thing to try. Nobody in IT needs to be involved, and nothing in your existing setup changes. Three things are worth doing before you roll it out.

1. Start with a small trial. Ask two or three radiologists to use it for a week on their normal work, and then ask them plainly whether it saved time and whether the reports read better. Their answer matters more than any brochure.
2. Agree a few report formats with your radiologists, so structured output stays consistent across readers.
3. Check your data responsibilities. Under India's DPDP framework, patient information in reports needs proper handling, whatever tool produces them. Read the Act and Rules on the MeitY site (our DPDP guide summarises them for imaging centres), talk to your counsel, and ask us how Trinity handles report data.

The practical upshot is that better reporting does not have to wait for a PACS replacement or an integration project. A standalone reporting engine gives radiologists most of the benefit on day one, at the cost of a copy-paste step and no access to priors; a centre that later wants worklists, priors and delivery in the same place can move to the full platform without changing how its radiologists write.

Related reading

• Structured reporting — when templates help and where AI removes their cost.
• What radiologists told us at IRIA 2026 — the conversations behind this product.
• Priors on screen — what an integrated system adds that a standalone tool cannot.

FAQ

What is the Trinity Reporting Engine?

Trinity is SOMATIQ's AI reporting environment for radiologists. Used standalone, it runs in the browser next to any PACS or viewer, structures findings, refines impressions, suggests differentials and answers clinical questions, and produces a report you can paste into any RIS or PACS.

Does Trinity need to be integrated with my PACS or RIS?

No. Standalone Trinity does not connect to your PACS or RIS. You open it in a browser tab alongside your viewer and copy the finished report into your existing system. That is why it works with any RIS or PACS without IT involvement.

Does Trinity read the images?

No. The radiologist reads the images and describes the findings by dictating or typing. Trinity helps structure the report, refine the impression and answer questions, and the radiologist remains responsible for the final report.

What is the difference between Trinity and the full SOMATIQ platform?

Trinity covers reporting only. The full platform also handles registration, scheduling, billing, the worklist, the archive and report delivery, so reporting there can see priors and the order.