Decide whether a procedural workflow is ready for Seldinger discovery.

Use this worksheet before requesting access. It keeps early conversations focused on public-safe workflow fit, data boundaries, deployment constraints, and measurable evaluation targets.

Workflow fit

The decision loop is frequent, visible, and variance-sensitive.

Good fit: Teams can point to a repeatable moment where planning, imaging, or intraoperative judgment changes the case trajectory.
Needs scoping: If the pain is mostly scheduling, billing, or generic documentation, it is probably outside Seldinger's first product wedge.

Bring to discovery

Procedure family and approximate case volume
Where the handoff or intraoperative decision currently breaks down
Which team member owns the decision today

Data boundary

The site can describe available artifacts without sharing PHI up front.

Good fit: Discovery can start with de-identified examples, public-safe workflow descriptions, and clear data-governance boundaries.
Needs scoping: If access requires raw PHI, private exports, or unresolved licensing questions before a conversation can begin, scope the boundary first.

Bring to discovery

Imaging modalities and systems involved
Whether example cases can be de-identified or synthesized for discussion
Who approves data-sharing and review workflows

Deployment path

The first value can arrive without new hardware in the critical path.

Good fit: The workflow can start as planning support, live perception support, coaching, or quality review around existing imaging infrastructure.
Needs scoping: If the only useful version requires robotics, actuation, or a regulated clinical claim on day one, it is a later-stage path.

Bring to discovery

Current room setup and imaging systems
Where a software-only assistant could sit in the workflow
Constraints for network access, review stations, and room display

Evaluation target

There is a measurable signal for safer, faster, or more consistent work.

Good fit: The team can name a metric, review artifact, or outcome proxy that would show whether procedural intelligence is helping.
Needs scoping: If success is only a broad aspiration, define the review target before building a partner pilot around it.

Bring to discovery

Baseline metric or review cadence
Decision quality, time, complication-watch, or training signal to improve
Who reviews results and decides whether the loop is useful

If the signals are clear, send the worksheet. If the workflow is still vague, start from concrete use cases first.

Send readiness worksheet Compare use cases