Integration
One more platform is the last thing you need.
So AyniHealth connects to what your department already runs, rather than asking anyone to keep two records of the same thing.
Where change actually lives
Your team already has enough systems.
A department runs an identity provider, a learning platform, an information system for treatment, and a folder of spreadsheets holding everything the others cannot. A change programme touches all of them, which is exactly why it usually ends up in the spreadsheets. AyniHealth is not a replacement for that estate. It is the layer that runs a change across it and keeps the record of who is competent to deliver it.
Three ways in
Connect at the level you need.
Sign in with your hospital identity
Staff use the credentials they already have. AyniHealth supports Microsoft Entra ID and Google Workspace single sign-on, so accounts follow your directory and nobody is issued a fourth password to forget. Email and password stays available for external and guest members who sit outside your tenant.
Your IT team, once, at rollout.
Run vendor activities in place
A simulator, an assessment, or a training module hosted by your equipment vendor can be part of an AyniHealth challenge without being rebuilt inside it. The learner starts it from their worklist, completes it on the vendor’s site, and the result comes back as a completion on their credentialling record.
Your vendor, against a published protocol.
Read the record from your own tools
Every organisation can issue its own API keys, and the platform exposes a Model Context Protocol server behind OAuth. That means an AI assistant, a reporting tool, or a script can ask who is credentialled for what and get an answer, without anyone exporting a spreadsheet first.
Your team, or ours, in an afternoon.
Available now
What is already built.
- Microsoft Entra ID single sign-on, multi tenant or tenant restricted
- Google Workspace sign-in, and email and password for external members
- Organisation-scoped API keys, issued and revoked by the organisation owner
- Personal API keys for individual scripts and assistants
- A Model Context Protocol server, so Microsoft 365 Copilot and Claude can read your data with your permission
- A published two-tier protocol for partner-hosted activities
- Accreditation-ready export of the credentialling record, on request rather than on a project
For equipment and content vendors
Three tiers, and you pick the shallowest one that works.
The partner protocol is deliberately boring. There is no signing secret to rotate and no schema to negotiate. Pick the tier that records what you need recorded, and no more.
Tier 1
Static embed
Lowest effort, hours of work
Your existing page, video, or article appears inside an AyniHealth challenge, and learners complete a short AyniHealth-side quiz on top of it.
- Best for
- Showing existing articles, videos, or product material as part of a learning module.
- You provide
- A public URL that allows being framed by AyniHealth.
- We provide
- Embedding inside our viewer, plus a quiz layer to confirm comprehension.
Tier 2
Hosted activity
Medium effort, a day or two
Your hosted experience, whether a quiz, simulator, exercise, or assessment, launches from inside an AyniHealth challenge, and your service reports the result back when the learner finishes.
- Best for
- Interactive experiences where only your service can judge whether the learner succeeded.
- You provide
- A page that receives a handoff token, then posts the completion back. Two HTTP calls, no cryptography.
- We provide
- A token-based handoff and completion API, and the completion recorded against the learner’s credentialling record.
Why this is special: Designed so a domain expert working with an AI coding assistant can build a working integration in an afternoon.
Tier 3
Deep integration
Highest effort, a scoped engagement
AyniHealth’s servers call your API on behalf of each learner. Users never leave AyniHealth and never see your domain. Suited to paid content, gated material, and strict data-handling requirements.
- Best for
- Paid or gated content, regulated material, and partnerships where privacy or branding control is critical.
- You provide
- A REST API your engineering team maintains.
- We provide
- A server-to-server broker that proxies all traffic, billing handoffs where applicable, and tailored content surfacing inside AyniHealth.
Why this is special: Scoped per partner. Get in touch to discuss requirements.
How a partner integration starts.
Most go from first conversation to live integration in under a month.
- 1
Send us a note describing the content or service you would like to bring into AyniHealth.
- 2
We pick the tier together, based on what your team can support and what your content needs.
- 3
You build to the published spec for Tier 1 or Tier 2, or we scope a custom engagement for Tier 3.
- 4
You, or any organisation admin using your service, self-serve in AyniHealth: pick your partner from the list, paste the handoff URL, and attach it to a challenge.
Bring your own systems.
Tell us what your department already runs and we will be straight about what connects today and what does not.