Minimal patient data
Appointment events are processed to send a request. Contact details are not stored with clinical identifiers, and clinical notes are never read.
Swarna Shivansh only needs to know that a visit happened, where and how to reach the patient. The rest of the design follows from that.
Appointment events are processed to send a request. Contact details are not stored with clinical identifiers, and clinical notes are never read.
Designed for TLS 1.3 in transit and AES 256 encryption at rest for customer data.
Customer reviews, replies and data are not used to train public models.
Role based permissions, multi factor authentication and SAML single sign on.
Every draft, edit, approval and publish is logged with who did it and when.
No public reply is published without a person your organization authorizes.
Related: subprocessors, data processing agreement and business associate agreement.