Caché and Ensemble moved to IRIS before maintenance runs out.
We migrate Caché and Ensemble to InterSystems IRIS, upgrade IRIS and HealthShare, build HL7 and FHIR interfaces in Health Connect, and staff InterSystems developers who hold current certifications.
Cohash works on InterSystems IRIS, IRIS for Health and HealthShare.
We migrate Caché and Ensemble to IRIS ahead of 31 March 2027, after which InterSystems plans no more maintenance releases for them. We also help pick between Extended Maintenance and Continuous Delivery releases, build HL7 and FHIR interfaces in Health Connect, deploy Unified Care Record and staff certified InterSystems developers.
you probably need this if
Caché or Ensemble still runs production and the March 2027 date is close.
Upgrades are skipped because nobody chose a release track.
Health Connect productions run interfaces nobody has documented.
ObjectScript, production and interface inventory with owners
Release track decision with upgrade calendar
Caché or Ensemble to IRIS migration runbook with rehearsal timings
+ 2 more documents
who does it
InterSystems ObjectScript developerHealth Connect interface engineer (HL7, FHIR)HealthShare Unified Care Record specialist
InterSystems IRIS Development Professional
InterSystems ObjectScript Specialist
25 Mar 2026IRIS 2026.1 (Extended Maintenance) 2026.1 is generally available for IRIS, IRIS for Health and HealthShare Health Connect, as an Extended Maintenance release. source ↗
22 Jul 2026IRIS 2026.2 (Continuous Delivery) Generally available for IRIS, IRIS for Health and Health Connect. 2026.2 is a Continuous Delivery release. source ↗
today · Oct 22, 2026
31 Mar 2027aheadCaché and Ensemble maintenance ends No more Caché or Ensemble maintenance releases are planned after this. An end date for product support hasn't been announced. source ↗
the story · intersystems iris & healthshare estate
From the first call to a setup your own team can run.
Here's what usually prompts a call about your InterSystems IRIS & HealthShare estate, what we do about it and in which order, and where you end up.
01 · where it hurts02 · what we change03 · how it runs04 · where you end up
incident board · intersystems iris & healthshare…3 open
openCaché or Ensemble still runs production and the March 2027 date is close.
recurringUpgrades are skipped because nobody chose a release track.
blockedHealth Connect productions run interfaces nobody has documented.
exposure
Caché and Ensemble to IRIS…IRIS and HealthShare upgradesInterface development in Health…Unified Care Record deploymentVector search and AI on IRISCertified staffing
EpicOH
startrehearsehandover
Code and production inventory
Release track and plan
Rehearsal
Cut-over and handover
we are here
ready to hand over
Interfaces run on IRIS with documentation, and the team is on a supported release track.
Clinicians see one record per patient, and new sources join on a documented matching…
ObjectScript, production and interface inventory with owners
Release track decision with upgrade calendar
chapter 01 · where it hurts
Why teams reach out
Caché or Ensemble still runs production and the March 2027 date is close.
Upgrades are skipped because nobody chose a release track.
Health Connect productions run interfaces nobody has documented.
chapter 02 · what we change
How we solve it
Caché and Ensemble to IRIS migration
IRIS and HealthShare upgrades
Interface development in Health Connect
Unified Care Record deployment
Vector search and AI on IRIS
Certified staffing
chapter 03 · how it runs
Our approach
Code and production inventory
Release track and plan
Rehearsal
Cut-over and handover
chapter 04 · where you end up
What changes
Interfaces run on IRIS with documentation, and the team is on a supported release track.
Clinicians see one record per patient, and new sources join on a documented matching pattern.
ObjectScript, production and interface inventory with owners
Release track decision with upgrade calendar
what we do
Our InterSystems IRIS & HealthShare work
6 kinds of InterSystems IRIS & HealthShare work, each run by engineers who have done it on live tenants.
An inventory of ObjectScript classes, productions, globals and integrations, a conversion plan and rehearsal on a copy of production before the switch.
Upgrade plans that pick Extended Maintenance or Continuous Delivery releases on purpose, with regression testing of productions and interfaces.
HL7 v2, FHIR and X12 interfaces built as productions, with business rules, data transformations and alerting documented.
HealthShare Unified Care Record set up across sources, with patient identity matching, data feeds and consumer access planned per organization.
Embeddings stored next to the source records in IRIS, with access rules kept on the source tables and retrieval tested against real questions.
ObjectScript developers, interface engineers and HealthShare specialists, onsite in the US or from nearshore and offshore teams across time zones, within your data access rules.
capability 01 / 06in production
EpicOH
Caché and Ensemble to IRIS migration
An inventory of ObjectScript classes, productions, globals and integrations, a conversion plan and rehearsal on a copy of production before the switch.
ObjectScript developers, interface engineers and HealthShare specialists, onsite in the US or from nearshore and offshore teams across time zones, within your data access rules.
InterSystems IRIS & HealthShare situations we walk into
We pieced these together from InterSystems IRIS & HealthShare situations that come up a lot. They're patterns. You won't find a specific client in them.
case file 01
Ensemble running a hospital's interfaces with March 2027 approaching
composite · not a client story
Beforethe situation
Ensemble runs most of a hospital's HL7 interfaces. Productions were built by staff who have since left, and maintenance releases stop after 31 March 2027.
What we dothe work
We inventory every production, business rule and transformation and write down what each interface actually does. Then we rehearse the move to IRIS for Health on a copy of production and regression-test the interfaces against recorded messages.
Afterwhere you end up
Interfaces run on IRIS with documentation, and the team is on a supported release track.
case file 02
Unified Care Record stuck on patient matching
composite · not a client story
Beforethe situation
A regional network is rolling out HealthShare Unified Care Record across several organizations. Patients are showing up twice, because every source formats identifiers its own way.
What we dothe work
We profile identifiers per source, agree normalization rules with each organization and tune matching in a test environment with real duplicate cases. Data feeds are corrected at source where possible.
Afterwhere you end up
Clinicians see one record per patient, and new sources join on a documented matching pattern.
How a InterSystems IRIS & HealthShare engagement runs
We don't start a step until the last one has produced something you can check.
step 01
Code and production inventory
We list ObjectScript classes, productions, business rules, transformations and integrations. Then we track down who owns each one and whether anybody still uses it.
step 02
Release track and plan
You pick Extended Maintenance or Continuous Delivery with us, and we write the migration or upgrade plan around it.
step 03
Rehearsal
The conversion or upgrade runs on a copy of production first. Interfaces get regression-tested there, and the timings set the cut-over window.
step 04
Cut-over and handover
We stay through cut-over and watch the productions afterwards. When we leave, the interfaces are documented and the runbooks are in your hands.
ai on intersystems iris & healthshare
Where AI fits on InterSystems IRIS & HealthShare, and where it needs guardrails.
InterSystems puts AI into the data platform itself. Vector search is part of the core engine. IRIS AI Hub, embedded in IRIS and IRIS for Health, is meant for building and deploying agents and governing them. IntelliCare, on the EHR side, has generative AI built in. For us the practical part is that retrieval data can stay inside IRIS instead of being copied to a separate vector store.
AI agentasks for data or an action
Scoped identityonly the access it needs
MCP serverthe one door into the platform
Logged, approveda person signs off on writes
InterSystems IRIS & HealthSharedoes the work
InterSystems doesn't currently offer a supported MCP server. A community IRIS MCP Server Suite is on Open Exchange. It's pre-release, and InterSystems doesn't support it. In production we'd have agents use IRIS REST or FHIR endpoints, with a dedicated user and minimal roles, audit logging, and approval for writes.
Vector search in IRIS
IRIS works as a vector database, so embeddings sit right next to the clinical or operational data they describe. For us the design work is which records get embedded. Access rules stay on the source tables, and we test retrieval against real questions.
IRIS AI Hub for agents
InterSystems describes AI Hub as a set of capabilities for building, deploying and governing AI agents and agentic workflows, embedded in IRIS and IRIS for Health. For us, what your version and licence include gets confirmed before we design around it.
InterSystems IntelliCare
IntelliCare is InterSystems' EHR, with generative AI at its core. If you're evaluating it, for us the work is integration with your existing HealthShare and IRIS interfaces, and how clinicians review AI output.
AI around HealthShare interfaces
AI can document old production classes and data transformations, explain HL7 and FHIR mappings and draft tests for interface changes. For us, engineers check every change in a test namespace first.
Where IRIS and HealthShare sit between clinical systems
Health Connect productions carry HL7, FHIR and X12 messages between the EHRs and departmental systems. Unified Care Record pulls together a shared patient record. Data and vector embeddings for analytics and AI sit in IRIS.
What a InterSystems IRIS & HealthShare engagement leaves behind
These are working documents, written against your configuration, so your team can run them without us.
inventory01
ObjectScript, production and interface inventory with owners
yours to keep
plan02
Release track decision with upgrade calendar
yours to keep
runbook03
Caché or Ensemble to IRIS migration runbook with rehearsal timings
yours to keep
tests04
Interface regression pack for Health Connect productions
yours to keep
plan05
Unified Care Record source and patient matching plan
yours to keep
talent and delivery · intersystems iris & healthshare
Certified engineers, wherever you need them.
Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.
Put these to anyone bidding on your InterSystems IRIS & HealthShare work. The ones who've done it answer differently from the ones who've read about it.
Q1
How many Caché or Ensemble instances do we run, and what runs on each?
Maintenance releases stop after 31 March 2027. The inventory sets the migration plan.
Q2
Should we follow Extended Maintenance or Continuous Delivery releases?
The choice sets how often you upgrade and test. Teams that pick by default end up skipping upgrades.
Q3
How will interfaces be regression-tested during the move to IRIS?
Recorded production messages replayed against the new instance catch transformation breaks early.
Q4
Which InterSystems certification does each engineer hold, and is it current?
InterSystems retires exams. A certification under a retired name may not match the current product.
Q5
How will patient matching be tuned for Unified Care Record?
Duplicate patients undermine a shared record. Matching rules need real duplicate cases from your sources.
01When does Caché maintenance end?
InterSystems has said no Caché or Ensemble maintenance releases are planned after 31 March 2027. It hasn't given an end date for product support. Without maintenance releases there are no fixes, though, and most organizations plan to be on IRIS before then.
02Should we follow Extended Maintenance or Continuous Delivery releases?
It comes down to how often you can test and upgrade. If you upgrade less often, Extended Maintenance releases like 2026.1 suit you. Continuous Delivery releases like 2026.2 get you features sooner, but you'll upgrade more often.
03How long does a Caché to IRIS migration take?
It depends on code volume, how many productions and interfaces you run, and how much downtime you can take. We size it after an inventory and a rehearsal on a copy of production.
04Which InterSystems certifications do your engineers hold?
InterSystems publishes its exams. They include InterSystems IRIS Development Professional and InterSystems ObjectScript Specialist, plus HealthShare Unified Care Record Deployment Specialist and InterSystems EHR Integration Specialist. We match each engineer's certification to the work.
05Do you also work on Epic or Oracle Health?
Yes. HealthShare and Health Connect often run next to Epic or Oracle Health. Both of those have their own pages here.
services
Related services
Projects on InterSystems IRIS & HealthShare usually end up touching one of these, so they're worth a look.
Reviewed by the Cohash teamInterSystems IRIS & HealthShare is a trademark of its owner, used here to identify the platform.how we handle facts and data →
next step
Tell us what you're running. We'll tell you what we'd do first.
A 30-minute working session with a senior engineer. No slides.
