Manage the existing environment
Server and storage administration, DICOM routes, user access, backups, and vendor coordination within the agreed support scope.
PACS support & DICOM services · New Jersey
PACS support for current and legacy systems
HealthDesk IT manages PACS servers, DICOM routing, archive access, and imaging infrastructure for New Jersey practices. If vendor support has ended, we review what can be maintained and plan the move to a supported system.
Routine and planned support, subject to version, licensing, and agreed scope. Keep patient information and credentials out of the public form.
What does your PACS need next?Start with your current system and support status.
PACS support or end-of-life review
Legacy management, DICOM routing, archive access, and a transition plan.
Legacy management, DICOM routing, archive access, and a transition plan.
Legacy PACS support
Vendor support ended. Your archive still matters.
An end-of-life notice leaves a practical question: who will look after the imaging environment while you decide what comes next? HealthDesk provides independent infrastructure management and transition planning after reviewing the installed system.
Plan access to historical studies
Map the archive, priors, reports, export options, and retrieval tests before changing the PACS or retiring a viewer.
Prepare a supported replacement
PACS data migration, a pilot, validation, cutover, rollback, and an agreed retirement decision for the legacy system.
Support has limits. Infrastructure management does not restore manufacturer patches, licenses, warranties, or clinical validation. If continued operation is unsuitable, the plan focuses on replacement and access to retained studies.
Recognize your PACS or DICOM viewer?
Support status depends on the exact release and contract. Share the product name, version, and any vendor notice so we can review your options.
Philips iSite 3.6
Philips identifies iSite 3.6 as end of life and end of service. Review archive access, connected viewers, and the migration path.
Philips lifecycle advisory (opens in a new tab)Merge eFilm Workstation 4.2 / 4.2.1
This is a DICOM viewer. NLM lists commercial distribution ending June 30, 2022. Review existing study access and viewer replacement.
eFilm 4.2.1 product record (opens in a new tab)GE Centricity PACS / PACS-IW
Start with the release, server, archive, and DICOM conformance statement. The product name alone does not establish end-of-support status.
GE version-specific documentation (opens in a new tab)McKesson Horizon Medical Imaging
Identify the HMI release, archive, interfaces, and current support terms before scoping legacy access or PACS migration.
Discuss your installed HMI systemThese are product-identification examples, not manufacturer affiliations or a promise to support every release. HealthDesk reviews licensing, access, export options, and technical feasibility before taking on the work.
PACS server support and DICOM workflow review
We map the route from acquisition to authorized viewing, then assign the infrastructure and vendor work needed at each handoff.
Acquisition + routing
How a study enters the environment
- Modalities, AE titles, IPs, ports, destinations, and routing rules
- Modality Worklist, order, accession, patient-context, and correction paths
- Send queues, forwarding, teleradiology, outside-study, and multi-site handoffs
- Network, firewall, VPN, DNS, bandwidth, and approved vendor access
Archive + lifecycle
Where studies live and how they return
- PACS, archive, cloud or hybrid location, interfaces, and responsibility
- Study volume, growth, retention decisions, retrieval expectations, and priors
- Backup, recovery, routing fallback, legacy access, and migration readiness
- Export terms, proprietary data, metadata mapping, and retirement gates
Viewer + ownership
How authorized users reach the study
- Diagnostic and clinical viewers, workstations, browsers, roles, and remote access
- RIS/EHR launches, reporting, sharing, and access for referring clinicians
- Logging, encryption, user access, support, and BAA responsibilities where applicable
- Named owners, evidence, escalation, acceptance, and handoff
Scope boundary: HealthDesk IT reviews and coordinates the infrastructure side of imaging workflows. Clinical interpretation, modality operation, regulatory approval, medical-device certification, and product-specific warranties remain with the qualified clinical team and applicable vendors.
Troubleshooting should follow the study, not the ticket queue
These checkpoints create a shared language for the practice and its vendors. Exact tests depend on the participating modality, PACS, RIS/EHR, archive, viewer, workflow, and approved access.
| Checkpoint | Evidence to review | Decision before moving on |
|---|---|---|
| 1 · Identify | Affected modality, site, workflow, timing, users, scope, and operational impact. | The symptom and safe evidence-collection owner are clear. |
| 2 · Order / worklist | Registration, order, accession, scheduled procedure, worklist query, patient-context, and correction workflow. | The study identity is consistent or the mismatch owner is assigned. |
| 3 · Send / route | AE titles, destinations, ports, connectivity, queue state, route rules, transfer response, gateway, and logs. | The last confirmed handoff and next receiving owner are known. |
| 4 · Store / retrieve | Archive receipt, indexing, storage availability, priors, query/retrieve behavior, lifecycle tier, and recovery path. | Custody, retrieval expectation, exception, and escalation are documented. |
| 5 · View / share | User role, launch context, workstation or browser, remote access, viewer performance, and downstream workflow. | The workflow completes or the remaining blocker has an owner. |
Decision-ready documentation
Leave with an imaging map vendors can act on
Your agreed scope defines the deliverables: a current-state map, named owners, validation evidence, and a practical support or migration plan.
Current-state study journey
Modalities, worklist/order sources, routes, PACS, archives, viewers, locations, destinations, and known exceptions.
Connection and ownership register
Approved endpoints, vendors, contacts, support boundaries, access method, evidence sources, and escalation sequence.
Validation and recovery checklist
Representative workflow tests, expected results, acceptance owner, failure evidence, fallback, and exception handling.
Migration or change-readiness decisions
Archive access, export constraints, metadata, priors, pilot, coexistence, rollback, cutover, handoff, and retirement gates.
New Jersey imaging operations
Remote evidence and onsite reality belong in one plan
HealthDesk IT connects vendor calls and logs to the network, workstations, modalities, staff workflow, and physical environment around them. Scheduled onsite work is available in New Jersey when the agreed scope requires hands-on infrastructure review.
Discuss the imaging pathRemote discovery and vendor coordinationRoute mapping, log and queue review, access paths, documentation, migration planning, and escalation.
Scheduled onsite infrastructure review in New JerseyApproved access to modalities, workstations, switches, firewalls, local servers, or location-specific workflow.
One owner for the cross-vendor conversationA single current-state map and next-action register without pretending one vendor controls the complete path.
Technical basis and documented work
Imaging decisions should follow published standards, real vendor conformance, and checkable experience
These resources support the workflow and interoperability boundaries used here. They do not replace current product conformance statements, contracts, qualified clinical oversight, or testing in the actual environment.
DICOM Standard · current editionPrimary specifications for medical-imaging objects, services, conformance, exchange, network communication, storage, and web services.IHE Radiology · Scheduled WorkflowConnects registration, ordering, scheduling, acquisition, storage, and viewing across HL7- and DICOM-based systems.HealthDesk PACS archive planning guideA practice checklist for routes, viewers, archive growth, retention, access, recovery, and vendor ownership.Hudson River Imaging case recordClient-corroborated PACS networking, imaging workstation, backup, endpoint security, and managed infrastructure support.Urgent Care Imaging · client-corroborated Azure DICOM projectThe updated public review aligns with the project record on Azure Health Data Services DICOM, Entra ID authorized access, controlled sharing, MedDream viewing, and completion of the agreed implementation scope.
Plain-language answers
PACS support questions from imaging practices
We can take on agreed infrastructure management after reviewing the version, licenses, access, dependencies, and technical risks. Work may include servers, storage, DICOM routing, backups, archive access, and a migration plan. This does not renew manufacturer support or make every legacy release suitable for continued clinical use.
Bring the modality and location list, PACS/RIS/EHR and viewer vendors, current route or AE-title documentation, archive location, access methods, vendor contacts, recent failure patterns, planned changes, and workflows most sensitive to interruption. Share PHI only through an approved method after scope and responsibilities are established.
Yes, within the agreed infrastructure scope. We can review connectivity, routes, queues, ports, firewall or VPN paths, workstation behavior, access, and available logs, then document the last confirmed handoff and assign the next action.
No. A responsible scope also considers study and metadata inventory, patient and accession reconciliation, priors, reports or non-DICOM content, proprietary data, export terms, throughput, pilot testing, coexistence, validation, rollback, legacy access, retention, support, and decommissioning.
No. Each product implements specific DICOM roles, services, objects, and transfer syntaxes. Compare current conformance statements and test the intended workflow before changing production.
PACS workflow review
Plan support for your current or legacy PACS
Tell us the PACS or viewer name, installed version, location, and support concern. We will review ongoing management, archive access, or migration options with your practice.
For current and legacy PACS, DICOM routing, archive access, viewer replacement, and migration
Current-state path, evidence, validation, vendor ownership, escalation, and handoff
BAA available when the agreed HealthDesk IT role involves ePHI
Request a PACS support review
Name and an email or phone number are required. Share system details only; no patient information or credentials.