Requires validation Security & trust How Sift intends to protect access to sensitive health information.
Sift’s intended integration uses patient authorization and OAuth-based access tokens rather than collecting healthcare-organization passwords directly.
Access should be constrained by granted scopes, patient context, and source API availability. Caregiver access requires explicit authorization and enforceable separation between the acting person and patient record owner.
Important [REQUIRED] Verify authentication methods, session lifetime, account recovery, multifactor options, access revocation, and administrative access controls.
Important [REQUIRED] Verify encryption, key management, environment isolation, logging, backup, vulnerability management, and hosting practices. No certification or independent audit is claimed.
Important [REQUIRED] Verify audit events, monitoring, incident response, notification procedures, and an operational security-reporting contact.
Documentation home Get help →