Software and systems consulting
Healthcare systems that actually exchange data
We connect EHRs to referral partners, clearinghouses, and health information exchanges for small practices, and take on InterSystems and general software work for larger teams. Based in Columbia, SC.
Registration feed
Running
Inbound · HL7 v2 from the EHR
MSH|^~\&|PRACTICE_EHR|CLINIC|HIE|SC|ADT^A04PID|1||48213^^^MRN||DOE^JANE||19840512|FPV1|1|O|THERAPY^^^CLINIC
Mapped and validated
Outbound · FHIR R4
{ "resourceType": "Patient", "name": [{ "family": "Doe", "given": ["Jane"] }], "birthDate": "1984-05-12"}
Health information exchange
ACK AA
Billing clearinghouse
ACK AA
Referral partner
ACK AA
Works with
- HL7 v2
- FHIR
- InterSystems IRIS
- HealthShare
- ObjectScript
- EHR exports
- Claims files
- REST APIs
- SFTP
- COBOL
Approach
Start with what you already have
Most integration problems come from systems that were never meant to talk to each other. Here's how we handle the three we see most.
Small-practice EHR integration
We start with the messages and files your EHR already produces instead of selling you a new platform. Most small practices need a few dependable connections, and that's what we build.
InterSystems work
We work inside your existing productions and naming conventions so your team can maintain what we build. Each interface ships with notes on what it does and how to test it.
Audits and modernization
Before recommending a rewrite, we find out what the old system does that nobody wrote down. The roadmap separates what has to change now from what can wait.
Services
What we work on
Healthcare integration is the main focus. General software and systems work is a real second offering, not an afterthought.
Therapy, behavioral health, and ambulatory practices
Healthcare integration for small practices
We connect your EHR to referral sources, your billing service or clearinghouse, and your health information exchange, then keep those connections running.
Hospitals, HIEs, and vendors running HealthShare or IRIS
InterSystems development
Productions, routing rules, data transformations, and ObjectScript on InterSystems HealthShare and IRIS.
Organizations running legacy or COBOL systems
Technical audits and modernization
A written review of an aging system and a prioritized roadmap for what to change first. Implementation is optional.
Any team re-keying data between systems
Systems integration and automation
Scheduled, monitored jobs and API connections that replace manual exports and copy-and-paste between systems.
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.