PACS

PACS
Name	PACS
Acronym meaning	Picture Archiving and Communication System
First deployed	1980s
Developers	Various vendors and research groups
Industry	Healthcare imaging

PACS

PACS is a medical imaging technology that stores, retrieves, presents, and distributes images produced by medical imaging modalities. It connects modalities such as Computed Tomography, Magnetic Resonance Imaging, Ultrasound, Nuclear Medicine and Digital Radiography with viewing stations, archives, and reporting systems used in hospitals and clinics. Major vendors, academic centers, and standards organizations contributed to its evolution alongside initiatives at institutions such as Mayo Clinic, Johns Hopkins Hospital, Massachusetts General Hospital, Stanford Health Care and Cleveland Clinic.

Overview

PACS centralizes images from modalities like Siemens Healthineers devices, GE Healthcare scanners, and Philips Healthcare systems into digital archives accessible by clinicians at workstations from manufacturers such as Agfa Healthcare and Fujifilm. It replaces film-based workflows pioneered during the era of institutions like Karolinska Institute and Walter Reed National Military Medical Center and intersects with reporting solutions from companies such as Nuance Communications and Sectra. PACS deployments vary from single-site implementations at community hospitals to multisite networks operated by systems such as UK National Health Service trusts and integrated delivery networks like Kaiser Permanente.

History and development

Early PACS prototypes emerged in the 1970s and 1980s in research environments including Massachusetts General Hospital and Mayo Clinic laboratories, influenced by projects at NASA and standards work at National Electrical Manufacturers Association committees. Commercialization accelerated in the 1990s with vendors including Agfa Healthcare, GE Healthcare, Philips Healthcare, Siemens Healthineers, and startups that later merged with firms like Fujifilm. The 2000s saw adoption of the DICOM standard promulgated by NEMA and integration with electronic records driven by programs at Department of Veterans Affairs and initiatives from organizations such as HL7 International. Cloud-hosted models and vendor-neutral archives emerged in the 2010s with involvement from technology companies like Amazon Web Services, Microsoft Azure, and Google Cloud Platform as well as healthcare integrators including Cerner Corporation and Epic Systems.

Technical architecture and standards

A typical PACS architecture includes modality interfaces, a central archive, a RIS/PACS integration layer, and diagnostic viewers from vendors like Carestream Health and Canon Medical Systems. Key standards include DICOM for image encoding and exchange, IHE integration profiles from Integrating the Healthcare Enterprise, and networking protocols standardized by organizations such as IETF. Storage tiers use technologies from NetApp, EMC Corporation and object stores in cloud platforms like Amazon S3; databases range from relational engines by Oracle Corporation to open-source systems such as PostgreSQL. Middleware and APIs enable connectivity with picture archiving services and viewer frameworks built on toolkits from OpenJPEG and rendering engines that leverage graphics libraries supported by NVIDIA.

Clinical applications and workflows

PACS supports radiology workflows including image acquisition, hanging protocols, diagnostic interpretation, and report finalization interfacing with reporting vendors like Nuance Communications and M*Modal. It enables subspecialty workflows for Neuroradiology at centers like Barrow Neurological Institute, Musculoskeletal Radiology in academic departments such as University of California, San Francisco, and Cardiac Imaging programs at institutions like Cleveland Clinic. Workflow optimizations incorporate scheduling systems used by health systems like Mount Sinai Health System and referral patterns in networks such as Intermountain Healthcare. Advanced visualization for 3D reconstructions, cardiac post-processing, and oncology follow-up integrates toolkits from companies like Siemens Healthineers and academic research groups at Johns Hopkins University.

Integration and interoperability

Interoperability is achieved by mapping PACS to radiology information systems and electronic health records from vendors including Epic Systems, Cerner Corporation, and Allscripts. IHE profiles such as Scheduled Workflow (SWF) and Cross-Enterprise Document Sharing for Imaging (XDS-I) facilitate cross-organizational exchange used by health exchanges like Carequality. Vendor-neutral archives and middleware from firms such as Change Healthcare and Hyland assist in consolidating image repositories across networks operated by organizations such as HCA Healthcare. Cross-domain integration also links to laboratory systems at institutions like Mayo Clinic and oncology systems in networks such as MD Anderson Cancer Center.

Security, privacy, and compliance

PACS implementations must comply with regulatory frameworks including Health Insurance Portability and Accountability Act requirements overseen by agencies like U.S. Department of Health and Human Services and regional regulations such as the General Data Protection Regulation enforced by institutions across the European Union. Security controls include access management with directories from Microsoft Active Directory, encryption standards endorsed by NIST, and audit logging integrated with security information and event management solutions from companies like Splunk. De-identification for research aligns with guidance from entities such as Institutional Review Boards at universities like Harvard Medical School and research hospitals like Stanford Health Care.

Performance, scalability, and deployment models

PACS scales from single-server configurations at community hospitals to enterprise deployments across systems like Kaiser Permanente and multisite networks managed by Veterans Health Administration. Deployment models include on-premises appliances from vendors such as Carestream Health, hybrid clouds using Microsoft Azure or Amazon Web Services, and fully cloud-native offerings by technology partners and healthcare vendors including Philips Healthcare and GE Healthcare. Performance considerations address network bandwidth in wide-area networks connecting hospitals such as Mount Sinai Health System and cold/hot storage tiers provided by vendors like Dell EMC to ensure throughput and retrieval latency suitable for diagnostic tasks performed in centers such as Yale New Haven Hospital.

Category:Medical imaging