Launch · CathIQ™
Pilot and limited market release.
Winning has one meaning: the robot is the choice the majority of the time. That share is the number behind utilization on every site, and the loop is how a launch succeeds beyond the pilot.
Before and after the sale
Eight steps, each shown in the demo.
- 01
The room is won
The system is chosen; everything above it depends on that.
- 02
Approvals
IT, biomed and privacy approve how the suite handles people and data. Review
- 03
Identity
Identity from the hospital directory, no passwords of its own. Plan
- 04
The first plan
Tomorrow's procedure lands on the phone the night before. Plan
- 05
The first proctored procedure
Booked on the hospital schedule, guided from home. Connect
- 06
The run reviewed
Phases tagged, the clip shared inside the hospital's terms. Review
- 07
The rehearsal
Built on the next anatomy, weighted toward what Review flagged. Train
- 08
The record
The committee reviews the readiness record under its own criteria. Train
Who buys, who uses, who approves
Three groups, three conversations.
- Who buys
The service line and the program lead
Faster new operators, which fills schedules, and a record the hospital uses to credential its own people. Proctor travel, supervision hours and the time to a first procedure alone come off a staffing budget the service line already controls.
- Who uses
Two clinicians at once
The one who wants to get better and the one who wants to get home. The same phone moments serve both.
- Who approves
IT, biomed, privacy and the committee
IT and biomed own the room network, privacy sets the sharing terms, and the committee keeps the review and the decision.
Pilot
Up to ten sites. Approved, used, a reference site.
- What has to be proven
- Each site goes live, gets used on its own procedures, and the hospital approves how the suite handles its people and its data.
- The measures
- Time to go live. Time to first procedure. Active clinicians per site. Procedures per system per month, a baseline in the first ninety days. Time to working alone, in proctored procedures per operator. Engagement between procedures: sessions from a phone, bookings by clinicians.
- Site readiness
- Capture installed with IT and biomed. Identity from the directory. Sharing terms set during contracting. A proctor network the first operators can reach from a phone.
Limited market release
Ten to fifty sites. Repeatable without the first team in the room.
- What has to be proven
- It repeats without the first team in the room, and demand repeats beyond the pioneers.
- The measures
- Procedures per system per month against the pilot baseline. Time to working alone, trending down. Proctor capacity: operators per proctor, specialist minutes per procedure. Engagement between procedures, for each clinician, each week. Sites live on the template. Software attached at install.
- The gate
- Limited release opens when a site the first team never visited goes live on the template, gets used, and its committee reviews a record the suite assembled.
- Why Connect leads
- The one application that takes two people, so its value compounds with every site added. It decides how many clinicians ever see the system work.
From experience
Three notes, in short form.
- Pilot
Sign in should land on the clinician's day.
What stalled: a generic dashboard after sign in got delegated to a coordinator. What I would do differently: open onto the clinician's own procedure, which is what clinicians open themselves.
- Limited release
Procedure schedules move, so the session moves with them.
What stalled: the most common reason a remote session was lost was the procedure schedule changing after the session was booked, more often than bandwidth. What I would do differently: book on the hospital schedule from the start.
- Pilot
Settle data governance before a feature is promoted.
What stalled: a feature was promoted as central to the clinician workflow, and end users could not use it because data governance had not been set during contracting. What I would do differently: settle the terms with the right stakeholders before the launch message goes out.
The rest are titles in the demo, and a conversation.
Thirty minutes on Google Meet.
Target types only. No results are claimed; the measures are what a program would instrument. CathIQ is a trademark of Jake Isley.