Site
- A self-contained set of processes and their configuration
- Often split by environment or by system group
- Its own network configuration file
- Promoted from test to production as a unit
Integrations / Infor Cloverleaf
Infor Cloverleaf Integration Services
Hundreds of threads, Tcl procs written by people who left years ago, and a new lab system going live next quarter. Agnotic Technologies builds and changes interfaces inside your Infor Cloverleaf estate, documents what is already there, and keeps it on a supported version.
Threads and routesXlate and Tcl workVersion upgradesEstate documentation
Trusted by global innovators
What do Infor Cloverleaf integration services cover?
Infor Cloverleaf integration services are the build, change and support work on an existing Cloverleaf engine: new threads and routes, Xlate translations and Tcl procedures for a new system, version upgrades, test to production promotion and documentation of the estate. Agnotic Technologies does this work inside your Cloverleaf sites, alongside your interface team.
Most hospitals that run Cloverleaf are not looking to replace it. They need more hands for a backlog of feeds, and a clear picture of logic that only lives in code. If you have decided to move to another engine, our interface engine migration page covers that path.
Cloverleaf's model
How does Cloverleaf's model map to interface work?
Every change request lands on one or more of these parts. Knowing which one keeps a small change small.
Process and thread
- A process runs a group of threads
- Each thread is one connection to one system
- Inbound or outbound, with its own protocol settings
- Restarted or cycled after changes
Route
- Sends messages from an inbound thread to destinations
- Can filter by message type or trigger event
- Names the Xlate applied on the way
- One inbound feed often fans out to several systems
Xlate and variants
- Xlate maps fields from source to target structure
- Variants describe each system's own message format
- Lookup tables translate local codes
- Most field-level change requests end here
Tcl procedures
- Run at user points of control on threads and routes
- Handle filtering, splitting and logic an Xlate cannot
- Frequently the least documented part of an estate
- Reviewed and tested like any other code
Estate review checklist
What does a Cloverleaf estate review check?
We start most engagements with this review. It shows what you have, who owns it and where the risk sits before any change is made.
| Area | What we check | Why it matters |
|---|---|---|
| Sites and processes | How sites are split, which processes run where, and what each one serves | A clear layout lets one feed change without restarting unrelated ones |
| Thread inventory | Every thread with its system, direction, protocol and a named owner | Threads with no owner are the ones nobody notices when they stop |
| Xlates and Tcl procs | Which translations and procedures have no documentation or tests | Undocumented logic is the largest risk in any upgrade or system change |
| Lookup tables | Code tables, who updates them and when they were last changed | Stale tables cause wrong codes that pass every technical check |
| Alerting | Which threads raise alerts, to whom, and on what condition | Many estates alert on errors but not on a feed going quiet |
| Version and support status | The running release against Infor's support position for it | An unsupported version limits fixes and security updates |
| Test site parity | Whether test sites match production configuration and files | Changes tested on a different setup can fail on go-live |
The output is a written inventory and a ranked list of risks, which your team keeps whether or not we do further work.
What Cloverleaf work do teams bring to us?
Scoped one change at a time, or as a backlog worked through with your interface team.
New feeds
Inbound and outbound threads, routes and Xlates for a new lab, radiology, pharmacy or device system.
Xlate changes for a new system
Remapping fields and code tables when the EHR or a downstream system is replaced.
Tcl procedure fixes and rewrites
Reading old procs, adding tests, and replacing fragile logic with documented code.
Version upgrades
Moving the estate to a supported Cloverleaf release with side-by-side output comparison.
Test to production promotion
A repeatable way to move changed sites and files, with a record of what changed.
Certificates and connections
Expiring certificates, new endpoints and network changes handled before they stop a feed.
Decision
Should you keep, upgrade or move off Cloverleaf?
The answer depends on support status and your team, not on the engine's age.
01
Keep and document
Example: Supported version, a team that knows it, a backlog of feeds
Approach: Estate review, documentation of undocumented logic and extra capacity for the backlog.
02
Upgrade in place
Example: A version approaching or past the end of its support, with feeds working well
Approach: Side-by-side upgrade with output comparison, site by site.
03
Plan a move
Example: Your organization has chosen another engine for licence, skills or platform reasons
Approach: The estate review becomes the migration inventory; the move itself follows our engine migration method.
Upgrades
How is a Cloverleaf version upgrade run without breaking feeds?
An upgrade changes the engine under every interface at once, so we prove each feed's output before switching it.
Inventory and freeze list
All sites, threads, Xlates and procs listed, with changes paused or tracked during the upgrade.
Stand up the new version in test
The new release installed beside the current one, with the estate copied across.
Replay and compare
Captured production messages run through both versions, and the outputs compared field by field.
Fix the differences
Tcl procs and Xlates that behave differently on the new release corrected and retested.
Cut over site by site
Each site moved in its own window, with the previous version kept ready for rollback.
Hand-over
How do you hand the estate back to your team?
The goal is an estate your own engineers can run, not one that depends on us.
Documentation per thread
Purpose, systems, message types, Xlate and procs for every thread we touch.
Reviewed Tcl
Procs read, commented and tested, with changes made through your version control.
Runbooks
What to check when a thread stops, errors or slows, written for your on-call staff.
Pairing sessions
Your engineers work alongside ours on real changes before we step back.
Who it is for
Who uses our Cloverleaf services?
Teams that run Cloverleaf today and want it well understood.
Hospital interface teams
A backlog of new feeds and changes, and not enough people to clear it.
Health systems after a merger
Several Cloverleaf estates, or one estate serving newly joined sites.
Teams replacing an EHR or lab system
Xlates and routes remapped to the new system without touching unrelated feeds.
Teams that lost key engineers
Logic that only one person understood, now needing documentation.
IT leaders planning an upgrade
A supported version reached with evidence that every feed still works.
Compliance-First Healthcare App Development Services Backed by Global Standards
01
HIPAA
Health Insurance Portability and Accountability Act
Protect PHI with privacy-first architecture, encrypted storage and transmission, strict access controls, and traceable audit logs.
02
GDPR
General Data Protection Regulation
Implement lawful consent flows, data minimization, retention controls, and secure processing for sensitive health data.
03
FHIR
Fast Healthcare Interoperability Resources
Enable standardized health data exchange across apps, care teams, and systems through standards-based FHIR APIs.
04
HL7
Health Level Seven International
Support enterprise-grade interoperability with HL7-based integrations for records, events, and clinical messaging workflows.
05
HITRUST
Health Information Trust Alliance
Align security programs to healthcare-specific control and risk management practices trusted by providers and ecosystem partners.
06
HITECH
Health Information Technology for Economic and Clinical Health Act
Design with breach notification readiness, digital record safeguards, and operational controls that support regulated care programs.
07
SaMD
FDA Software as a Medical Device
Plan software quality, traceability, and documentation pathways for products that may require SaMD review and submission.
08
MDR (EU)
Medical Device Regulation (European Union)
Prepare EU market-ready processes for risk classification, evidence tracking, and lifecycle governance under MDR expectations.
09
SAMHSA
Substance Abuse and Mental Health Services Administration
Apply confidentiality controls and consent-aware sharing models for behavioral and mental health data experiences.
Facts and sources
Which sources shape Cloverleaf work?
Short facts the work is designed around, each linked to its primary source.
Infor describes Cloverleaf as a healthcare integration engine that standardizes and transforms HL7 v2, FHIR, CDA and X12 data, and that can run in the cloud, on premises or in a hybrid setup using Docker containers.
Source: Infor, Infor Cloverleaf product pageHL7 describes Version 2 as a messaging standard designed to support a central patient care system as well as a distributed environment where data resides in departmental systems, and as generally backward compatible.
Source: HL7 International, HL7 Version 2 Product SuiteThe HIPAA Security Rule requires hardware, software or procedural mechanisms that record and examine activity in information systems that contain or use ePHI.
Source: 45 CFR 164.312(b) (eCFR)The HIPAA Security Rule requires technical security measures that guard against unauthorized access to ePHI being transmitted over an electronic communications network.
Source: 45 CFR 164.312(e)(1) (eCFR)
How we work
How does a Cloverleaf engagement start?
Three stages, starting with the estate as it is.
1.
Scoping call
We hear about your sites, current backlog and the change that is most urgent.
Backlog
2.
Estate review
The checklist above, run against your sites, with a ranked list of risks and quick fixes.
Fixed scope
3.
Build, upgrade and hand over
Feeds, Xlate and Tcl changes or an upgrade, then documentation and pairing with your team.
Ongoing
Frequently Asked Questions
Yes. We work in your test sites through your change process, and changes reach production the way your team already promotes them. We do not need a parallel engine.
Yes. We read each proc, write down what it does, add test messages that prove the behavior, then fix or simplify it. The documentation stays with your team.
Field mapping and code translation belong in Xlates, where they are easier to read and change. Filtering, splitting and logic that depends on several messages fit Tcl better. We keep that split consistent across the estate.
Captured messages from the feed are run through the changed thread in test, and the output is compared with the expected result for the receiving system before the change is promoted.
The number of threads involved, how much undocumented Tcl sits behind them, whether test sites match production and how many receiving systems must sign off. We size each change or backlog on the scoping call.
This page makes no partner claim. Agnotic Technologies is a software development services company that works on the Cloverleaf licence you already hold. Licences and product support come from Infor.
AI tools may help an engineer explain an old Tcl proc or draft test messages from synthetic data. A person checks every change, and production messages with PHI never leave your environment.