Specialised legacy platform
InterSystems IRIS (formerly Caché) underpins much of the NHS estate, large parts of US healthcare, and significant European deployments. ObjectScript expertise is increasingly scarce.
Vision sample · bundled with OpenLI HIE
Natural language is the only programming language enterprises need to modernise legacy systems.
IRIS CoPilot is the canonical demonstration of the OpenLI thesis. Engineers and clinical analysts modernise InterSystems IRIS productions, business hosts and ObjectScript code in plain English — generating, refactoring and migrating legacy code without ever opening Studio or VS Code.
IRIS CoPilot is bundled inside OpenLI HIE as a Claude Agent SDK skill set. It is the most concrete proof of the company-wide thesis that drives every product on the OpenLI family tree: tomorrow’s software is built and modernised in natural language, with enterprise-grade governance and quality.
Vision sample
Bundled with HIE v1.9.7
Claude Agent SDK skill set
InterSystems IRIS
THE OPENLI VISION
In tomorrow’s software, natural language is the development language.
Across every regulated industry — healthcare, finance, pharma, banking, taxation — the same problem repeats: critical systems are built on legacy code that fewer and fewer engineers can read, let alone safely modify. The cost of maintaining them rises every year. The risk of touching them keeps growing. The talent pool keeps shrinking.
OpenLI’s thesis is simple: natural language replaces code as the development surface for legacy systems. Engineers describe the change they need; the agentic runtime generates, refactors, tests and deploys the underlying code — under human approval, with full audit trails and one-command rollback. The legacy code becomes an implementation detail. The development experience becomes a conversation.
IRIS CoPilot proves it. InterSystems IRIS — a deeply specialised legacy platform with a small expert pool and high clinical-safety stakes — becomes accessible to anyone who can describe what they want in English.
Why InterSystems IRIS?
IRIS is the canonical example because it is hard. ObjectScript is unfamiliar to most modern developers. Productions and business hosts have a steep learning curve. Documentation is scattered. Clinical-safety expectations are high. The talent pool is thinning. If natural language can modernise IRIS — with audit and governance that satisfies an NHS Trust — it can modernise anything.
High stakes, high cost
IRIS systems carry clinical workloads. Mistakes carry patient-safety risk. Specialist contractors are expensive. Routine changes get deferred. Technical debt accumulates.
The exact problem we solve
Natural-language modernisation, with enterprise governance, is the only way out at scale. IRIS CoPilot is the first proof. Other legacy platforms (Mumps, COBOL, MUMPS, classic ASP, Caché) come next.
What IRIS CoPilot does today
IRIS CoPilot ships as a Claude Agent SDK skill set bundled inside OpenLI HIE v1.9.7. The capabilities below are in production today.
Plain-English ObjectScript
Describe what you want in English; IRIS CoPilot drafts the ObjectScript class, the method signature, the SQL query or the storage definition. Reviewable as a diff before anything is applied.
Production & business host editing
Add, modify or remove business services, processes and operations from a natural-language description. The agent understands the production XML schema and generates valid configuration.
Refactoring & modernisation
Refactor legacy ObjectScript into modern style. Migrate from older Caché idioms to current IRIS patterns. Generate test fixtures alongside the refactor so you can verify it.
Code review and explanation
Read existing ObjectScript code and explain it in plain English. Generate documentation. Identify areas of clinical-safety concern. Surface deprecated patterns.
HL7 & FHIR mapping in IRIS
Author HL7 v2 and FHIR mappings using IRIS’s native interoperability features, all from natural language. The same skill set powers OpenLI HIE’s integration authoring.
Same governance as HIE
RBAC, audit trails, approval workflows, PII sanitisation hooks — all inherited from OpenLI HIE and the OpenLI Codex foundation. No separate review process.
How it works
1. Describe the change
"Add a new business operation that posts inbound HL7 ADT messages to the EPR REST API, with retry logic and dead-letter handling."
2. Review the draft
IRIS CoPilot generates the production XML, the ObjectScript class and the test fixtures. Everything is presented as a reviewable diff in the operator portal.
3. Approve, deploy, audit
On approval, the change applies via HIE’s hot-reload mechanism. A snapshot is created for one-command rollback. The audit trail records every step.
The bigger picture
IRIS CoPilot is the first OpenLI demonstration of natural-language modernisation for a specialised legacy platform. The same approach extends to:
Other healthcare integration engines
Orion Health Rhapsody and NextGen Mirth Connect modernisation use the same pattern, surfaced through OpenLI Integrai for full-engine migration projects.
Other regulated legacy stacks
The next CoPilot-style products will target equally specialised legacy stacks in finance, pharma and banking. Each becomes accessible via natural language with the same governance posture.
The same foundation
Every CoPilot variant is built on the same OpenLI Codex foundation. One AI-substrate strategy, one audit framework, one operational model across the entire portfolio.
FOUNDATION
Built on OpenLI Codex
IRIS CoPilot is a Claude Agent SDK skill set inside OpenLI HIE. The dual-runner architecture, the prompt template library, the workspace registry and the audit trail all come from the OpenLI Codex foundation.
See the vision in production
IRIS CoPilot ships today inside OpenLI HIE v1.9.7. Open the HIE portal to see it in action, or view the source on GitHub.