The messaging protocol that lets clinical AI agents delegate tasks to each other safely. Built on JSON-RPC 2.0 (JavaScript Object Notation Remote Procedure Call) with 13-point route admission validation on every request.
Every agent-to-agent interaction follows a deterministic lifecycle. The requesting agent never loses visibility, and every state transition is logged to a hash-chained audit trail.
An agent publishes a task request specifying capability needed, patient context, urgency, and purpose of use. The request is signed with the sender's Decentralised Identifier (DID).
The receiving agent passes all 13 admission checks. If every gate clears, it accepts the task and acknowledges with a session token bound to both agent identities.
During execution, the working agent emits checkpoint events via Server-Sent Events (SSE). The requesting agent maintains real-time visibility into progress and intermediate results.
The task completes with a structured result, or escalates to a human clinician if confidence thresholds are not met. Both outcomes are recorded in the audit trail.
Before any agent can accept a delegated task, the request must pass all 13 admission checks. A single failure rejects the route and logs the reason. No exceptions outside emergency override.
HelixCare is the reference implementation that demonstrates Nexus in a realistic clinical environment. 25 agents organised into 5 clinical demo groups, each handling a distinct healthcare workflow.
Central dashboard providing real-time visibility into all agent activity, task queues, admission decisions, and escalation events across the network.
API (Application Programming Interface) gateway that routes external requests to the correct clinical agent group, handling load balancing, rate limiting, and session affinity.
Agents that perform initial patient assessment, symptom classification, urgency scoring, and clinical pathway selection before delegating to specialists.
Agents that generate and manage longitudinal care plans, coordinate multi-disciplinary team input, and track outcome measures over time.
Agents that coordinate lab orders, interpret diagnostic results using AI models from providers such as OpenAI, and flag abnormal findings for clinical review.
Agents managing medication reconciliation, interaction checking, formulary compliance, and electronic prescribing workflows.
A 3D avatar interface that delivers clinician-patient consultations using established medical communication frameworks. Every persona follows structured clinical methodology, not free-form conversation.
Consultations follow the Calgary-Cambridge guide to the medical interview — initiating the session, gathering information, building the relationship, explanation and planning, and closing the session. Every stage is tracked.
For pain presentations, the avatar uses the SOCRATES framework: Site, Onset, Character, Radiation, Associations, Time course, Exacerbating and relieving factors, and Severity.
Emergency presentations follow the ABCDE approach: Airway, Breathing, Circulation, Disability, and Exposure — ensuring systematic assessment and prioritisation of life-threatening conditions.
The avatar system supports 68 distinct clinician personas spanning 3 countries. Each persona carries jurisdiction-specific clinical knowledge, language preferences, and regulatory awareness.
Nexus agents are not anonymous services. Every agent holds a Decentralised Identifier (DID), belongs to an Identity and Access Management (IAM) group, and is registered in the Global Agent Registry (GHARRA).
Each agent's identity is anchored to a Decentralised Identifier (DID) document containing its public keys, service endpoints, and capability declarations. Identity verification happens on every request, not just at registration.
68 personas are organised into Identity and Access Management (IAM) groups with fine-grained policies. Groups define which agent capabilities a persona can invoke, which patient data scopes are permitted, and which jurisdictions apply.
Every agent is registered in GHARRA (Global Healthcare Agent Registry and Routing Architecture). The registry provides discovery, health monitoring, capability indexing, and revocation checking for the entire agent network.
Every task request, admission decision, checkpoint, and completion is recorded in a hash-chained audit trail. Cryptographic signatures ensure non-repudiation — no agent can deny an action it performed.
See the protocol in action
Nexus provides guaranteed delivery for clinical and AI workflows. 13-point admission control on every interaction. Explore the protocol specification or book a walkthrough to see it in action.
JSON-RPC 2.0 • 7,000+ test scenarios • 13-point admission control