Effective date: [EFFECTIVE DATE]
Draft — under counsel review. This page is not yet in effect; the bracketed items are placeholders.
The HealthTech Builder platform and the applications built on it provide tools that run clinical and operational services: scheduling, tracking, pathways, checklists, forms, messaging, and policy operations. These tools organize, track, surface, and inform; they are designed so that licensed clinicians remain the decision-makers and can independently review the basis of anything a tool surfaces. They are not medical devices: they do not acquire or analyze medical images or signals, do not direct diagnosis or treatment, and must not be relied on in place of the professional judgment of a qualified clinician. Nothing in the platform or in any application built on it constitutes medical advice.
The platform ships security architecture and compliance documentation — control matrices, policy templates, evidence guides — as engineering and documentation aids. They are not legal advice, and using the platform does not by itself make any organization compliant with HIPAA, SOC 2, or any other law, regulation, or framework. Compliance is a property of an operating organization: its risk analysis, training, agreements, and practices. Consult your own counsel and compliance professionals.
By default, applications built on the platform are designed to persist no patient data — the customer's electronic health record system remains the system of record, and any exception is named, minimal, and approved by the customer on the record. This is a design posture, not an exemption: an application that displays patient information processes it, and organizations remain responsible for their own obligations regarding protected health information, including appropriate agreements. The platform's build surfaces are not intended to receive patient information — do not include patient-identifying details in build conversations, project descriptions, or decision notes.
The platform uses artificial-intelligence systems to assist in building applications and drafting content, including drafting operational rules from customer policy documents. AI output can be incomplete, outdated, or incorrect. The platform is designed so that consequential outputs take effect only after human review and approval, and those reviews are the responsibility of the people performing them. Draft rules cite their source documents so reviewers can check the AI's reading against the original.
Epic and other electronic-health-record, product, and company names referenced in the Service are trademarks of their respective owners. Their use is for identification only and does not imply any affiliation with, sponsorship by, or endorsement from those companies.
Features described in the Service, in sales materials, or in documentation may change, and statements about planned capabilities are not commitments. Your organization's written agreement with us governs what is committed. See also our Terms of Service and Privacy Policy.