Have you worked on HIPAA-regulated systems?+
Yes — extensively. Our healthcare engagements span clinical operations, telehealth, RPM, EHR integration, and revenue-cycle work. Every healthcare engagement is run under a BAA with the relevant subprocessor agreements in place. The case study we publish anonymously on this site (a Series B clinical platform's migration to three-region Kubernetes) is a representative engagement.
Do you do FHIR integration or just HL7 v2?+
Both, but we lead with FHIR R4 wherever the integration partner supports it. Most modern engagements end up as a FHIR-first integration with HL7 v2 fallbacks for legacy interfaces. We have built SMART on FHIR launch contexts, bidirectional ADT/ORU/SIU pipelines, and bulk-data flows. We do not pretend HL7 v2 is dead — most hospitals will still need it.
Can you help us pass SOC 2 Type II?+
We can build the technical environment and the operational evidence stream that makes Type II achievable, but the audit itself is between you and your auditor. Most clients arrive without SOC 2 and need it within 12–18 months to close enterprise deals — we work that into the engagement plan from day one.
Do you build SaMD (Software as a Medical Device)?+
We build software that may be regulated as SaMD, in collaboration with your regulatory consultant or in-house quality team. We are engineering specialists, not regulatory specialists — we will not represent ourselves as the latter. We have shipped under IEC 62304 and ISO 14971 lifecycles and work fluently with regulatory partners.
What does data residency look like in practice?+
Active-active multi-region architecture, with PHI routed to the customer's residency region by data classification. EU customer PHI never leaves the EU plane; US customer PHI never leaves the US plane. Cross-region writes only happen for non-PHI shared data and are async. This is one of the highest-impact design decisions for healthcare SaaS today and one of the most common deal-blockers when it is missing.
Will you sign a BAA?+
Yes — every healthcare engagement runs under a BAA, signed before the kickoff. We carry the subprocessor agreements with our infrastructure providers (AWS, GCP, etc.) so the BAA chain is unbroken from your platform down to the hosting layer.