Hawva Health

Security & privacy

Principles we can show you, not certifications we cannot.

This page describes how Hawva is built. It claims no certification, accreditation, or regulatory status, because Hawva holds none.

Architectural principles

  • Authenticated staff access

    Every staff surface requires an authenticated session. No anonymous access, no shared open door.

  • Organization-scoped permissions

    A person acts within an organization they belong to, and the server decides what they can see — not the screen.

  • Explicit roles

    Entering a result and releasing it are separate authorities. So are ordering and reviewing. Roles are granted, never implied by being logged in.

  • Auditability

    The network records what happened, in sequence, under whose authority. Corrections create new versions rather than overwriting what a clinician acted on.

  • Order-scoped patient access

    A patient link authorizes exactly one order. It is not an account, it does not accumulate a history, and the issuing clinic can revoke it.

  • A deliberately limited data boundary

    A laboratory receives the patient detail the work requires, not a general record. This is not meant to become a lifelong medical record.

  • No patient data to third-party AI services

    Patient data is never sent to a third-party AI or machine-learning service. This is a standing product rule, not a configuration option.

Access follows the organization and the order, not the network.
  1. Staff sign in to an organization

    An account belongs to a facility and to a role within it.

  2. A clinic sees the orders it created

    Its own work, and the results released back against it.

  3. A laboratory sees the work sent to it

    What it was authorized to receive. Not a clinic's wider records.

  4. A patient sees one order

    From a link issued for that order.

Joining the network does not make one facility's patients visible to another.

Built for organizations, not silos

A shared network is not a shared filing cabinet.

A clinic sees the orders it placed. A laboratory sees the work assigned to it, and no more. Two clinics sending work to the same laboratory gain no view of each other.

A diagnostic network is not a lifelong medical record, and this is deliberately not designed to become one.

Clinics and laboratories on one network

Hawva Exchange

  • Clinic A Lab Central
  • Clinic B Lab Central
  • Clinic C Lab Horizon

No view between clinics

A laboratory can serve many clinics. The clinics remain separate organizations.

What we do not claim

Hawva is not certified, accredited or approved under any regulatory scheme. Where recognised standards inform the design, that is a design input, not a certification.

  • No regulatory certification or accreditation is claimed.
  • No compliance attestation is claimed.
  • No government approval is claimed.
  • Mentioning a standard is never a claim to be certified against it.

Reporting a security concern

Found a security problem? Write through the partner form and say so; we will reply with a direct channel. Please do not include patient or clinical information.

Contact us