Frequently Asked Questions
1. How long does it take to launch a minimum viable platform?
An MVP can typically be delivered in 12–16 weeks. The timeline is broken down into three main phases: (1) a two-week Discovery Sprint where we align on scope, compliance requirements, and stakeholder goals; (2) a four-week Design & Architecture phase covering UX prototypes, technical blueprint, and integration specifications; and (3) 6–10 weeks of Agile Development in two-week iterations. Design, development, and compliance activities run in parallel so that penetration testing, clinical safety reviews, and user acceptance testing (UAT) do not delay go-live. You receive a detailed project Gantt and burndown chart at the end of Discovery so everyone has absolute clarity on milestones, dependencies, and critical paths.
2. Can you integrate with our existing EHR and PAS?
Yes. We adopt an API-first approach using HL7 FHIR, legacy HL7 v2 messaging, NHS Spine services, and secure file transfers to integrate with virtually any Electronic Health Record or Patient Administration System. Our interoperability team conducts a connectivity assessment to identify available endpoints, data mappings, and message triggers. We then configure a lightweight integration engine—often powered by Mirth or Azure Integration Services—to translate, validate, and route messages. End-to-end integration testing, including synthetic test-bed data and live parallel-run scenarios, ensures zero disruption to clinical operations during cut-over.
3. What hosting options do you support?
We support fully managed deployments on Microsoft Azure, Amazon Web Services, or on-premises data centres. For cloud builds we provision multi-AZ, auto-scaling clusters, with data residency constrained to UK regions to meet NHS and GDPR obligations. All environments include encrypted storage, hourly snapshots, disaster-recovery orchestration, and 99.9 % service-level guarantees. On-premises installations leverage Kubernetes or Docker Swarm for portability and are hardened to CIS benchmarks. A hybrid architecture can also be implemented if you require direct HSCN connectivity while maintaining elastic compute capacity in the cloud.
4. How do you ensure data security and compliance?
Security is baked into every stage of our SDLC. We start with formal threat modelling and Data Protection Impact Assessments (DPIAs). All data is encrypted in transit (TLS 1.2+) and at rest (AES-256). Access is strictly role-based, enforced through OAuth 2.0, OpenID Connect, and granular attribute-based policies. Each release passes static code analysis (SonarQube), dynamic scanning (OWASP ZAP), and independent penetration testing. We also prepare and submit the Data Security & Protection (DSP) Toolkit on your behalf, and our processes are aligned with ISO 27001 and NHS Digital Clinical Risk Management standards DCB 0129/0160.
5. Do you provide training for clinical staff?
Absolutely. We deliver a comprehensive training programme that combines self-paced e-learning modules, CPD-accredited classroom sessions, and “train-the-trainer” workshops to cultivate internal champions. Interactive, in-app guidance is embedded directly into the platform via tool-tips and walk-throughs. Adoption metrics—such as task completion rates and login frequency—are monitored through analytics dashboards, enabling targeted refresher sessions where necessary. All materials are designed to accommodate varying digital literacy levels and shift patterns, ensuring minimal disruption to clinical workflows.
6. What post-launch support models are available?
We offer three support tiers, each underpinned by ITIL service-management principles. The Standard tier (8×5) covers core business hours with a four-hour response SLA for P1 incidents. The Enhanced tier (12×5) adds extended evening coverage, a two-hour response SLA, and monthly security patching. The Premium tier (24×7) delivers round-the-clock monitoring, 30-minute P1 response, quarterly performance reviews, and a dedicated Technical Account Manager. All tiers include proactive health checks, automated alerting, and a shared feature backlog that feeds directly into our continuous-improvement roadmap, ensuring the platform evolves alongside your organisational needs.