Connect health and care systems in real time.
Nexus retrieves current information from the systems used across a pathway and delivers it where it is needed, when it is needed. Each organisation keeps control of its data, while frontline teams continue working in the tools they already use.
The information teams need sits in other organisations’ systems.
A discharge, MDT or safeguarding review can involve acute, community, mental health, social care and homecare services. Each team holds part of the picture. Staff are left to find the rest through phone calls, emails and separate portals, and important changes are easily missed.
Secure data exchange across a whole pathway.
Nexus is a federated integration layer for health and care. When an authorised user, application or workflow needs information, Nexus retrieves it from the source, applies the data owner’s permissions and delivers only what is required for that task. There is no persistent central copy and no new portal for frontline teams to use.
Current by design
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.
Controlled by the data owner
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.
No shared platform to maintain
There's no central database for anyone to own, fund or maintain. Organisations keep their data in the systems they already run.
What that changes for your system.
Connect once, exchange with 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.
Retrieve data when it is needed
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.
Bring information together around the task
Nexus brings the relevant data together around the task at hand, whether that is a discharge, MDT or safeguarding review. Applications using Nexus can then present it in context, summarise it or surface risks.
Keep teams in the tools they already use
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
The acute service records an NCTR date of 21 August. The reablement service records that it can start on 24 August. Nexus writes each date into the other system, so both teams plan from the same information without rekeying it or chasing an update.
- 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
Information from partner organisations appears alongside the record a practitioner already has open. They can see what has changed across the pathway without searching another system or opening a separate portal.
Mrs E. Hargreaves
Shared with you by three services
Acute trust · Ward 5
02 Aug to 14 Aug · Admission
Community hospital · Ward 4
14 Aug to 27 Aug · Admission
Reablement · Neighbourhood team
27 Aug to presentLive
Recent activity
- 26 AugPackage confirmed, three visits a day
- 25 AugHome assessment completed
- 22 AugReferral received from the community hospital
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 simplified integration across industries such as finance and HR. Nexus applies the same model to health and care, with the identity, permissions, auditability and shared data standards the sector 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.
Fine-grained permissions
Permission sets are evaluated using FHIRPath, allowing a publisher to share a whole resource, selected fields or only records meeting defined criteria.
No persistent central record
Nexus holds data only for the duration of the pipeline processing it. It does not create a persistent central copy. Data is encrypted in transit and during any transient processing using dedicated AWS KMS keys.
Auditable by default
Configuration changes, data requests and exchanges are recorded against the system, purpose and permissions involved, creating a complete audit trail across the connection.
Frequently asked questions
- Querying across independent systems without pooling anything into a shared record. Each organisation keeps control of its own data, exchange happens on demand and against its own permissions, and the pipeline that does the work holds nothing once it has finished.
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.