Every demo, by platform layer
Each one runs in your browser on synthetic data, and each one can be embedded in another page.
Applications
What patients, staff, surgeons and device partners actually use.
Concentra Scheduler: patient scheduling
The scheduling interface on DocSpera’s scheduling engine, which Concentra staff use to book patients across 600+ centers. It shows real-time center and clinician schedules, suggested clinicians and times, and clash warnings. A reschedule queue is fed by patient text replies.
Two-way texting and self-reschedule
The next phase for Concentra: patients ask questions by text and get answers drawn only from their appointment, reschedule themselves within guardrails, and telemed outreach moves off a separate tool. Exceptions still land with a person.
Clinician availability
Shift templates, eligibility rules, pickups and leave approvals for clinicians across markets, feeding availability straight into patient scheduling.
Living Depot: surgical referral to readiness
One patient’s path from an Epic referral to a prioritized queue, automated outreach when the scheduling window is missed, booking, and condition-specific readiness nudges before surgery.
SurgiCheck daily check-in
What an Avanos SurgiCheck patient sees each day after surgery: consent, a pain score, opioid use, and satisfaction with their pain management, branded for their surgeon’s practice.
VELYS™ portal: robot analytics and Patient Path
Johnson & Johnson MedTech’s VELYS™ portal on DocSpera. Surgeons see analytics from their robotic knee cases and run Patient Path care plans with outcome surveys, reminders, wound photos and high-pain alerts. Patients and admins get their own views.
Surgeon schedule and DocBox
The provider side of DocSpera: upcoming surgeries in the daily and weekly schedule, and each case’s DocBox with PACS imaging, the implant template, participants and readiness, the same cases device partners see in advance.
AI appointment agent conversation
How the AI appointment agent handles a patient’s text: answering from the appointment record, confirming, rescheduling, refusing a prompt injection, and handing off to staff. Each step is labelled as observed in sandbox runs or designed and in development.
Workflow · AI coordination engine
Scheduling, rules, exceptions and engagement running underneath.
HL7 message, end to end
Follow one SIU^S12 scheduling message from an EMR through the Excelsior gateway: MLLP receipt and ACK, field-by-field mapping, canonical event, schema validation, and fan-out to platform workflows.
Advanced Case Management
Advance notice of surgical demand for device companies. Each scheduled case reaches the device partner weeks ahead with imaging, templating and patient measurements, so ASCs get right-sized trays just in time instead of full consigned sets.
Imaging worklist auto-assign
When a case’s imaging can’t be matched automatically, it becomes worklist items for the operations team. Auto-assign spreads the work evenly and rebalances with the fewest possible moves.
Outreach planner and dispatcher
Pick an appointment and see exactly when and how the platform reaches the patient: quiet hours, time zones, SMS versus voice, delivery failure fallback, and what happens when the appointment moves.
Connector certification
Any scheduling system can plug into the platform by implementing five operations. This is the certification suite run against a reference connector, passing, then failing on purpose.
Data + integration
Excelsior, contracts and the data each workflow runs on.
Scheduler integration contract
The canonical, signed-webhook contract Concentra’s systems use to push appointments, centers and shifts into the platform. Browse the schemas or build a payload.
FHIR R4 bundle builder
The tool used to define the FHIR R4 bundles Excelsior produces from Kaiser’s infusion-scheduling files for delivery to the WRAPT partner app.
Live interface network
Every inbound and outbound connection Excelsior runs today, by protocol: HL7 v2 over VPN and TLS, SFTP flat files, FHIR R4 export, PACS and partner APIs.