Skip to content
halden

Compliance

Comply first. Then optimise.

Halden is built so the safe path is the only path: patient data stays inside a protected boundary, providers make every clinical call, and nothing is hidden from regulators or patients.

Principles

Rules built into the product, not a policy document.

Each of these is enforced by how the platform works, so it does not depend on anyone remembering it.

Software, not a clinic

Licensed providers make every clinical decision. Licensed pharmacies dispense. Halden does not practise medicine.

No path to approval but a provider

The workflow has no rule, timeout or admin override that can approve a prescription.

No templated medical necessity

Prescribers write their own reasons. The software never offers pre-selected rationales or defaults to a compounded product.

No charge before approval

Checkout only authorises the card. Capture happens after a provider approves.

Health data stays inside

Intake answers, conditions, medications and treatment names never reach an ad platform.

Your data is yours

Patients, subscriptions and prescription history are exportable, and card tokens live with your gateway.

The boundary

What never leaves the platform.

Ad platforms receive only allowlisted events from steps before any health question. Shipping trackers receive a carrier and a tracking number. Nothing else crosses.

  • Intake answers and medical history
  • Conditions, symptoms, weight and BMI
  • Medications, treatments, products and doses
  • Approval or eligibility outcomes
  • Patient lists for ad audiences
  • Health details in URLs, logs or error messages

Protection in layers

How patient data is protected.

Select a layer to see what it does. Each one holds even if another fails.

Layer 1

Tenant isolation

Each operator's data is walled off in the database itself.

  • Row-level security on every table that holds operator data
  • The application cannot bypass it; a missing scope returns nothing
  • Tested on every release by trying each query as the wrong operator

Where we are

Honest about what is done and what is next.

Halden is in build with its first design-partner operators. This is the current status, and we will keep it current.

Business associate agreements

From launch

Halden signs one with each operator, and uses only vendors that sign one for anything that touches patient data.

Independent audits

Planned

Audits such as SOC 2 are planned. We will publish their status when they are complete, not before.

Penetration testing

Before launch

An external test before the first operator goes live, then on a regular schedule.

Ad platform certification

In onboarding

Each operator brand needs its own LegitScript certification to run prescription ads. We help you through it.

Nothing on this page is legal advice. Your counsel should review how your brand uses the platform.

FAQ

Compliance questions.

Something else? Ask us directly.

Halden is built to HIPAA requirements: patient data only on infrastructure covered by a business associate agreement, encryption, audit logging and access control. Compliance also depends on how each operator runs their business, so we work through it with you and your counsel.

Build a brand regulators would be happy to look at.

We are working with a small group of design-partner operators. Tell us what you sell and where it hurts.