Independent IT Solutions

IT Expertise You Can Rely On

Over 20 years of hands-on experience across systems, networking, medical imaging, and DICOM services. Fast turnaround and flexible scheduling.

20+
Years of IT Experience
100%
Remote (Limited On-Site Capability)
Flexible Hours
Available Evenings & Weekends

Specialized IT Services for Healthcare & Business

From DICOM medical imaging to full IT infrastructure β€” practical solutions with a personal touch.

πŸ₯

DICOM Patient Database Conversion

Complete CK/RX patient database conversion to DICOM format. Scalable pricing from 10 to 3,500+ patients β€” remotely or offsite.

πŸ–₯️

PACs Server Setup

Configuration of Dicoogle, Orthanc, or Sante Free PACs β€” included with data conversion. Enables remote search, view, and retrieval.

πŸ“¦

Patient DICOM Exporter App

Per-machine licensing for the Patient DICOM Exporter App, complete with a detailed instruction manual. $2,500 per machine.

βš™οΈ

IDMS Server & VM Migration

Full IDMS server and database migration to virtual machines β€” Hyper-V, Proxmox, VirtualBox, or VMware supported.

πŸ”„

All-in-One Review Workstation

Multiplan / Precision migration to an all-in-one review/research workstation. Run CDMS or IDMS as a VM, includes 4-TB SSD.

🌐

General IT Support & Networking

Networking, computer support, and data recovery from failed HDDs, RAID volumes, and NAS systems.

Services Not Listed? Just Ask.

We offer flexible, customized IT solutions. If you don't see what you need, reach out.

Transparent, Scalable Pricing

No hidden fees. Clear pricing based on scope. Contact us for custom quotes on unlisted services.

Medical Imaging & DICOM Services

CK/RX Patient Database Conversion (DICOM)

Patient VolumePrice
10 – 250 patients$5,000
251 – 500 patients$7,500
501 – 1,000 patients$10,000
1,001 – 1,999 patients$12,500
2,000 – 3,499 patients$15,000
3,500+ patients$20,000
Note: Can be performed remotely or offsite. Requires remote access to system, or customer ships HDD with patient database. Network storage or USB external drive required for output. The cost of an encrypted HDD used for data transfer is not included in the price above, if required. The Conversion is time-consuming and may require up to two weeks for turn-around time.

Additional IT Services & Products

ServicePrice
PACs Server Setup
Dicoogle, Orthanc, or Sante Free PACs β€” enables remote search, view, and retrieval of DICOM files. Included with DICOM data conversion above.
Included*
Patient DICOM Exporter App and instruction manual
Licensed per machine -- Save money by running the conversion in-house via dedicated resource. (Independent third-party tool - Not affiliated with or endorsed by Accuray, Inc.)
πŸ“„ Download User's Manual (PDF)
$2,500
X-ray to DICOM Converter App and instruction manual
Licensed per workstation -- View & convert your CK live X-ray images to DICOM for use in QA Tools or export to 3rd party modalities. (Independent third-party tool - Not affiliated with or endorsed by Accuray, Inc.)
πŸ“„ Download User's Manual (PDF)
$500
IDMS Server & Database Migration to Virtual Machine
Customer provides server and VM platform (Hyper-V, Proxmox, VirtualBox, VMware). Windows & SQL licensing by customer.
$15,000
Multiplan / Precision β†’ All-in-One Review Workstation
Converts Multiplan/Precision into a standalone research workstation. Includes 4-TB SSD. Customer provides workstation and Windows/SQL licensing.
$15,000
Data Recovery β€” Failed HDDs, RAID Volumes, or NAS SystemsContact for quote
Import Patient Archives from Another Site
Import one or more archived patients from another site for review and replaning.
Contact for quote

Services not listed above are available upon request.

βœ“ Included with DICOM Conversion Service

Patient Data Export

Overview & guide for batch conversion of CDMS/IDMS patient records to DICOM and hierarchical file system β€” enabling long-term, system-independent access to your data.

What Is Patient Data Export?

πŸ“€

What Is It?

Batch conversion of CDMS/IDMS patient records to DICOM format and hierarchical file system β€” making records portable and future-proof.

πŸ’‘

Why Export?

Long-term data access, cost savings, security compliance, and hardware/software independence from proprietary systems.

πŸ› οΈ

What's Needed?

Planning station access or external drive with a copy of the database and patient archives, plus network/USB storage and the Patient Export Application.

Per-Patient Export Contents

βœ“ Exported Items

  • βœ“ Treatment plans (deliverable through completed)
  • βœ“ Imported DICOM CT, PET, MRI, RTSS
  • βœ“ Plan-specific RTDOSE, RTSS, RTPLAN, RTRECORD
  • βœ“ Plan-specific XML files
  • βœ“ Fraction files and treatment logs
  • βœ“ Treatment screenshots
  • βœ“ Live X-ray images
  • βœ“ Scanned PDFs

βœ• Exclusions & Limitations

  • βœ• Phantoms, QA plans, LOT sim plans
  • βœ• Setup & alignment plans
  • βœ• Physician plans
  • βœ• Custom report generation/printing
  • βœ• Fused moving images download
  • βœ• Archived patients (must be de-archived first)

Example Directory Structure

Each exported patient is organized into a standardized hierarchical folder layout for easy navigation and retrieval.

Patient Data Export – directory structure Tree showing Patient Directory with DICOM and Plan Directory subfolders. Plan Directory contains DICOM, PDFs, Fractions, XRay, Logs, PlanFiles, and Screenshots subfolders. Patient Directory (LastName_FirstName_MedicalID) DICOM\ (all patient DICOM series) Plan Directory\ DICOM\ (plan-specific DICOM structures) Documents\ (scanned PDF documents) Fraction_Files\ (treatment fraction files) Live_Images\ (live x-ray and setup images) Logs\ (treatment log files) Plan_Files\ (plan-specific files and XML) Screenshots\ (delivery screenshots taken during treatment)

Indexing & Cataloging via PACs Server

Included at no extra cost with the data extraction service β€” customer provides the workstation.

Indexer & Archiver

Dicoogle

Primarily an indexer and archiver. Requires an external viewer (e.g., Weasis) to view DICOM images. Best suited for query and retrieve from another application.

πŸ” Query & Retrieve
Full-Featured PACs

Orthanc

Full-featured PACs with search, view, export, and download. Accessible via web browser from any station on your network.

🌐 Web Browser Access
Full-Featured PACs

Sante Free PACs

Full-featured PACs with search, view, export, and download. Available as a desktop app or accessible via web browser from any station.

πŸ–₯️ Desktop + Web
πŸ”
Query & Search
Query patient database and view DICOM images from remote stations across your network.
πŸ“₯
DICOM Retrieve
DICOM query and retrieve from any application supporting this functionality.
πŸ’°
No Extra Cost
Included with the data extraction service. Customer provides the workstation.

Ready to Export Your Patient Data?

Contact TC Consulting to discuss your patient volume, system type, and delivery preferences.

Two Decades of IT Expertise

Trusted Computer Consulting Services was founded by an independent IT professional with over 20 years of hands-on experience across systems, networking, hardware, software, and medical imaging.

We specialize in DICOM medical imaging and patient database conversion β€” services that require deep technical expertise and trust. Whether your facility needs to migrate thousands of patient records or set up a new PACs server, we deliver quality results with a personal, flexible approach.

Available evenings and weekends, we pride ourselves on fast turnaround and flexible scheduling that works around your organization's needs β€” not the other way around.

TC

Trusted Computer Consulting

Independent IT Professional

  • B.S. Computer Engineering Technology
  • 20+ years across systems, networking, hardware & software
  • Specialized in Medical Imaging & DICOM Services
  • Remote & limited on-site services available
  • Available evenings and weekends

IT Insights & Medical Imaging News

πŸ₯
Why DICOM Conversion Is Critical Before Retiring Legacy Oncology Systems
When facilities upgrade or replace CDMS and IDMS platforms, patient treatment data is often at risk. DICOM conversion preserves decades of clinical records in an open, vendor-neutral format that remains accessible regardless of future software changes.
Read More β†’
πŸ–₯️
Orthanc vs. Dicoogle vs. Sante: Choosing the Right Free PACs for Your Facility
Not all free PACs solutions are built alike. This guide compares the three leading free options β€” Orthanc, Dicoogle, and Sante Free PACs β€” across system requirements, benefits, disadvantages, and key selection criteria.
Read More β†’
πŸ”„
Migrating IDMS to a Virtual Machine: What to Expect
Server virtualization can dramatically reduce hardware dependency and operating costs for clinics running IDMS. A complete guide covering platform selection, database backup, VM build, software installation, and deployment.
Read More β†’

Comments

Loading comments…

Leave a Comment

βœ“ Your comment has been submitted. Thank you!

Let's Discuss Your IT Needs

Whether you need a DICOM conversion quote, PACs setup, or general IT support β€” reach out and we'll respond promptly. Available evenings and weekends.

πŸ“ž
πŸ•
Availability
Evenings & Weekends Β· Remote & Limited On-Site

Send a Message

βœ“ Thank you! Your message has been sent. TC Consulting will be in touch shortly.

Orthanc vs. Dicoogle vs. Sante Free PACs:
Choosing the Right System for Your Facility

A detailed comparison of the three leading free PACS solutions β€” covering system requirements, benefits, disadvantages, and when to choose each one.

When TC Consulting performs a patient DICOM data conversion, one of the most valuable components included at no extra cost is a configured PACs (Picture Archiving and Communication System) server. A PACs gives your facility the ability to remotely search, view, and retrieve exported DICOM studies from any workstation on your network β€” without requiring proprietary hardware or software. Three free options are supported: Orthanc, Dicoogle, and Sante Free PACs. Each has distinct strengths depending on your facility's technical resources and workflow goals.

🌐

Orthanc

Full-Featured PACs Β· Web Browser Access Β· GPLv3

Orthanc is a lightweight, open-source DICOM server developed by the University Hospital of Liège. It transforms virtually any computer into a fully functional PACS without complex database administration. Orthanc communicates over a built-in REST API and a web-based viewer (Orthanc Explorer), making it accessible from any browser on your network.

System Requirements

  • OS: Windows, Linux, or macOS (64-bit recommended)
  • RAM: 2 GB minimum; 4–8 GB recommended for larger archives
  • Storage: Depends on DICOM volume; SQLite used by default (PostgreSQL recommended for larger deployments)
  • Network: Standard TCP/IP; DICOM port 4242, REST API port 8042
  • Additional: Can run on minimal hardware including a Raspberry Pi for small deployments

Benefits

  • One-click install-and-use experience β€” minimal configuration required
  • Built-in web viewer (Orthanc Explorer) accessible from any browser on the network
  • Full DICOM Storage, Query, and Retrieve (C-STORE, C-FIND, C-MOVE) support
  • RESTful API enables integration with custom applications and workflows
  • Extensive plugin ecosystem: DICOM Web (WADO/STOW/QIDO), Stone Web Viewer, PostgreSQL backend, and more
  • Cross-platform: runs on Windows, Linux, and macOS
  • Active community and excellent documentation
  • Can push/pull DICOM to and from other modalities or PACS

Disadvantages

  • Default SQLite backend not recommended for large-scale or high-concurrency deployments β€” PostgreSQL plugin required
  • Built-in viewer (Orthanc Explorer) is functional but basic; advanced viewing requires a third-party viewer plugin
  • Plugin management and configuration done via JSON files β€” requires some technical comfort
  • No built-in worklist management or RIS integration in the free version
  • Community support only (no commercial SLA in the free tier)

Best For

Facilities that want a reliable, browser-accessible archive for remote image review and DICOM retrieval. Also ideal for IT teams who want API-driven automation or plan to integrate DICOM data into a broader clinical workflow. Orthanc is the most widely deployed free PACs in the world and has a large support community.

πŸ”

Dicoogle

Indexer & Archiver Β· Research-Grade Β· Java-Based

Dicoogle is an open-source, plugin-based PACS archive developed by the University of Aveiro in Portugal. Rather than using a traditional relational database, Dicoogle indexes DICOM metadata using an Apache Lucene full-text index engine, enabling powerful free-text searches across large archives. It is particularly well-regarded in academic and research settings.

System Requirements

  • OS: Windows, Linux, or macOS β€” platform-independent (Java-based)
  • Java: Up-to-date Java Virtual Machine (JVM) required β€” JDK 11 or later recommended
  • RAM: 200 MB minimum; more recommended for production workloads
  • Storage: 500 MB free disk space for the application; additional space for DICOM objects
  • Network: Standard TCP/IP; configurable DICOM and web ports

Benefits

  • Powerful full-text metadata indexing via Apache Lucene β€” search across any DICOM tag
  • Highly extensible plugin architecture with a published SDK for custom development
  • Platform-independent thanks to Java β€” runs anywhere a JVM is installed
  • Peer-to-peer federated archive support β€” multiple Dicoogle nodes can be linked
  • Very lightweight minimum requirements β€” can run on minimal hardware
  • Excellent for research environments requiring flexible metadata querying and analytics
  • DICOM C-STORE, C-FIND, C-MOVE supported via plugins

Disadvantages

  • No built-in DICOM image viewer β€” requires an external viewer such as Weasis, OsiriX, or RadiAnt
  • Configuration and plugin management are done via command-line and config files β€” steeper learning curve
  • Web interface is functional but less polished than Orthanc or Sante
  • Requires Java to be installed and maintained on the host
  • Less suited for pure clinical workflows without additional tooling
  • Community support only; less commercially mature than Orthanc

Best For

Research institutions, teaching hospitals, and facilities that need powerful metadata querying, archive analytics, or extensible plugin-based customization. Dicoogle is best paired with a dedicated DICOM viewer (such as Weasis) for clinical image review. If your team already works in Java environments or has developer resources, Dicoogle offers the greatest flexibility for custom integrations.

πŸ–₯️

Sante Free PACs

Windows-Only Β· Built-in Viewer Β· DICOM 3.0 Compliant

Sante Free PACs Server, developed by Santesoft LTD, is a DICOM 3.0–compliant PACs server for Windows. Unlike Orthanc and Dicoogle, it includes a full-featured built-in DICOM viewer (Sante PACs Viewer), making it a self-contained solution that requires no additional software for image review. It also includes a built-in HTTP web server for browser-based access.

System Requirements

  • OS: Windows only (Windows 7, 8.1, 10, 11 β€” 64-bit)
  • RAM: 2 GB minimum; 4 GB or more recommended
  • Storage: Space varies by DICOM archive size; no separate database engine required
  • Network: Standard TCP/IP; DICOM and web ports configurable
  • Additional: No Java or external database required β€” self-contained installer

Benefits

  • Self-contained installation β€” no external dependencies (no Java, no separate database)
  • Includes a full-featured built-in DICOM viewer (Sante PACs Viewer) β€” no third-party viewer needed
  • Desktop application with an intuitive Windows GUI β€” easiest to set up and manage
  • Built-in HTTP web server for browser-based DICOM access from other network stations
  • Full DICOM 3.0 compliance: Storage, Query/Retrieve, Modality Worklist
  • Supports all major DICOM modalities: CT, MR, US, CR, NM, XA, MG, DX
  • Migration tool available for importing existing DICOM folders from USB or external storage
  • Upgrade path available to full Sante PACs Server (PostgreSQL-backed) for larger deployments

Disadvantages

  • Windows-only β€” cannot be deployed on Linux or macOS servers
  • Free edition is limited in scalability; designed for small-to-medium deployments and evaluation
  • No REST API or SDK β€” limited options for custom integration or automation
  • Less extensible than Orthanc or Dicoogle β€” no plugin architecture in the free version
  • Commercial product (free tier) β€” future feature availability is vendor-dependent

Best For

Clinics and facilities running Windows servers that want the simplest possible out-of-the-box experience β€” install, run, and view DICOM images immediately. Sante Free PACs is ideal when non-technical staff need to manage the system, or when a dedicated DICOM viewer is not already in use. It is also a strong choice for smaller patient volumes where scalability is not a primary concern.

Side-by-Side Comparison

Feature Orthanc Dicoogle Sante Free PACs
Operating SystemWindows, Linux, macOSWindows, Linux, macOSWindows only
Built-in ViewerBasic (Orthanc Explorer)None β€” external requiredFull-featured (Sante Viewer)
Web Browser Accessβœ“ Yesβœ“ Yesβœ“ Yes
REST APIβœ“ Yesβœ“ Yes (via plugins)βœ— No
Plugin / Extension Supportβœ“ Extensiveβœ“ Extensive (SDK)βœ— Limited
External DependenciesNone (SQLite built-in)Java JVM requiredNone
Ease of SetupEasyModerateVery Easy
ScalabilityModerate–High (with PostgreSQL)ModerateLow–Moderate
Best Use CaseClinical + developer workflowsResearch + metadata analyticsSimple clinical deployment
LicenseGPLv3 (open source)GPLv3 (open source)Freeware (proprietary)

Implementation Considerations

Network Planning

Ensure the PACs host is on the same network segment as the workstations that will query it. Configure firewalls to allow DICOM traffic (typically port 4242) and the web interface port (8042 for Orthanc, 8080 for Dicoogle, configurable for Sante).

Storage Sizing

DICOM files are large. A single CT study can range from 50 MB to several GB depending on slice count and modality. Plan for at least 2–3x your current archive size to accommodate growth, ideally on a RAID-backed NAS or network share.

Security & Access Control

All three systems support basic authentication. For HIPAA compliance, ensure the PACs host is on a secured, access-controlled network segment. Enable HTTPS where supported and restrict DICOM port access to known IP ranges.

Backup & Redundancy

The PACs server itself should be backed up regularly β€” both the DICOM file storage directory and the database (SQLite file for Orthanc, Lucene index for Dicoogle). Consider automated nightly backups to a separate storage location.

TC Consulting installs and configures your choice of PACs server as part of every DICOM data conversion service. Not sure which one is right for your facility?

Why DICOM Conversion Is Critical Before
Retiring Legacy Oncology Systems

When legacy oncology hardware reaches end of life, the data it holds doesn't have to go with it. Here's why proactive DICOM conversion and virtualization are the smart path forward.

The Gap Manufacturers Don't Fill

When a medical facility invests in a new oncology system, the manufacturer is there every step of the way β€” pre-installation planning, on-site setup, clinical training, and long-term technical support. It's a comprehensive lifecycle of care, and rightfully so. But that support has a defined endpoint: the life of the machine itself.

What happens after the machine is decommissioned is a different story. The patient treatment data accumulated over years β€” dose records, imaging series, plan files, treatment histories β€” is often left in a precarious position. Manufacturers typically advise customers to retain the physical hardware for the purpose of historical data review. While this is a reasonable short-term strategy, it introduces a set of long-term challenges that compound over time:

πŸ”§

Hardware Maintenance

Aging proprietary hardware fails. Replacement parts become scarce or unavailable entirely. The cost of keeping decommissioned machines operational solely for data access can be disproportionate to the actual access frequency.

πŸ›‘οΈ

IT & Security Compliance

Legacy operating systems and unpatched software present ongoing cybersecurity risks. Maintaining these systems within a HIPAA-compliant, network-secured environment requires continuous effort and expense.

πŸ“‹

Traceability & Audit Readiness

Retrieving a specific patient record from a legacy system for audit, legal review, or state inspection can be a time-consuming, manual process β€” assuming the hardware is still functional at all.

🏒

Facility Transitions

If a clinic is acquired, merged, or sold, retaining a subset of vendor-specific physical machines may not be feasible or permitted. Data locked in proprietary hardware becomes a liability rather than an asset during these transitions.

The core problem: Legacy oncology hardware was designed to deliver treatment β€” not to serve as a long-term data archive. Relying on it in that role creates compounding risk that grows every year the machine sits powered on.

Two Paths Forward: Export or Virtualize

At TC Consulting, we recognize that the challenge of legacy data preservation requires purpose-built solutions β€” not workarounds. We offer customers two complementary approaches, which can be deployed independently or together depending on the facility's needs.

πŸ“¦

Option 1 β€” Batch DICOM Export & PACS Archival

Portable Β· Vendor-Neutral Β· Immediately Queryable

We extract all patient records from the legacy system in bulk and export them as standard DICOM files alongside human-readable flat-file reports. The resulting archive is loaded into a free, open-source PACS server (Orthanc, Dicoogle, or Sante) that runs on commodity hardware β€” no proprietary software required.

Once configured, any authorized workstation on the facility network can query the PACS by patient name, ID, date, or modality, retrieve the full DICOM study in seconds, and open it in any DICOM-compatible viewer. The legacy machine can then be safely decommissioned.

πŸ–₯️

Option 2 β€” Physical-to-Virtual (P2V) Machine Conversion

Hardware-Independent Β· Preserved Environment Β· Cost-Efficient

For situations where the full software environment of the legacy system must be preserved β€” including proprietary applications, license configurations, or specialized clinical interfaces β€” we offer physical-to-virtual (P2V) migration. The entire server is imaged and encapsulated as a virtual machine (VM) running on a modern hypervisor such as Hyper-V, Proxmox, VirtualBox, or VMware.

Why Virtualize Instead of Keeping the Physical Hardware?

  • Eliminate hardware dependency. Vendor-specific server hardware is expensive, increasingly difficult to source parts for, and has a finite operational lifespan. A VM runs on any modern server or workstation β€” hardware failure no longer equals data loss.
  • Reduce long-term maintenance cost. A single physical host can run multiple VMs. Instead of maintaining several aging dedicated servers, one modern machine handles the workload at a fraction of the energy and maintenance cost.
  • Snapshot and disaster recovery. VMs can be snapshotted, cloned, and backed up in minutes. Rolling back to a known-good state after a software issue takes seconds β€” a capability physical machines simply do not offer.
  • Portability across facilities. A VM is a file. It can be transferred to another host, a cloud environment, or a colocation facility β€” making it fully compatible with facility mergers, acquisitions, and relocations.
  • Security patching without hardware constraints. The VM guest OS can be patched and updated without concern for proprietary driver compatibility β€” reducing the attack surface that legacy hardware creates in a clinical network.

TC Consulting supports P2V migrations to Hyper-V, Proxmox, VirtualBox, and VMware. The physical server is retained in a powered-down state for 30–60 days post-migration as a rollback option before formal decommission.

The Real Cost of Access: A Workflow Comparison

The time savings of properly exported, PACS-indexed data become strikingly clear when compared against the workflow of retrieving patient data from a legacy system with an archive. Multiply these differences across hundreds of records per year and the operational impact is significant.

Step βœ… Exported Data in PACS ⚠️ Legacy Hardware with Archive
1 Query the PACS server
Search by patient name, ID, date, or modality from any authorized workstation on the network. Results return in seconds.
Determine patient active status
Log into the legacy system and check whether the patient record is in an active state or has been moved to long-term archive storage.
2 Download or export DICOM images
Select the desired study and export the full DICOM series directly from the PACS to a workstation or DICOM viewer. Total retrieval time: 1–3 minutes.
Restore patient from archive
If the record is archived (common for inactive patients), initiate a manual restore process. This typically takes 20–30 minutes depending on archive size and system speed.
3 Done
The full study is available for review, sharing, or export immediately.
Export DICOM series one by one
Manually export each DICOM image series individually from the legacy application β€” there is typically no bulk export capability. This adds several additional minutes per series on top of the restore time.
⏱ Total time: 1–3 minutes Total time: 30–45+ minutes per patient

Long-term impact: If your facility retrieves an average of just 5 archived patient records per week, that translates to roughly 2–4 hours of staff time lost weekly under the legacy hardware workflow β€” time that compounds into hundreds of hours and thousands of dollars annually. With PACS-indexed DICOM data, that same workload takes under 15 minutes. Staff time is redirected from manual archive retrieval to clinical care, and the risk of delayed access during time-sensitive audits or legal requests is effectively eliminated.

The Strategic Case for Vendor-Neutral, Portable Data

Beyond the operational benefits of faster access, there is a broader and increasingly urgent reason to ensure patient data exists in a portable, open, vendor-neutral format: the demands of regulatory compliance, legal accountability, and long-term institutional continuity.

βš–οΈ

Legal & Litigation Readiness

Medical malpractice claims, personal injury litigation, and workers' compensation cases frequently require access to treatment records from years or even decades prior. DICOM files in a queryable PACS can be retrieved and produced for legal review in minutes. Records locked in proprietary legacy hardware may be inaccessible if that hardware has failed β€” a defensibility risk no facility should accept.

πŸ›οΈ

State & Regulatory Requirements

Most U.S. states mandate that oncology and radiology records be retained for a minimum of 7–10 years, and in some cases longer for minors. Regulators and accreditation bodies (TJC, ACR, state health departments) may audit data accessibility at any time. DICOM in a PACS satisfies these requirements with a documented, searchable audit trail that proprietary archives typically cannot provide.

πŸ”’

HIPAA Compliance & Audit Trails

HIPAA's Security Rule requires covered entities to maintain documented access logs and ensure the integrity of protected health information (PHI). Modern PACS systems log every query, retrieval, and export event β€” producing the kind of audit trail that HIPAA investigators and Office for Civil Rights (OCR) auditors expect to see. Legacy proprietary systems often lack this capability entirely.

πŸ”„

Future-Proof Interoperability

DICOM is an ISO-recognized international standard maintained by NEMA. It is supported by every major imaging viewer, EMR platform, and clinical workstation in use today. Storing data in DICOM guarantees it will remain readable as technology evolves β€” unlike proprietary formats that become inaccessible when a vendor discontinues support or exits the market.

Vendor lock-in doesn't always announce itself clearly. It often reveals itself at the worst possible moment β€” during a system failure, a legal discovery request, or a facility acquisition β€” when proprietary data formats suddenly become a barrier rather than a resource. Investing in DICOM conversion before decommissioning legacy hardware is not merely a data management task; it is a risk mitigation strategy with direct implications for regulatory compliance, financial liability, and continuity of care.

Planning to retire or replace a legacy oncology system? TC Consulting can assess your data, outline the right preservation strategy, and handle the full conversion β€” remotely or on-site.

Migrating IDMS to a Virtual Machine:
A Complete Guide

Covering platform selection, database backup, VM build, software installation, data migration, testing, and licensing considerations.

Migrating an IDMS (Integrated Data Management System) server to a virtual machine is one of the most impactful infrastructure projects a radiation oncology facility can undertake. By moving IDMS off aging physical hardware and into a VM, organizations reduce dependency on proprietary server equipment, improve disaster recovery posture, simplify backups, and extend the operational life of the software well beyond its original hardware. This guide walks through the full process β€” from choosing a virtualization platform to deploying the completed VM in production.

Licensing Note: The customer is responsible for providing valid Windows Server and Microsoft SQL Server licenses for the virtual machine environment. Running IDMS in a VM without proper licensing for the underlying OS and database engine is a violation of Microsoft's terms and may expose your organization to compliance and audit risk. TC Consulting will assist with installation and configuration but does not provide OS or SQL Server licenses.

Choosing a Virtualization Platform

Four platforms are supported for IDMS VM migration. Each has different cost profiles, management models, and suitability for clinical environments. Below is a detailed breakdown of each.

Proxmox VE

Open Source Β· KVM-Based Β· Free (Enterprise Support Optional)

Proxmox Virtual Environment is a Debian Linux-based open-source hypervisor that uses KVM (Kernel-based Virtual Machine) for full virtualization and LXC for containers. It includes a polished web-based management console, built-in cluster support, Ceph storage integration, and live migration capabilities β€” features typically found only in enterprise-grade commercial platforms.

βœ“ Advantages

  • Completely free β€” no per-host licensing fees
  • Enterprise-class features (clustering, HA, Ceph) at no cost
  • Excellent web UI β€” manage all VMs from a browser
  • Strong community; widely used in healthcare and education
  • Built-in backup and snapshot management
  • Can import VMs from VMware and Hyper-V

βœ— Considerations

  • Linux-based host β€” IT staff must be comfortable with Linux
  • Requires a dedicated server (bare-metal install)
  • Commercial support subscription available but not free
  • Not pre-certified for some regulated healthcare environments

Best for: Organizations seeking enterprise VM capabilities without licensing costs. Ideal for IT teams comfortable with Linux administration.

VMware vSphere / ESXi

Industry Standard Β· Enterprise Β· Commercial Licensing Required

VMware ESXi is the most widely deployed enterprise hypervisor in the world and has long been the gold standard for regulated industries including healthcare and finance. VMware vSphere adds centralized management via vCenter. Following Broadcom's acquisition of VMware in 2023, licensing has shifted to subscription-only models, significantly increasing costs for many organizations.

βœ“ Advantages

  • Industry-leading stability and performance
  • Widely supported by hardware vendors and software ISVs
  • Extensive compliance certifications (FIPS, FedRAMP, HIPAA-ready)
  • Mature ecosystem of backup, DR, and management tools
  • Enterprise support contracts with guaranteed SLAs

βœ— Considerations

  • Subscription licensing now required β€” significantly higher cost post-Broadcom acquisition
  • Free ESXi tier discontinued in 2024
  • Full feature set requires vCenter (additional cost)
  • Many organizations migrating away due to cost increases

Best for: Larger healthcare organizations with existing VMware infrastructure, enterprise support requirements, or compliance mandates requiring certified vendor support.

Microsoft Hyper-V

Windows-Native Β· Included with Windows Server Β· Microsoft Ecosystem

Hyper-V is Microsoft's built-in hypervisor, included at no additional cost with Windows Server. For organizations that already own Windows Server licenses, Hyper-V is a natural choice β€” there is no additional hypervisor licensing, and management is integrated into Windows Server Manager and System Center. Since IDMS itself runs on Windows Server, Hyper-V provides tight OS-level compatibility.

βœ“ Advantages

  • Included with Windows Server β€” no separate hypervisor license
  • Native integration with Active Directory, SCOM, and Azure
  • Familiar management tools for Windows administrators
  • Strong support for Windows Server guest VMs
  • Live migration and failover clustering supported

βœ— Considerations

  • Windows Server license required for the host
  • Less capable than VMware or Proxmox for Linux-heavy workloads
  • Advanced features (live migration, replication) require Datacenter edition
  • Standalone Hyper-V Server product has been discontinued by Microsoft

Best for: Windows-centric IT environments that already have Windows Server licenses and prefer to stay within the Microsoft ecosystem. The natural choice when the organization uses Azure, Active Directory, or System Center.

Oracle VirtualBox

Free Β· Desktop Hypervisor Β· Development & Testing

VirtualBox is a free, open-source desktop hypervisor from Oracle. It runs on top of an existing OS (Windows, Linux, or macOS) rather than directly on bare metal. VirtualBox is widely used for development, testing, and evaluation environments. While it can run an IDMS VM adequately for non-production use, it is generally not recommended for production IDMS deployments due to performance and reliability limitations compared to bare-metal hypervisors.

βœ“ Advantages

  • Completely free β€” no licensing costs
  • Runs on top of any existing OS β€” no dedicated server needed
  • Very easy to install and configure
  • Cross-platform: Windows, Linux, macOS host
  • Useful for testing and staging IDMS configurations

βœ— Considerations

  • Type-2 hypervisor β€” lower performance than bare-metal alternatives
  • Not recommended for production clinical workloads
  • Host OS instability can affect VM uptime
  • Limited enterprise features (no live migration, HA clustering)
  • Oracle licensing terms for extensions can be restrictive

Best for: Testing, staging, and development environments. Also suitable for low-volume, non-mission-critical IDMS deployments where cost constraints are paramount and downtime risk is acceptable.

Platform Comparison at a Glance

Feature Proxmox VMware Hyper-V VirtualBox
Hypervisor TypeType-1 (bare metal)Type-1 (bare metal)Type-1 (bare metal)Type-2 (hosted)
CostFree (support optional)Subscription requiredIncluded w/ Windows ServerFree
Host OSDebian LinuxESXi (proprietary)Windows ServerAny OS
Production Readyβœ“ Yesβœ“ Yesβœ“ YesNot recommended
Live Migration / HAβœ“ Yesβœ“ Yesβœ“ Yes (Datacenter)βœ— No
Web Management UIβœ“ Built-invCenter (extra cost)Windows Admin Centerβœ“ Built-in
Best ForCost-conscious IT teamsEnterprise / regulatedWindows-centric shopsTesting / staging

The Migration Process

Regardless of the virtualization platform chosen, the IDMS migration follows a consistent process. TC Consulting handles all phases of this process remotely on behalf of the customer.

1

Assessment & Planning

Review the existing IDMS environment β€” Windows Server version, SQL Server version, CDMS/IDMS version, installed patches, storage requirements, and network topology. Confirm the customer's choice of virtualization platform and verify that the host server meets minimum resource requirements. Confirm with customer there is remote access to the site.

2

IDMS Database Backup

Before any migration work begins, a full backup of the CDMS/IDMS database is taken using SQL Server Management Studio (SSMS) or a SQL backup agent. The backup file is verified for integrity and stored securely on external media or a network location separate from the source server. Archived patient data may be consolidated from multiple locations to a single location if preferred. This backup serves as the restore point and must be completed successfully before proceeding.

3

Virtualization Platform Setup

The customer is responsible for installing the chosen hypervisor of choice. For Proxmox, this means a bare-metal Linux install. For Hyper-V, the Windows Server role is enabled. For VMware, ESXi or VMWare Workstation is deployed. The host is configured with appropriate networking (VLANs, static IP), storage (local SSD, NAS, or SAN), and management access.

4

Building the Virtual Machine

TC Consulting will create the Virtual CDMS/IDMS machine, install relevant Windows Server operating system and CDMS/IDMS server application, and make the Virtual Disk or Virtual Machine avaialble for download. Customer IT will need to download and import the virtual machine into their virtualization platform, or create a new Windows Server VM using the downloaded virtual disk on the hypervisor with sufficient vCPUs, RAM, and virtual disk space to match or exceed the original physical server's specifications. The customer-provided Windows Server license is applied. Best practices for VM configuration are followed: virtio or SCSI drivers for disk I/O, sufficient CPU allocation for SQL Server workloads, and snapshot capability enabled for rollback safety.

5

Database & Data Restoration

The database backup taken in Step 2 is restored onto the new VM using SSMS. Database integrity checks are run post-restore to confirm no corruption. IDMS is configured, licensed, launched and the database connection is validated before any clinical testing begins.

6

Testing & Validation

Comprehensive testing is performed before the system goes live: patient record retrieval, plan loading, DICOM connectivity with 3rd party imaging modalities, and network share access from clinical workstations. A representative set of patients is loaded and verified against the original system to confirm data integrity.

7

Production Cutover & Deployment

Once testing is complete and the customer's clinical team has approved the VM environment, the production cutover is scheduled. The physical IDMS server is taken offline, the VM is promoted to production, and clinical workstations are pointed to the new system. The original physical server is retained in a powered-down state for a defined period (typically 30–60 days) as a rollback option before being decommissioned.

Licensing Requirements

To remain in compliance, the following licenses must be provided by the customer prior to the start of the migration project:

  • Windows Server License β€” Required for the guest VM operating system. The edition (Standard or Datacenter) should match the intended workload and VM density. Datacenter is required for unlimited VM rights on a licensed host.
  • Microsoft SQL Server License β€” Required for the IDMS database engine. SQL Server Standard is typically sufficient; SQL Server Developer edition is not licensed for production use.
  • Hypervisor License (if applicable) β€” Proxmox and VirtualBox are free. Hyper-V is included with Windows Server. VMware vSphere requires a current subscription through Broadcom.

Note: TC Consulting is not a Microsoft licensing reseller and does not provide OS or SQL Server licenses. Customers should work with their Microsoft volume licensing agreement or a Microsoft partner to obtain the required licenses before the project begins.

Ready to move your IDMS server to a virtual machine? TC Consulting manages the entire process β€” from backup through production deployment.

Privacy Policy

Effective Date: June 1, 2026  Β·  TC Consulting Services

TC Consulting Services ("we," "us," or "our") is committed to protecting the privacy of visitors to this website. This Privacy Policy explains what information we collect, how we use it, and your choices regarding that information.

1. Information We Collect

We collect information in two ways:

Information you provide voluntarily. When you submit the contact form or post a blog comment, we collect your name, email address, and any message or comment text you provide. Phone number and service type are optional fields on the contact form.

Automatically collected information. This site maintains a basic visitor counter that records the total number of page visits. No personally identifiable information is captured by the counter. We do not use cookies, tracking pixels, analytics platforms (such as Google Analytics), or any third-party behavioral tracking on this site.

2. How We Use Your Information

  • To respond to inquiries submitted through the contact form.
  • To display approved comments on the blog.
  • To communicate with you regarding services you have requested or expressed interest in.

We do not use your information for marketing, advertising, or any purpose beyond direct communication related to your inquiry.

3. How We Share Your Information

We do not sell, rent, or share your personal information with third parties, with the following limited exceptions:

  • Formspree β€” Contact form submissions are processed through Formspree (formspree.io), a third-party form handling service. Formspree receives your name, email, and message in order to deliver it to us. Please review Formspree's Privacy Policy for details on how they handle data.
  • Legal requirements β€” We may disclose information if required to do so by law or in response to a valid legal process.

4. Data Storage & Security

Blog comments are stored in a MySQL database on our privately hosted server. We take reasonable technical measures to protect stored data from unauthorized access. However, no method of electronic transmission or storage is 100% secure, and we cannot guarantee absolute security.

5. Your Rights & Choices

You may contact us at any time to:

  • Request deletion of a blog comment you submitted.
  • Ask what personal information we hold that is associated with your email address.
  • Request correction or deletion of that information.

To make a request, email us at trustedcomputing26@yahoo.com with the subject line "Privacy Request."

6. Children's Privacy

This website is intended for healthcare and IT professionals and is not directed at children under 13. We do not knowingly collect personal information from children.

7. Trademark Disclaimer

TC Consulting Services is an independent IT consulting firm. All product and company names referenced on this site β€” including but not limited to Accuray, IDMS, CDMS, Multiplan, Precision, Orthanc, Dicoogle, and Sante β€” are trademarks or registered trademarks of their respective owners. TC Consulting Services is not affiliated with, authorized by, sponsored by, or endorsed by Accuray, Inc. or any other manufacturer or software vendor.

8. Changes to This Policy

We may update this Privacy Policy from time to time. Any changes will be reflected on this page with a revised effective date. We encourage you to review this page periodically.

Questions about this policy? We're happy to help.