Neutrino
AccessFabric · Module

Patient 360

One patient, one view, every actor.

A unified, real-time view of each patient's access journey — scoped to each actor's need-to-know, with audit-grade lineage.

HubsSpecialty PharmacyPharmaProviders
Problem

Why Patient Access teams need this

The realities we hear from operators — the ones that don't show up in product demos.

×
Many systems, no patient

Each actor sees a slice — no one sees the whole journey.

×
Duplicate outreach

Patients receive overlapping calls and messages across actors.

×
Stale status

Information is out-of-date by the time it's surfaced to the team that needs it.

×
Compliance risk

Over-sharing PHI across actors creates governance exposure.

What this solves

Outcomes, not algorithms

We lead with the business outcome — the mechanism sits behind a stable interface.

Journey-level view

Status across enrollment, benefits, PA, fulfillment, adherence — in one place.

Role-scoped access

Each actor sees only what they need, governed centrally.

Coordinated outreach

A single next-best action surfaces across teams.

Audit-grade lineage

Every data element tied to its source and access log.

How it works

A controlled view of the flow

We share the stages — not the internal logic, models, or scoring methods.

1Stage
Assemble
Journey reconstructed from Data Fabric events.
2Stage
Scope
Role and purpose-based filters applied.
3Stage
Surface
Embedded widgets, full console, or API.
4Stage
Act
Next-best actions and coordinated workflows.
High-level stages shown — internal logic, models, and scoring methods are intentionally abstracted.
Inside the solution

The Patient 360 workbench

A role-scoped, longitudinal view of a patient's access journey — assembled from the Data Fabric.

accessfabric.neutrino.health / accessfabric/patient-360
Open ↗
Synthetic data only. No PHI.
Another view

Patient adherence snapshot

The adherence view inside Patient 360 — barriers, outreach history, and next-best-action in context.

accessfabric.neutrino.health / accessfabric/adherence
Open ↗
Synthetic data only. No PHI.
Agents at work here

The agents that run inside this solution

Each agent operates inside explicit boundaries — with confidence thresholds, audit logs, and human escalation built in.

Ecosystem fit

Where this sits in Patient Access

This capability isn't a silo — it plays with every actor across the journey.

Hub agent
Sees the case and its surrounding journey context.
SP coordinator
Sees referral, PA status, and fulfillment handoffs.
Pharma field team
Sees aggregated, de-identified performance views.
Provider office
Sees status relevant to upcoming visits.
Value delivered

Measured against the metrics that matter

We publish outcome ranges, not point claims — every number is validated in-context.

Duplicate outreach
Fewer redundant patient contacts across actors.
Coordination lag
Lower latency between actors on status changes.
Adherence
Improved therapy continuation through better coordination.
Deployment

Fits the way you work

Embed inside your platform, run alongside it, or consume through API — your call.

Embedded
Surfaced directly inside your existing UX.
Sidecar
Runs alongside your platform without disrupting it.
API
Consume capabilities programmatically.
Ready when you are

See Patient 360 in your environment.

A focused walkthrough against scenarios that mirror your hub or SP — no theoretical decks.