TruClinic

TruClinic

TruClinic emerged from Salt Lake City’s quiet but persistent health-IT cluster, co-founded by Justin Kahn to address the infrastructure gap between patients and providers. The company developed a cloud-based telehealth platform supporting both real-time video consultations and store-and-forward messaging, deployed primarily across US hospital networks and specialty practices. Its customer base skewed toward mid-sized health systems seeking a compliant, embeddable virtual-care module rather than a standalone consumer app. The platform covered primary care, specialty consults, and behavioral health workflows, integrating with existing electronic health record systems. Confirmed deployment contexts included rural health networks and accountable care organizations using TruClinic to extend specialist access without physical expansion. The company operated a B2B software-as-a-service model, licensing its technology per seat or per encounter rather than taking a percentage of clinical revenue — a structure that aligned it with enterprise procurement cycles rather than venture-scale consumer growth. Kahn led the company through the early telehealth regulatory patchwork, navigating state-by-state licensure rules and evolving reimbursement codes. The team remained lean by design, with engineering and client-success functions concentrated in Utah. TruClinic’s fate was sealed by the broader consolidation wave in telehealth: as larger platforms sought bolt-on capabilities for their existing hospital contracts, standalone vendors became acquisition targets. Intelichart acquired TruClinic to fold its virtual-care module into a broader patient-engagement suite (per public record). TruClinic’s structural differentiator was its vendor-to-provider posture. Unlike direct-to-consumer telehealth startups that marketed to patients and then recruited clinicians, TruClinic sold infrastructure to the institutions that already held the patient relationship. That enterprise-sales motion produced slower growth but deeper integration — each contract required HL7 interfacing, security reviews, and credentialing workflows that created switching costs. The company’s absorption into Intelichart reflects the category logic: standalone telehealth modules rarely survived independently once the EHR-adjacent platforms bundled virtual care as a feature rather than a separate product.