Services
Integration work, from one interface to a full audit
Four kinds of work, all done in-house. Healthcare data integration is the core of it. The rest comes from the same skill: getting systems to agree on what the data means.
What we offer
Each service lists who it usually fits. If your situation sits between two of them, that's normal.
Therapy, behavioral health, and ambulatory practices
Healthcare integration for small practices
Plenty of small-practice EHRs can send HL7 v2 or FHIR but have never been connected to anything. We set up the interfaces to your referrers, your clearinghouse, and your regional HIE. After go-live we watch them, because interfaces tend to break quietly when a vendor changes a field.
Hospitals, HIEs, and vendors running HealthShare or IRIS
InterSystems development
We build and maintain interfaces on InterSystems IRIS and HealthShare: new business services and operations, DTLs, routing rules, and the ObjectScript around them. We can work inside your team's conventions or take a backlog of interface requests off their plate.
Organizations running legacy or COBOL systems
Technical audits and modernization
When a critical system is old and lightly documented, we start by reading it: the code, the batch jobs, the data flows, and the interfaces around it. You get written findings and a roadmap ranked by risk and effort. The report is yours to act on with us or with any other team.
Any team re-keying data between systems
Systems integration and automation
Not every problem is clinical. We connect business systems through APIs, file transfers, and scheduled jobs, and retire the spreadsheet export someone runs by hand every Friday. Ongoing support is available so each integration has an owner after launch.
Small practices
How the small-practice plan works
A practice shouldn't need an IT department to keep its interfaces working. The plan has two parts.
Setup
A one-time setup fee covers mapping your EHR's data, building each connection, testing it with your partners, and taking it live.
Annual support plan
After go-live, the plan covers monitoring, fixes when a partner or vendor changes something on their end, and small changes as you add connections.
The cost depends on how many connections you need and what your EHR supports. We quote it after the first call, once we know what's involved.
Process
How an engagement runs
Four steps, the same for a single interface or a larger project.
A short call
You describe the problem and the systems involved. We ask questions until we can explain it back to you.
A written scope
We send a short document covering what we'll build, what we won't, what we need from you or your vendors, and the cost.
Build and test
We work against test data first and show you real messages or files moving before anything touches production.
Handoff and support
You get written notes on what was built and how to check it. If you want someone watching it afterward, that's the support plan.
Have a system that won't cooperate?
Send us a short note about what you're working with. We'll reply within a business day.