Why a radiologist studies imaging informatics

About a year ago I shared a short note on LinkedIn: I had officially earned my Certified Imaging Informatics Professional (CIIP) credential from the American Board of Imaging Informatics.

It was a one-line post. A few people asked me afterwards why a practising radiologist would sit an exam about networks, standards and systems. That is a fair question, and the answer is a big part of why SOMATIQ exists, so I want to give it properly here. First, a few words about what imaging informatics is and what the credential involves; then why I think it matters for radiologists, and for the centres they work in.

What imaging informatics actually is

That sounds abstract until you follow one CT scan through a hospital.

The referring doctor needs the images and the report, sometimes at midnight, sometimes in another city. Somewhere along the way the data has to be secured, audited and kept for years. (Our guides to DICOM and to connecting radiology to the HIS walk through each of these steps in more detail.)

Every one of those handoffs can fail. A wrong patient ID at registration, a modality sending to the wrong destination, a prior that never loads, a report that sits unsigned because nobody saw it in the queue. Most of these failures are invisible to the patient. They show up as delay.

Imaging informatics is the discipline of making those handoffs work. It covers standards such as DICOM and HL7, system architecture, workflow design, data management, security, and the people and processes around all of it.

What the CIIP credential is

The CIIP is awarded by ABII, a non-profit founded by the Society for Imaging Informatics in Medicine (SIIM) and the American Registry of Radiologic Technologists (ARRT). (About ABII) A few practical points, from ABII's own pages:

1. Eligibility is based on a points system that counts experience, formal education and other credentials or continuing education. (Qualification requirements)

2. The exam has 170 questions across ten knowledge domains, with a maximum time of 170 minutes. Candidates can take it at a Pearson VUE centre or at home with a remote proctor. (About the test)

3. Keeping the credential requires continuing education and meeting ABII's 10-year requirements. (Maintaining certification)

The credential is not designed only for doctors. The professionals ABII features on its site include PACS administrators, IT and informatics analysts and software engineers. That is exactly what makes it useful for a radiologist. It forces you to learn the language of the people who build and run the systems you work in every day.

Why a radiologist should care

I have read more than 100,000 scans. For most of that time, the software was something that happened to me. Slow PACS. Too many clicks. Poor access to priors. Multiple logins. Reports typed in Word and pasted into the RIS/HIS.

Like most radiologists, I complained about it and carried on. The worklist does not wait.

Studying informatics changed how I saw those irritations. A prior that takes a minute to load is not bad luck; it is a design decision about where data is stored and how it is fetched (we wrote about exactly this in Priors on screen). A report that has to be retyped is an integration that was never built. Once you understand the cause, you stop accepting it as part of the job.

There is also a simpler reason. Radiology is one of the most digital specialties in medicine. Our entire work product passes through software. A cardiologist can examine a patient without a computer. A radiologist today cannot read a single digital study without one. It seems odd that so few of us understand how that software works.

Why radiologists building software matters

Over the last decade, I've watched medical imaging evolve from both sides of the fence, first as a radiologist and later from within the technology ecosystem.

I wrote recently, in Beyond the Algorithm (also on our blog), that engineering often underestimated the depth of radiological judgement, while radiologists were rarely embedded deeply enough in the process to correct for it. We stayed out for rational reasons: no protected time, tedious annotation work, genuine medicolegal caution, and development processes that brought us in only at the end. Both professions behaved sensibly inside a badly designed process.

The fix is not for every radiologist to become a programmer. It is for radiologists to be in the room from the start, and to know enough about the systems to ask the right questions. Informatics gives you that vocabulary.

In practice, this shows up in small decisions. Which priors should load first when a follow-up CT opens? What should happen when a study arrives with an unexpected series description (Naveen covered why that is so common in DICOM headers and AI routing)? Where should an AI result appear so that a tired radiologist at 2 a.m. actually sees it, and how much should it be allowed to reorder the queue (see AI triage on the worklist)? An engineer can build any of these. A radiologist with informatics training can say which one matters, and why.

What this means for a centre

You do not need a CIIP on staff to run a good imaging centre. But a few habits from informatics are worth borrowing.

1. Treat radiology software as clinical infrastructure. It is not an accessory to the scanner. When it slows down, ER physicians, surgeons, oncologists and patients wait.

2. Ask about standards when you buy. Does the system follow DICOM and HL7 properly? Can it integrate with your HIS? How does it handle priors from other centres?

3. Give someone ownership. In many Indian centres, PACS and RIS problems fall to whoever is nearest. Name a person, even part-time, who understands the workflow end to end.

4. Bring your radiologists into decisions. They are the heaviest users of the system. Their complaints are usually precise descriptions of design problems.

If a radiologist on your team is curious about informatics, encourage it. SIIM and ABII publish a lot of material, and the CIIP is one structured way to learn it. The larger point is that the software a radiologist works in is part of the diagnosis, because every delay and every missing prior ends up in the report or in the time it takes to arrive. Understanding that software, even a little, is part of doing the job well.

Related reading

• Beyond the algorithm — the missing specification in medical AI.
• The most compressed decade — why the pace of change makes this urgent.
• Why we built SOMATIQ — the founders' reasons, in their own words.
• How to choose a PACS in India — the standards questions, turned into a buyer's checklist.
• AI is with the radiologist — why the platform has to come before the algorithm.
• Prima Diagnostics case study — eight centres on one system, registration to signed report.

FAQ

What is imaging informatics?

ABII describes it as the subspecialty concerned with how medical images are used and exchanged throughout complex healthcare systems. In practice it covers standards like DICOM and HL7, PACS and RIS architecture, workflow, data management and security.

What is the CIIP credential?

The Certified Imaging Informatics Professional (CIIP) is a certification awarded by the American Board of Imaging Informatics, which was founded by SIIM and ARRT. Candidates qualify through a points system based on experience, education and other credentials, then pass a 170-question exam.

Can a radiologist in India take the CIIP exam?

ABII states that the exam can be taken at a Pearson VUE centre or at home with a remote proctor. Check ABII's qualification requirements and test pages for current eligibility and logistics.

Why does it matter that radiologists help build radiology software?

Because radiologists are the heaviest users of these systems and understand which delays and errors matter clinically. When they are involved from the start, rather than only at validation, the software is more likely to fit how radiology is actually practised.