Extend Ospia, don't replace it
Every module ships as an installable package declaring its own routes, events, permissions and configuration. The mechanism already exists in the core — a marketplace is a storefront over it, not a new architecture.
Extension points
Eight ways the platform grows
Each with its honest status: what you can use today, and what is Phase 7.
Marketplace
Install capability packs onto a live tenant — specialty modules, compliance packs, reporting suites — with no code change to the core.
Phase 7Certified partners
Implementation and specialty partners trained and certified, with published competencies.
Programme formingAI skills
New agent capabilities composed from governed blocks — bounded tools, prompt templates, evaluation sets.
Phase 7Workflow packs
Proven operational workflows installed as configuration — discharge pathways, claims routines, procurement chains.
Phase 7Clinical templates
Specialty order sets, assessment forms, care pathways and documentation templates.
Phase 7Third-party apps
Independent developers build against published contracts, certified before listing.
Phase 7Integrations
A connector catalog with configuration-driven onboarding: LIS, PACS, ERP, HRMS, payments, messaging, devices.
Core availableSDK & API
Versioned REST API with generated OpenAPI and typed SDK, published event catalog, signed webhooks.
Core availableThe mechanism is built; the storefront is Phase 7. Module manifests, per-tenant installation and feature flags exist from the foundations because they are impossible to retrofit — which is precisely why we built them before we needed them. See the phase plan.
What it means for you
What a hospital gets out of an extensible platform
Extensibility is only worth paying for if it shortens your implementation and removes future cost. Here is what it is actually meant to do for the hospital buying it.
What you gain
- You start on packs and configuration already proven in live hospitals, rather than specifying every rule from a blank system.
- Specialty capability — an oncology regimen set, an IVF cycle model — installs as configuration instead of becoming a development project.
- New capability arrives on the platform you already run, so there is no rip-and-replace to fund later.
- You can extend the platform yourself, or bring your own partner, without waiting in our roadmap queue.
What it does not mean
- Your patient data is never part of what travels between hospitals. Only the structure of a configuration can be shared, and only if you opt in.
- Your commercial terms, tariffs and negotiated rates stay yours and stay private.
- Installing a pack does not hand a third party access to your tenant; extensions run under the same permissions and audit as everything else.
- Nothing installs itself. Every pack is an explicit, audited decision by your administrators.
Certification exists for your protection, not ours: third-party packages are reviewed before they can be listed, and they run inside the same boundary gates, permission checks and audit trail as the core modules. An extension cannot do anything a module could not do — see the architecture.
Next step
See your hospital running on Ospia
An executive demonstration takes forty-five minutes. We seed a hospital with synthetic data shaped like yours, put the digital workforce on duty, and answer the hard questions with the architecture open.
synthetic data · zero real patients
self-hosted or managed cloud
one database per hospital