[object Object]

MultiScale Health Networks: Helping clinicians make sense of data

Industry

Healthcare

Company Size

30

Location(s)

Seattle, WA

MultiScale Health Networks is a healthcare startup based out of a hospital in Seattle. Their customers are the clinicians themselves — “the people that touch other people and save lives,” as Stacey Kinkead, Chief Product Officer at MultiScale, puts it. It’s no secret that the American healthcare system often suffers from inefficiencies, like the inability to effectively share patient data across providers, or analyze what’s causing the bottlenecks in ER patient processing time. MultiScale Health Networks was created to address some of the problems that clinicians face in getting their hands on the right patient data at the right time. MultiScale Health Networks creates the Hive product suite and Clubhouse helps them put the information in the hands of the healers.

Scaling Up

When Chris Drackett, lead frontend developer and UX designer, first joined MultiScale, the company was much smaller and they were using Trello. “It wasn’t scaling very well for the size of our team, though, and it didn’t have a lot of features that normal issue-trackers have — like, it wasn’t linking to our code at all, and it just wasn’t working out well for the size we were getting to be.” From there, Chris started looking at other tools such as GitHub Issues and GitLab’s tracking system, and eventually came across Clubhouse. It had a lot of the functionality that he liked (and that the team found useful) from Trello, but had more of the power that others on the team were looking for, like burndown charts and productivity reports. “We started using it on our team and it grew out to other teams, and at this point, almost every person in the company is using it.”

From there, Chris started looking at other tools such as GitHub Issues and GitLab’s tracking system, and eventually came across Clubhouse. It had a lot of the functionality that he liked (and that the team found useful) from Trello, but had more of the power that others on the team were looking for, like burndown charts and productivity reports. “We started using it on our team and it grew out to other teams, and at this point, almost every person in the company is using it.”

I think that’s one of the most powerful things about Clubhouse — every team, whether it’s Applications or DevOps, has a different workflow that they’re using, and it’s been really easy to customize to their needs without a large time investment.Nic Myers, Technical Product Manager

Development and Data

Their teams include Applications, DevOps, Platform, and Pipeline. Out of these teams, some are more focused on development and some are focused on ensuring data integrity.

The Applications team has a sub-team that’s strictly focused on ensuring the displayed data is accurate, and there are added steps in the workflow (like “Ready for Validation”) to reflect the different steps needed to get a scope of work to completion. Their sub-teams are represented by different Projects in Clubhouse, with each story having different Projects assigned to it based on who’s working on it.

Within a single Applications team (there are multiple), there might be Front-end, Back-end Services, Data Validation, Data Research, Testing, and Product Management sub teams, each represented by Projects. If a sub-team wishes to get a greater understanding of what is assigned to them, they use the Clubhouse Workspaces view to quickly filter the work to be done.

In Clubhouse, the MultiScale team has found a great tool to support their teams’ Scrum workflow. With processes in order, they can more easily focus on making life better for clinicians and the patients.