Newgate Systems

Case study · Med tech

Product

Video calling, rebuilt for the operating room.

Avail Medsystems lets medical professionals connect, consult and collaborate on surgical procedures through remote telepresence.

Avail browser client during a remote surgical session
Client context
Avail Medsystems is a US med-tech company providing remote telepresence for surgical procedures.
The problem
The software behaved like a general video-calling tool. People in an operating room have different needs from someone at a desk, and the portal and in-call experience did not reflect that.
What Newgate owned
The platform engineering: the portal and the in-call telepresence experience across iPad, the in-room console and browser, built release by release. Passage Studio was the design team. Avail owned the hardware, the clinical requirements and the roadmap.
What went live
A rebuilt portal and in-call telepresence experience across iPad, the in-room console and browser, on a shared component system.
What followed
Newgate’s engagement ended well before Avail’s October 2023 software refresh announcement.
Client
Avail Medsystems
Industry
Medical technology, telepresence
Region
United States
Platform
iPad, console and browser clients
Credits
Design by Passage Studio, engineering by Newgate Systems

01

The client

Avail puts a remote expert in the operating room: a specialist, a proctor or a device representative can see the procedure and advise in real time without travelling. The product spans an in-room console, tablets and a browser client, plus a portal for scheduling and managing sessions.

02

The problem

A surgeon cannot stop to find a button. Hands are occupied, attention is on the patient, and the people joining remotely range from clinicians to industry staff. Software modelled on office video calls asks for more attention than the room can give. The portal that sits around the calls had the same problem at a smaller scale.

03

Requirements

  • R1An in-call experience usable in an operating room
  • R2A portal for the scheduling and session work around each call
  • R3Consistent behaviour across iPad, console and browser
  • R4A component system so later changes stay consistent
  • R5Delivery in sprints alongside Avail's product roadmap

04

The solution

The work started from an audit of the existing software and a list of changes ranked by effort and value, which went into Avail’s roadmap. We then engineered the portal and the in-call experience in parallel, sprint by sprint, from Passage Studio’s designs, because together they hold most of the product’s functionality.

Why the two were done together: a session starts in the portal and happens in the call. Fixing one without the other leaves the seam between them, which is where users were getting lost.

05

The work

  • 01Audit and backlog. Existing software reviewed and changes ranked by effort and value.
  • 02Portal. Rebuilt flows for scheduling and managing each session.
  • 03In-call experience. The telepresence interface for iPad, console and browser: camera feeds, layouts, presets, telestration and the participant panel.
  • 04Component system. Shared components so each release stays consistent.
  • 05Sprints. Incremental releases alongside Avail’s product team.
TelepresenceiPadWebComponent systemMedical software

06

Outcome

3 touchpoints

On one system: iPad, console, browser

Sprint by sprint

Releases alongside Avail’s product team

One seam

Portal and call rebuilt together

Screens

More product work

Other records.

Next

Facing something like this?