Trust & governance
Trust you can check.
What holds AI back in clinical care is no longer the technology. It is whether the people who must rely on it can trust it. Every record in the Library says where its facts came from, who checked them, and what is not yet known.
The four pillars
No patient data
The platform stores deployment metadata only. Identifiable patient information is never collected.
Audit trail
Every stage change and every signature is logged. The journey of each record can be reconstructed.
Approval is not the whole answer
A CE mark or an FDA clearance shows that a device is safe and performs as claimed, for its stated use. It does not show that it is fair, that a clinician can oversee it, that it works in your hospital, or that it will still work next year. The Lab's governance dossier asks those questions too, section by section.
Explicit evidence
Every record shows how far it has been checked, and by whom: software, a Lab reviewer, the provider, or an independent party. Most have been checked by software only, and the record says so.
Why trust, and why now
The obstacle to AI in clinical care is rarely the invention any more. A new AI model can reach millions of users overnight; a hospital has to move carefully, because a patient is at the end of every decision. What earns a clinician's trust is concrete: the AI fits into their work, they keep the decision, it changes on a known schedule rather than without warning, and what it says can be traced to a source.
The Library records these conditions wherever a source states them: how much the AI decides on its own, how human oversight works, whether its performance is monitored once it is in use, and whether it changes after release, how often, and who decides when an update goes live. Most sources say little about them. The Library shows that gap rather than filling it with a guess.
Compliance
AIH Lab supports compliance work; it does not replace it. It sets out what the EU AI Act, the MDR and IVDR, and the GDPR ask of a clinical AI system and of the hospital that runs it, and it shows where a record does not yet answer. It is not a regulator, and a record is not a certificate.
Technical security
Row-level security in the database decides who may read or change each record, and column privileges decide which fields a visitor can see. The database is hosted in the EU, in Frankfurt. All access is over TLS. The key that can bypass these rules is held only on the server and never reaches a browser.
Raise a concern
If you have seen a problem with an AI system recorded in the Library, tell us. With an account, raise a safety signal on the record itself: the Lab triages it, and it is shown on the record's page. Without one, use the contact form; it reaches the Lab's staff directly.