Comparative Analysis
Compare the job a system performs before comparing suppliers. An EHR, an integration engine and a FHIR server can participate in the same service while solving different problems. The distinctions below are a synthesis of the cited product documentation, checked on 9 September 2026; they are not a performance ranking.
Compare the Same Product Role
| Job | InterSystems offering | What a useful comparison should cover |
|---|---|---|
| Run clinical and administrative work | TrakCare, with IntelliCare covered separately | Compare the same care setting and enabled modules: recording, prescribing, orders, appointments and administration. A data API does not establish these workflows. |
| Operate a laboratory | TrakCare Lab Enterprise | Compare the laboratory process and its EHR interfaces separately from an organisation's EHR replacement. |
| Exchange data between systems | Health Connect | Compare interfaces, transformations, error handling, monitoring and operating responsibilities. Distinguish the engine from its cloud service. |
| Assemble and present records across organisations | HealthShare UCR, Clinical Viewer and selected companion components | Compare source coverage, identity matching, reconciliation, provenance, access and clinical presentation. Merely storing FHIR resources does not establish a working shared-care record. |
| Build applications and manage healthcare data | IRIS for Health | Compare development, persistence, interoperability and analytics requirements against the chosen platform and deployment model. |
| Store and expose FHIR data | FHIR Services / FHIR Server | Compare the same FHIR release, operations, profiles, terminology, access controls, hosting and support scope (SRC-008, SRC-050, SRC-095 to SRC-100). |
Sourced FHIR Comparators
These are examples of alternative delivery models, selected to explain the category rather than define a procurement shortlist.
| Option | Publicly documented scope | Comparison boundary |
|---|---|---|
| InterSystems FHIR Services | Managed FHIR infrastructure; the wiki separately records server, profile and cloud-service capabilities (SRC-008, SRC-050, SRC-095 to SRC-100). | Match the actual service subscription and supported operations to the workload. IRIS for Health is a broader platform and should not be substituted silently in the comparison. |
| HAPI FHIR | Apache-2.0 Java client/server project. Its project site documents parsers, clients, servers and a deployable JPA/database server. | An open-source implementation offers a different operating model from a managed service. For a self-hosted deployment, include engineering, hosting, security, upgrades and support in the comparison. No specific HAPI release or local implementation was benchmarked here. |
| Azure Health Data Services | Microsoft's managed service family includes FHIR and DICOM services. Its FHIR service documents SMART on FHIR and Microsoft Entra role-based access. | Compare its FHIR service with managed FHIR infrastructure; do not infer a complete EHR, integration engine or shared-care workflow from the wider service family. |
Azure naming matters: Microsoft schedules the older Azure API for FHIR for retirement on 30 September 2026 and has blocked new customer deployments since 1 April 2025. Use the Azure Health Data Services FHIR service for the current comparison; the retirement date is still in the future at this review date.
What the Evidence Supports
The sources establish product categories, documented features and delivery models. They do not provide a common workload benchmark, comparable prices, independent clinical outcomes or a UK supplier-assurance comparison.
A defensible evaluation would hold the workflow and dataset constant, then assess completeness, terminology and profile handling, access and audit, failure recovery, operational effort and total cost. NHS onboarding and local clinical-safety evidence remain separate from both FHIR capability and software licensing. Use the existing Standards and Interoperability and UK NHS Digital Connectivity and Interoperability Evidence pages for those boundaries.