Integration & implementation

Connected systems, tested before go-live.

Teleradiology integration for facility IT, PACS and RIS teams. Remote radiology reading depends on four flows working every time: images, orders, prior studies and reports. Implementation gives each flow an owner, builds the connection and proves the whole pathway before the first patient study.

How a study moves

Six systems, one pathway.

Integration is planned around your existing systems. Compatibility, interface needs and any required changes are confirmed during scoping.

  1. ModalityAcquires the images
  2. PACSStores and sends by DICOM
  3. Secure connectionVPN or TLS, agreed with IT
  4. Reading worklistPrioritized and matched
  5. Signed reportPreliminary or final
  6. RIS, EHR or PACSFiled where clinicians look
Orders and clinical history reach the worklist alongside the images, and relevant prior studies are available to the reader. Colors show who usually owns each system: your facility, the reading service, or both.

Responsibility map

Who owns each flow.

Choose a flow to see what your facility owns, what the reading service owns, what is agreed together, and the test that proves it before go-live.

Orders & history

Your facility

  • Order entry with the reason for examination
  • Protocol selection and technologist notes
  • Priority set at ordering or acquisition

Reading service

  • Receives order details with the study
  • Flags missing history through the agreed route

Agreed together

  • Order interface or worklist format
  • Priority mapping: STAT, urgent, routine

Test before go-live: An order with a known reason for examination appears correctly in the reading worklist.

Integration options

Common options, and what to watch.

DICOM carries images and HL7 carries orders and results in most radiology departments; IHE’s Scheduled Workflow profile describes how the two fit together. The right choice for each flow depends on your systems and your IT team’s standards.

Is a modality worklist the same as a reading worklist?

No. DICOM Modality Worklist supplies scheduled procedure information to image-acquisition equipment. The radiologist’s reading queue and delivery of the required clinical history are separate parts of the integration plan. A modality worklist alone does not provide comprehensive access to clinical information.

The DICOM Modality Worklist definition, K.6.1.1 describes this acquisition role. See also the modality worklist glossary entry.

Integration options for each flow and what to watch for
FlowCommon optionsWatch for
ImagesDICOM send from PACS or modality over a VPN or TLS connection; a gateway appliance; DICOMwebAE titles, ports and certificates that expire; routing failures that nobody notices
Orders & historyAn agreed HL7 order/history interface; an approved requisition documentPriority mapping, and required clinical context lost between systems
Prior studiesSent with the new study; retrieved on request; viewer access to the archiveWhich priors count as relevant, and how long they are kept on the reading side
ReportsHL7 results to RIS or EHR; a document or DICOM structured report to PACS; portal accessAddenda reaching every destination, and report status updates
IdentifiersMedical record number with its issuing facility; site prefixes on accession numbersCollisions between sites, merges and corrections

Exception handling

When something doesn’t arrive as expected.

Every pathway has bad days. These are the exceptions worth rehearsing before go-live, and what should happen in each.

Images arrive incomplete

  1. The reader stops before reporting on partial data.
  2. The facility contact hears what is missing, through the agreed route.
  3. The study returns to the worklist when complete, and the delay is recorded as an exception rather than hidden in turnaround.

A relevant prior is not available

  1. The reader checks the agreed prior sources.
  2. If a relevant prior exists but cannot be retrieved, the report says so and a request goes to the facility.
  3. If the prior later changes the interpretation, an addendum follows.

The order or history is missing

  1. The reader asks through the named contact route instead of guessing.
  2. Urgent studies are read with what is available, and the limitation is stated.
  3. Recurring gaps are reviewed with the facility, usually as an order-entry fix.

An urgent finding at 02:00

  1. The reader calls the clinician on the call list for that location and hour.
  2. If nobody answers, the documented escalation takes over.
  3. The call is documented: who was reached, when, and what was communicated.

An interface goes down

  1. Define how interrupted study flow is detected, who alerts the other team and when the fallback route takes over.
  2. Urgent studies use the fallback route agreed in the downtime procedure.
  3. After recovery, both sides reconcile everything read during the downtime.

Identifiers do not match

  1. The study is held, not read against the wrong record.
  2. The facility corrects the identifiers at the source.
  3. Repeated mismatches lead to a routing or numbering fix.

A report needs correcting

  1. The reader issues an addendum, preserving the original report.
  2. A significant change is communicated directly to the clinician who acted on the first version.
  3. The event feeds peer review and discrepancy follow-up.

Planning example

Is an image connection the whole integration?

No: one study needs its order, images, report and reconciliation to move as a single pathway, so this example gives each step an explicit owner and shows what that owner does during a synthetic interface outage.

Example, not a client case.

Planning example: one study’s pathway from order to reconciliation, with the owner of each step and its part in a synthetic outage.
StepWhat movesOwnerDuring the synthetic outage
Order and clinical questionThe order, reason for examination and priority reach the reading worklist with the study.Facility RIS teamOrders keep queuing locally, and the facility contact keeps a list of studies waiting to send.
Images and relevant priorsImages and the agreed priors travel by DICOM from the facility PACS over the agreed secure connection.Facility PACS team, with the reading service watching for arrivalsIn this example the image route stops sending. The reading side notices the missing arrivals and alerts the named facility contact.
Worklist and readingMatched studies follow the agreed routing and locking rules; missing information is flagged to the responsible clinical contact under the facility’s escalation procedure.Reading serviceUrgent studies move to the fallback route written in the downtime procedure; routine studies wait for recovery.
Report returnThe signed report and any addendum return to the RIS, EHR or PACS where clinicians look for them.Reading service sends; facility interface team receivesReports issued through the fallback route are listed so they can be filed once the interface is back.
ReconciliationEvery study read during the interruption is matched to its order, report status and destination.Both teams, working from one shared listDuplicates and missing reports are resolved before the outage is closed and reviewed together.

A synthetic example for planning only: it shows no real facility, system, vendor, connection or patient data. Compatibility, interfaces and the downtime procedure are confirmed with your teams during scoping.

Implementation

Five stages, two in parallel.

Eligibility and connectivity usually take the longest, so they start as soon as the scope is clear and run side by side.

  1. Scope

    Examinations, windows, priorities, report types and onsite boundaries written down, starting from your coverage brief.

  2. Eligibility & agreements

    Licensure, credentialing and privileges; the service agreement; privacy and security review, including a business associate agreement where required.

    Runs in parallel
  3. Connectivity

    Image, order, prior and report routes built and tested with approved test data.

    Runs in parallel
  4. Validation

    End-to-end test studies, delivery to every destination, an urgent-call drill and a downtime walkthrough.

  5. Go-live & first review

    A closely watched start and an early review of routing, communication and measures while issues are small.

Use the implementation workbook to map proposed owners and open decisions. The onboarding checklist covers the documents and tests to prepare.

Where responsibility sits

Four layers, each with an owner.

Interoperability, the reading workflow, clinical responsibility and quality review each have a clear owner. Software, including any AI tool, works inside these layers rather than above them.

  1. Interoperability

    Owner: Shared with your IT team

    DICOM, HL7 and FHIR connections that move images, orders, prior studies and reports between your systems and the reading worklist.

    Software and AIAny tool connects through the same standards, and its outputs are labeled and routed like any other data.

  2. Reading workflow

    Owner: Reading service, by agreed rules

    Worklist priority, case matching, study locking and agreed handling of missing or incomplete information.

    Software and AIA tool may suggest; priority and assignment rules stay under radiologist control.

  3. Clinical responsibility

    Owner: The signing radiologist

    Interpretation, the signed report, and direct communication of urgent findings and significant changes.

    Software and AIEvery output is reviewed by the radiologist, who can disagree with it and remains accountable for the report.

  4. Quality review

    Owner: Reading service, with your team

    Peer review, discrepancy follow-up and service measures, reviewed with your team on an agreed cadence.

    Software and AITool performance is monitored over time, with a clear way to pause it when results drift.

AI and accountability

Useful tools, a radiologist accountable.

AI-enabled software is changing parts of radiology workflow, from worklist support to reporting checks. Radstead approaches it the way a reading service should: start from a defined task, prove it locally, keep the radiologist accountable and watch it over time.

The evaluation path for any tool

  1. Define the task

    A specific job in the workflow, and a benefit for patients, clinicians or turnaround that can be measured.

  2. Check its status

    Regulatory status appropriate to the intended use. The FDA’s public list of AI-enabled devices is a starting point, not a substitute for local evaluation.

  3. Validate locally

    Performance checked on representative studies from the sites and equipment it would serve, including where it fails.

  4. Integrate with oversight

    Outputs delivered through standard interfaces, visible to the radiologist and open to challenge, with a fallback when the tool is unavailable.

  5. Monitor and review

    Results tracked after introduction and reviewed with quality data, with a clear way to pause or switch the tool off.

Where Radstead stands today

Interpretation and reporting in the Radstead service are physician-led. No AI tool is part of the reading service described on this site, and any tool considered in future would follow the path set out here.

If your facility already uses AI software

  • Whether remote radiologists see its outputs, and in which system
  • How outputs are displayed, for example as worklist flags or attached images
  • How a disagreement between the tool and the radiologist is documented
  • Who monitors the tool, and what happens when it is unavailable

Questions to ask any reading provider about AI

  • Which tools touch our studies, and for what task?
  • What is each tool’s regulatory status for that use?
  • How was it validated on studies like ours?
  • Who reviews its outputs before they affect a report or a priority?
  • How is its performance monitored over time?
  • Are our images or reports used to develop software, and under what agreement?

The multi-society statement on AI tools in radiology from the ACR, CAR, ESR, RANZCR and RSNA sets out these considerations in detail for developers, purchasers and users.

Questions

Technical questions, early.

Do we need to replace our PACS or RIS?

The starting point is your existing PACS and RIS. Confirm compatibility, interface needs and any required changes during integration planning, using your system names and current report workflow.

Is a VPN required?

Not necessarily. Site-to-site VPNs and TLS-secured connections are both common. The choice is made with your IT team against your security standards, and network details are exchanged through their process, not by email.

How are prior studies made available?

They can be sent with each new study, retrieved on request, or viewed through archive access. The agreement defines which priors count as relevant and how long copies are kept on the reading side.

What happens if the connection goes down?

The implementation plan defines how an interruption is detected, who alerts the other team and when the fallback route takes over. Both sides agree the downtime procedure and how studies read during an outage will be reconciled afterwards.

Does the Radstead service use AI to read studies?

No. Interpretation and reporting are physician-led, and no AI tool is part of the reading service described on this site. Any tool considered in future would follow the evaluation path above, with the radiologist accountable for every report.

Can remote reading work with AI software our facility already uses?

That is decided during scoping: whether remote radiologists see the tool’s outputs, how they are displayed, how disagreements are documented and who monitors the tool. The answers depend on the tool, its intended use and your systems.

Can we send images through this website?

No. Do not send images or patient information through this public website. Contact the imaging facility or your care team for their established clinical channel.

References

Primary sources

Standards, professional guidance and public resources referred to on this page.

  1. DICOM PS3.1: Introduction and Overview (current edition)Medical Imaging & Technology Alliance, a division of NEMA · Current edition 2026d at the time of review
  2. DICOM PS3.4 K.6.1.1: Modality Worklist SOP Class DescriptionMedical Imaging & Technology Alliance, a division of NEMA · Current edition 2026d at the time of review
  3. Scheduled Workflow integration profileIHE International
  4. ACR–AAPM–SIIM Technical Standard for Electronic Practice of Medical ImagingAmerican College of Radiology · Revised 2022
  5. Developing, purchasing, implementing and monitoring AI tools in radiology: practical considerations. A multi-society statement from the ACR, CAR, ESR, RANZCR & RSNAACR, CAR, ESR, RANZCR and RSNA · Insights into Imaging, January 2024
  6. List of Artificial Intelligence-Enabled Medical DevicesU.S. Food and Drug Administration
  7. When is a health care provider a business associate of another health care provider?U.S. Department of Health and Human Services

Next step

Bring your systems into the conversation.

Tell us which PACS, RIS and reporting systems you use and how studies move today. Integration planning starts from there.