Predictika · Transcatheter heart valve case orders

An AI sales agent's heart valve case order, checked before it goes out

An AI sales agent prepares an order for a transcatheter heart valve case: the valve size chosen from the patient's CT annulus area, the delivery system, the introducer sheath and the vessel access. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the sizing and compatibility rules and returns a verdict, every reason and the figures it computed.

Scope: SAPIEN 3 / SAPIEN 3 Ultra valve case orders: valve size against CT annulus area, COMMANDER delivery system, introducer sheath and minimum vessel diameter. See everything this validator covers

This validator models SAPIEN 3 and SAPIEN 3 Ultra valve case orders as described in the public instructions for use, not just the scenarios shown below.

  • Valve size — the 20, 23, 26 and 29 mm valves are each sized for a range of CT annulus areas; an area outside the range of the chosen size is blocked, and an area that fits two sizes goes to a person to confirm.
  • Delivery system — each valve size has its own COMMANDER delivery system (20, 23, 26 and 29 mm), and the 29 mm system uses a 16F introducer sheath set or equivalent.
  • Vessel access — the minimum vessel diameter is 5.5 mm for the 20, 23 and 26 mm valves and 6.0 mm for the 29 mm valve.

Any SAPIEN 3 / SAPIEN 3 Ultra valve case order that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (hospital contract pricing is not public, so this validator produces no price build-up or line-item quote), other Edwards valves and monitoring products, clinical decisions, and delivery routes other than the table values applied here as stated.

The AI sales agentBuilds the valve case order from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

8 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI sales agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      
Waiting for the call.

Where rules-based CPQ gets it wrong

Click to expand

Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

What the validator caughtTypical rules-based CPQPredictika
A valve size that must fit the measured annulus areaOnly with care
Each size has its own area range; a rule per size works, but the ranges overlap and have to be kept in step with the instructions for use.
The area is compared with the range of the chosen size on every call, and areas that fit two sizes are flagged for a person.
A delivery system that must match the valve sizeOnly with care
A product rule per size pairing. It works, but every new size or model is another set of rules to maintain.
The valve and delivery system are in one request and the pairing is checked with every other rule.
A minimum vessel diameter that depends on the valve sizeOnly with workarounds
The limit depends on the size on one line and a patient measurement on another, so it needs a cross-line rule that interacts with the rest.
Every choice and measurement is in one request, so the conflict is found whichever order they arrive in.
A sheath requirement that applies to one size onlyOnly with workarounds
A rule that applies to a single size of one product against an accessory on another line, easy to miss in a generic rule set.
Size and sheath are checked together on every call.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the order is saved or a step is completed, so a rep often fixes one error and meets the next.
All findings come back together, whatever order the choices arrived in.

What this validator catches: findings from its test cases

Click to expand

Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.

1The CT annulus area is 272 mm2; the 20 mm valve is sized for 273 to 345 mm2.
2The CT annulus area is 684 mm2; the 29 mm valve is sized for 540 to 683 mm2.
3The CT annulus area is 500 mm2; the 23 mm valve is sized for 338 to 430 mm2.
4The 26 mm valve needs the 26 mm COMMANDER delivery system; the order has the 23 mm one.
5The 20 mm valve needs the 20 mm COMMANDER delivery system; the order has the 29 mm one.
6The minimum vessel diameter for the 26 mm valve is 5.5 mm; the vessel diameter on the order is 5.4 mm.
7The minimum vessel diameter for the 29 mm valve is 6.0 mm; the vessel diameter on the order is 5.9 mm.
8The 29 mm system uses a 16F introducer sheath set or equivalent; the order has a 14F set.
9The CT annulus area of 340 mm2 falls in the range of two valve sizes; a person should confirm the size choice.
10The CT annulus area of 430 mm2 falls in the range of two valve sizes; a person should confirm the size choice.
11The CT annulus area of 545 mm2 falls in the range of two valve sizes; a person should confirm the size choice.
12The CT annulus area is 547 mm2; the 26 mm valve is sized for 430 to 546 mm2.
13The 20 mm valve needs the 20 mm COMMANDER delivery system; the order has the 23 mm one.
14The CT annulus area is 500 mm2; the 29 mm valve is sized for 540 to 683 mm2.
15The 29 mm valve needs the 29 mm COMMANDER delivery system; the order has the 20 mm one.
16The minimum vessel diameter for the 29 mm valve is 6.0 mm; the vessel diameter on the order is 5.0 mm.
17The CT annulus area of 338 mm2 falls in the range of two valve sizes; a person should confirm the size choice.
18The CT annulus area is 337 mm2; the 23 mm valve is sized for 338 to 430 mm2.

Scenarios and results

Click to expand

The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

1. Valve size, delivery system and vessel: A 23 mm valve with a 26 mm delivery system for a narrow vessel

The agent's request. Please order a 23 mm SAPIEN 3 valve with the 26 mm COMMANDER delivery system for a patient with a CT annulus area of 480 mm2 and a vessel diameter of 5.2 mm. It is ready to send.

Verdict: Blocked.

  • Annulus area outside the valve size range. The CT annulus area is 480 mm2; the 23 mm valve is sized for 338 to 430 mm2.
  • Delivery system does not match the valve size. The 23 mm valve needs the 23 mm COMMANDER delivery system; the order has the 26 mm one.
  • Vessel too small for the valve size. The minimum vessel diameter for the 23 mm valve is 5.5 mm; the vessel diameter on the order is 5.2 mm.

2. Valve size, delivery system and vessel: The agent resubmits after fixing the errors

The agent's request. Please order a 26 mm SAPIEN 3 valve with the 26 mm COMMANDER delivery system for a patient with a CT annulus area of 480 mm2 and a vessel diameter of 5.6 mm. It is ready to send.

Verdict: Allowed.

  • Case summary. 26 mm valve for an annulus area of 480 mm2; the minimum vessel diameter is 5.5 mm.

3. Large valve, delivery system and sheath: A 29 mm valve with a 26 mm delivery system and a 14F sheath

The agent's request. Please order a 29 mm SAPIEN 3 valve with the 26 mm COMMANDER delivery system and a 14F introducer sheath set for a patient with a CT annulus area of 620 mm2 and a vessel diameter of 5.8 mm. It is ready to send.

Verdict: Blocked.

  • Delivery system does not match the valve size. The 29 mm valve needs the 29 mm COMMANDER delivery system; the order has the 26 mm one.
  • Vessel too small for the valve size. The minimum vessel diameter for the 29 mm valve is 6.0 mm; the vessel diameter on the order is 5.8 mm.
  • 29 mm valve needs a 16F sheath. The 29 mm system uses a 16F introducer sheath set or equivalent; the order has a 14F set.

4. Large valve, delivery system and sheath: The agent resubmits after fixing the errors

The agent's request. Please order a 29 mm SAPIEN 3 valve with the 29 mm COMMANDER delivery system and a 14F introducer sheath set for a patient with a CT annulus area of 620 mm2 and a vessel diameter of 6.2 mm. It is ready to send.

Verdict: Blocked.

  • 29 mm valve needs a 16F sheath. The 29 mm system uses a 16F introducer sheath set or equivalent; the order has a 14F set.

5. Large valve, delivery system and sheath: The agent resubmits after fixing the errors

The agent's request. Please order a 29 mm SAPIEN 3 valve with the 29 mm COMMANDER delivery system and a 16F introducer sheath set for a patient with a CT annulus area of 620 mm2 and a vessel diameter of 6.2 mm. It is ready to send.

Verdict: Allowed.

  • Case summary. 29 mm valve for an annulus area of 620 mm2; the minimum vessel diameter is 6.0 mm.

6. Small valve at the edge of its range: A 20 mm valve with a 23 mm delivery system

The agent's request. Please order a 20 mm SAPIEN 3 valve with the 23 mm COMMANDER delivery system for a patient with a CT annulus area of 340 mm2 and a vessel diameter of 5.5 mm. It is ready to send.

Verdict: Blocked.

  • Delivery system does not match the valve size. The 20 mm valve needs the 20 mm COMMANDER delivery system; the order has the 23 mm one.
  • Annulus area fits two valve sizes. The CT annulus area of 340 mm2 falls in the range of two valve sizes; a person should confirm the size choice.

7. Small valve at the edge of its range: The agent resubmits after fixing the errors

The agent's request. Please order a 20 mm SAPIEN 3 valve with the 20 mm COMMANDER delivery system for a patient with a CT annulus area of 340 mm2 and a vessel diameter of 5.5 mm. It is ready to send.

Verdict: Needs approval.

  • Annulus area fits two valve sizes. The CT annulus area of 340 mm2 falls in the range of two valve sizes; a person should confirm the size choice.
  • Case summary. 20 mm valve for an annulus area of 340 mm2; the minimum vessel diameter is 5.5 mm.

8. Small valve at the edge of its range: The agent resubmits after fixing the errors

The agent's request. Please order a 23 mm SAPIEN 3 valve with the 23 mm COMMANDER delivery system for a patient with a CT annulus area of 380 mm2 and a vessel diameter of 5.5 mm. It is ready to send.

Verdict: Allowed.

  • Case summary. 23 mm valve for an annulus area of 380 mm2; the minimum vessel diameter is 5.5 mm.

Narration transcript

Click to expand

The text of the narrated walkthrough, step by step.

  1. Welcome to a demo of Predictika's Validator. An AI sales agent prepares an order for a transcatheter heart valve case: the valve size chosen from the patient's CT annulus area, the delivery system, the introducer sheath and the vessel access. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the sizing and compatibility rules and returns a verdict, every reason and the figures it computed.
  2. I will start with the first request by the agent.
  3. The agent says. Please order a 29 mm SAPIEN 3 valve. It is ready to send. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with three findings, all in one answer. The 29 mm valve needs the 29 mm COMMANDER delivery system; the order has the 26 mm one. The minimum vessel diameter for the 29 mm valve is 6.0 mm; the vessel diameter on the order is 5.8 mm. The 29 mm system uses a 16F introducer sheath set or equivalent; the order has a 14F set.
  6. The validator returned three blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the quote are checked against each other.
  7. What this shows: for a delivery system that must match the valve size, a rules-based CPQ is error-prone for this.
  8. Now the agent resubmits.
  9. The corrected request. It changes the delivery system to 29 mm COMMANDER and the vessel diameter to 6.2.
  10. It calls the validator again.
  11. Still blocked, with one finding, all in one answer. The 29 mm system uses a 16F introducer sheath set or equivalent; the order has a 14F set.
  12. Two findings cleared. Still blocking: 29 mm valve needs a 16F sheath.
  13. The agent resubmits once more.
  14. The revised request. It changes the introducer sheath set to 16F.
  15. It calls the validator once more.
  16. This time the validator clears it.
  17. The earlier finding is cleared.
  18. Three problems caught in one call, fixed in two passes, and a clean quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.