GLOSSARY
PACS Integration in Clinical Trials
PACS integration in a clinical trial is the direct connection between a hospital or imaging centre's Picture Archiving and Communication System and the trial's central imaging platform, enabling images to be routed to the central platform with minimal or no manual steps by site staff — depending on the integration model. It improves submission completeness, reduces site burden, and reduces a common source of missing or delayed imaging data in multi-site trials.
What is PACS integration in clinical trials?
PACS integration in a clinical trial — also referred to as DICOM PACS integration or cloud PACS integration — is the direct connection between a hospital or imaging centre's Picture Archiving and Communication System (PACS) and the trial's central imaging platform, enabling images to be routed to the central platform with minimal or no manual steps by site staff, depending on the connection model used.
A PACS is the local system hospitals use to store, display, and manage medical images. Without integration, site staff must manually identify trial participant images, export them, and upload them to the trial platform — a workflow that adds steps, introduces opportunities for error, and is one of the most common sources of missing or delayed imaging data in multi-site trials, based on QMENTA's operational experience across imaging studies.
Why PACS integration matters more in clinical trials than in routine clinical care: in clinical care, a missed or delayed image means a radiologist has less data than ideal — inconvenient but not irreversible. In a clinical trial, a missed image at a specific visit means that the patient's endpoint data for that timepoint is permanently gone. Protocol windows cannot be reopened, and the dataset carries a gap that no amount of reconciliation can recover. This asymmetry in consequence is what makes PACS integration a trial infrastructure decision, not just an IT preference.
How PACS integration works
PACS integration uses the DICOM standard's networking protocols — primarily DICOM Send (C-STORE) and DICOM Query/Retrieve (C-FIND/C-MOVE) — to transfer images between the site's PACS and the trial platform. Three connection models are used in practice.
Push routing
The site's PACS is configured to automatically forward trial images to the central platform when they match defined routing rules — a specific study description, scheduled protocol name, or modality type.
The radiographer acquires the image as part of their normal imaging workflow. The routing rule sends it to the trial platform without any additional submission steps from site staff.
Best suited for: sites with cooperative IT departments that can modify PACS routing configuration, and trials where consistent automatic submission is the primary objective. This is the cleanest integration model and the one QMENTA recommends as a default where it is achievable.
DICOM anonymization in push configurations is most reliably performed at the site level — configured in the PACS routing rule or a local gateway — before images are transmitted. When correctly implemented, this design is intended to prevent PHI from leaving the site network. The effectiveness depends on correct anonymization rule configuration and complete coverage of all relevant DICOM tags for that site's scanner and modality.
Pull retrieval
The trial platform queries the site's PACS for images matching trial criteria — by patient ID, study date, or protocol name — and retrieves them on a defined schedule or on demand.
Best suited for: sites whose IT departments cannot or will not modify PACS routing configuration, or where the PACS vendor does not support standard push routing. Pull retrieval requires less change at the site level but places more operational burden on the trial's imaging operations team to monitor and trigger retrievals.
In pull configurations, DICOM anonymization is typically performed at the receiving platform on arrival rather than at the site, because images travel from the PACS to the platform before site-level anonymization can be applied. Receipt-side anonymization and quality checking must be verified before images are made available to readers or analysis pipelines.
Gateway-based integration
A lightweight software agent — installed at the site or hosted in the site's network — acts as an intermediary between the local PACS and the cloud-based trial platform. The gateway handles DICOM routing, anonymization, image quality checking, and transmission without requiring changes to the site's core PACS configuration.
Best suited for: sites with restrictive IT environments, legacy PACS systems with limited DICOM networking support, or complex multi-protocol environments where a dedicated gateway reduces configuration complexity at the PACS level. Gateway-based integration is the most flexible model and often the most practical at large, complex academic medical centres.
Gateway configurations allow anonymization to be applied at the gateway before images leave the local network — combining the privacy benefits of source-level anonymization with lower PACS configuration requirements.
Worried about site setup timelines for your next trial?
QMENTA's site onboarding team manages PACS integration configuration across all major vendors. Technical setup is typically completed within 48 hours of IT approval.
Talk to site operations →
PACS integration vs. manual upload
Manual upload requires a site staff member to identify trial participant images in the PACS, export them as DICOM files, and submit them through a web interface or dedicated uploader tool. This adds workflow steps and creates specific, predictable failure modes.
A concrete example: a site radiographer correctly submits images for a patient's first four visits. At visit five, she misidentifies the images as belonging to a different protocol and omits them from the trial upload. The error surfaces six weeks later during manual reconciliation — after the protocol window for reacquisition has closed. The patient's visit five endpoint data is permanently unrecoverable.
Integrated PACS transfer routes images automatically or through a gateway-based integration as part of the normal acquisition workflow. The radiographer acquires the image; the routing rule handles the rest. This eliminates the identification and submission steps entirely, removing the failure mode above.
For sites with high patient volumes or complex multi-study environments, PACS integration is the most operationally reliable approach to maintaining consistent, timely image submission across a long trial. When an expected submission is not received within a defined window, robust imaging platforms generate an automated alert to the imaging operations team — allowing proactive intervention before the protocol window closes.
Common PACS integration challenges
Despite the operational benefits, PACS integration in clinical trials introduces implementation complexity that sponsors and site teams should anticipate.
Vendor variability
PACS systems from Siemens, GE, Philips, United Imaging, Fujifilm, and other manufacturers implement the DICOM standard with varying degrees of fidelity. Routing configuration, tag structures, and anonymization capability differ across vendors and software versions. QMENTA's PACS Nexus supports direct DICOM routing from all major commercial PACS vendors with pre-built configuration templates that reduce per-site setup time.
IT access constraints
Many hospital IT departments restrict changes to PACS routing configuration, requiring formal approval processes that can extend site setup timelines by days to weeks. The technical integration itself — once IT approval is granted — is typically completed by QMENTA's site onboarding team within 48 hours per site. The limiting variable is almost always the institutional IT process, not technical complexity. A gateway-based integration facilitates this as there is no need to change routing rules.
Multi-protocol sites
Sites participating in multiple concurrent clinical trials may have competing routing rules for the same modalities. Careful configuration — typically handled by the imaging platform's site onboarding team — prevents cross-routing of images between trials. A gateway-based integration facilitates this as there is no need to change routing rules.
Anonymization gaps at complex sites
Sites that apply anonymization locally before routing may not strip all required DICOM tags, or may miss burned-in pixel PHI. Receipt-side quality checks should verify anonymization completeness for every incoming submission, with non-compliant files flagged and quarantined rather than silently rejected.
Key takeaways
- PACS integration automatically routes trial images from the site's imaging system to the central trial platform — eliminating manual upload steps and the errors they introduce
- Three connection models exist: push routing (cleanest, requires PACS configuration), pull retrieval (lowest site IT burden, platform handles retrieval), gateway-based (most flexible, minimal PACS changes)
- In clinical trials, a missed image at a specific visit means permanently lost endpoint data — the consequence is categorically different from a missed image in clinical care
- Anonymization workflow depends on the integration model: push and gateway configurations support site-level anonymization; pull retrieval typically requires platform-side anonymization on receipt
- PACS integration setup is limited by institutional IT approval timelines, not technical complexity — in QMENTA's operational experience, the actual configuration is typically completed within 48 hours once site IT access is granted
- Automated submission monitoring — alerting the imaging ops team when expected images are not received — is the operational safeguard that catches integration gaps before protocol windows close
By Paulo Rodrigues, PhD, Chief Technology Officer and Co-Founder at QMENTA
Paulo Rodrigues leads technology strategy at QMENTA and writes about imaging clinical trials, protocol standardization, real-time QC, and compliance-ready neuroimaging workflows for multi-site studies. View executive leadership.
Connect your sites' PACS to QMENTA in days, not weeks
QMENTA's Imaging Hub supports end-to-end central review workflows — from automated site upload and de-identification to blinded reader assignment, reading plan management, adjudication, and inspection-ready audit trails.
See PACS Nexus in action →
Frequently asked questions
What is a PACS in a hospital?
A PACS — Picture Archiving and Communication System — is the software infrastructure hospitals use to store, retrieve, and display medical images. PACS systems receive images from imaging equipment such as MRI and CT scanners via the DICOM protocol, store them in a central archive, and make them accessible to radiologists and clinicians through a viewing workstation. Most commercial PACS systems support image routing to external destinations via standard DICOM networking protocols, which is the technical foundation for PACS integration in clinical trials.
Does PACS integration require changes to the hospital's clinical systems?
It depends on the integration model. Push routing requires the site's PACS to be configured with a new routing rule and destination — a change that requires IT department approval at most institutions. Gateway-based integration minimises changes to the core PACS by adding a software agent at the network level, which typically requires less IT involvement and approval. Pull retrieval requires the least change at the site level, as the trial platform queries the PACS remotely rather than requiring site-side configuration. For sites with restrictive IT environments, gateway-based or pull retrieval models are generally the most practical.
Can a trial platform connect to any PACS system?
Most modern cloud-based imaging platforms can connect to any PACS system that supports standard DICOM networking protocols — which covers the vast majority of commercial PACS in active clinical use. Older or proprietary PACS systems with non-standard implementations may require additional configuration or a gateway agent. QMENTA's PACS Nexus supports direct DICOM routing from major vendors including Siemens, GE, Philips, United, and Fujifilm, with pre-built connection templates that reduce per-site configuration time.
How long does PACS integration setup take at a new site?
The technical setup — configuring the routing rules, testing the DICOM connection, and verifying anonymization and receipt confirmation — is typically completed by QMENTA's site onboarding team within 48 hours once site IT access is granted. The variable that determines the actual calendar timeline is the site's internal IT approval process, which ranges from a few days at smaller institutions to several weeks at large academic medical centres with formal change-management requirements. For trial planning purposes, sponsors should build four to six weeks of site setup time into their activation timeline and use that window to run the IT approval process in parallel with other site initiation activities.
What happens if the PACS integration fails or expected images are not received?
Robust imaging platforms include automated submission monitoring that generates an alert to the imaging operations team when an expected submission has not been received within a defined window after the scheduled imaging visit. The alert identifies the specific patient, visit, and site — allowing the operations team to contact the site immediately and resolve the issue while the protocol window is still open. In parallel, a fallback upload mechanism — typically a web-based DICOM uploader or a smart uploader tool installed at the site — allows images to be submitted manually if the PACS integration is temporarily unavailable. The combination of proactive monitoring and a reliable fallback is what makes the difference between a recoverable submission gap and a permanent endpoint data loss.