A design, not yet built
Onboard a laboratory through an agent.
Code mapping, interface setup, and release scoping as tools an agent can call. Patient data stays out of it. This does not exist yet.
Not built. This is a design, published early
The server described on this page does not exist. It is written down first because the constraints below are the design, and a constraint published before implementation is much harder to quietly drop during one.
The three rules
Configuration plane only
Code maps, interface parameters, tenant structure, release scoping. No patient data crosses the tool boundary, in either direction.
Tools propose, humans commit
Every change is a pending proposal with its evidence. A named person approves it, and the approval is what takes effect.
No tool widens a permission
A tool can narrow or scope down. Moving a cell toward release needs a human with authority and the agreement on file.
Bring the thing that breaks today.
Thirty minutes. Your laboratories, your practices, and the one stakeholder you cannot easily give data to.
Book a 30-minute call service@meta.clinic