Skip to content

IntelliCare

This page tracks the IntelliCare EHR, its product changes and named deployments. Deployment status was checked on 8 September 2026; the AI-workflow and EMC-outcome review was extended on 9 September 2026.

Official InterSystems Positioning

InterSystems positions IntelliCare as an EHR with built-in GenAI and ambient documentation. Its current feature descriptions cover encounter transcription and draft notes, patient-record summaries, suggested actions/orders and diagnosis/procedure coding for professional review. These are product capabilities; the enabled features, release and approval workflow must be established for each deployment.

Role in the Portfolio

IntelliCare is built on TrakCare and IRIS for Health. The product page describes clinical, administrative, departmental and revenue-cycle functions, with Personal Community and TrakCare Lab Enterprise among the options. Keep the application, TrakCare foundation and IRIS platform roles distinct. A TrakCare customer or a country where IntelliCare is marketed is not automatically an IntelliCare deployment.

User Interface

IntelliCare demonstration at SantExpo 2025 showing a projected mobile encounter-recording screen with a timer, microphone, pause and stop controls.

Mobile encounter recording. The phone interface shows a recording timer and pause/stop controls during InterSystems' SantExpo 2025 demonstration. This is a frame from a filmed presentation, so fine text is limited; watch the demonstration at 9:39 to follow the interaction. The official recording was published in 2025; the product build is unstated. Captured 15 September 2026. Select the image to open it at full size.

AI-to-TrakCare Workflow Map

This is a functional mapping of public product descriptions, not a verified internal API or deployment architecture. IntelliCare changes how information is retrieved, drafted and entered into the existing clinical and business workflows. TrakCare Core and optional modules supply the underlying record, departmental, medication and financial functions.

Underlying TrakCare workflow IntelliCare AI function Described output Control to verify locally
Reviewing the patient record AI Assistant with natural-language questions and configurable prompts Retrieved information and history summaries Correct patient/encounter, source coverage and clinician review.
Clinical documentation and care planning Ambient capture or dictation Draft encounter notes, reports and visit summaries Consent, editing, attribution and approval before record inclusion.
Structured chart maintenance Actions Terminology-mapped allergies, alerts and diagnoses from voice/text Validate meaning, terminology, duplicates and inclusion.
Orders and referrals Actions Proposed laboratory/imaging orders, referrals or equipment requests Authorised review and the configured downstream order workflow.
Coding and revenue cycle AI-enabled Coding Workbench Suggested diagnosis/procedure codes Professional validation before the established billing/claim process.
Handover and patient communication Generated documents and summaries Draft handover or patient-facing text Verify recipient, content, release and communication workflow.
Medicines prescribing, pharmacy and administration Existing integrated medication workflow remains relevant The reviewed AI material does not establish autonomous prescribing or administration Retain formulary, decision-support, pharmacy-review and administration controls.

The AI-column descriptions come from the brochures and current revenue-cycle material; the final column is the wiki's proposed assurance work, not a claim that a particular site has supplied those controls. The brochure's Actions examples cover structured chart items and selected orders; they should not be expanded into approval-free execution or support for every order type.

Upgrade and Availability Boundary

InterSystems says modern TrakCare configurations can persist when moving to IntelliCare, without a full reimplementation. That statement does not resolve local release compatibility, configuration validation, model/service dependencies, licensing, data processing or enabled AI features. Public descriptions are not a version-by-version implementation guide.

The 2025 brochures still contain pre-certification EU/UK availability wording. Treat that footer as dated material alongside the later May 2026 EU MDR announcement; neither establishes current UK market clearance or a customer's release/module scope.

Regulatory and Customer Evidence

InterSystems' 19 May 2026 announcement and MDR page state that IntelliCare and TrakCare achieved Class IIa certification under EU Regulation 2017/745. The announcement describes clinician approval of proposed documentation and orders. Certificate, intended-use, version/module and market scope remain separate assurance requirements; the statement does not establish NHS clinical-safety completion or UK rollout.

Named Deployment Status

Organisation Country Public evidence and date Defensible status
EMC Healthcare Indonesia March 2026 investor presentation and 2025 sustainability report confirm implementation, with the latter explicitly covering all EMC hospitals. Customer-reported implementation; individual feature/site activation and independent outcomes remain distinct.
Medcare Hospitals & Medical Centres UAE Vendor MoU announcement, 25 June 2026, covers six hospitals and 25 medical centres. Medcare's own 21 July post confirms adoption using future deployment language. Adoption agreement and planned rollout, progressing from TrakCare. No completed clinical go-live or operational site list established.
King's College Hospital London–Jeddah Saudi Arabia Hospital announcement, 7 September 2026; InterSystems clarification, 8 September, describes a signed agreement and intended first EMEA IntelliCare go-live. Adoption/implementation forthcoming. The vendor's future-tense go-live wording does not establish completed use.
RedSalud Chile Vendor announcement dated 1 June 2026 describes incorporation of IntelliCare into the existing TrakCare estate. Announced adoption/transition; completed rollout not established by this source.

Middle East Interpretation

There are now named UAE and Saudi adopters, but the checked sources do not establish completed Middle Eastern IntelliCare clinical go-live. Medcare's first-EMEA-provider adoption claim and King's intended first-EMEA-go-live claim concern different milestones; retain attribution instead of treating either as an independently established regional ranking.

Do not convert Saudi/UAE market availability, regional awards, summit attendance, generic InterSystems customer lists or existing TrakCare installations into an IntelliCare installed base. EMC provides the strongest customer-side implementation evidence in this pass; its integrated-HIS scope does not establish that every AI function is active at every site.

EMC Outcome Evidence

The 9 September review strengthens implementation evidence while limiting benefit attribution. The customer sustainability report describes AI Assistant retrieval/summaries and Ambient documentation drafts, but states that the report has no external assurance. Its financial audit does not independently validate the AI statements.

Reported claim What the evidence supports Interpretation limit
All EMC hospitals implemented IntelliCare Customer reporting, with a 2025 implementation milestone. Installation scope is not a per-feature activation list or a causal outcome.
75% fewer clicks Eight to two clicks for laboratory-result retrieval with AI Assistant. Narrow usability example; no measured 75% time or workload reduction.
Clinical-data completeness rose from 68% to 98% The earlier interview attributes this to TrakCare. Do not relabel it an IntelliCare AI effect; denominator and audit method are absent.
Seven hospitals in 18 months after first go-live Earlier TrakCare deployment pace. Deployment speed is not an IntelliCare clinical benefit.
More than 700 clinicians supported November 2025 vendor adoption claim. No active-use denominator, feature breakdown or measurement period.
AI-adoption pilot research Parent group reports a study involving GPs and specialists. No published protocol, sample, results or independent analysis in the disclosure.
Grha Kedoya EMRAM Stage 6 External digital-maturity assessment reported by HIMSS Media. Does not estimate IntelliCare's incremental AI effect.

Independent Evaluation Boundary

No qualifying independent EMC IntelliCare clinical, safety or productivity evaluation was found in the bounded 9 September search. Customer interviews, vendor releases, press republications and partner-award coverage remain attributed evidence. A study needs methods and results; the existence of a pilot or a maturity assessment does not supply those results.

Searches covered English and Indonesian outcome/evaluation terms, PubMed/PMC, Ministry of Health and indexed research material, customer/group disclosures and original reporting. The Research Log records the scope and exclusions. This is a search limit, not proof that no study exists. Requests for pilot methods, denominators, review/correction time and clinically significant errors remain in the existing Evidence Validation Queue.

Evidence Status

Confidence is high for dated primary-source statements and customer-reported EMC implementation; independent incremental AI benefit remains unestablished. The Middle East sources confirm agreements rather than completed go-live. Regulatory scope, enabled AI functions, customer-specific safety/data flows and independently measured outcomes remain distinct. No named UK IntelliCare deployment was established by these checks (SRC-007, SRC-299, SRC-337 to SRC-340).

Follow-up Evidence

  • Named Medcare and King's Jeddah live sites, go-live dates, enabled features and clinical operating scope.
  • RedSalud implementation evidence and EMC/EMTEK pilot protocol/results with site, version, participant/task denominators, comparator, review/correction time, errors, follow-up and evaluator independence.
  • Certificate/intended-use and release/module scope, applicable market evidence, clinical safety, AI governance and data flows.