Your patients’ data never leaves the EU.

On AWS in Paris, an HDS-certified host.

Live in France since September 2026. US hosting and a HIPAA program are on our roadmap.

The AI reads. Your staff approves.

Claude by Anthropic, on Amazon Bedrock. No model is trained on your data.

AWS data policy

Sample data

  • Your codes, never the model’s

    Every line points to an entry in your own dictionary. If none fits, it’s marked “Needs coding.”

  • What’s written, nothing more

    Sex isn’t inferred from a first name. An unreadable field stays blank.

  • Doubts get flagged

    A half-legible provider ID, a daughter’s order handed over by her mother: the AI flags it, your staff decides.

  • A name on every order

    Nothing reaches the LIS without “Send” or “Approve.” That person’s name stays in the audit trail.

Your coding rules, written as sentences.

Type “if CREA, ask for weight”; the AI drafts the rule and a person saves it. From then on, plain code applies it, not the AI: same input, same output.

HPRIM into your LIS. No inbound ports.

  • Attachments included

    On approval, the order goes out over SFTP in HPRIM Santé 2.5, France’s lab-order format, with the scanned order, ID, cards, and consents.

  • A read-only connector

    A Windows PC in the lab reads patients, providers, and phlebotomists from your LIS four times a day. It sends only the rows that changed.

  • One key, one right

    The connector’s key can only import, and only from the lab’s IP address. The API returns no patient data.

  • Your LIS is the reference

    When values differ, your LIS wins.

What your IT team does

  1. 1In your LIS: an HPRIM Santé 2.5 interface to our SFTP drop, one receiver code per site.
  2. 2Network: the lab’s fixed public IP address.
  3. 3A Windows PC with read-only access to your LIS, left signed in (locked is fine).

Where every record lives.

AWS has held HDS v2, France’s health-data hosting certification, since April 21, 2026, Paris and Ireland included. The certificate, on AWS

DataWhereProtection
Records, visits, accountsParis · 2 zonesEncrypted database, cut off from the internet
Orders, cards, consentsParisPrivate S3, encrypted, versioned
Screen replaysParisAdmins only, deleted after 30 days
AI readingAWS regions in the EUClaude on Amazon Bedrock
Home-visit addressesFrankfurt · EUAmazon Location, address only: no name, no health data

Backed up nightly, locked for 35 days.

Database restorable to any point in the last 35 days; deleted files recoverable for 90 days.

One account each. Rights by role.

  • Passkeys first

    Face ID, Touch ID, Windows Hello, or a hardware key. Bound to Asynia’s address, they don’t work on a fake site.

  • Email code

    Without a passkey: a six-digit code, valid 10 minutes, single use.

  • Lockouts and sessions

    Account locked 15 minutes after 5 failures. Sessions close after 4 idle hours, 14 hours at most.

  • The Asynia team

    No direct database access: every technical session is logged.

Who sees what

Front deskBack officeAdmin
Front deskPatient check-in
Lab directorReview, coding, approval
AdminUsers, audit trail, settings
  • Front deskPatient check-inFront desk
  • Lab directorReview, coding, approvalFront deskBack office
  • AdminUsers, audit trail, settingsFront deskBack officeAdmin

Every request is walled off to your lab.

Every action has an author.

  • Before and after

    Every correction keeps the old value and the new one: identity, codes, attachments.

  • Screen replay

    An admin can replay what the front-desk screen showed. Passwords masked; images, scans, and signatures aren’t recorded.

  • Sign-in log

    Sign-ins, failures, devices added or removed, admin actions: all recorded.

Your lab decides. Asynia processes.

Data controller

Your lab

Sets the purposes, informs patients, answers their requests.

Processor · GDPR Art. 28

Asynia

Processes data on your instructions.

Subprocessor

Amazon Web Services

Hosts in Paris, runs the AI and computes home-visit routes in the EU.

All our subprocessors
  • Legal basis: provision of health care (GDPR Art. 9(2)(h)).
  • For your privacy officer: security questionnaire and data processing agreement (Art. 28), on request. Contact us

A demo, with your IT and privacy leads.