NewMissing Records Detection: flags every visit, provider, and date missing from the file. See how →

Built for PHI from the ground up.

This page exists to be bookmarked and forwarded. Everything your security review, procurement team, or client audit needs: stated plainly, with nothing overstated. HIPAA compliant and SOC 2, TLS 1.2 or better in transit, AES-256 at rest, a BAA and DPA available before you upload anything, and records that never train a model.

HIPAA SOC 2 TLS 1.2+ AES-256 BAA / DPA available

Is the workspace up right now? Run the live status check.

PHI audit log LIVE
AES-256 · record encrypted verified
OCR extraction → page 14 verified
Citation linked → source p.12 verified
Access: case #2291 only verified
Export blocked: no BAA enforced

Your records never train an AI model. Ever.

Not ours, not a vendor's, not "de-identified for research." Your files are processed to produce your outputs, and that is the end of their journey. This is contractual (it's in the BAA), not a settings toggle.

What we do learn from is the software: which features get used, how long a review takes, where a draft gets corrected, what fails. That telemetry is engineered to exclude record content: the number of edits a draft receives is ours to measure, the edit itself is not. The boundary is written down in Terms Section 8.3.

6 controls your reviewer will ask about.

Encryption

TLS 1.2+ in transit, AES-256 at rest, for every file and every environment.

Case-level access control

HIPAA-minimal by default: people see only the cases assigned to them. Nothing else exists for them.

PHI audit logging

Every PHI access event is logged: who, what, when. Exportable for your own audits, appeals, and records requests.

Secure sessions

Token-validated sessions with strict expiry handling. No shared credentials, anywhere.

SOC 2

Readiness report dated November 3, 2026, free to download. Controls documentation and evidence packages under NDA.

Human-guided AI

Every output cited, reviewable, and traceable to its source. AI does the reading and helps your experts make the call. The last word is theirs.

Download our compliance reports.

Both reports are dated . Attach them to your vendor review or forward them to procurement. No form, no NDA.

Generated

SOC 2 readiness report

Every SOC 2 control we run, mapped to the criteria it answers, with its current monitoring status.

PDF · 50 pages · 627 KB · Sprinto
Download the PDF
Generated

HIPAA readiness report

Every HIPAA Security Rule safeguard we address, with the controls and checks behind each one.

PDF · 96 pages · 1.2 MB · Sprinto
Download the PDF

These are readiness reports from continuous control monitoring in Sprinto, not an auditor's attestation. Need the full evidence package, penetration-test summaries or a countersigned BAA/DPA? Request them under NDA below. Evaluating us for your team? Read the 16-answer FAQ, each answer linked to its source.

Deployment and integration

For carriers, TPAs, and public-sector programs deploying at scale.

Connect (API)

Secure REST API and CRM token exchange, no shared credentials, with outbound webhooks into your case-management and claims systems.

Usage and cost analytics

Per-feature, per-file metering, so you can bill costs back to a case, a client program, or a desk.

Data lifecycle

Retention controls, de-identified export for sharing without exposing PHI, and deletion on request.

Everything procurement asks for, in one PDF.

Controls documentation, the sub-processor list, BAA/DPA templates, and the SOC 2 evidence summary, sent under NDA.

This opens your email app; nothing is submitted from this page. Do not include PHI.

See it run

Watch the safeguards behind every case

The clip opens on a demo upload: Rivera_records_4821.pdf, 212 pages, crosses from the browser to Medrecords AI over TLS 1.2 or better and lands in storage encrypted with AES-256. Next, Settings, Legal lists the Terms of Service, the Privacy Notice and the Business Associate Agreement, each accepted. Opening the BAA row shows who accepted version 1.0, when, the method (a sign-up checkbox) and the SHA-256 hash of the text, with a button to export the certificate. The third view shows where records go: into your case, for the chronology, summaries, ledger and reports, and never into training any AI model. Then the 4 vendors that can touch records, all under a BAA: AWS stores files in US data centers, OpenRouter routes AI requests, and Anthropic and OpenAI are backup models reached only through OpenRouter. The access view shows that your team and Medrecords AI staff see only assigned cases, that support access needs your approval, and that every access is logged. Next comes breach notice, no later than 72 hours after we confirm a breach, and the way out: a 30-day export window, then destruction with backups included and a deletion certificate. The clip closes on HIPAA compliant and SOC 2, with readiness reports free to download, a BAA and DPA available before you upload, and a PHI audit log. Every name, provider and date in the demo is invented.

Transcript
  1. Your records stay encrypted, logged and yours.
  2. Every file is encrypted in transit with TLS 1.2 or better, and in storage with AES-256.
  3. A business associate agreement, or BAA, is the contract HIPAA requires. You accept it at sign-up. The version, the time and a fingerprint of the text stay on record.
  4. Your records are used for your case. They never train an AI model. That's in the contract.
  5. Only 4 vendors can touch your records. AWS stores them in the US. OpenRouter routes AI requests, with Anthropic and OpenAI as backup models. All 4 sign a BAA.
  6. People see only the cases assigned to them. Our staff too, and support access needs your approval. Every access is logged.
  7. If a breach happens, we notify you no later than 72 hours after we confirm it. When you leave, you get 30 days to export. Then your records are destroyed, backups included, with a deletion certificate.
  8. Readiness reports for HIPAA and SOC 2 are free to download on our security page. No form, no NDA.
  9. Medrecords AI is HIPAA compliant and SOC 2. BAA and DPA available.

Watch it with voiceover · Download the video (MP4, 82 seconds)

Who touches your data, and what happens if something goes wrong.

Breach notification

Notice of any breach of unsecured PHI without unreasonable delay, and in no event later than 72 hours after we confirm it, as set out in the DPA and the BAA.

Who can touch your records

4 vendors, all under BAA, zero-retention, no-training. Your files are stored on AWS in US data centers. Every AI model request goes through OpenRouter, mostly to open-source models, with Anthropic and OpenAI as a backup reached only through OpenRouter. Full detail: Subprocessor List.

Data residency & retention

Customer Content is processed in the US only. At termination, PHI is returned within a 30-day export window, then destroyed (including backups) with a deletion certificate.