AI solution providers · Healthcare
Clear every hospital's security review with the controls it asks for.
Run one Meilynx gateway per hospital in your own cloud account. Patient data stays in your account, and requests reach the model only after the PHI and PII the gateway detects are redacted. Each hospital sees what your AI did on its own patients' calls.
Four questions, answered on the gateway.
A hospital's security review asks where patient data goes, who approves what the agent does, and how the hospital will know. Each answer happens on the gateway, before a request reaches the model or the record system.
Detected PHI and PII are redacted before the model sees them
Requests reach Anthropic models, directly or through Amazon Bedrock, only after the PHI and PII the gateway detects are redacted. The gateway runs in your cloud account.
Allowed · redacted
An action the policy holds waits for the hospital's reviewer
For example, a medication change the hospital's policy holds. It waits until a reviewer the hospital names releases or declines it.
Held for a reviewer
A request for records the agent may not touch is refused
Each hospital has a declared reach: the record types the agent may touch. A call for anything else is refused before it reaches the record system, and the hospital is notified.
Refused · hospital notified
A wider scope waits for the hospital's approval
A new tool or a new record type widens what the agent may do. The change waits for the hospital, unless it delegated that kind of change to you.
Awaiting the hospital
A reviewer the hospital names decides each held action.
Holds are part of the policy you set for each hospital. Your team cannot release a hold the hospital's reviewer owns, and a hold nobody decides expires without the action being carried out.
Your agent
Proposes a medication change.
Waiting
The gateway holds it: the hospital's policy holds medication changes.
Hospital's reviewer
Named by the hospital. Your team cannot release it.
Released
The record system receives the change.
Declined or expired
The change is not sent.
On the hospital's record
Who decided, when, and under which policy.
- Conditions
- Approved models on your listNotice before any change to the service
- On your patients' calls
- 1,284PHI redacted37held for your reviewers3refused
- Change notice
- New model proposed for the patient assistant.AcknowledgeObject
- Record
- Hash-chained, independently timestamped Verifiable offline
Illustrative figures
Each hospital sees what your AI did on its own patients' calls.
The hospital signs in to its own view of your service.
Its conditions
The models it approved and the notice it gets before your service changes.
What was enforced
Redactions, holds, releases and refusals on its own patients' calls.
Change notices
Each change to your service, which it can acknowledge or object to.
Its gateway's status
If the gateway stops reporting, the view shows it.
A record it can check
Hash-chained, independently timestamped and verifiable offline. Its team can confirm the record has not been altered since it was written.
What you can tell a hospital's CISO.
Statements your team can make in a security review, each backed by the gateway and by a record the hospital checks itself.
- “Patient data stays in our cloud account, on a gateway that serves your hospital alone. Requests reach the model only after the PHI and PII the gateway detects are redacted.”
- “Meilynx receives each call's outcome (allowed, redacted, held, refused), the policy that applied and counts, with no prompt, reply or tool-argument content.”
- “Actions your policy holds wait for a reviewer you name. Our team cannot release a hold your reviewer owns.”
- “A held action that nobody decides expires without being carried out.”
- “A call for records outside the types we declared for your hospital is refused before it reaches your record system, and you are notified.”
- “Changes that widen the agent's reach or authority wait for your approval, unless you delegated that kind of change to us.”
- “If your gateway stops reporting, your view shows it.”
- “You can verify the record offline and confirm it has not been altered since it was written.”
Meilynx has completed its SOC 2 Type I audit, covering Security, Availability and Confidentiality. The Type II observation period is underway.
Trust Center →One gateway per hospital, in your own cloud account.
Each hospital's traffic runs through its own gateway, next to your product, and your agent reaches Anthropic models directly or through Amazon Bedrock.
Your cloud account · patient data stays here
Your product
agent · voice · chat
Gateway · hospital A
its own policies
Gateway · hospital B
its own policies
Your engineers
read a redacted copy on the gateway
Anthropic models
directly or through Amazon Bedrock
Each hospital's record system
Meilynx
your console · each hospital's view
Requests to the model
Sent after redaction
Meilynx receives
Outcomes, policies and counts
Added latency
<5 ms p95 added latency, measured under sustained load (Oct 2026)
What deployment takes
Your team runs
One gateway per hospital in your cloud account, next to your product.
Your team updates
Each gateway. The console shows the release every hospital runs and which need an update.
Hospital IT
Signs in to the hospital's own view and names the reviewers who decide held actions.
Your team runs the service. The hospital keeps its decisions.
Your team
01- Runs a gateway for each hospital in your cloud account
- Updates each gateway
- Sets each hospital's policies: tools, the record types the agent may touch, redaction and holds
- Reads a redacted copy of a call on the gateway to troubleshoot
The hospital
02- Names the reviewers who release or decline held actions
- Approves changes that widen the agent's reach or authority, unless it delegated that kind of change to you
- Acknowledges or objects to each change notice
- Verifies the record offline
Meilynx
03- Receives each call's outcome, the policy that applied and counts, with no prompt, reply or tool-argument content
- Runs your console and each hospital's view
- Publishes the verifier under an open-source license
- Runs the public status page the badge links to
The hospital answers to
Bring us one hospital's scenario.
We'll run a held action, a refused request and the hospital's own view on a gateway set up for your product.
links to a public status page
Embed the Governed by Meilynx badge on your site. It links to a public page that shows, when opened, whether your deployment is governed and whether its gateway is reporting.