Real-time data connection for health and social care.
Nexus retrieves information from systems across partner organisations just in time, and surfaces only the data a specific user, task and context requires. No data lake. No new system for anyone to learn.
Teams cannot see the full view of the patient.
Someone’s journey through health and care routinely involves multiple teams from an acute trust, community health, mental health, reablement, social care and homecare. The digital value chain that should support that pathway was built around organisations, not around the person moving through it.
One connection to the systems around you.
Nexus is a real-time data integration engine for health and social care. It retrieves information from partner systems just in time and surfaces only what a specific user, task and context requires. No central copy of the data, and no new system for frontline staff.
Currency
Data is fetched when it's asked for, so what a team sees is the latest version in the source system rather than a copy from last night's batch.
Governance
Publishers set and enforce their own access rules. Each organisation decides what it shares, with whom, and for what purpose, and can change that at any time.
Autonomy
There's no shared database for anyone to own, fund or maintain. Organisations keep their data in the systems they already run.
What that changes for your system.
Set up once, connect to many
Interoperability usually means maintaining a separate integration with every partner, or a workaround where none exists. With Nexus each organisation configures its outbound connections and permissions once, and Nexus handles secure routing to everyone else.
Just-in-time, federated sharing
Data stays in its source system until a valid, permissioned request is made. Nothing is batch-synced or duplicated into a central store, which keeps the volume of personal data being processed down and makes data minimisation straightforward to evidence.
Data in context, ready to act on
Shared data usually arrives fragmented and from a single source. Nexus assembles it around the task at hand, whether that's a discharge, an MDT or a safeguarding review, and can summarise it, surface risks and deliver it as structured, decision-ready information.
No one has to move systems
Integration programmes stall when they ask frontline staff to adopt a new portal. Nexus brings the right data into the tools teams already use, through Amelio apps, embedded widgets, or its API.
Sharing live data between systems
A single field or a whole record, moving in either direction, arriving in the system staff already use. Here the acute records that someone has no criteria to reside, the community service records when it can start, and each date is written into the other system so both teams work from the same two facts.
- Ward
- Not setWard 5
- Admitted
- Not set14 Aug
- No criteria to reside
- Not set21 Aug
- Available to start
- Not set24 Aug
- Consultant
- Not setDr S. Ahmed
- Referral received
- Not set15 Aug
- NCTR date
- Not set21 Aug
- Assessment
- Not set19 Aug
- Key worker
- Not setJ. Ellis
- Available to start
- Not set24 Aug
Surfacing information in context
The cross-organisation picture appears over the record the practitioner already has open, rather than asking them to go and look somewhere else.
Mrs E. Hargreaves
Shared with you by three services
In hospital since 14 Aug
Acute trust
No criteria to reside, 21 Aug
Community health
Reablement from 24 Aug
Local authority
Recent activity
- 20 AugPackage confirmed, four visits a day
- 18 AugHome assessment completed
- 15 AugReferral received from the acute trust
Once systems can be used as tools, agents can do the coordinating.
The same connections, permissions and audit trail that carry data between systems can let an agent act across them.
One integration surface, instead of dozens.
Unified API platforms have already done this for HR and financial software. Nexus applies the same pattern to health and social care, with the identity, governance and semantics the sector actually requires.
Request integration detailsFHIR-native
Nexus speaks HL7 FHIR R4, R4B and R5. Register a data source against a supported model and publish by push, by pull, or both.
Publish and subscribe
Publishers expose data sources; consumers register interest in the topics they care about and receive data at their own ingestion endpoint as it changes.
OAuth 2.0 machine-to-machine
Systems are registered as M2M applications and exchange a client secret or a private-key-signed JWT for a scoped access token. Every endpoint is protected by the scopes it requires.
Field-level permissions
Permission sets attach to each data source and are evaluated with FHIRPath, so a publisher can share a whole resource, a handful of fields, or everything except one record.
Nothing persisted in the middle
Records live in an in-transit store only while a pipeline is running. Everything at rest and in flight is encrypted with dedicated AWS KMS keys.
Auditable by default
Every configuration change, whether to data sources, permissions or subscriptions, is captured as an event and retained for audit.
Frequently asked questions
- No. A shared care record pools copies of data into one place that somebody then has to own and fund. Nexus leaves data where it is and fetches it when a permissioned request is made, so there's no central store to keep current, secure or paid for.
Technical detailsFederated access, and how this compares with a data lake
Federated access, not another copy of the data.
Federated access means querying across independent systems without pooling anything into a shared record. Each organisation keeps control of its own data, exchange happens on demand against its permissions, and the pipeline that does the work holds nothing once it’s finished.
Why not a data lake?
Warehouses, lakes and shared care records all start by copying data somewhere central. That decision is what makes them slow to stand up, expensive to keep aligned to live workflows, and awkward to govern.
| Data lake / shared care record | Nexus | |
|---|---|---|
| Where data lives | Extracted and copied into a central lake or shared record | Stays in the source system until it's requested |
| How current it is | As fresh as the last batch ingestion | Retrieved at the moment of the request |
| Getting started | Upfront extraction, schema mapping and storage design | Configure your connections and permissions once |
| Governance | Access rules set centrally, away from the data owner | Each publisher sets and enforces its own rules |
| GDPR posture | More personal data processed, wider attack surface | Data minimisation, purpose auditing and storage limitation by design |
| What partners adopt | Often a new portal or shared platform | Nothing. Data arrives in the tools they already use |
Let’s talk about what you need to connect.
Whether you’re commissioning a pathway or building the system at one end of it, the first conversation is the same: which data, between whom, for what.