Hypex

Security & data-handling evidence

Patient names never get kept, and you can prove it

Hypex receives PHI to do the work, as a Business Associate under HIPAA, and destroys it on a clock. What never happens: names and identifiers reaching the database, the model, or a stored letter. That is an architectural fact you can test, not a promise.

Names or IDs retained: 0Vault: 24h after sending, 400-day ceilingBreach notice deadline: 60 daysConformance checks: public

Names and identifiers stay out of the database

Direct patient identifiers never reach the Hypex database. They live in an encrypted vault and are destroyed within 24 hours of transmission to a payer, and always within 400 days of first receipt. What is retained is claim-level billing data: payer, codes, amounts, dates, the payer's own claim number, and the reason the payer gave. That is billing data, not identity data, and it is what an appeal has to be written from. Your biller re-attaches identity at the payer portal or fax step, which stays on your side.

The model never sees PHI

Appeals backed by de-identified clinical notes are drafted by the model from de-identified summaries only; other appeals use AI-authored deterministic templates with no model call at runtime, as does any claim when the model is unavailable. Multiple independent filters strip names, locations, and ID numbers from anything sent to a model. If a filter cannot run, the pipeline stops rather than risk exposure.

Every decision is verifiable

From intake to payment, every action on every claim is permanently recorded. Records are tamper-evident: any alteration is visible and alertable. Your team can inspect the complete history at any time.

You can test us, not trust us

The conformance suite fires synthetic identifier-shaped probes at a running Hypex instance and asserts nothing leaks back, then checks the de-identification engine and the fail-closed boundary directly. Ask for it and the runner arrives with no conditions attached: your team runs it against production today and re-runs it quarterly, and attaches the PASS/FAIL report to your security review. It contains no patient data - every probe is a random marker in a realistic identifier shape.

Data flow

Where PHI touches, and for how long

1, Arrives

T+0

Your denial file or feed arrives. Raw identifiers exist only long enough to be removed.

2, De-identifies

seconds

Names, dates of birth, and record numbers are stripped automatically. Only billing codes and amounts continue.

3, Works & purges

24h post-send

All the work (root cause, drafting, your review) happens with no patient data present. Once an appeal is transmitted to the payer, the identifiers attached to it are destroyed within 24 hours.

4, Hard ceiling

400 days

Independent of the above, every claim is destroyed within 400 days of first receipt. A claim that is never transmitted is covered by this ceiling as well.

Procurement checklist

Control commitments

The table your IT/security team asks for. Where a control is enforced in code rather than only in policy documents, the row says so. Where something is staged but not yet live, this table says that too.

Data residency

Your data runs on infrastructure Hypex operates, behind Cloudflare's edge. Every request is scoped to your organization, so one practice's records are never visible to another. Your claims are never resold, aggregated, or cross-referenced against anyone else's.

Encryption

TLS 1.2+ in transit; encrypted at rest for the vault and letter storage.

PHI retention

Direct identifiers live in an encrypted vault and are destroyed within 24 hours of being transmitted to a payer. Every claim is also subject to a 400-day hard ceiling from first receipt, measured from that first receipt. A claim that is never transmitted is the worst case, and it is governed by that ceiling, not by the 24-hour clock. Letters are drafted de-identified from codes, amounts, and dates; identity re-attaches only at your own submission step.

Audit

Every action is permanently recorded in a tamper-evident history. Any alteration breaks the record visibly. Audit events are exportable as CSV on demand.

Access control

Every request is scoped to your organization, so your records are separated from every other practice's, and team members see only what their role requires. Access is logged and exportable for your own review.

Breach response

Affected covered entities are notified without unreasonable delay, and no later than 60 calendar days after discovery, per 45 CFR 164.410 and the BAA. The written breach-response procedure is provided on request during security review.

BAA

Business Associate Agreement executed with each customer before any PHI is processed: Hypex's (8 elements per 164.504(e)) or yours, which Hypex reviews and signs.

Model data path

Drafting works from the denial facts and the criteria you supply. Where a payer's own manual has been read and verified, it is used and named; where it has not, the letter says so rather than inventing a citation. Any AI-assisted drafting works from codes, amounts and dates only, never names or identifiers, and no patient data is ever used for training.

Submission safety

Every finished appeal is checked over before it is offered to you, and anything incomplete is held back rather than handed over. The same appeal cannot be submitted twice.

Breach response procedure

If something goes wrong

The written procedure, provided on request during your security review.

Detection

Vault access and database access are logged as part of the audit trail. Destruction of identifiers runs on a published schedule and does not depend on a human step: within 24 hours of transmission, and within 400 days of first receipt in every case.

Containment

Affected container is frozen and rotated; all service tokens in scope are revoked automatically.

Assessment

Forensics team determines whether any PHI was exposed. Identifiers are destroyed within 24 hours of being transmitted, and within 400 days of first receipt in every case, which bounds how long any exposed identifier could have existed.

Notification

Covered entities are notified without unreasonable delay, and no later than 60 calendar days after discovery, per 45 CFR 164.410.

Remediation & report

Root cause fixed, written report delivered, and a post-incident review published internally. A copy is provided to affected customers on request.

Verify it yourself

Run the conformance suite against us

Request the conformance suite and the runner arrives, unconditionally. It fires synthetic identifier-shaped probes at a running Hypex instance and asserts nothing leaks back, then checks the de-identification engine and the fail-closed PHI boundary directly. It outputs a PASS/FAIL report as JSON, carries no patient data, and your security team can run it against the production instance today and re-run it quarterly, unannounced.

1

Clone the suite

One link, no credentials, no setup call. Built to run without us in the room.

2

Point it at us

One flag: --base-url https://api.hypexrcm.com. Black-box probes run immediately.

3

Read the verdict

A PASS/FAIL report with per-check detail, safe to attach to your security review.

Get the suite link Re-run it whenever you like. A failing check is a reportable bug.

What we are not (yet), and exactly what changes it

  • SOC 2 Type II: not yet held, and we will not show a badge for one. The controls such an examination would test run in production today; ask us for the control matrix above and the audit timeline.
  • Penetration test: scheduled before any hospital-direct production go-live. Micro-RCM and clinic deployments run on the same hardened stack meanwhile.
  • US entity: formed when the first client requires it (it is revenue-gated, not calendar-gated). Until then the BAA is signed by the registered entity with a W-8BEN on file.