Medical Imaging AI#

Conceptual Explanation#

DICOM (Digital Imaging and Communications in Medicine)

DICOM is the international standard for medical imaging data and communications. It defines:

• Image storage format: A DICOM file (.dcm) contains both the image pixel data and a structured header (DICOM attributes) that stores patient demographics, study metadata, acquisition parameters, and equipment information.
• Network protocol: DICOM defines services for sending, receiving, querying, and retrieving images between PACS, modalities, and viewing workstations.
• Structured reporting: DICOM Structured Reports (SR) store coded measurements, observations, and annotations in a machine-readable format attached to an imaging study.

For AI integration, the relevant DICOM services are:

• C-STORE: Sending a DICOM image from one system to another (used when PACS sends a study to an AI system for analysis)
• C-FIND / C-MOVE / C-GET: Querying and retrieving specific studies from a PACS
• DICOMweb (WADO-RS, STOW-RS, QIDO-RS): RESTful equivalents of the traditional DICOM network services, used by modern AI platforms that prefer HTTP over the traditional DICOM protocol stack

PACS (Picture Archiving and Communication System)

PACS is the system that stores, retrieves, and displays medical images. It is the central hub of the radiology workflow: images flow from imaging modalities (CT scanners, MRI machines, X-ray systems) to PACS, and from PACS to radiologist workstations for reading. For AI integration, PACS is the source of imaging studies and the destination for AI-enhanced worklist management.

Core Architecture#

Common Mistakes#

Deploying Outside Cleared Indication. Using a 510(k)-cleared ICH detection AI on pediatric patients when the clearance covers adults only, or using it on MRI when cleared for CT, creates regulatory and liability exposure. Verify the cleared indication against the intended use before procurement and again before deployment.

DICOM Header PHI Exposure. Organizations that send DICOM studies to cloud AI services without DICOM header de-identification transmit patient identifiers (name, MRN, date of birth) to the AI vendor. Confirm whether the AI service requires patient identity, and de-identify the DICOM header if it does not.

Assuming Radiologist Will See the AI Overlay. AI overlays that require a separate workflow step to view (clicking a separate AI review button, opening a separate viewer) are rarely used. Design AI output delivery so that the AI overlay is visible in the radiologist's default study view without additional steps.

Best Practices#

• Verify 510(k) clearance status and cleared indication before procurement and before deployment
• Confirm BAA coverage for any cloud-based AI service that receives DICOM images containing PHI
• Deliver AI findings in the radiologist's standard PACS viewer — overlays that require workflow changes are not adopted
• Monitor AI performance with institution-specific ground truth quarterly — vendor-published performance metrics may not generalize to your scanner hardware and patient population
• Govern radiology AI through the same Model Review Board as other clinical AI use cases

Trade-offs#

Interview Questions#

Q: A radiology department wants to deploy AI that automatically flags intracranial hemorrhage on CT head studies. What regulatory and integration questions must be answered before deployment?#

Category: Architecture / Regulatory Difficulty: Senior Role: AI Architect / Healthcare AI Consultant

Answer Framework:

Regulatory questions first: What is the product's FDA clearance status? Is there a 510(k) clearance for adult head CT ICH detection? What is the cleared indication — does it match the patient population (adult vs. pediatric)? Does the cleared indication cover the use as "triage" (flagging for radiologist review) or as "detection" (the AI identifies ICH)? These are different intended uses with different evidentiary requirements.

If the product is 510(k)-cleared for the intended use: does the healthcare organization need to do anything for regulatory compliance? In most cases, no — the 510(k) is held by the vendor, not the deploying organization. But the deploying organization must ensure the deployed version matches the cleared device description, and must have a process for applying FDA-required software updates in a timely manner.

Integration questions: How does the AI receive studies — C-STORE from PACS, or DICOMweb? How does the AI return its output — DICOM SR, worklist message, or overlay? Does the radiology workflow allow automatic re-prioritization of studies, or does the radiologist control the worklist? How long does AI inference take — is the latency acceptable for emergency use (under 60 seconds)?

HIPAA question: Does the AI service receive DICOM images in the cloud? If so, is a BAA in place? Does the AI require patient identifiers from the DICOM header, or can it operate on de-identified images?

Key Points to Hit:

• 510(k) clearance verification, including patient population and intended use scope
• Vendor holds the clearance; deploying org must deploy within the cleared indication
• DICOM integration mechanism and AI output format
• Worklist modification mechanism and radiologist workflow impact
• HIPAA BAA if cloud-based

Key Takeaways#

• Radiology AI operates on DICOM images, not text — integration with PACS and the radiology worklist, not the EHR, is the primary engineering challenge
• Almost all clinical radiology AI requires FDA 510(k) clearance as SaMD — verify clearance and match the cleared indication to the intended use before procurement
• The DICOM router is the orchestration layer for multi-AI radiology workflows — it routes incoming studies to the appropriate AI services based on modality and indication
• Deliver AI output in the radiologist's standard PACS viewer without additional workflow steps — overlays that require extra clicks are not adopted
• Monitor performance with institution-specific ground truth — vendor performance metrics on public datasets may not reflect your scanner hardware and patient population