PACS

A PACS must reliably receive images from any DICOM-compliant modality, including CT, MRI, CR, DR, US, and NM. The system acts as a Service Class Provider (SCP) , listening for incoming C-STORE requests from acquisition devices. Key capabilities include:

• Modality Worklist (MWL) Integration: Automatically populates patient demographics at the scanner, eliminating manual entry errors.
• Transfer Syntax Negotiation: Accepts various compression schemes (JPEG Lossless, JPEG 2000) during Association Negotiation.
• Secondary Capture Support: Ingests images from non-DICOM sources, such as endoscopy video feeds or imported JPEGs, converting them to valid DICOM objects.

PACS architectures implement a tiered storage strategy to balance performance and cost. The system automatically migrates studies across storage tiers based on configurable rules, such as study age or retrieval frequency.

• Tier 1 (Short-Term Cache): High-performance SSD or RAM cache for studies being actively read or recently acquired.
• Tier 2 (Nearline Archive): Spinning disk RAID arrays for studies from the last 12-24 months, providing sub-second retrieval.
• Tier 3 (Long-Term Archive): Low-cost object storage, tape libraries, or cloud cold storage for disaster recovery and legal retention. The PACS manages the DICOM UID index to locate any study regardless of its physical location.

The core function of a PACS is to enable authorized users to find and display historical imaging data. The system acts as both a Service Class Provider (SCP) for queries and a Service Class User (SCU) when fetching data from a VNA or another PACS.

• C-FIND: Enables workstations to query the database at the Patient, Study, Series, or Image level using attributes like Patient ID or Accession Number.
• C-MOVE: Instructs the PACS to push identified DICOM objects to a specified destination Application Entity Title (AET).
• C-GET: A less common operation where the SCU receives the data directly over the same association.
• DICOMweb (WADO-RS): Modern PACS provide RESTful APIs for retrieving specific instances or frames using HTTP, enabling zero-footprint viewers.

Beyond simple image display, a modern PACS provides a suite of clinical tools embedded within the diagnostic viewer. These capabilities are often provided via server-side rendering to support thin-client workstations.

• Multi-Planar Reconstruction (MPR) : Generates coronal and sagittal views from axial source data in real-time.
• Maximum Intensity Projection (MIP) : Projects the brightest voxels in a volume to visualize contrast-filled vessels.
• 3D Volume Rendering: Creates photorealistic 3D models for surgical planning.
• DICOM GSDF Calibration: Ensures that grayscale images are displayed consistently across all monitors using the Grayscale Standard Display Function, a critical requirement for primary diagnosis.

A PACS is responsible for the absolute integrity of the medical record. It must ensure that no data is lost or corrupted over decades of storage.

• DICOM De-identification: Applies profiles from DICOM Part 15 to remove Protected Health Information (PHI) for research or teaching files, handling both header tags and Burned-in Annotations.
• Reconciliation: Matches unscheduled or misidentified studies against the Electronic Health Record (EHR) using accession numbers or patient IDs.
• Retention Policies: Automatically purges or migrates studies based on legal mandates, ensuring compliance with local medical record retention laws.
• Integrity Checks: Performs routine checksum verification to detect bit rot and automatically repairs data from redundant copies.

A PACS does not operate in isolation. It must seamlessly exchange data with a broader healthcare IT ecosystem using HL7 and DICOM standards.

• HL7 ORM/ORU: Receives order messages (ORM) from the EHR to populate the worklist and sends back finalized report messages (ORU).
• DICOM Structured Report (SR) : Stores measurements and key images as machine-readable data objects rather than just text blocks.
• Cross-Enterprise Document Sharing (XDS) : Enables the PACS to publish imaging documents to a regional or national health information exchange (HIE).
• Single Sign-On (SSO) : Integrates with LDAP or SAML identity providers to streamline user authentication across clinical applications.