Intelerad’s IntelePACS is a radiology PACS described in versioned technical documents and current product pages as software for receiving, storing, routing, retrieving, and displaying medical images and related data from imaging sources. Public materials also say the product is offered with cloud-based image access, remote reading, and portal-based communication, while the technical guides define message and DICOM interfaces for specific release families. [1][2][3][4]
Product scope and intended use
The technical documents state that IntelePACS receives digital images and data from CT, MR, ultrasound, R/F, computed radiography, secondary capture, scanners, imaging gateways, and related sources. The DICOM statement identifies the software as an image management system that accepts DICOM association requests for image storage and query/retrieval, and that can send images to external application entities. These sources define a PACS role rather than a general enterprise health record system. [1][4]
The public product pages describe a cloud-first image access model for radiology. One page says the platform consolidates imaging infrastructure into a centralized cloud-based platform and is intended to support radiologists reading from any location. Another current page describes secure and efficient image access and storage, plus collaboration through web-based remote reading and software integrations. These are vendor descriptions, not independent evaluation results. [3][5][6]
Documented workflow and imaging functions
The DICOM conformance statement lists several supported functions, including DICOM Verification SCP, short-term storage, storage commitment, automatic routing to destinations such as viewing workstations and archive servers, and RIS-triggered prefetching based on radiology orders. The same document says application entity functions can be combined on hybrid servers in lower-volume installations or where less redundancy is required. That frames deployment choices around system design rather than a single fixed architecture. [4]
The product pages also describe imaging work across multiple specialties. Current marketing pages mention breast imaging, nuclear medicine, ultrasound digital worksheets, advanced visualization, and integration with third-party viewers, voice recognition software, and AI programs. The material treats these as examples of what the platform can connect to or support; it does not present a formal taxonomy or exhaustive feature list. [3][5][7]
Implementation boundary example
A site planning an interface test could configure a RIS, modality, and IntelePACS around one order with a single study instance UID, then verify that the ZDS segment is present and consistent in the HL7 and DICOM workflow. If the site also uses a portal or a referring-physician workflow, it would still need to keep diagnostic viewing in the appropriate workstation path described in the documentation. This is only an example of how the documented rules could be exercised; it does not state results or suitability for any deployment.
Interfaces, messages, and data consistency
The HL7 integration guides identify supported inbound message types as ADT, SIU, ORM, and ORU, and they list required and optional segments for those flows. They also state that the guides are for HL7 version 2.3 interfaces, and that messages are accepted under the rules described for the documented release family. This is a specific interface guide, not a statement about every possible HL7 deployment. [2][8]
The HL7 guide says that when a RIS provides a DICOM Modality Worklist, the RIS must supply the ZDS segment so that the study instance UID is consistent between the modality and IntelePACS. If the ZDS segment is missing, or if the UIDs are inconsistent, images might not pass validation in IntelePACS. The same guide says that, when multiple procedures are assigned to one order, a unique study instance UID is required for each procedure. Those are implementation conditions, not a claim about all sites. [2][8]
The guides also describe acknowledgement behavior for PACS-to-RIS messages. Messages sent from PACS to a RIS should be acknowledged with an ACK, and the resend behavior can be configured on the IntelePACS side if no answer or a NACK is received. This is a narrow message-handling rule tied to the documented interface, not a broader networking or reliability claim. [2][8]
Reading, collaboration, and portal use
Current product pages describe an InteleViewer workstation and an Enterprise Viewer for image review, along with remote reading access and collaboration tools. The April 2025 vendor article says radiologists can use InteleViewer and Enterprise Viewer, with tools such as PET-CT fusion, multi-modality comparison, and real-time sequence protocol synchronization. The same vendor article describes in-context messaging and integrated screensharing as collaboration capabilities supporting consultation without leaving the study. These remain vendor descriptions of clinical workflow support, not measured outcomes. [3][7]
The same April 2025 vendor article describes portals for referring physicians and patients. The vendor article says the referring physician portal is intended to give secure access to order status, imaging, and finalized reports, while it presents the patient portal as a channel for patient access to results. The technical documents also mention residual-risk language that images in referring-physician use, InteleConnect, CD burning, and the Nuage patient portal are for review only and are not appropriate for diagnostic purposes, with InteleViewer named for diagnostic viewing. That boundary is explicit in the documents and should not be generalized beyond those contexts. [1]