FAQ
Questions we hear before a first call
Compliance, the systems we work with, how pricing is structured, and what happens after go-live. If your question isn't here, send it over.
Healthcare data and compliance
How do you handle protected health information (PHI)?
We keep PHI where it already lives. Whenever possible, we work inside your environment using access you grant and can revoke, instead of copying data to our own systems. Development and testing use de-identified or synthetic data, like the sample messages on our home page. When real records are needed to troubleshoot an interface, we look at the minimum necessary, never store it in email or on personal devices, and give up our access when the work ends.
Can I send patient details through the contact form?
Please don't. The form is for describing the project. If the work needs access to PHI, we set that up under a written agreement once we're working together.
Working together
Do you work remotely?
Yes. We're based in Columbia, South Carolina, and work remotely with clients across the United States.
What counts as a small practice?
Therapy, behavioral health, and ambulatory practices that need their EHR connected to referral partners, a clearinghouse, or a health information exchange, and don't have an integration team of their own.
Do you only work in healthcare?
No. Healthcare data integration is the main focus, but we also take on general software architecture, systems integration, and automation work outside healthcare.
What do you need from us to get started?
A short description of the problem, the systems involved, and who your vendor contacts are. If you have a test environment or sample files, that helps, but it isn't required for the first call.
Pricing and support
How is pricing structured?
Small-practice integrations have a one-time setup fee and an annual support plan. Other work is scoped and quoted individually. We don't publish prices because the cost depends on how many connections you need and what your systems support.
Am I committing to anything by reaching out?
No. The first call is for understanding the problem and deciding whether we're a fit. If it isn't, we'll say so and point you somewhere better if we can.
What happens after go-live?
You get written notes on what was built and how to check it. If you want ongoing monitoring and fixes when a partner or vendor changes something, that's covered by the annual support plan.
Can you work on old or COBOL-based systems?
Yes. Technical audits of aging systems, including legacy and COBOL environments, are one of our services. You get written findings and a prioritized roadmap, and implementation is optional.
Do you work with InterSystems HealthShare and IRIS?
Yes. We build and maintain productions, routing rules, data transformations, and ObjectScript on InterSystems IRIS and HealthShare.
Have a question that isn't here?
Send it over. We'll reply within a business day.