For CIOs, Clinical Information Officers and IT teams
We run the platform. You run the service.
iQemo is a cloud-hosted prescribing and medicines administration platform for systemic anti-cancer therapy (SACT), used by 7,500 clinicians across 108 hospitals in the UK and Australia. iQ HealthTech hosts it, secures it, keeps it current, and works alongside your team on the integrations. We take on the complexity of running a system like this, so your team can spend its time on the service rather than the software.
What this means for your organisation
No hardware, servers or patching for your team to maintain
Browser access, with nothing to deploy to endpoints and no upgrade project to resource
Connections to the patient administration, laboratory and pharmacy systems you already run
Access governed from your own user directory, with high-risk prescribing restricted to named or trained staff
ISO certification, medical device registration and clinical safety documentation available as evidence
Patient data held in your own country, in line with local data sovereignty requirements
A browser-based service, not an installed system
iQemo is delivered as a hosted service, run by iQ HealthTech and accessed through a standard web browser. There is no client software to package and install, and no servers of your own to maintain. Updates reach every user at once, so there is no desktop estate work and no upgrade project to resource.
Remote working is a property of the design rather than an addition to it: a pharmacist verifying off site, a consultant prescribing from a satellite unit and a nurse administering at the chair all use the same system, reached the same way. Your footprint is integration and identity, not infrastructure.
It supports multi-site and multi-organisation configuration, so a shared regimen library can serve a network of hospitals while each keeps its own workflow rules and formulary settings.
One record, from prescribing to reporting
iQemo prescribes from a governed regimen library rather than free text. Doses are calculated to protocol, interactions and allergies are checked, and pathology results and pre-treatment assessments are visible at the point of decision. Administration is recorded at the chair, with dual-check where required, and the audit trail follows the patient rather than the department.
Because the whole pathway runs in one system, the record it produces is complete. Reporting draws on that record for clinical audit, service management and mandatory data submissions — activity, prescribing patterns, workflow and capacity — without a separate data collection exercise.
Built to work with the systems you already run
iQemo connects to your patient administration and electronic patient record systems, laboratory systems, third-party pharmacy manufacturing and dispensing systems, and even some infusion pumps, using standard healthcare messaging. Where you run an integration engine of your own, iQemo connects to that rather than to each source system.
Integration traffic runs separately from clinical user access, over a private connection. Message types, data flows and network requirements are documented in full and worked through with your integration team as part of our onboarding programme.
Redundant by design, inside your jurisdiction
iQemo is hosted in Microsoft Azure. UK services are processed in the UK, in accordance with NHS guidance, UK GDPR and the Data Protection Act 2018. Services outside the UK are hosted in the region for that country, in accordance with data sovereignty rules.
The system is replicated and load balanced across physically separate datacentres with independent power, cooling and networking, and fails over automatically without data loss. Backups are encrypted and held in immutable storage, so they cannot be altered or deleted by ransomware or malicious action. The platform is monitored continuously, and security patching is carried out monthly without service loss.
How the service is protected, and who can do what
All traffic is encrypted in transit and at rest. A managed firewall and a web application firewall sit in front of the service, with DDoS protection and intrusion detection available. Security events are collected and monitored through a security information and event management (SIEM) platform. User access can be governed from your own directory, with group membership driving iQemo roles, and multi-factor authentication is supported.
Role-based access control scopes what each user can see and do by organisation and site, and can restrict high-risk activity — clinical trial regimens, intrathecal and first-cycle prescribing - to named or trained staff. Every action is recorded with the user, the time and the change.
Assurance and governance
Regulatory
iQemo is currently classified a Class I medical device in the UK. It is CE marked and registered with the MHRA in the UK.
Quality management
iQ HealthTech's quality management system is certified to ISO 13485:2016, the international standard for medical device quality management, and is audited annually by BSI. The standard governs how the product is designed, built, tested, released and supported — design controls, document and record control, supplier management, non-conformity and corrective action, traceability and post-market surveillance. It means the process that produces each release is independently audited, not only the software that comes out of it.
Information governance and security
Information security is managed through an information security management system certified to ISO 27001:2022. The standard requires risks to information to be identified, owned and treated, under controls covering access, cryptography, supplier relationships, logging and monitoring, incident management and business continuity, with the whole system subject to management review and independent audit rather than a one-off assessment.
Clinical risk management
For NHS services, iQ HealthTech maintains a clinical safety case under DCB0129 with a hazard log kept across the development lifecycle. Our Clinical Safety Officer is Ed Hawley-Jones, an oncology pharmacist who has completed NHS Digital’s Clinical Safety Officer training. A named officer is assigned to every implementation.
Secure development
Development follows a documented secure software development lifecycle with defined gates, static code analysis on every build, regular vulnerability scanning, and annual independent penetration testing.
Service and support
Availability. A 99.9% availability commitment across the production service, excluding agreed planned maintenance and events outside iQ HealthTech’s control. Planned maintenance is communicated in advance.
Support. Office-hours support by telephone, email and a support portal, with everything logged as a ticket and triaged on receipt. Enhanced out-of-hours and 24/7 cover is available above standard support hours.
What a deployment involves
Implementations run in five stages, each with defined deliverables and joint sign-off, and a named project manager on both sides. The technical work is integration and identity; the substantial work is clinical.
01
Planning
Workshops map how the service works now and how it will work in iQemo. Integration, reporting, training and clinical safety approaches are agreed and documented.
02
Build and configuration
We stand up the environments, configure iQemo to the agreed design, test the integrations, and build the regimen library with your pharmacists validating it.
03
User acceptance testing
Integrations are signed off first, because they drive the clinical workflow. Your clinical stakeholders then sign off that the configuration is safe to use live.
04
Training
Delivered by user role to the agreed plan, with guides and quick reference materials provided.
05
Go-live
Configuration is promoted to production and revalidated, a service readiness review is approved, and cutover follows a go-live plan with a documented fallback. We are on site where appropriate.
The project team then hands over to our customer success team, and the project closes with a lessons-learned review.
What drives the timeline. Regimen library size and pharmacist availability to validate it, integration complexity, and your own change-freeze windows. Implementation is planned around your clinical calendar, not ours.
See how clinical teams use iQemo
Discuss how iQemo could fit your digital environment
Most technical questions are answered faster in a conversation than in a document. Our own technical team — the people who build and run iQemo are happy to talk to your security, information governance and architecture leads, work through the areas you care about, and tell you plainly where iQemo would fit your service and where it would not.