Source A
Nexus-built
Applications we build and maintain, shipped with the platform and carrying their own status labels.
AI Ecosystem
One integration foundation.
Many clinical applications.
Nexus-built applications, cleared third-party products and models an institution builds itself all run against the same data access, isolation and audit model.
Source B
Third-party cleared
A vendor's product, running under its own regulatory clearance, hosted on the hospital's infrastructure rather than the vendor's cloud.
Source C
Institution-built
Models an academic centre develops itself, deployed through the same manifest, scopes and audit path as anything else.
What a vendor supplies
An application manifest -what it is, what it needs, what it returns.- Declared data scopes -approved by the hospital before anything runs.
- Regulatory documentation -the clearance, in the jurisdiction of the site.
- A container that expects no outbound network
What the platform supplies
- An integration the hospital has already made once.
- One patient identity across the systems that feed it
- Scope enforcement and pseudonymization on every request.
- An audit trail the hospital already relies on, carrying the vendor's outputs.
Beyond applications
The catalogue holds models, not only applications.
An application is one way to add capability. A model is another — and on this platform both are installed, version-pinned, scoped and audited the same way.
Open-weight models
Language, speech-to-text, embedding and clinical text models under permissive licences, delivered in the signed bundle and run on your own hardware.
Architected
Licensed third-party models
Medical language and foundation models you hold the licence for. We integrate them; the licence stays yours.
Architected
Institution-built models
A model your own team trained, deployed through the same manifest, scopes and audit path as any vendor's.
ArchitectedNo model on this platform is offered for diagnosis. A model that would influence a diagnosis is a regulated product and carries its supplier's clearance.
For AI vendors
If your product holds clearance and your blocker is the hospital's own infrastructure, this is the route in.
Talk to NexusNo third-party vendor integrations are signed today, and no vendor logos appear on this site. The onboarding model above is the model the platform is built around.
