Pinnacle³ TAR → DICOM Conversion

Convert Pinnacle TAR Archives to DICOM

Complete technical guide on converting Philips Pinnacle³ proprietary TAR archive files to standardized DICOM RT objects (RTStruct, RTPlan, RTDose, CT Image) for compatibility with modern radiotherapy systems.

Understanding Pinnacle TAR to DICOM Conversion

The Problem

Philips Pinnacle³ treatment planning system stores all patient radiotherapy data in a proprietary .tar archive format. This format includes:

  • Patient information - Demographics, identifiers, and metadata
  • CT Images - Planning CT series in Pinnacle's native format
  • Structure Sets - Contoured organs at risk and target volumes
  • Treatment Plans - Beam parameters, dose prescriptions, and delivery instructions
  • Dose Distributions - Calculated 3D dose distributions

While efficient for Pinnacle³ itself, this proprietary format creates interoperability challenges when:

  • Migrating to a new treatment planning system (Eclipse, RayStation, Monaco, etc.)
  • Upgrading PACS or oncology information systems
  • Archiving data for long-term retention
  • Sharing data with external facilities or researchers
The Solution

Converting Pinnacle TAR archives to DICOM RT objects provides:

  • Universal compatibility - DICOM is recognized by all modern radiotherapy systems
  • Data preservation - Ensures long-term access to historical treatment data
  • Regulatory compliance - Meets standards for medical imaging data archival
  • Storage optimization - Typically reduces storage footprint by ~50%
  • Future-proofing - DICOM standard is maintained and evolved by NEMA
Conversion Process Flow
Input Pinnacle TAR Archive
Processing Archive Exporter Service
Output DICOM RT Objects
Storage PACS / TPS / Archive

How Pinnacle TAR to DICOM Conversion Works

Input Format: Pinnacle TAR Archive

Pinnacle³ TAR archives contain the following data structures:

Pinnacle_TAR_Archive/ ├── Patient_001/ │ ├── PatientInfo.tar │ ├── CT_20240101/ │ │ ├── CT_Images.tar │ │ └── CT_Parameters.xml │ ├── Structures/ │ │ └── StructureSet_Prostate.tar │ ├── Plans/ │ │ └── Plan_78Gy.tar │ └── Dose/ │ └── Dose_Distribution.tar └── Patient_002/ └── ...

Each .tar file contains proprietary binary data specific to Pinnacle³. The Archive Exporter service reads these files directly without requiring an active Pinnacle workstation.

Conversion Process

The conversion involves several technical steps:

  1. Archive Parsing - Extract and parse the TAR archive structure
  2. Metadata Extraction - Read patient, plan, and structure metadata from proprietary format
  3. DICOM Object Creation - Generate standardized DICOM datasets for each RT object type
  4. Attribute Mapping - Map Pinnacle-specific attributes to DICOM standard attributes
  5. Relationship Establishment - Create proper DICOM references between related objects
  6. Validation - Automated checks for data integrity and DICOM compliance

This process preserves all clinical data including:

  • Patient identifiers and demographics
  • CT image pixel data and geometry
  • Structure contours and names
  • Plan beam parameters and MU values
  • Dose grid data and normalization
  • Spatial relationships between all objects
Supported Pinnacle Versions

Archive Exporter supports the following Philips Pinnacle³ versions:

Pinnacle Version Support Status Notes
Pinnacle³ v6 to latest✓ SupportedAll versions from v6 through the latest

Note: If your version is not listed, contact us to discuss compatibility. The conversion process is designed to be version-agnostic where possible.

What DICOM Objects Are Produced

DICOM RT Object Types

Archive Exporter produces the following standardized DICOM objects:

1. RT Struct (RT Structure Set)

  • Purpose: Defines contoured structures (targets, OARs, etc.)
  • DICOM SOP Class UID: 1.2.840.10008.5.1.4.1.1.481.3
  • Contains: Structure names, ROI numbers, contour data, approximation method
  • Referenced by: RT Plan, RT Dose

2. RT Plan (RT Treatment Plan)

  • Purpose: Defines treatment plan parameters and beam geometry
  • DICOM SOP Class UID: 1.2.840.10008.5.1.4.1.1.481.5
  • Contains: Beam parameters, dose prescription, fractions, treatment machine, accessories
  • Referenced by: RT Dose
  • References: RT Struct, CT Image

3. RT Dose (RT Dose Distribution)

  • Purpose: Defines calculated dose distribution
  • DICOM SOP Class UID: 1.2.840.10008.5.1.4.1.1.481.2
  • Contains: Dose grid, normalization point, dose units, grid frame offset
  • References: RT Plan, RT Struct, CT Image

4. CT Image (CT Series)

  • Purpose: Defines planning CT image series
  • DICOM SOP Class UID: 1.2.840.10008.5.1.4.1.1.2
  • Contains: Pixel data, image position, slice thickness, window level/width
  • Referenced by: RT Struct, RT Plan, RT Dose
Output Folder Structure

Exported DICOM files are organized in a hierarchical folder structure:

DICOM_Export/ ├── Patient_001_DOE_JOHN/ │ ├── Patient_Info.dcm │ ├── CT_Planning_20240101/ │ │ ├── CT_0001.dcm │ │ ├── CT_0002.dcm │ │ └── CT_0003.dcm │ ├── RT_StructureSet_Prostate.dcm │ ├── RT_Plan_78Gy_30fx.dcm │ └── RT_Dose_Prostate.dcm ├── Patient_002_SMITH_JANE/ │ ├── Patient_Info.dcm │ ├── CT_Planning_20240215/ │ │ ├── CT_0001.dcm │ │ └── CT_0002.dcm │ └── RT_StructureSet_Breast.dcm └── Export_Report.pdf

This structure makes it easy to:

  • Locate specific patient records
  • Verify completeness of conversions
  • Import into PACS or TPS systems
  • Navigate during clinical review
DICOM Attribute Mapping

Pinnacle-specific data is mapped to DICOM standard attributes:

Pinnacle Data DICOM Attribute DICOM Tag
Patient IDPatient ID(0010,0020)
Patient NamePatient Name(0010,0010)
Study DateStudy Date(0008,0020)
CT Slice LocationImage Position (Patient)(0020,0032)
Structure NameStructure Set Label(3006,0020)
ROI NumberReferenced ROI Number(3006,0084)
Plan NameRT Plan Label(300A,0002)
Prescription DoseDose Reference(300A,0006)
Beam EnergyNominal Beam Energy(300A,00B2)
Dose GridPixel Data(7FE0,0010)

Note: This is a simplified mapping. The complete conversion includes hundreds of DICOM attributes to ensure full clinical data preservation.

Pinnacle TAR vs DICOM RT Objects

Pinnacle TAR Archive
  • Proprietary Philips format
  • Readable only by Pinnacle systems
  • Single file per data type
  • Contains proprietary metadata
  • Larger file sizes
  • No standard validation
DICOM RT Objects
  • Universal medical imaging standard
  • Readable by all modern TPS and PACS
  • Individual files per object
  • Standardized metadata schema
  • Optimized file sizes
  • DICOM compliance validation

Why Convert Pinnacle TAR to DICOM

Converting your Pinnacle archives to DICOM provides significant benefits for your department:

Interoperability

DICOM is the universal standard for medical imaging. Converting to DICOM ensures:

  • Compatibility with all modern treatment planning systems (Eclipse, RayStation, Monaco, etc.)
  • Seamless import into PACS and oncology information systems
  • Easy data sharing with external facilities and researchers
  • Future-proof access as systems evolve
Data Preservation

As Pinnacle³ reaches end of support, maintaining access to historical data becomes increasingly difficult:

  • Legacy Pinnacle workstations have limited lifespan
  • Modern operating systems may drop support for old hardware
  • Pinnacle³ infrastructure requires ongoing maintenance
  • DICOM files can be stored on any standard storage system
Storage Efficiency

DICOM optimization typically reduces storage requirements by ~50%:

  • Elimination of proprietary overhead in TAR format
  • Removal of redundant data structures
  • Better compression of DICOM pixel data
  • Efficient organization of related objects

Example: A 500GB Pinnacle archive typically converts to 250-350GB of DICOM files with zero clinical data loss.

Regulatory Compliance

DICOM is the standard for medical imaging archival:

  • Meets DICOM PS3.3 RT object standards
  • Compliant with IHE RO profiles
  • Supports long-term retention requirements
  • Facilitates audits and inspections
Clinical Value

Converted DICOM files enable:

  • Treatment plan comparison across different time periods
  • Historical data analysis for research and QA
  • Patient follow-up with access to prior treatment information
  • Second opinions with easy data sharing
  • Staff training using historical cases
Ready to Convert?

Start Your Pinnacle TAR to DICOM Migration

Archive Exporter provides a professional, validated, and supported service for converting your Philips Pinnacle³ TAR archives to standardized DICOM RT objects. Contact us to discuss your specific needs and get a customized quote.

Request Quote → View 2026 Deadline →