Case Study: ZOLL Web Console

This post continues our series of interviews with users of Dojo. This time, we interview Eric W. Brown who led the technical team that created the ZOLL Web Console and ZOLL TBI Console during his days at ZOLL Medical (Eric is now with Iotopia Solutions). ZOLL is a resuscitation company known for its defibrillators. Its Web Console runs on its high-end mobile monitors and defibrillators and enables the device not just to stream waveform data live to browsers on desktops or mobile devices, but also to collect the streamed output from up to forty devices for a single display on a desktop browser. This makes it easier for nurses to monitor a whole ward of patients. The TBI Console helps provide additional information for emergency personnel treating traumatic brain injury patients and is displayed on a mobile device. So far as we know, these were among the first JavaScript-based medical products to receive FDA approval.

Q: How did you first learn about Dojo?

I’ve been using Dojo for years. Its Pythonesque “batteries-included” approach made it appealing for some internal mapping products I did at another company long ago back in the Dojo 0.4.1 days. I’ve been using it off and on for various projects since.

Q: Why did you choose Dojo?

A: For the ZOLL projects we needed a solution that could accommodate several developers working in parallel on a complicated application with high demands on performance. If streaming waveform data doesn’t get displayed at its destination within a tiny fraction of a second, it’s useless to the medical personnel.

Dojo’s modules and pub/sub capabilities allowed us to nicely isolate the different components developers were working on while still delivering excellent performance.

Dojo’s extensive selection of modules also saved us a lot of work outside our project domain, and its build system enabled us to get the tightly optimized components we wanted for our embedded devices.

Dijit’s built-in i18n features and DOH were also big wins for us.

Q: Were you previously using another toolkit?

A: No, it was Dojo from the get-go.

Q: What does your application or service do?

A: The ZOLL Web Console provides two primary capabilities: it enables a nurse to watch over up to forty connected patients on a single desktop browser, and it enables emergency personnel to see patient information on a different screen in addition to the one built into the monitor itself.

Q: How does your application use Dojo?

A: It’s built with Dojo from the ground up. Visual elements are made with Dijit, and Dojo core is used everywhere.

Q: Overall what is your experience with Dojo?

A: Very positive. ZOLL has now built two products using Dojo. If it had been a bad experience we wouldn’t have built a second one.

Q: What’s your favorite thing about Dojo?

A: I have a different favorite Dojo feature associated with each Dojo project I’ve worked on, and perhaps this is Dojo’s greatest strength: whatever it is one is working on, there’s bound to be something Dojo already has that’ll save time and effort.

Q: What are your future plans with Dojo?

A: I am now working at Iotopia Solutions rather than ZOLL, but when I left they were considering Dojo for additional projects. Here at Iotopia Solutions we’re using it on behalf of clients in their projects plus internally to provide nicer front-ends for output on our own tests.

Thanks!

Thanks Eric for telling us about your experience with Dojo. If you would like to share your experience with Dojo, please contact us.

2 thoughts on “Case Study: ZOLL Web Console

  1. I’m new to Dojo and I’m trying to understand how it compares to other libraries and frameworks. This might be relevant to some extent for others trying to determine how Dojo compares. It should be noted that Eric left ZOLL in 2014, according to this Facebook profile https://www.facebook.com/TheRealFeneric, which puts this “cutting-edge” use of Dojo a couple of years back. Since I am new to the toolkit I’m not familiar enough with it to knock it, but I think that if Dojo is posting in 2016 about the use of the toolkit in 2014 it definitely makes a statement.

    1. Case studies are published for a small minority of projects, because they require the consent of the company that created the applications, and they almost always trail the launch of an application by a year or two.

      That said, one of Dojo’s strengths is longevity (we’ve been going strong for more than 12 years). Code that was authored with Dojo nearly a decade ago should for the most part work today with minor fixes to major browser changes (though there are certainly much better things you could do to improve it).

      Today most of our efforts are focused on getting Dojo 2 released. Follow our progress at http://github.com/dojo/meta and https://dojotoolkit.org/community/roadmap/ .

      Finally, when choosing a technology, you should evaluate if it solves the needs and challenges you are trying to solve, in a way that you understand. A superficial analysis based on a case study seems a bit arbitrary.

Leave a Reply

Your email address will not be published. Required fields are marked *