Patient trust · Malaysia pilot

Care is personal.
Access should be deliberate.

SANQO is designed to connect care without making patient records public. Identity, clinic membership and sharing permissions determine who can see a record.

Verified patient and guardian access

Signing in does not automatically connect records. A participating clinic verifies the patient’s identity or a parent, guardian or caregiver’s authority before granting access. Delegated access is reviewed and can be revoked.

Sharing with clear limits

Patients or verified representatives choose the recipient clinic, record categories and duration. Revocation stops future access through that permission; it cannot recall copies or override a clinic’s record-retention obligations.

Private workspaces

Clinical records require authenticated access and server-side authorization. The PWA does not cache patient API responses or clinical pages for offline use. Reconnect to load current records.

Clinical oversight

AI assistance supports the workflow. Licensed clinicians remain responsible for clinical decisions. Clinical information must be kept separate from public content and marketing automation.

Before live pilot onboarding

Production readiness includes verifying hosting and processing locations, encryption for connections, storage and backups, managed key access, staff multifactor authentication, audit protection, recovery testing and independent security review. These controls require deployment verification; this page does not claim certification or completion of that review.

SANQO’s January–June 2027 pilot is being prepared with Malaysian privacy requirements in view. Privacy notices, processing arrangements and retention policies must reflect the participating clinics and deployed services.