The platform inside
our customers’ products.
Concentra, Kaiser Permanente, Johnson & Johnson’s VELYS™ and Avanos run DocSpera services inside their own branded products. Platform services are hard to see from the outside, so here they are running: the real apps on synthetic data, and guided views of the engines underneath.
How the three layers connect
Click any node to open the customer demos that exercise it.
The platform, through your eyes
The same demos, chosen and narrated for one kind of organization.
Customer deployments
Each customer ships its own product. Underneath, they share the same integration engine, workflow services and engagement stack.
Concentra’s appointment scheduling and patient texting run on DocSpera.
A FHIR R4 partner feed in production, and a surgical referral concept built with Kaiser’s team.
Avanos launched SurgiCheck on DocSpera to follow every patient through the first week after surgery.
Advance notice of every case, with its imaging, for the device partner.
Robotic surgery data and patient engagement in one portal, on DocSpera.
One platform, many products
Which platform services each deployment runs on.
| Platform service | ConcentraConcentra Scheduler | Kaiser PermanenteFHIR partner feed | AvanosSurgiCheck | J&J MedTechAdvanced Case Management | J&J MedTechVELYS™ |
|---|---|---|---|---|---|
| L1Excelsior integration engine | ✓ | ✓ | · | ✓ | · |
| L1Imaging + DICOM pipeline | · | · | · | ✓ | · |
| L1Outcomes + PROMs capture | · | · | ✓ | · | ✓ |
| L2Advanced case notification | · | · | · | ✓ | · |
| L2Scheduling engine | ✓ | ✓ | · | · | · |
| L2Rules + readiness | ✓ | ✓ | ✓ | ✓ | ✓ |
| L2Exception worklists | ✓ | ✓ | · | ✓ | · |
| L2Patient engagement | ✓ | ✓ | ✓ | · | ✓ |
| L2AI appointment agent | ✓ | · | · | · | · |
| L3Real-time staff apps | ✓ | · | ✓ | ✓ | ✓ |
Honest about what you’re looking at
Every demo carries a label. Nothing here touches a production system or real patient data.
The real application or algorithm, built from the production codebase and pointed at a mock API or synthetic data that lives in your browser.
Interactive concepts built with the customer to agree the next phase. They show where each deployment is heading.
Step-through views of back-end engines that have no screen of their own, such as message routing and AI agent decisions.
Contracts, connectors and a certification suite
How customers and partners plug their own systems into the platform without forking it.