UTSW · VitalSign⁶
UT Southwestern needed VitalSign⁶ to run as a fully SMART on FHIR application. We worked directly with their team and delivered the first version in time for a major public demonstration.
Consulting
Bring us the project.
We get it to production.
New builds, rescues, and AI implementation for healthcare organizations. Scoped by the engineers who do the work, led by our founder.
When teams call us
The build that stalled
The demo went fine. Production keeps slipping, and the reasons keep changing.
The product that doesn’t exist yet
You need clinical software built right the first time, on a foundation that survives real patient data.
The AI mandate
You need working software and a sensible place to start.
The integration that won’t hold
Your product has to live inside the EMR and the systems your customers already run.
What we take on
Custom Development
Book a call →Most clinical software fails at the data layer, so that is where we start. We design the foundation first, then build the product on top of it, a small senior team working from architecture to production. You get working software, live in your environment, with documentation your team can run with.
Project Rescue
Book a call →A stalled project burns budget every month it slips. We step in, find what is actually breaking, and fix that first, whether it is code, architecture, or scope. You get a project that moves again, and a date you can stand behind.
AI Implementation
Book a call →We help you find where AI actually fits your operation, then build it into the systems your team already uses. You get a working implementation on your own data, and a team that knows how to run it.
How engagements work
- 01
Book a call
Thirty minutes with Steve. Bring the project, the history, and the parts that worry you.
- 02
Get a plan
If it is a fit, you get a written scope: one outcome, one metric, one date.
- 03
We build
A small senior team, working with yours, until the software is live.
The smallest way to start
The Production Readiness Review is an assessment of your build. We find what is blocking it and hand you a plan with a date, whether or not you hire us to execute it.
Book a call
Work we can point to
National diagnostics platform
For a prominent diagnostics company, we set the FHIR strategy, staffed the first engineering team, and did the hands-on development for a platform that now runs in more than 2,000 clinics across seven EMRs.
Questions we get
Who actually writes the code?
Our own engineers. Everyone on your project is a senior engineer employed by Helios Software, and Steve leads the work himself. We don’t subcontract it or hand it off.
Will you sign a BAA and work with PHI?
Yes. We sign BAAs and work directly with PHI. Almost every project we take on involves patient data, so it’s routine for us.
Can you take over a codebase another vendor wrote?
Yes. We start by finding out what the code actually does and where it breaks. Some projects are best fixed in place, and some need parts rebuilt. We tell you which, and why, before we change anything.
Who owns the code, and what happens when you leave?
You own everything we write. We hand it over continuously, not in a box at the end, so your team has it the whole way through. You don’t have to use the Helios FHIR Server either. We know FHIR well beyond our own product, including the pros and cons of the other FHIR-based options, and we recommend what fits your situation.
How do you price work?
Most engagements are time and materials. Before we start, we agree in writing on what we’re building, how we’ll know it works, and when it should be done.
What we put into production, we answer for.
We take a small number of engagements at a time. Thirty minutes with Steve will tell you whether we can help.
Book a call