Does the public MVP contain PHI?
No. The public MVP uses synthetic patient records only. It is not connected to a live EHR and is not for clinical care.
Security and compliance posture
The hosted Closr MVP is intentionally synthetic so buyers can evaluate the workflow safely. A paid readiness pilot can start the same way. A production deployment that handles real patient data must run under health-system contracting, HIPAA-appropriate controls, and customer clinical governance.
No. The public MVP uses synthetic patient records only. It is not connected to a live EHR and is not for clinical care.
Yes. Closr's first pilot motion is a paid readiness engagement using synthetic records, aggregate workflow information, schema samples, and properly de-identified examples. It does not require EHR access or real patient identifiers.
Do not provide real names, MRNs, full dates of birth, addresses, phone numbers, emails, account numbers, record numbers, device identifiers, free-text notes about a real patient, or any EHR export tied to an identifiable person.
Yes. The real product is intended to use real health-system patient data from EHR, FHIR/Bulk FHIR, interface, data warehouse, or governed CSV sources under the health system's privacy and security controls.
A BAA-covered deployment, tenant-scoped authentication and authorization, encryption in transit and at rest, audit logs, PHI-safe logging, retention policy, access review process, and clinical governance for ruleset changes.
The MVP is positioned as human-in-the-loop clinical workflow software for screening adherence operations. It does not diagnose cancer, replace clinical judgment, or autonomously order care.
The MVP labels simplified or licensed-model stubs. Production calculator use requires model validation, license review, source citation, version pinning, and customer governance approval.