Use case

Your health product needs a defined pilot boundary

Your clinical AI or device product has a pilot opportunity. Settle the EHR handoff or test configuration, with technical evidence and permission for patient use kept separate.

  1. ProblemA promising prototype still leaves the receiving team with unresolved work.
  2. DecisionChoose the integration, test configuration and ownership for one pilot.
  3. CTO selectionSelect experience at the health-system or device boundary your pilot needs.

Our network includes CTOs, engineering leaders,
and technical advisers with experience at and around companies such as:

IBM Stripe UBS Citi Fujitsu Wipro InHealth GSK TransUnion Deloitte J.P. Morgan
SAP NHS Marie Curie BBC Anthropic CMH Clinic SE Health Sartorius Illumina Achilles Therapeutics Prevayl

Health pilot blockers

Typical blockers concern one of two primary pilot lanes. Choose the lane and one unresolved handoff.

  • An unresolved EHR handoff

    Clinical AI / EHR: clinicians cannot inspect and correct the AI documentation draft where they work, or the receiving note's version is unclear. Manual transfer may remain sufficient; the gap needs evidence.

  • Bench behavior does not repeat

    MedTech device / wearable: bench behavior does not repeat when firmware, model and app versions change together.

  • Configuration and owner needed

    MedTech device / wearable: the next technical test needs a named configuration and receiving owner.

Set the pilot boundary

For one documentation flow or device configuration, identify the open decision and who will accept its evidence.

  1. The receiving EHR operation

    Clinical AI: which permitted EHR operation can receive the clinician-reviewed note?

  2. Where processing runs

    Clinical AI: where can each processing step run under the partner's data-use conditions?

  3. The next test configuration

    Device: which hardware, firmware, model and app configuration will the next test cover?

  4. An agreed human handoff

    Supporting use: which non-diagnostic support journey has an agreed human handoff?

  5. Who gives each acceptance

    For this pilot, which separate acceptances are needed, and who has agreed to give each?

Choose the next technical step

Request interface evidence, compare a test boundary or secure missing partner inputs before a new build.

  • Use the existing supported route

    If a supported EHR connector or component covers the need, keep it. Ask the supplier for interface evidence for your configuration; your existing lead verifies the fit with partner IT or the technical receiver.

  • Compare one disputed pilot boundary

    If EHR routes or processing locations remain disputed, use Technology assessment services to compare the open boundary. The CTO recommends a technical path; partner IT and data owners decide their conditions.

    Technology assessment services
  • Own the next test configuration

    When component changes lose the tested configuration, use Fractional CTO services for interface priorities and candidate builds for test. The technical receiver accepts the evidence, not permission for patient use.

    Fractional CTO services
  • Establish the missing pilot prerequisites

    If permitted data, a clinical partner or a qualified acceptance owner is missing, the sponsor secures those inputs first. This is prerequisite work for the sponsor, not a reason to commission a CTO or a new build.

Who accepts what

Technical evidence informs the pilot decision; the responsible qualified owners determine permission for patient use. Identify the relevant owners.

  1. Clinical lead

    Intended clinical use, clinical content and review.

  2. Privacy, data-protection and security owners

    Permitted data handling, access and retention.

  3. Partner IT

    Interface and environment access.

  4. Service owner, where relevant

    Receiving human queue and its response.

  5. Quality and regulatory owners

    Applicable route and approvals.

  6. Technical owner

    Interface, configuration, test and failure evidence.

Evidence for the next milestone

Agree one documentation flow or device configuration separately from the curator conversation. Proposed outputs may include the following; your team or chosen vendor implements changes.

Workflow and data-flow map
With named receiving owners.
Technical options
With interface assumptions and unresolved dependencies made explicit.
Technical test plan
Configuration-specific, naming who can stop or change tests.
Pilot handoff
Separating engineering findings, open issues and domain acceptance.

The CTO may hold agreed authority over technical priorities and candidate builds for test, not patient-use approval. Needed specialists participate and approve their scopes separately; CTO work neither supplies nor replaces their review, certification or assessment of clinical effectiveness.

Bring us your case

Bring the blocked EHR operation or device configuration and identify who will receive the next technical evidence. Use nonconfidential context, without patient records or restricted device data.

Pick a time
What we believe

We work best with founders who believe in what they are building

Every founder brings a different challenge. What stays the same is how we approach it.

Grand Rounds video session: David Carroll with CTOs Neil Catton and Edoardo Turelli, and curator Jane Vyshnova
David Carroll Founder of Euryan David came to Grand Rounds with two open questions he wanted pressure-tested before taking them to investors: how Euryan should handle LLM and cloud strategy across different client environments, and whether the core product wedge, dynamic FMEA/8D automation, was the right foundation to build the rest of the roadmap on.
Grand Rounds video session: Susie Williams with CTOs Neil Catton and Jerome MacGillivray, and curator Jane Vyshnova
Susie Williams Founder of LinkEDtohome Susie came to Grand Rounds with two questions she wanted pressure-tested before LinkEDtohome moved beyond its first school: how to scale the team and technology without building too far ahead of real demand, and what needed to be in place around AI liability, training and governance before broader adoption.
Grand Rounds video session with Alexander Gorrie, Krupa Shankar, CTO Berkan Sesen and curator Jane Vyshnova
Alexander Gorrie Founder Alex came to CTO Grand Rounds with several important technical decisions already being actively worked through. One question from the panel reframed the discussion: “How will you know that the result is actually good?” It sharpened the conversation around how those decisions should be sequenced and prioritised.
Grand Rounds video session with Tomas Jankauskas, CTOs Neil Catton and Thomas Döhler and curator Jane Vyshnova
Tomas Jankauskas Founder of Neural DEEP Tomas came to Grand Rounds with a question he'd been wrestling with while bringing AI-driven innovation into Toyota: which ideas to pursue, and how much to build before anything was approved, in an organisation where every new idea needs to pass through many hands.
Grand Rounds video session with Dr. Lars Zimmermann, CTO Reon Smits and curator Jane Vyshnova
Dr. Lars Zimmermann Founder of Ahead Care GmbH Lars came to Grand Rounds looking for an experienced second opinion on the hardware challenges facing MOIO, Ahead Care's wearable care technology. He wanted to explore practical options for the product's development and gain a fresh perspective from someone who had navigated similar challenges in medical wearables.
  • Products with a purpose

    Technology that delivers a real outcome for people, not technology for its own sake.

  • Energy and enthusiasm

    Founders and teams with the passion and drive to address a problem they have seen for themselves.

  • The story before the numbers

    The first question is what you are trying to do and why: what you saw and why you started.

  • Listening more than talking

    Nobody walks in to say “I know better.” We ask what drives a decision and what has not been considered, then work through the options together.

  • Understanding before fixing

    First the people, the business and the why, and what has and has not worked, so the first problem found does not start constant firefighting.

  • Experience, not just knowledge

    Modern and AI tools assist. Architecture, security, recovery and user experience still need people who have built and run real systems.

Select for the actual boundary

Health-platform integration and multidisciplinary device/software leadership are represented in our CTO network. Select against the interface or configuration your pilot actually needs.

Look for a CTO who can show:

  • EHR work tied to the required operation, version and receiving record.
  • Device integration across firmware, model and app configuration changes.
  • Processing-location decisions with named operators and data boundaries.
  • Technical handoff evidence kept separate from qualified domain approval.

For the curator discussion, identify the receiving record or test configuration and the specialist owners still needed. Fit and availability are confirmed separately.

Jane Vyshnova
About us

Jane Vyshnova

Curator of Grand Rounds

I've spent 12 years building partnerships between founders, technical teams, and the people who fund them. Somewhere along the way I noticed the same pattern over and over: brilliant fractional CTOs, and founders who had no idea they existed, let alone how to reach them.

Grand Rounds is my answer to that gap. The name comes from medicine, when a case is hard, doctors don't decide alone, they bring senior specialists around the table together. I built the same thing for technology.

"People need people. Nothing else works."

I'm the one who listens to your problem, asks the questions you didn't think to ask yourself, and explores which experience in the network is relevant to it.

Jane has been working across the industry since 2014, connecting startups, retailers, B2B companies, manufacturers, and expert teams around meaningful partnership opportunities.

Her experience includes building bridges between companies and ecosystems, ready-made technology solutions, manufacturing-focused initiatives, and sustainability-driven projects. Over the years, she has helped create practical collaboration models between businesses, technology providers, and industry experts.

For Jane, partnership strategy is not just part of the work - it is the DNA of her professional experience. Her focus is on identifying where teams, platforms, products, and industries can strengthen each other and turning those connections into real opportunities.

What founders say after their Grand Rounds session

It's like a hackathon for your real business problems. You bring your challenges and bright minds work on them - with no obligation, no pressure. I walked away with perspectives on investors, encryption solutions, and a connection that could directly benefit my product. Honestly, why rely on one mind, when you can have many?

Saif Alam
Saif Alam CEO at Keepsta

It was an incredibly welcoming space to connect with senior technical minds I wouldn't normally have access to as a non-technical founder. A fantastic opportunity to get real, honest answers to the challenges I was facing - and to walk away with meaningful connections who continue to support me.

Audrey Lee
Audrey Lee Founder of Lumi

CTO Grand Rounds was the best event by far. This is where the founder world and the tech world actually merge, with real introductions instead of leaving people to stay siloed. I was deep in a conversation about cybersecurity and feedback loops - practical advice I could act on immediately.

Hélène Le Roux
Hélène Le Roux CEO at Trippin'

What I valued most was the mix of CTO styles at the table - some all-in on AI, others more measured. As a founder, you don't want someone else's answer, you want enough perspectives to make your own call. I walked away with two strong contacts - people who hit the mark on build support, strategic fit, and investor credibility. The relaxed format made room for real technical conversation, not just quick decisions. Worth coming back for.

Hew Williams
Hew Williams Founder of Zeorb
FAQ

Before committing the pilot