Frequently Asked Questions
1. How long does a typical PAC integration take?
Most NHS trust projects run 8–16 weeks from assessment to go-live. The timeline is driven by three key factors: 1) the number of systems and modalities that need to be connected, 2) the complexity of data migration (volumes, legacy formats, retention rules), and 3) the availability of clinical stakeholders for testing and sign-off. We break the work into clearly defined sprints—Discovery, Build, Validation, and Go-Live—so progress is transparent and risks are managed early. For urgent requirements such as a single-site cloud PACS implementation, we have fast-track options that can be delivered in as little as four weeks.
2. Will there be downtime during data migration?
No. We operate a near-zero-downtime migration strategy that runs the legacy and new environments in parallel until every study has been checksum-verified and reconciled. Reads and writes continue on the legacy PACS while historical images are ingested in the background. Once our automated reconciliation reports show 100% completion and clinicians have performed final acceptance tests, we schedule a brief “switch-over window” (usually 1–2 hours outside clinical peak times) to make the new archive authoritative. Rollback plans are documented and rehearsed, although they are rarely needed.
3. Can you integrate with our existing EPR and RIS vendors?
Absolutely. We have production-level interfaces with Cerner Millennium, Epic Hyperspace, Allscripts Sunrise, EMIS Web, System C Medway, Sectra RIS, GE RISi, and many more. Our team is fluent in HL7 v2/v3, FHIR RESTful APIs, DICOM MWL/MPPS, and IHE-XDS profiles, allowing us to map fields, handle proprietary extensions, and maintain data integrity. Where vendor APIs are closed, we collaborate under “vendor-bridge” agreements or use interface engines such as Rhapsody and Mirth Connect to translate messages without compromising support contracts.
4. How do you handle patient data security?
Security is embedded in every layer of our solution. Data is encrypted in flight using TLS 1.3 and at rest with AES-256. Access is role-based and federated to your Active Directory or NHS Identity, with multi-factor authentication enabled for privileged accounts. All servers reside in ISO 27001 and NHS DSP-compliant data centres, and connections to on-prem systems transit secure VPN tunnels over the HSCN. We perform quarterly penetration tests, maintain Cyber Essentials Plus certification, and provide full audit trails that align with Caldicott and GDPR requirements.
5. Do you provide post-implementation support?
Yes—support is a core component of our value proposition. Every project transitions into a managed service that includes 24/7 monitoring, automatic alerting, and an SLA-driven helpdesk with 30-minute critical response. Clients receive a named Technical Account Manager, quarterly performance reviews, and access to our self-service knowledge base. We also offer on-site engineering for major upgrades or if your internal policy mandates physical presence for certain tasks. All support metrics—uptime, incident resolution time, and user satisfaction—are shared transparently with your governance board.
6. What are the typical cost savings?
Clients commonly achieve: 1) up to 30% reduction in storage costs by de-duplicating datasets and leveraging tiered cloud storage, 2) 25% faster report turnaround through automated worklists and AI triage, 3) a tangible drop in repeat scans (3–5%) because images are readily available across sites, and 4) reduced vendor lock-in penalties when moving to vendor-neutral architectures. Combined, these savings deliver a payback period of 12–18 months for most trusts, with ongoing OPEX reductions in the years that follow.
