HealthBridge Africa

Compliance and security

The controls that protect health information on this platform, described at the level an evaluator needs and no further.

Last updated 20 August 2026

Tenant isolation, enforced by the database

Every request runs against the database under a role that cannot bypass row-level security. Access rules are enforced by the database itself rather than by application code alone, so a defect in a single screen cannot expose the records of another organisation.

The default is to deny: a record is invisible unless a rule explicitly grants access to the person asking for it.

Encryption of health information

Health information is encrypted in transit and at rest. The most sensitive fields are additionally encrypted individually, using keys held in a managed key vault that the application itself cannot export.

National identity numbers are never stored in readable form. They are held as irreversible cryptographic hashes, so a record can be matched without the number being recoverable.

Consent-gated sharing between organisations

A record created by one organisation is not visible to another simply because both use the platform. Cross-organisation access requires an active consent grant, scoped to a category of information and limited in time.

Emergency access exists for situations where waiting for consent would cause harm. It is deliberately narrow: it is time-boxed, it never disables the underlying access controls, and every use is recorded and reviewable.

A tamper-evident audit trail

Access to health information is recorded in an append-only log. Each entry carries a cryptographic hash of the entry before it, so removing or altering a historical entry breaks the chain and can be detected.

Those records are additionally mirrored to immutable storage that cannot be rewritten or deleted for the duration of its retention period.

Prescription integrity

Prescriptions are cryptographically signed when they are issued, using a key held in a managed key vault. A pharmacy verifies that signature before dispensing, so a prescription altered after issue does not verify.

Once signed, a prescription is sealed: its clinical content cannot be edited.

Data residency

Platform data is hosted in data centres in South Africa, with private networking between platform components rather than the public internet.

Who inside HealthBridge can see records

Platform administrators do not have standing access to patient records. Administrative roles are scoped to governance work such as organisation lifecycle, verification queues and audit review, and are separated from clinical information by the same database-enforced rules that separate organisations from each other.

Where a support engineer needs temporary access to investigate a problem, that access is granted explicitly, limited in time, recorded, and visible while it is active.

Reporting a security concern

If you believe you have found a vulnerability or a privacy problem, please tell us before disclosing it publicly and give us a reasonable opportunity to fix it.

  • Include enough detail for us to reproduce the issue
  • Do not access, modify or retain information about another person while testing
  • Do not run tests that degrade the service for other people

support@healthbridge.africa