<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by MindSea on Medium]]></title>
        <description><![CDATA[Stories by MindSea on Medium]]></description>
        <link>https://medium.com/@MindSeaTeam?source=rss-3b53535c9a60------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7b3bGOCZqcL95IaRSL7uPw.png</url>
            <title>Stories by MindSea on Medium</title>
            <link>https://medium.com/@MindSeaTeam?source=rss-3b53535c9a60------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:13:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@MindSeaTeam/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What the VA Can Teach You About Real Healthcare Interoperability with FHIR — MindSea]]></title>
            <link>https://medium.com/mindsea-development-inc/what-the-va-can-teach-you-about-real-healthcare-interoperability-with-fhir-mindsea-1ebc08c4c19d?source=rss-3b53535c9a60------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ebc08c4c19d</guid>
            <category><![CDATA[healthtech]]></category>
            <dc:creator><![CDATA[MindSea]]></dc:creator>
            <pubDate>Wed, 09 Jul 2025 19:17:47 GMT</pubDate>
            <atom:updated>2025-07-10T12:51:53.038Z</atom:updated>
            <content:encoded><![CDATA[<h3>What the VA Can Teach You About Real Healthcare Interoperability with FHIR</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2wQod19vGwS3omr0.jpg" /></figure><p>Our guest this episode was Brian Book, President at Book Zurman. Brian joined Reuben Hall to discuss healthcare interoperability, and how veteran-led innovation is reshaping digital health.</p><p>“As a disabled veteran, I am a consumer of the VA product. And so I have a vested interest in making sure that the work that we do not only benefits me, but also benefits other veterans and disabled veterans.” — Brian Book on building meaningful, standards-based digital health tools.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FxtDq-W8XApw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DxtDq-W8XApw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FxtDq-W8XApw%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a2b5a54edc5561eb334b4309a2a4dd81/href">https://medium.com/media/a2b5a54edc5561eb334b4309a2a4dd81/href</a></iframe><p>Find <em>Moving Digital Health</em> on <a href="https://podcasts.apple.com/us/podcast/moving-digital-health/id1610546047">Apple Podcasts</a> and <a href="https://open.spotify.com/show/0OXaAaHQkfa4cfUg1BKf4M">Spotify</a>, and <a href="https://share.hsforms.com/1EgOC1hDpQjmPHAmNnKQc5Q185gy?__hstc=71280975.d141b9bdeedddd7967e2f47b2e5014ca.1639602052475.1661870519476.1663607831453.158&amp;__hssc=71280975.3.1663607831453&amp;__hsfp=817607603">subscribe to the MindSea newsletter</a> to be notified about future episodes.</p><p><strong>Read Transcript:</strong></p><p>Reuben Hall (00:01)<br>Welcome to the MindSea podcast series, Moving Digital Health. Our guest today is Brian Book, president at Book Zurman, incorporated and healthcare interoperability expert at CareNexus. Thanks for joining us today, Brian.</p><p>Brian Book (00:16)<br>Thanks for having me. Happy to be here.</p><p>Reuben Hall (00:19)<br>Great, could you start by telling us a little bit about your background?</p><p>Brian Book (00:23)<br>Sure. So Book Zurman Incorporated started in 1996. And in 2010, we decided to move into the government space. And so we’ve worked as a government contractor since 2010 and almost exclusively for the Veterans Administration since we started.</p><p>Over the years have worked with just about every part of the VA except for cemetery. And we, for the last 15 years or so, have been representing the VA in the interoperability standards development community. And we have leadership roles in those communities like HL7 and OMG and ISO and a bunch of others. And we actively participate in the development of health care standards on behalf of the VA. We vote for them in those communities and then we bring that subject matter expertise back to the VA and advise them on interpretation and implementation of their standards.</p><p>Reuben Hall (01:37)<br>So you’ve had a remarkable journey from serving in the US Army during the Gulf War to leading healthcare IT innovation. What inspired you to transition into healthcare technology specifically?</p><p>Brian Book (01:51)<br>The majority of my professional experience was in manufacturing. And when I got out of the military, I worked in circuit board manufacturing and glass and plastic and building products. I’m a disabled veteran. And I read an article that the federal government was setting aside contracts for disabled veteran-owned companies.</p><p>One of the friends, Craig Zurman, who’s the Zurman of Book Zurman, him and I went to high school together and I was living in Texas and I moved back to Florida where I am now. And I was fishing with him and I had told him that I read that article about them setting aside work for veteran companies. And he’s been an entrepreneur his whole, his entire career.</p><p>And I said, you know, we should we should start a company and try to do something with this. And he blew me off and fast forward to Christmas time. And he goes to a Christmas party and he meets a pretty high up VA guy who says, if you really want to do something, you should go find a disabled veteran and start a company. And so that’s how the company got started in the first place. But we, over the years, we did a lot of work around program and project management for the VA. And we met a group of people that were in the interoperability space. And at the time it was really super niche and behind the scenes and hardly anybody knew anything about healthcare standards or anything related to electronic health records. The VA has pretty much been a leader in electronic health records over the years. And a lot of the things that they were doing were decades ahead of other parts of healthcare from an IT standpoint. And so we met a group of people and we helped them to continue to do the work that they were doing and that moved us into the interoperability space.</p><p>Reuben Hall (03:55)<br>Okay, interesting. So it really is a success story of the government supporting veterans and disabled veterans to become entrepreneurs and really add value to the system.</p><p>Brian Book (04:26)<br>Absolutely, without the set-aside programs that they have, it makes it very difficult for small companies to compete against the big monsters like Deloitte and Booz Allen and those types of companies. So there’s a lot of expertise that is in those small companies. A lot of those large companies will tell you that none of the small businesses have anything that they don’t have in exponential scale from small business.</p><p>But a lot of small business has a level of expertise that those large companies struggle in a lot of ways to try to capture. So it makes that competitive landscape a little fairer from a financial perspective. So I’m really happy that the government has put those programs into place.</p><p>Reuben Hall (05:31)<br>And I would assume from being disabled, you’ve had your own journey through the healthcare system. And how has that shaped your drive to improve the patient experience through technology?</p><p>Brian Book (05:47)<br>Absolutely. I’m as a disabled veteran, I am a consumer of the VA product. And so I have a vested interest in making sure that the work that we do not only benefits me, but also benefits other veterans and disabled veterans. So, I’m hypersensitive to the mission of trying to deliver the best healthcare that can be delivered to veterans and interoperability is a big piece of that.</p><p>So the VA and the DOD for a couple of decades now have had a level of interoperability between them that no other healthcare organization has. And I think they get a bad rap in the media trying to portray the VA systems and the DOD systems as antiquated. But in a lot of ways, they can do things that nobody else can setting the standard and a lot of the work that we’ve done in the community is the community benefits from the money that VA and DOD has spent to foster development of solutions, interoperability solutions and healthcare standards that never would have happened if it wasn’t for them.</p><p>Reuben Hall (07:11)<br>I don’t think a lot of people know that VA is actually leading in some of these categories when it comes to interoperability. And I know Book Zurman has been a key contributor to healthcare standards over the years. What are some of the milestones or wins that you’re most proud of there?</p><p>Brian Book (07:32)<br>I think that our work with FIRE has been pretty key in pushing that standard forward. We started working in that, in those workspaces and in that part of the community since its inception. And as I’ve said, we have leadership roles in those work groups that have allowed us to shape how that particular standard has evolved over the years.</p><p>And we’re finally at the point now where CMS is trying to roll out the requirements for the private sector to leverage fire as a standard. And so I’m really proud that we’re finally at a point where we’re starting to see implementations in the community that at some points I thought we would never see.</p><p>Reuben Hall (08:29)<br>And could you walk us through the mission behind CareNexus? How is that different from the work you do at Book Zurman?</p><p>Brian Book (08:36)<br>So, CareNexus was a proof of concept that there’s an organization in the federal government called SAMHSA that built a care coordination platform that was called Omnibus CurePlan. And we did some work with them to try to shape that product when there was a change in administration, the funding for that project went away.</p><p>And so, CareNexus originally was the continuation of the work of Omnibus Care Plan. And in a lot of ways, it was a proof of concept leveraging the implementation guides that we created in the standards community for things like FHIR and eCare plan and several other healthcare related standards where we took the implementation guides from the community that we had created and built CareNexus as a platform, a care coordination platform to support care coordination within a patient’s healthcare journey. And it was originally set up to be a patient facing or provider facing product. And now that Fire is finally starting to get traction in the community and that there are Fire endpoints that we can connect you to pull patient related data. We’re starting to move CareNexus from a provider facing tool to a patient centered tool. for example, people that have more than one chronic condition and are dealing with multiple comorbidities, it’s really difficult for multiple providers to share information with each other.</p><p>And so from a care team perspective, the care teams are scattered and the doctors don’t talk to each other. And it makes it really difficult for a patient to try to keep all of that healthcare information organized and consolidated in a way where they’re not having duplicate tests done and have information readily available that they can provide to a doctor when they see them that ensures that the doctor sees a full spectrum of what their care is rather than just the part of their healthcare journey that that doctor is providing to the patient. And so it’s filling a void that the community had, or the patient side of the community has had for, you know, since they started collecting patient data for patients.</p><p>Reuben Hall (11:38)<br>And CareNexus, is that strictly for integration with VA as well, or is that outside and available for other pairs?</p><p>Brian Book (11:55)<br>It’s available to anybody who wants to leverage that. And if you want to find more information about it, you can go to carenexus.app and find more information about it. But it’s not, and this is the beauty of healthcare standards, is because it’s a fully standards compliant platform, can be used, anybody can use it. So it’s not locked into just the VA or locked into any other EHR providers software ecosystem.</p><p>And it also has a smart on fire app store. And so we can build apps within care nexus that extend the functionality of the software so that we can rapidly build solutions that meet workflow needs that would take months or years in other platforms to develop. And then those smart on fire apps can also be launched from within other EHR platforms that are FHIR compliant. So anybody that’s FHIR compliant could take those smart on FHIR apps and launch them within their system. And so it’s not locked into a single platform.</p><p>Reuben Hall (13:14)<br>Excellent. Yeah, I’ll have to look into that more as well. It’s very interesting. I know working with the Department of Veteran Affairs must be both challenging and rewarding. How hard has it been to watch the impact of the recent funding cuts?</p><p>Brian Book (13:33)<br>It definitely has been a challenge, at one point Doge completely wiped out everything that we were doing at the VA. So every VA contract that we had was canceled initially. so I want to, although that was very difficult for us and we’re still trying to recover from it. The one thing that I will say is that Doge didn’t come in and just willy nilly kill everything. They came in and they said, if you can justify the work that you have, you can keep it. And so all they asked was that the owners of contracted work create a justification for the work that they’re doing. And so a lot of, and I’m going to say this and it’s going to get me in trouble, but a lot of the program and project related people, they threw themselves on the floor and they whined that Doge was taking everything away.</p><p>And they came in a second time and said, justify it and you can keep it. And in a lot of cases, they didn’t even care about the substance of the justification. They just wanted them to take the act of justifying the work that they had. And anybody that justified the work got to keep the work and the ones that didn’t take the time or energy to write that justification, all of the work went away. And so the work that we had that where our, the program people that we worked with were willing and able to write those justifications, that work came back to us. And we had others that didn’t write the justifications and all of that work went away.</p><p>So there are some programs that got crippled because they didn’t justify the work and others that may have been hurt a little bit, but that they’re still going. but it was, it really was an exercise that needed to happen within the VA. But I’m disappointed that they didn’t look at the Cerner implementation or the Oracle Cerner project that they have going on because that one is, it started as a $10 billion contract and it quickly went to $16 billion. It’s almost 10 years into that contract now. And there’s only a handful of VA facilities where they’ve implemented that software. And so the projections right now are that they need another 10 years and $50 billion to finish that project.</p><p>You know, we lobbied in the beginning when they were getting ready to implement that contract for the VA to go in a different direction. But that decision was made. And if it was up to us, would have we would have advised them to to create a data rights contract that basically says that anything all the patient records at the VA are owned by the VA and that they’re going to move all that into a standards-based format like FHIR, and then require the community to also adopt FHIR and build solutions to meet the requirements of the VA in FHIR.</p><p>And then you would have had an entire ecosystem working on solving problems for the VA instead of one monster company working on it who so far has really struggled to deliver anything. And even the implementations that they have so far, the few that they have completed, the capacity in those facilities is less than what it was before they started. So it’s hard for me as a taxpayer and as a veteran to justify how much money is being spent for so little return.</p><p>Yeah, that is, it’s hard to fathom the amount of money going towards that and the lack of execution and the time it’s taking. that so much money has been poured into that they’ll never switch away because it’s, we spent too much money onboarding Cerner to start all over from scratch with another solution right, and they’re just so embedded into the system.</p><p>There’s 147 VA hospitals. They’ve implemented that solution in like six. And so even though they’ve spent a ton of money, it’s never going to get any better. They’ve already proven that they can’t make the progress that they thought that they could make in the timeframe that they said that they could make it. if they quit now, it’s not like they lose a whole lot Vista is still in place, so they could put money into Vista modernization and fire all those projects back up again. And I think they would be in a better place than they are now. like I said earlier that the VA gets a bad rap. They try to portray that Vista is old and antiquated, but there are more than 1200 implementations of Vista outside of the VA.</p><p>So the VA isn’t the only one that is using that platform it’s based on the same software operating system that Epic is. So if VA is antiquated, then so is Epic. And Epic is number one as an EHR probably in the world now. So I think that that rings a little hollow for me that Vista is not worthy of continuing to be developed.</p><p>Reuben Hall (20:05)<br>Right, so if you were to go back into the past before they made the move to Epic, and it was up to you, what do you think the right way forward would have been or could be now?</p><p>Brian Book (20:20)<br>Well, there are two approaches that I think that they could have done. If they were going to use a COTS product and off the shelf product like Epic or Cerner, I think that they’ve already implemented Cerner in the DoD. It’s Oracle now, but Oracle Cerner, they already implemented it in the DoD. And if you really wanted to create true interoperability in the community, they should have contracted Epic to do the installation at VA and make the requirement that Oracle and Epic have to be interoperable with each other at the VA. And if they did that, then not only would you have interoperability between the two biggest EHR providers on the planet, but you would drive the development between the two of them to create interoperability that would spill over into the private sector. And if you didn’t want to do that, then like I said earlier, the other approach that I would have done is to set up a data rights contract and say everything is going to be in the FHIR format now. so anybody who wants to build a FHIR solution, you can market and sell and the VA and the community can leverage those FHIR solutions in that format.</p><p>And then you’re, you you become the, you drive the community to adopt standards rather than trying to force the proprietary EHRs to adopt standards because there’s no benefit for them to adopt standards. It destroys their stranglehold on patient data. So they’re not If they were going to become interoperable, they would have already done it.</p><p>Reuben Hall (22:20)<br>And what are some of the common challenges organizations face when implementing interoperability? Why is it so hard?</p><p>Brian Book (22:31)<br>It’s hard because I think that the approach to trying to get the community to adopt standards has been fractured. And in a lot of ways, they haven’t communicated it well to the community. For example, CMS has interoperability rules that they were rolling out that came out just before COVID happened. And so COVID delayed a lot of the timeline for the implementation of things like fire.</p><p>And then after the dust settled from COVID, they redid the timeline and started to move it out again. But they didn’t communicate well to the community that those requirements existed. Like one of the requirements in the interoperability rule says that every provider has to have a Firebase API that is available to patients to be able to access their patient record. And there was a timeline for that. But if you go into the community and you talk to providers in the community, I have yet to find anybody, any provider that knew that that requirement was coming or had already passed. so that timeline has already gone past. And there are still providers that don’t know that that is a requirement from CMS.</p><p>Reuben Hall (24:02)<br>What major trends or shifts do you see coming in healthcare interoperability over the next five to 10 years?</p><p>Brian Book (24:09)<br>Well, I think that you’re going to see a more workflow-driven approach to healthcare. A lot of the workflows for how patients are being treated are being digitized. Things like OMG, their BPM plus standard is a standard for creating automation and workflows for healthcare. And so I think that historically healthcare has really struggled to look outside of healthcare for solutions to their problems. And I think they’re starting to realize now that a lot of the problems that they have are not unique to healthcare and that there are solutions, IT solutions to their problems that have solved those problems with fabulous success over and over and over again. in other industries outside of healthcare.</p><p>Reuben Hall (25:11)<br>What’s one example of that that you could kind of hold up to move towards?</p><p>Brian Book (25:18)<br>Sure, like the workflow automation that I’m talking about that we’re outside of healthcare, the IT community has created dynamically driven workflow solutions that are not platform dependent. So you can have a workflow that captures everything that all the work that is required in that workflow.</p><p>But it’s not tied to technology in any way. And so then you can have automation engines like Red Hat has an automation engine that’s called PAM, which is a process automation manager. And what that does is take that platform independent workflow model and it can dynamically create that workflow in any architecture that you want to put that in. And so you can then the workflow doesn’t become constrained by each company’s architecture that they’ve created. So when you install PAM, you connect that to your architecture, to all the existing architecture that you have. And then you can drop that process model into PAM. And it can take that independent model and make it a dependent model for your architecture.</p><p>But it’s not constrained by the architecture. So when you pull that out, I can take it over to somebody else who has an implementation of PAM and I can drop it in over there and it dynamically creates that workflow in their architecture. so BPM plus within the OMG community is the start of the work to create that same kind of process automation within healthcare. And so that BPM Plus is built on business process modeling, which has been done outside of the VA and the manufacturing community has been leveraging that methodology for 40 years now. so the healthcare community is finally starting to realize that they can leverage the power of that and add the things that are specific to healthcare.</p><p>And still realize the benefits that everybody outside healthcare has been able to achieve in the IT development and IT technology that we have everywhere outside of the VA. I mean, when you think about the VA is, or not the VA, but the healthcare community is keeping the fax machine alive. They consider that interoperability in healthcare is the ability to send a fax from one organization to another because it’s secure. So that’s how many decades the healthcare community is behind the IT community outside of healthcare.</p><p>Reuben Hall (28:17)<br>Yeah. So if you could pick one issue in healthcare IT to fix Wave with Magic Wand and just make it work, what would that be? Kill the fax machine?</p><p>Brian Book (28:44)<br>So, well, the fax machine has to go, but I think the biggest problem that we have in healthcare right now is patient ID. And because we don’t have a meaningful approach to matching patient records and creating IDs across systems that ensure the reliability of matching patient records from one place to another. That failed process has created an enormous data quality problem that until we solve that, we won’t be able to leverage a lot of the things that are coming like meaningful analytics and machine learning and eventually AI that right now the data quality doesn’t exist in the current data that we have for us to even start to do machine learning in the healthcare community. And I’ll give you an example that I read an article, and this was several years ago now, that there was an organization in New England that was trying to build a machine learning platform that could predict Alzheimer’s. And I said that until we solve the data quality problem that we have, the first couple of passes of machine learning on the data that exists now, it’s going to make it seem like machine learning has Alzheimer’s in the output that we’re going to get from the existing data that we have. And so until we can solve that problem, we’re going to really struggle from a data standpoint. And we’ve had a couple of contracts over the years where we’ve built AI solutions that where we ran into that data quality problem over and over and over again, and until we solve it, it’s always going to be a challenge.</p><p>Reuben Hall (30:51)<br>Yeah, AI can’t work without good quality data and interoperability, really, the ability to connect different data sources together.</p><p>Brian Book (31:04)<br>Absolutely. If the data is in 10 different formats, the first thing that we have to do is go and try to map all the data into one common format before we can do anything with it. And that mapping exercise is just wasted energy, where if everybody would adopt standards, then everybody that’s compliant to the standard could share information easily from one organization to another without having to do any mapping exercises to try to get the same data in the same place from one organization to another.</p><p><em>Originally published at </em><a href="https://mindsea.com/moving-digital-health-brian-book/"><em>https://mindsea.com</em></a><em> on July 9, 2025.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ebc08c4c19d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mindsea-development-inc/what-the-va-can-teach-you-about-real-healthcare-interoperability-with-fhir-mindsea-1ebc08c4c19d">What the VA Can Teach You About Real Healthcare Interoperability with FHIR — MindSea</a> was originally published in <a href="https://medium.com/mindsea-development-inc">Moving Digital Health</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Taking a Patient-oriented Approach to Developing a Family Mental Health App]]></title>
            <link>https://medium.com/@MindSeaTeam/taking-a-patient-oriented-approach-to-developing-a-family-mental-health-app-0891b6971ebc?source=rss-3b53535c9a60------2</link>
            <guid isPermaLink="false">https://medium.com/p/0891b6971ebc</guid>
            <category><![CDATA[healthtech]]></category>
            <dc:creator><![CDATA[MindSea]]></dc:creator>
            <pubDate>Thu, 29 May 2025 12:55:09 GMT</pubDate>
            <atom:updated>2025-05-29T12:55:09.041Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*g33mE7hQzXWAwfuM.png" /></figure><p><strong>When the University of Manitoba’s research team set out to develop a digital health app for their BEAM program-designed to support family mental health and ease parenting stress-they knew they needed more than just a developer. They needed a true partner. That’s why they chose MindSea. Through open communication and strong, ongoing collaboration, they tapped into MindSea’s deep industry expertise and experience working with universities and research institutions.</strong></p><p>During the COVID-19 pandemic, many families faced unprecedented challenges that contributed to a significant rise in parent mental health concerns and increased difficulties in accessing essential care. These barriers underscored the need for innovative, evidence-based programs designed to support parent well-being, enhance parenting capacities, and mitigate the long-term effects of stress on young children.</p><p>To address this gap in care, a research team from the University of Manitoba used a patient-oriented approach to co-develop an app-based psychoeducation and social-connection platform called Building Emotional Awareness and Mental Health (BEAM).</p><p>The BEAM program supports family mental health and well-being for parents and caregivers with young children. It provides:</p><ul><li>Weekly psychoeducational videos</li><li>1-on-1 peer coaching support</li><li>A private interactive forum to access peer support</li><li>Opportunities to connect with experts who specialize in mental health and parenting</li></ul><p>After receiving a recommendation from within the academic community, the research team decided to engage MindSea to design and develop the app that underpins BEAM.</p><h3>Green Flags: Finding the Right App Dev Partner</h3><p>The MindSea partnership was not the university’s first foray into developing the BEAM app. Before engaging with MindSea, the research team used a different app development company. They felt that, although there were some things that went well in that build, there were also communication challenges.</p><p>Dr. Leslie Roos, an Associate Professor at the University of Manitoba and co-lead of the program along with Dr. Lianne Tomfohr-Madsen, Associate Professor at the University of British Columbia, explains, “It’s been a steep learning curve for us as we have never worked in the app development space before. We didn’t know much about building and maintaining an app and testing it out on different devices, and we didn’t know upfront what we were paying for. In terms of output and functionality, we had a steep hill to climb to get the app to where we wanted it to be.”</p><p>The research team then met with a few app development companies to find a better fit company before landing on MindSea. From the outset, the research team appreciated MindSea’s ways of communicating and understanding of their vision.</p><p>“They brought expertise to the table in terms of app development and user experience, but they were also really respectful of our expertise and knowledge in working with families and delivering interventions and understanding the mental health needs of parents,” explains Roos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*g0qHMvzNMYJyKQv0.png" /></figure><h3>Test, Tweak, Repeat</h3><p>MindSea started working on the build of the app in June 2023 and it launched in January 2024; it took seven months to build. MindSea’s first step in the process was to build user journeys through story mapping. This helped the research team understand how users would interact with and move through the app, as well as what kind of features they needed and what specific needs they had. MindSea also provided branding support.</p><p>The next step was to build the prototype to troubleshoot and test the features, main user flows, and overall journey. This helped the team overcome problems they had with their old app.</p><p>“We had challenges with our old app in that it didn’t work particularly well on Android phones or older versions of operating systems,” says Roos. “MindSea were really dedicated to problem solving and checking that this wasn’t the case with the new app.”</p><p>The team was particularly happy with the feel and functionality of the app and the overall product that MindSea created. They also learned a lot about how users engage with the app throughout the process.</p><p>“The app feels very professional and works seamlessly without being glitchy,” says Roos. “You can easily move between different features and it doesn’t do things like lock you out of the video streams. I wouldn’t have appreciated all of those things had I not had other experiences with apps that didn’t work as well.”</p><p>MindSea has the added benefit of being a Canadian digital health app development company, which was important in terms of data privacy and security. Academic researchers need to have all data stored and managed within Canada to meet ethics and regulatory best practices. MindSea was able to ensure all data stayed in Canada and didn’t leave the country in order to meet the necessary standards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XSYVRA8T2nQAv4QQ.png" /></figure><h3>Why Industry Expertise Matters</h3><p>MindSea’s experience working with universities and academic institutions to develop digital health apps also enabled the company to provide support with regulatory compliance. The two teams worked together to figure out how to obtain ORCHA (Organisation for the Review of Care and Health App) digital health accreditation.</p><p>The first version of the app had a score of 64% (65% is the pass mark). MindSea supported the team in improving their adherence to best practices in digital mental health products. The results speak for themselves: the BEAM app now has a score of more than 80% and is an ORCHA recommended product.</p><p>MindSea’s industry expertise also enabled the company to incorporate feedback and revisions from the research team’s partners. This included the parent advisory board and others who have a strong interest and lived experience in managing family mental health. MindSea collected feedback about functionality, how things were flowing, and the way the app looked, and then incorporated this into the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aEr2FCns1iTPu3ep.png" /></figure><h3>The Secret to Long-Term App Success</h3><p>The research team has built an ongoing, long-term relationship with MindSea due to the company’s diligence, communication skills, collaborative nature, and industry experience.</p><p>“It has been an ongoing relationship opposed to them building something in the quickest, cheapest way possible,” says Roos. “We’ve had good communication throughout. When there’s been hurdles, both teams have been really interested in addressing them and making sure we can be on the same page moving forward.”</p><p>As part of this ongoing relationship, MindSea has continued to test the app across the different versions that have been released as part of a maintenance contract. According to Roos, the research team has submitted a lot of update requests for MindSea, which the app development company is always happy to talk about.</p><p>“They always think about how they can accommodate our requests and make something work with the budget that we have,” explains Roos. “They also proactively suggest ways to improve the app and update features. We appreciate their ability to align themselves with our vision for the app and the way it supports family wellness. This has really helped as we continue to improve the app over time.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pS5yKbUBtBI7qCm4.png" /></figure><h3>Ongoing Collaboration and Further Enhancing the BEAM App</h3><p>MindSea’s commitment has gone beyond tech support and post-launch services to develop into a true, ongoing partnership. As the BEAM team expands their research into new areas with additional funding, MindSea remains a trusted collaborator, providing the technological expertise and strategic support to help drive the team’s mission forward.</p><p>“We’ve done a lot of revisions so far in terms of upgrading the functionality and flexibility in the app since its launch and, as we are awarded more grants, we will continue to work with MindSea for the foreseeable future,” says Roos.</p><p>Currently, the BEAM app is designed to support a single program, but the vision is much bigger. The team is gearing up to expand its impact by introducing different cohort types, starting with a newly funded, self-directed program-an evolution from the current peer coaching model.</p><p>MindSea has supported the team in making this vision a reality. By implementing key infrastructure updates, they’ve ensured the app is not only fit for today’s needs but also adaptable for the future. As the research team continues to explore new ways to support perinatal mental health and beyond, MindSea remains deeply involved, helping to shape an app that evolves alongside the research, ready to serve more families in meaningful ways.</p><p>“The MindSea team has been really flexible in building what we want in an iterative way that works with our budget and capacity,” says Roos. “We’ve recommended them to multiple other research groups in the academic space, and will continue to do so in the future.”</p><p>Funding for the app and related clinical trials has come from a number of sources, including:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q_mKQVZDLp3GTpON.png" /></figure><h3>Ready to build an app that improves lives?</h3><p>Find out how <a href="https://mindsea.com/">MindSea</a> can help you reach your goals.</p><p><em>Originally published at </em><a href="https://mindsea.com/case-studies/projects-the-beam-program/"><em>https://mindsea.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0891b6971ebc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moving Digital Health, Episode 33: Farnoosh Abbas Aghababazadeh]]></title>
            <link>https://medium.com/mindsea-development-inc/moving-digital-health-episode-33-farnoosh-abbas-aghababazadeh-2bf54e38cf4d?source=rss-3b53535c9a60------2</link>
            <guid isPermaLink="false">https://medium.com/p/2bf54e38cf4d</guid>
            <category><![CDATA[healthtech]]></category>
            <dc:creator><![CDATA[MindSea]]></dc:creator>
            <pubDate>Tue, 27 May 2025 16:47:18 GMT</pubDate>
            <atom:updated>2025-05-29T13:01:47.421Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*p_2wHiox75DC4iro.jpg" /></figure><p>Our guest this episode was Farnoosh Abbas Aghababazadeh, who joined Reuben Hall to explore how machine learning and federated data approaches are shaping the future of cancer research.</p><p>“If you want to have reproducible research, you should start with the right data and standardized data” — Farnoosh Abbas Aghababazadeh on reproducibility in biomedical research.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FKXuxCSYTwPI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DKXuxCSYTwPI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FKXuxCSYTwPI%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bf157702815aeb74880f8735c126ff2e/href">https://medium.com/media/bf157702815aeb74880f8735c126ff2e/href</a></iframe><p>Find <em>Moving Digital Health</em> on <a href="https://podcasts.apple.com/us/podcast/moving-digital-health/id1610546047">Apple Podcasts</a> and <a href="https://open.spotify.com/show/0OXaAaHQkfa4cfUg1BKf4M">Spotify</a>, and <a href="https://share.hsforms.com/1EgOC1hDpQjmPHAmNnKQc5Q185gy?__hstc=71280975.d141b9bdeedddd7967e2f47b2e5014ca.1639602052475.1661870519476.1663607831453.158&amp;__hssc=71280975.3.1663607831453&amp;__hsfp=817607603">subscribe to the MindSea newsletter</a> to be notified about future episodes.</p><p><strong>Read Transcript:</strong></p><p>Reuben (00:00)<br>Welcome to the MindSea podcast series, Moving Digital Health. Our guest today is Farnoosh Abbas Aghababazadeh, postdoctoral research fellow at the Princess Margaret Cancer Center University Health Network. Thanks for joining us today Farnoosh!</p><p>Farnoosh Abbas (00:16)<br>Thanks Reuben for having me! It’s great to be here and looking forward for our conversation.</p><p>Reuben (00:23)<br>Excellent. Could you start by telling us a little bit about your background?</p><p>Farnoosh Abbas (00:28)<br>Sure, definitely. So I come from the strong statistics background. So I did both my undergrad and master in statistics and mathematical statistics in my home country. then in 2010, I moved to Canada to do my PhD program at the University of Ottawa.</p><p>Mainly focusing on the biostatistics. And after completing my PhD, I moved to the United States for a postdoctoral position training at the Moffitt Cancer Center. And that was amazing experience.</p><p>So that helped me a lot to dive deeper into a statistical genomics and gave me hands-on experience building computational pipelines for cancer research, including the omics data and more complex data. And then I eventually returned to Canada and joined Dr. Hepke’s lab at the Princess Margaret Cancer Center and more or less keep working on the same stuff that I did in the previous training and more in the intersection of the machine learning and computational pipelines, including the multi-omics with applications in pharmacogenomics and the precision oncology.</p><p>Reuben (01:54)<br>Okay, and as a research fellow at Princess Margaret Cancer Center, what does a typical day look like for you?</p><p>Farnoosh Abbas (02:03)<br>That’s really good question. Yeah, my days can vary, depend on the project needs.</p><p>It depends, but can be started by planning, by look at the my calendar, calendars and like check the to-do list and review any meetings or the deadlines or priorities for the day. And also can be started by starting the project, depending on the priorities to build up or improve the pipelines or debugging them. And even sometimes if the project finalized, I can focus on writing.</p><p>But these days, I think that I spend also most of the time for the meetings in terms of collaboration meetings that we have or even guiding the students that I’m supervising or co-supervising them and discuss about their progress or even, for example, the problems that they have in their tasks or even, for example, plan for the next steps. yeah, but I really try to do some sort of balancing in terms of the collaborations, the things that I’m doing and also the, like the deep focus on my learning and research, but sometimes I think that I should accept that sometimes it seems that it doesn’t go in a way that I expected.</p><p>Reuben (03:37)<br>Yes, for sure. And how many different projects might you be working on at the same time?</p><p>Farnoosh Abbas (03:45)<br>Many projects, but to be honest, the two main projects that I’m working on that, because the lab that I’m involved in, so we are mainly focused on improving the biomarkers pipelines for the discovery of the biomarkers and the two main projects, one of them, it’s related to the immunoncology and like build up the pipelines to see how we can improve the biomarker discovery that are associated with the immunotherapy and or for example, collect the data, immunotherapy data and also see that how, for example, we can have better pipelines to do the predictions for the immunotherapy response. It is one of the main projects that I think that it takes the majority of the time for me.</p><p>And I’m also leading at the BHK Lab for this project. And the other projects that’s more associated, again, with the biomarker discovery, but associated with the rare cancer sarcoma and soft tissue sarcoma. That one is also really interesting and it has its own challenges due to the limitations that we have for the soft tissue sarcoma data in terms of like the cell line data and also for the patient data and the other projects more associated with the collaborations or even collaborations with the clinicians inside the UHN and Princess Margaret Cancer Centers or even the pharma companies like the Roach and Coal.</p><p>Reuben (05:26)<br>I see, well that is a lot. I know the quality of the data is obviously very important. Where are you able to source the data sets that you need to do some of that research?</p><p>Farnoosh Abbas (05:43)<br>That’s really good question. So I think that in our lab, we focus mainly in the data curations and get access to the data that are really important for our projects. Sometimes we are waiting maybe long time to get access to the private data sets, but still we are trying to be patient and having them in the lab. But sometimes we maybe have the publicly available data sets, whether the clinical data or even the cell lines or the preclinical data.</p><p>But any data that we provide publicly available or the private one, we try to curate them. So we try to follow the standardizations that are defined in the lab in terms of the pharmacogenomics because I mainly work in the pharmacogenomics. So those standardizations can be like aligned with the codes for the clinical data sets to follow like the common platforms and for the like the genomics and the transcriptome data sets. So we have also the standardized pipeline and we are going through all these standardized steps for all the data to be curated.</p><p>Reuben (07:03)<br>So is there a lot of time spent cleaning up the data and standardizing it so you can do the research properly?</p><p>Farnoosh Abbas (07:12)<br>Exactly, it times a lot and usually we have like amazing curation team in the lab and also I was lucky to have the students to work with me and help for the both immunotherapy projects and also the sarcoma to curate the data and I think that sometimes the people or the researchers think that It doesn’t matter, but I think that if you want to have the reproducible research, you should start from the right data and the standardized data. Otherwise, it’s really difficult in this area or the time that we are living to have better collaborations.</p><p>Reuben (07:55)<br>And do you find there’s enough data out there to get really valuable insights? Do you find you’re always kind of looking for, I need more, I need more to get larger sample sizes?</p><p>Farnoosh Abbas (08:09)<br>That’s really good questions. It is exactly our concern for both like the projects that I’m working, the rare cancer sarcoma and also for the immunotherapy one. Always we are saying that we need more data.</p><p>So yeah, that’s really good question. So let me to open these for you that why we need more data. For example, for the immunotherapy project. So yes, still be a lot of research already done, but still it’s not enough. Maybe for example, some researchers mainly focus on the specific AMICS data like only RNA, but some others only DNA. Still we have, we need the biomarkers for the immunotherapy. So that’s the reason that how we can improve those biomarkers by having more data. Sometimes we have, we look at the publications and we see, yes, there are like maybe, I don’t know, more than 10 or more than 50 published biomarkers in the literature review,</p><p>but they are not really powerful biomarkers because maybe they drive from the data sets that doesn’t have enough samples or patient there, or maybe not enough validation already done on those biomarkers, or even maybe there are like the pan cancer biomarkers, they are not validated for the cancer specific. So these are a lot of questions available.</p><p>That’s the reason that even when we did the first paper for the immunotherapy, after that we noticed that, we are still at the beginning and we need more data, whether for example, waiting and get access to the more data because most of the amazing data sets, they are private and the data providers usually keep the privacy of the patients. That’s totally fine and we respect all the privacy for the patients, but we also want to have a better biomarkers. So we should try to get access or find better pipelines for the biomarkers discovery.</p><p>Reuben (10:08)<br>Okay. In addition to your work at the University Health Network, you also collaborate with the Terry Fox Research Institute. How did you get involved in that organization and how are you working with them?</p><p>Farnoosh Abbas (10:23)<br>Yes, that’s right. So in 2023, we were thinking that in terms of having more data, why not to start collaborations with Terry Fox and MOHCCN and Marathon of Hope team and network to get access to the more data that’s already provided in Canada across all the provinces.</p><p>So that’s the reason that in 2023, we sent applications for our projects, Immuno-Oncology projects, and that application was awarded. And so that was the start of the collaborations with the Terry Fox and MOHCCN And we granted to get access to the more relevant data for the Immuno-Oncology projects to see how we can improve the pipelines and the biomarker pipelines.</p><p>Reuben (11:25)<br>And so is some of that related to the recently published article in the Cancer Cell Journal, the Terry Fox Research Institute Marathon of Hope Cancer Centers Network, like you say, MOHCCN and the Pan-Canadian Precision Oncology Initiative.</p><p>Farnoosh Abbas (11:46)<br>Yes, some of them, because these MOHCCN it’s like the national network that was led by the Terry Fox and that support, for example, the projects that are like mainly relevant to the precision oncology. And they also provide like the MOHCCN gold cohorts that include, I think 15,000 patients.</p><p>That’s a lot, including the clinical genomic and even transcriptomic data set. And also this group can make connections between the scientists, patients, clinicians across all the provinces. And that’s a good connection for even like the sharing data between the groups and even like the improving the pipelines by getting access to those groups without moving the data between the institutes or between the provinces. So they also will consider some sort of federated systems and pipelines for even data and for sure for the pipelines as well.</p><p>Reuben (13:04)<br>Okay, so I know one of the major focuses of Terry Fox Research Institute is their digital health and discovery platform or DHDP with federated data sharing. For people who aren’t familiar, how would you explain what that means and why it’s important?</p><p>Farnoosh Abbas (13:28)<br>Yes, federated data sharing means we can work with data from multiple institutes or multiple cancer centers without sharing the data. So which means that instead of like centralize the data from different locations, so how about we send the pipelines or tools to those locations and they can train the models locally using their data and also they can have the control on the privacy of their data.</p><p>Because in the traditional way we usually centralize all the data and in this way, yes, we could have amazing data in house, like let’s say at the UHN. But we also had some sort of limitations because sometimes the data provider is not sharing the data due to the privacy or even the identified the patients, it’s not really helpful for them. So that’s there is an in a set of waiting or get access so we can improve the pipelines as a federated or decentralized. And for sure, in this way, we can cover more patients, improve the number of samples in the pipelines and also we can include some groups that we call it underrepresented groups, like for example, having more females in immunotropy datasets, right?</p><p>Because usually when we look at the data, we see we have more males compared to the females or maybe having more different races in the data also, for example, different cancer types or even for the rare cancers, I’m sure that this sort of federated works very well.</p><p>Reuben (15:22)<br>And in terms of standardization, like you mentioned, if you have all these data sets from different sources, is it a challenge to get them to line up and standardize them?</p><p>Farnoosh Abbas (15:39)<br>Yes, that’s really good questions. That’s really challenging. that’s what because as a use case that now we are working with the DHDP and Terry Fox for the immunoncology, we noticed that it is really challenging to standardize that. And that was a question for myself and the team that’s the Candid team, one of the parties in the DHDP and the Terry Fox.</p><p>So they try to harmonize and have some standardizations to follow through them to standardize all the data that they want to, for example, store for like as a federated. So because otherwise it’s impossible, right? So any script or any computationals, maybe at the beginning when we work on that in the lab as the centralized, so we have like the nice standardized curated data, right?</p><p>And then that is standardized should be some things that’s as a national or like the general format that can be like generalized across all other institutes and all other, for example, data providers also follow those steps.</p><p>Reuben (16:50)<br>So what are some of the most promising use cases you see for the federated learning in oncology, particularly around immune oncology?</p><p>Farnoosh Abbas (17:00)<br>I’m sure that there are a lot of applications we can have for the federated learning in oncology or even in the immunoncology. So that can be including like predicting the treatment response, right?</p><p>So for example, because one of the challenges that we have in the immunotropy right now is figuring out which patients will actually respond to the specific treatment like, for example, immune checkpoint inhibitors. So then these trophies can be really life-changing, right? But they don’t, for example, can be valuable or they can’t work for all the patients or everyone, right? But I’m sure that the federated learning can build the predictive models.</p><p>by using the data from multiple institutions include like more patients and more samples and even without moving those data. And then for sure we can have a better, for example, or we can have better biomarkers or we can have better identified that those likely to benefit which patients can benefit from that. The other thing is the biomarker discovery.</p><p>And again, we can have the same story that by federated pipelines. So in a set up, for example, using only one local cohort to find the biomarkers. So we can include the different cohorts or different institute data and then improve the biomarker discoveries. And then for sure, we can have more powerful biomarkers and all these to like projects that can be defined for sure that can lead to have like better precision medicine and also better to design the clinical trials. So, and for sure we can have the improving the outcomes and efficiency as well.</p><p>Reuben (19:06)<br>Okay, and how do you see federated approaches evolving in the precision medicine over the next three to five years, let’s say?</p><p>Farnoosh Abbas (19:17)<br>It can become the core part for the precision medicine. so by making easier, just like respect to the privacy of the patients, but also make it easier for all the groups or the scientists across the, for example, let’s say in Canada, across different provinces to collaborate and for example, include more data and improve the biomarkers and also, for example, improve the pipelines without even moving the data. So for sure, it can be one of the core key for deep precision medicine.</p><p>Reuben (20:03)<br>Okay, and I know you’ve touched on some of this already, but could you tell us any more about some of your work in predictive oncology?</p><p>Farnoosh Abbas (20:15)<br>So for the predictive oncologies, yes, the Immuno oncology, it was one of the projects that I mainly focus on that and like improving the biomarker discovery and also do the predictions for the treatment response by considering we start with like the simple models, like the linear or the Cox models.</p><p>And then we also move to the more complicated one as the federated one and include the machine learning approaches. And even in this immunoncology, we try to dive in more about considering the impact of bias that we have in data in terms of the demographic aspects.</p><p>As I mentioned, for example, we have more males, less than females in the immunotropy datasets, or even we have more like the melanoma cohorts, but less for the sarcoma ⁓ publicly available or was provided. So that’s the reason we try to improve the pipelines as a federated to see how we can involve more cancer types, how we can involve even as the like checkpoint inhibitors involve more like treatments like targeted CTLA-4 instead of just for example because more are about the PD-1, PD-L1.</p><p>So also for example, try to see that by this federated, how we can address those sorts of bias that we may have in the data. So it is one of the projects and the other one, it’s more associated with the sarcoma and for that rare cancer sarcoma, specifically with the soft tissue sarcoma with like more than 10 subtypes that we have for the soft tissue sarcomas. So that’s a little bit challenging to find the biomarker as well. So that’s why we decided to start with like the preclinical or the cell line data that we have. And there are still limited and we had also challenges to annotate the cell lines for the soft tissue sarcomas in the right way and then, Do they like the biomarkers, predictive biomarkers, after finding the biomarkers from the cell lines and validate them on the clinical trial data.</p><p>Reuben (22:43)<br>Looking forward, what will be the focus of your research over the next year?</p><p>Farnoosh Abbas (22:51)<br>I keep working on the more or less the same path, but that I’m doing right now mainly focus on the cancer research and the precision oncology, but including more data modalities because for now I mainly focus on the DNA or RNA data or the clinical or even the preclinical data.</p><p>But we will see that more like data sets, single cell data sets, special data sets. So they are also coming and for sure, like any of these data sets individually matters. And even if we combine together, so for sure we can improve the biomarkers. So it is one of the things that I really want to try in terms of like also beside including more data also improving the pipelines that can handle the the multi-omics data as well. And for sure the federated or the decentralized pipelines can be like the priority as well in terms of including like the different data modality as well.</p><p>And beside all these things, I’m working in the lab and with a team that we mainly focus on the open science. And that really matters for me as well as a researcher or the computational scientists still keep it as the open science and in terms of the data or even the pipelines that we build.</p><p>Reuben (24:28)<br>Okay, well I really appreciate your insight today and all the work and research that you and your team are doing on cancer and improving our understanding and ways to treat this disease. Thank you so much for joining me on the podcast, Farnoosh</p><p>Farnoosh Abbas (24:46)<br>Thank you so much Reuben for having me.</p><p><em>Originally published at </em><a href="https://mindsea.com/moving-digital-health-farnoosh-abbas/"><em>https://mindsea.com</em></a><em> on May 27, 2025.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2bf54e38cf4d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mindsea-development-inc/moving-digital-health-episode-33-farnoosh-abbas-aghababazadeh-2bf54e38cf4d">Moving Digital Health, Episode 33: Farnoosh Abbas Aghababazadeh</a> was originally published in <a href="https://medium.com/mindsea-development-inc">Moving Digital Health</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why We Recommend Using React Native Over Flutter for Cross-Platform App Development]]></title>
            <link>https://medium.com/@MindSeaTeam/why-we-recommend-using-react-native-over-flutter-for-cross-platform-app-development-6f2036376573?source=rss-3b53535c9a60------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f2036376573</guid>
            <category><![CDATA[healthtech]]></category>
            <dc:creator><![CDATA[MindSea]]></dc:creator>
            <pubDate>Tue, 15 Apr 2025 18:14:33 GMT</pubDate>
            <atom:updated>2025-05-29T12:59:07.185Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0prN0KW2VKsrGYlFpuZi7g.jpeg" /></figure><p>At MindSea, we’re passionate about building top-notch mobile apps that really work for our clients, making sure they’re intuitive, friendly, and meet every need. One of the key decisions we have to make to deliver this experience is the framework we build them on.</p><p>React Native and Flutter are two of the most popular frameworks for cross-platform mobile app development. They both allow you to build apps for multiple platforms with a single code base. While there are many other frameworks for mobile app development — such as Ionic and Kotlin — we will just look at React Native and Flutter in this article.</p><p>After weighing all our options, we decided to use React Native as our go-to framework for cross-platform development. This is because it best serves the needs of medium to large organizations over the long term, taking into account factors such as long-term viability, cost savings, and a better cross-device experience.</p><p>Read on to find out more about why we recommend React Native over Flutter.</p><h3>Uses a Familiar Language</h3><p>With <strong>React Native</strong>, developers can code in JavaScriptor more specifically TypeScript, which is a superset of JavaScript that adds syntax on top. Javascript is the language of the browser and it powers the World Wide Web, which means it’s one of the most widely used programming languages in the world. <strong>This makes it easier to find experienced React Native developers </strong>or even train a web developer to transition into mobile development.</p><p><strong>Flutter,</strong> on the other hand, uses Dart, a language created by Google that’s almost exclusively used for Flutter development. While it has its strengths, Dart doesn’t have the same industry-wide adoption or versatility as JavaScript, making it a more niche choice with fewer available developers.</p><h3>Backed By Big Names</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4J7ecm-tngMZAOr8.jpg" /></figure><p><strong>React Native </strong>has earned widespread trust at the enterprise level, with companies like Tesla, Walmart, Microsoft, and Shopify all using it to power their apps. This kind of industry-wide adoption gives us confidence that <strong>React Native will continue to evolve, improve, and stay future-proof</strong>, which is a critical factor for the long-term success of our projects.</p><p><strong>Flutter, </strong>on the other hand, is heavily reliant on Google’s backing and hasn’t gained the same level of traction among major enterprise organizations. This makes its long-term future feel a little less certain.</p><h3>Wider Variety of Ecosystems and Libraries</h3><p>As<strong> React Native </strong>is built in JavaScript, ithas a more mature ecosystem with a vast library of third-party tools. Many enterprises rely on React Native, meaning the framework’s libraries are more likely to be well-maintained and continuously supported. <strong>This reduces the risk of outdated or abandoned dependencies.</strong></p><p><strong>Flutter,</strong> being newer, still has gaps in its ecosystem, meaning some third-party packages may not be as polished or actively maintained. For example, if you need to integrate a specific Android Health feature, but the Flutter library hasn’t been updated in years, you might find yourself having to build and maintain it from scratch, which adds extra time and effort to the project.</p><h3>Larger, More Engaged Community</h3><p>With millions of developers around the world using JavaScript, the ecosystem around<strong> React Native</strong> is huge, diverse, and constantly evolving. That means there’s a ton of third-party resources, libraries, and tools available that make our job easier and <strong>help us solve complex problems.</strong></p><p>On the flip side, <strong>Flutter </strong>uses Dart, which has a much smaller, isolated community. Dart is growing, but it doesn’t quite match the reach and resources of JavaScript.</p><h3>Open Source Support</h3><p>One of the key differences between choosing React Native and Flutter comes down to who controls the technology.</p><p>With <strong>React Native</strong>, you’re using a framework developed by Meta, but they don’t own JavaScript. JavaScript is an open-source language that powers the web and is governed by an international standards committee, making it far less risky. Even though Oracle holds some patents related to it, JavaScript itself is widely adopted and not controlled by a single company.</p><p>When you choose <strong>Flutter</strong>, you’re fully committing to Google-not just their framework but also their programming language, Dart. This means you’re essentially living in Google’s ecosystem.</p><p>In addition, with <strong>React Native</strong>, you can use a partially open-source tool called Expo to improve the developer experience and <strong>make it easier to build and deploy apps</strong>. <strong>Flutter</strong> has no equivalent of that. Flutter Flow, for example, is just a drag-and-drop WYSIWYG app builder that doesn’t add anything to the developer experience.</p><h3>Better Native Experience</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CVl2J3AYWV_VT-CI.jpg" /></figure><p><strong>React Native </strong>uses the native components of each operating system, meaning it provides a more true-to-platform look and feel. By taking advantage of platform-specific UI elements, apps built with React Native <strong>feel more natural and perform better across different devices</strong>. For example, if you write a button component, then it’ll look slightly different on iOS or Android because they have their own standards for buttons.</p><p><strong>Flutter</strong> writes every pixel to the screen, meaning your app will look consistent across platforms but it might not look native to the particular operating system. It can lead to design inconsistencies or performance issues, especially on lower-end devices.</p><h3>Significant Cost Savings</h3><p><strong>React Native</strong>’s cross-platform capabilities also enable you to save money. By training your team in React Native, you break down silos. Your web developers can contribute to mobile apps, and your mobile developers can work on the web. Instead of needing separate teams for iOS, Android, and web, <strong>you can have a single, versatile team working across all three platforms with shared skills and code</strong>.</p><p><strong>Flutter </strong>doesn’t offer the same flexibility. Its open source support for web development is low and Flutter for web isn’t at the same standard as JavaScript for web. You also can’t apply any existing JavaScript knowledge for Flutter as it uses Dart instead.</p><h3>Stability and Long-Term Viability</h3><p><strong>React Native </strong>is a well-established framework and Meta is committed to making constant improvements. The introduction of the New Architecture, including Fabric and TurboModules, has significantly boosted performance and made native integrations smoother. This makes for a much <strong>more stable platform</strong> and gives us confidence in its long-term viability.</p><p><strong>Flutter</strong> is maintained and updated by Google, a company which has a history of abandoning their projects. Just take a look at the <a href="https://killedbygoogle.com/">Google graveyard</a> if you want to see all the projects they have abandoned.</p><h3>Flutter: A Great Framework For Certain Applications</h3><p>We always strive to provide the best recommendations and advice to our customers and, with that in mind, there are some case in which Flutter may be the better option for your business:</p><ol><li><strong>If pixel-perfect control is your top priority</strong>. Let’s take the gaming industry as an example. The focus isn’t necessarily on following platform design standards but on delivering an immersive experience. In this case, you need a framework that gives you creative control rather than adapting to each platform.</li><li><strong>Performance:</strong> In the gaming industry, where you have a lot of custom animations, Flutter has often been seen as the platform of choice. As Flutter uses the Skia rendering engine for smooth graphics, in the past it was considered to offer superior performance when it comes to graphics. However, there is now a React Native version of Skia, which could provide an alternative for game developers.</li><li><strong>Linux applications: </strong>If you want to build an app that runs on Linux, then Flutter is the better option. React Native has limited support for Linux, and you have to use Electron, which is a separate application. Flutter, on the other hand, provides full support for Linux applications.</li></ol><h3>React Native: Our Recommendation for App Design and Development</h3><p>Both React Native and Flutter have their advantages, but we have found that React Native provides the best balance of community support, industry adoption, performance, and flexibility. For your business, this means you can:</p><ul><li>Rely on a stable platform</li><li>Deliver a more consistent user experience users across devices</li><li>Access the best web development resources to further develop and maintain your app post launch</li><li>Work with one teamacross all app platforms</li></ul><p>With strong backing from major enterprises and a thriving ecosystem, React Native is built for the long haul, and helps us deliver cutting-edge apps and deliver seamless cross-platform experiences to our clients every time.</p><p>To find out more about how we can design and develop an app that provides a smooth cross-platform experience built on the right choice of development framework, <a href="https://mindsea.com/contact/">get in touch</a> with Alex today.</p><p><em>Originally published at </em><a href="https://mindsea.com/why-we-recommend-using-react-native-over-flutter-for-cross-platform-app-development/"><em>https://mindsea.com</em></a><em> on April 15, 2025.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f2036376573" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Apple Health, Google Fit: Integration Platforms for Health, Wellness, and Fitness]]></title>
            <link>https://medium.com/@MindSeaTeam/apple-health-google-fit-integration-platforms-for-health-wellness-and-fitness-e4d750815524?source=rss-3b53535c9a60------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4d750815524</guid>
            <category><![CDATA[healthtech]]></category>
            <dc:creator><![CDATA[MindSea]]></dc:creator>
            <pubDate>Thu, 10 Apr 2025 20:01:26 GMT</pubDate>
            <atom:updated>2025-05-29T13:00:26.850Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lSrZg6OREC8tLImhwRAM0w.jpeg" /></figure><p>Previous articles in this series looked at mobile app development in terms of the raw data available from the <a href="https://mindsea.com/smartphone-sensors/">sensors</a> that are built into smartphones, as well as the increasing role of connected wearables and other smart <a href="https://mindsea.com/connected-devices/">external devices</a>.</p><p>This post tackles the major topics of integrating <a href="https://health.google/health-connect-android/">Android Health Connect</a> and <a href="https://www.apple.com/ios/health/">Apple Health</a> — the two most significant and widespread platforms for sourcing and contextualizing health, wellness, and fitness data.</p><p>If you are interested in creating a health-related mobile app, what do you really need to know about the two major health and fitness platforms?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9NTz_4q-3wX2Hz69.png" /></figure><h3>The Platforms: Android Health Connect and Apple Health</h3><p>These platforms can help your app get instant liftoff. Both Android Health Connect and Apple Health are free and in use by millions of people. Apple Health comes pre-installed on iOS smartphones and watches, and Android Health Connect is a free download from the <a href="https://play.google.com/store/apps/details?id=com.google.android.apps.healthdata&amp;hl=en">Google Play Store</a>. The compatibility of your app with one (or both) adds value for mobile phone consumers.</p><p>Android Health Connect is available for Android devices. Health Connect is a secure, central repository that stores data from the various health and fitness apps on a user’s device. If a health and fitness app supports Health Connect, users can choose which data from the app can be accessed and stored by Health Connect. Users can browse the raw data entries that have been stored in Health Connect, but Health Connect does not visualize this data. Instead, users choose a favourite health and fitness app or two (and which data these apps are allowed to access), and Health Connect will funnel its stored data into those apps for visualization. Users can change these app permissions at any time.</p><p>Apple Health is an app available for iOS devices. Similarly to Android Health Connect, Apple <a href="https://developer.apple.com/health-fitness/">HealthKit</a> is a secure, central repository that stores data from the various health and fitness apps on a user’s device. In addition, HealthKit automatically tracks steps on iPhone or iPad, and automatically tracks Activity data on Apple Watch. While Android Health Connect does not visualize its stored data, Apple HealthKit does, through the Apple Health app. Apple Health has many features, including interactive charts that show health data over time; the sharing of health data with close family, friends, or care providers; and downloading and updating clinical records from healthcare institutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iuas2e9ZTDfW3TEP.png" /></figure><p>While Apple Health utilizes information from smartphone sensors, much of the functionality depends on pairing with <a href="https://www.apple.com/watch/">Apple Watches</a>. Both Apple Health and Android Health Connect collect data from various smartwatches and fitness trackers through their proprietary apps. <a href="https://play.google.com/store/apps/collection/promotion_all__health_connect">Leading health and fitness apps</a> that can be linked together with Health Connect include MyFitnessPal, Fitbit, and Samsung Health. Strava and Garmin Connect do not link directly to Health Connect, but third-party syncing apps can be used, such as <a href="https://play.google.com/store/apps/details?id=nl.appyhapps.healthsync&amp;hl=en_CA">Health Sync</a>. Health and fitness apps that are compatible with Apple Health include Strava, Garmin Connect, and MyFitnessPal. Fitbit does not link directly to Apple Health, but a third-party syncing app can be used to facilitate this, such as <a href="https://apps.apple.com/us/app/fitbit-to-health-sync-solver/id935306292">Sync Solver</a>.</p><p>These two platforms have a lot in common. They are competing in much the same space, using very similar methods, and in a changing, shifting landscape.</p><p>If a feature that you want to create in your app depends on data that is only collected via the tools of iOS or Android devices, you may decide to create only one version. Your mobile app could be designed for use on either Apple iOS or Android smartphones, or you could produce a version of each. The other option is to develop a cross-platform app with slightly different features using a development framework like React Native, Ionic, or Flutter.</p><h3>The History of Android Health Connect</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8XUZMfUldinXCfx_.png" /></figure><p>Google announced in 2022 that Android Health Connect was in development, and in March 2024 there was a beta release of Health Connect in Google Play. Starting in Android 14, Health Connect is part of the Android operating system and is accessible in Settings. In Android 13 or lower versions that are supported, Health Connect is a publicly available app on the Google Play Store.</p><p>Prior to the development of Android Health Connect, there was <a href="https://www.google.com/fit/">Google Fit</a>. The Google Fit app was first released in October 2014 (just a few weeks after the release of Apple Health) and is the Android equivalent to the Apple Health app for iOS. The Google Fit app focuses first of all on the frequency and intensity of physical activity using point systems. Other associated areas like nutrition, hydration, and sleep depend on user self-reporting or connected apps. The <a href="https://developers.google.com/fit">Google Fit SDK</a> (Software Development Kit) is the Android equivalent to Apple HealthKit for iOS, and is what allowed for the sharing of health and fitness data between Android apps. At the same time as Google announced the development of Android Health Connect in 2022, they also announced the depreciation of Google Fit in 2025.</p><p>With the move to Android Health Connect, Google is signaling to users that they place great importance on privacy and security. While Google Fit stored data in the cloud, Android Health Connect stores data locally on Android devices and encrypts that data for additional security. Apple HealthKit also stores data locally on iOS devices with encryption.</p><h3>Behind the Platforms: Data Integration Hubs, SDKs, APIs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gUEjgqNmFkpwmFoz.jpeg" /></figure><p>On the back end, Android Heath Connect and Apple HealthKit are secure open-source integration platforms that collect, organize, store, and track the health and fitness data from multiple services and applications. That’s where they become interesting for mobile app development.</p><p>Both platforms were architected to make data sharing and storing easier for developers. In addition to collecting vital user data needed for functionality, much of the development work for obtaining and sharing structured data has already been done. If your app meets certain criteria (more on that later), you can utilize the resources of the open-source software development kits and the platform APIs to support additional services.</p><p>The <strong>SDK</strong> (Software Development Kit) — or “Kit” for short — refers to the whole open-source platform that provides the tools and documentation that allow for the creation of applications. SDKs are organized in terms of intended operating systems, programming languages, and type of APIs (Android, REST) for the in-scope hardware.</p><p>About Apple HealthKit:</p><ul><li><a href="https://developer.apple.com/documentation/healthkit">Apple HealthKit and HealthKitUI</a> frameworks are available for iOS 8.0+, iPadOS 8.0+, Mac Catalyst 17.0+, macOS 14.0+, visionOS 1.0+, and watchOS 2.0+.</li><li>Swift is the primary programming language while Objective-C is still supported and used for maintaining legacy apps.</li><li>Health data is securely stored on the device itself, encrypted for privacy, with the option to back up and sync across devices via iCloud.</li></ul><p>About Health Connect SDK:</p><ul><li><a href="https://developer.android.com/health-and-fitness/guides/health-connect">Health Connect SDK</a> is available for Android 8.0+ and Wear OS 8.0+. It is compatible with any Android-powered device, including smartphones, tablets, smartwatches, and Wear OS devices, as long as it is running Android 8.0 or later.</li><li>Kotlin is the recommended programming language while Java is also supported to maintain existing Android apps.</li><li>Health data is securely stored locally on the device, with optional syncing across devices like smartphones and Wear OS devices. The core data stays on the device.</li></ul><p>APIs (Application Programming Interfaces) allow for the functioning of applications within the SDKs defined parameters and are what enable blending data from multiple apps and devices. The API is simply an interface that allows software to interact with other software, a set of public methods and properties that interact with objects in your application. Mobile apps can read data via APIs from dedicated URLs that return structured data “objects” that can interact with one another. Users decide the scope of permissions in terms of which kinds of data may be shared with specific apps and services.</p><p>Subclasses of data types define the schemas for a stream of data being collected by, inserted into, or queried. A data type can contain one or more fields, from stable data to complex data types that combine samples of data or compute aggregate values over sets of samples. Sources of data are identified, whether they are phone sensors, wearable devices, user input, connected apps and services, or data transformations on these.</p><h3>Apple HealthKit vs Android Health Connect Data: What Data Matters Most for Your App?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tljVo2RZMwxjD6TJ.png" /></figure><p>What kinds of data exist or are provided for by each platform, and how are they organized?</p><p>Pro-tip: Start thinking about what services your app could provide in this kind of space:</p><ul><li>What kinds of data might your app require, and why?</li><li>From what source or sources would that data originate — user self-reporting, Android and/or iOS smartphone sensors, watches/fitness trackers, Bluetooth-enabled external devices?</li><li>Will the app require the use of data that is sensitive, protected or restricted? How might you use or create calculations, correlations, aggregations, interpretations?</li></ul><p>Some kinds of metadata can be added to both platforms or within your own app. Here, you’d really need to consult with developers on best practices for utilizing the platforms.</p><p>As an illustration of the kinds of things that are possible, consider weightlifting. A user may add a workout session under a weightlifting category, and track some basic metrics about heart rate, exertion, duration, and the like.</p><p>However, additional workout activity variables are already available to be used as structured data. Specialized enthusiasts would want to use those variables to produce more meaningful analysis, perhaps to track combinations of repetitions, sets, weights, and types of exercises toward goals. Apps such as Strong have taken advantage of that expanded data set and added their own features to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/607/0*UzZVoLxUPDQVQP7_.jpg" /></figure><h3>Health Data Can Be Leveraged Across Apps</h3><p>In new mobile apps, nutritional information can likewise be repurposed and expanded for customized dietary plans. Water intake can be recontextualized for use cases like camping trip inventory planning, and depletion of stores. The whole health and fitness quadrant could be made a part of a more encompassing smart home dashboard keyed to each household member.</p><h3>Privacy, Access, Policies: Reading and Writing Data to Android Health Connect or Apple HealthKit</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*usgXrl_w2xFkS4dH.jpg" /></figure><p>Your app’s ability to obtain, hold, or share types of data is determined by many factors. User consent, privacy, security and other related app development guidelines are reviewed and enforced by Google, Apple, and governmental authorities. Some data is classified as restricted, protected, or sensitive. Some data can be written, but not read by other apps. Some user data is not available for use at all, and some user data is tied to the larger ecosystems of Google or Apple services.</p><h3>Start with a Streamlined Approach</h3><p>If your app is intended to fit into the health and fitness vertical, start with the bare minimum of metrics that you would need for your app to function in its intended way. Even with just a few data points and other features, new apps can provide valuable services.</p><p>If your app is focused on exercise, weight management, nutrition, or standard physical activity tracking, then you can drive value by articulating how exactly your app will use the architectural capabilities of either platform. Fitness-related apps can provide additional value, such as balancing activity types or comparing the results of different strategies toward fitness goals. The bar is higher for medical apps, such as those that might be used for diagnostics, remote monitoring, disease management, medication management, or personal health records.</p><h3>Case Study: Johns Hopkins’ Corrie Health Program</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1vKuNJ31-5Z2mHz6.jpeg" /></figure><p>Physicians at the Johns Hopkins University School of Medicine developed the with enrollment, informed consent, and frequent medical information gathering. They also added tasks, contacts, and care plan store modules from <a href="https://www.corriehealth.com/">Corrie Health</a> program to achieve remote monitoring, support, and data collection for recovering cardiac patients. For their app, they used data from Apple Watch, and from a Bluetooth blood pressure cuff that writes directly to the Apple Health app and is shared via HealthKit to their own app. They added consent and survey modules from Apple’s <a href="https://www.researchandcare.org/researchkit/">ResearchKit</a>, which is intended to help <a href="https://www.researchandcare.org/carekit/">CareKit</a>, which helps <strong>researchersmedical care teams</strong> stay connected with patients by making it easier for patients to record and share health data. Patients recorded daily progress on steps, heart rate and blood pressure, and were given resources for recovery on topics like diet, medication, and mindfulness techniques.</p><p>In this case, Corrie Health developers made an initial ecosystem choice: for Apple iOS devices and the Apple Health-related SDKs, including HealthKit. A second version released in the Google Play store allows their patients to use Android smartphones and substitutes Fitbit Versa in place of the Apple Watch and blood pressure cuff. Since none of the data was used for diagnostic purposes, but only for communication, encouragement, and basic aftercare, they were able to provide services to their patients without having to confront some of the regulatory difficulties involved with the use of strictly medical devices and apps. Still, this application may have been marketed in an overly medical fashion to be acceptable to Google Fit; it doesn’t appear to be integrated or compatible.</p><p>Health apps do need to categorize personal identifiers, health, and medical data differently than fitness data, in order to treat the data with a higher level of security.</p><p>Significant opportunities exist for robust apps that would do a better job of integrating or associating data from additional smart external device apps (thermometers, heart rate sensors, scales, and glucose meters) <strong>into</strong> Android Health Connect and/or Apple Health. Apple Health tends to restrict some external devices in terms of Apple branding and partnerships.</p><p>Due to increased caution after a global pandemic, a greater variety of robust non-contact smart <a href="https://www.nytimes.com/wirecutter/reviews/best-thermometer-for-kids-and-adults/">thermometers</a> would be helpful, even if that data is not used for official diagnostics. Some manufacturers like Kinsa and Vicks have built out their own apps.</p><h3>Regulatory Approval Is the Barrier Between a “Wellness” and a “Diagnostics” App</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZwIgWedSAl8u_RIT.jpg" /></figure><p>One of the big problems is that without regulatory approvals from governmental entities like the U.S. FDA (Food and Drug Administration), medical devices can only be used as a “wellness” feature, and not for diagnostic medical use. Apple did get clearance to use the <a href="https://www.govtech.com/question-of-the-day/why-isnt-apple-watchs-blood-oxygen-feature-fda-approved.html">EKG feature</a> of the Apple Watch as an early warning of irregular heart rhythms, but only for that scope of use.</p><p>The FDA’s Unique Device Identifier ( <a href="https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/unique-device-identification-system-udi-system">UDI</a>) initiative requires the assignment of a distinctive identification number to all regulated medical devices sold in the United States — from manufacturing through distribution to patient use and digital records.</p><p>General health, fitness, and wellness features that are not used to diagnose do not need FDA approval, so Apple, Google, and others are mindful about what is claimed, and how any of this is marketed.</p><p>Companies and developers must be aware, and compliant with law and policy when developing and distributing mobile apps. Both Android Health Connect and Apple HealthKit require fine-grained user permissions for reading and sharing data, and a multitude of security, privacy, and access policies and laws come into play for both platforms.</p><p>Apple Store <a href="https://developer.apple.com/app-store/review/guidelines/">review guidelines</a> for mobile apps must be adhered to, and <a href="https://developer.apple.com/documentation/healthkit/protecting-user-privacy">protecting user privacy</a> is of utmost importance. Health data, especially those involving clinical medical records, have significant <a href="https://developer.apple.com/documentation/healthkit/authorizing-access-to-health-data">additional requirements</a> for use. Each time your app requests incremental new permissions, the Health app displays a <a href="https://developer.apple.com/design/human-interface-guidelines/">form</a> to the user with all the requested data types.</p><p>For Android Health Connect, <a href="https://policies.google.com/">Google policies</a> apply, as do policies of the <a href="https://play.google/developer-content-policy/">Google Play Store</a>. Health Connect requires explicit user consent for apps and devices to access and share health data. Users can control what data is shared, with whom, and for what purposes. Only necessary data is collected, and apps must disclose their data usage practices. Users can manage and revoke access to their health data through Android settings at any time.</p><h3>The Changing Landscape of Health and Fitness Tech</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*x76GHxzIVuJcQrUY.jpg" /></figure><p>The biggest tech companies are all continuing to develop new tools for consumers, medical professionals, and insurers as healthcare is continually being reshaped. The number of connected devices is already in the <a href="https://techjury.net/blog/how-many-iot-devices-are-there/">billions</a>, increasing the need for smarter methods and platforms of interconnection. Eventually, more apps will seek medical-grade approvals.</p><p>A wide range of innovative applications are possible: integrations with hospital software, external device and services integration, AI-driven analysis, health monitoring and alerting, symptom checkers, medication management, risk of injury management, physical training effectiveness, patient locator, sleep quality monitoring, and guided therapies are only a few examples.</p><p>During the last few years, and especially as a consequence of the pandemic, the two ecosystems have moved toward one another, both in cooperation and competition. A few news items will suffice to illustrate the shifting ground.</p><ul><li>Apple and Google <a href="https://covid19.apple.com/contacttracing">worked together</a> on ways to find solutions to Covid-19 pandemic problems, including contact tracing with Bluetooth technology and an exposure notification system. Under newer data regulations in many countries, privacy and security concerns were front and center. Over 50 countries and public health authorities worldwide adopted the exposure notification system or built their apps using the framework. At the same time, there is an atmosphere of widespread criticism about anti-trust issues, advertising, markets, and perceptions of union-busting and other worker issues.</li><li>The CEO of Alphabet (Google’s now-parent company) is in the process of reviving the Google Health team and <a href="https://health.google/health-research/">expanding on its AI research in healthcare</a>. Since 2018, the Google Health group (Google Health, DeepMind, Verily, Google Cloud, Calico, and Fitbit) have been working on electronic health records, imaging and diagnostics, consumer and clinician tools, and research.</li><li>There has been some speculation about the reasons for delayed <a href="https://9to5google.com/2021/01/28/google-ios-app-updates/">Google iOS updates</a>.</li><li>Since <a href="https://blog.google/products/platforms-devices/fitbit-acquisition/">Google acquired Fitbit</a> in January of 2021, the two companies have worked to integrate Fitbit’s fitness trackers and smartwatches more closely with Google’s broader ecosystem. Enhanced fitness tracking features and more robust health data insights, particularly through AI and machine learning, have significantly improved the platform’s capabilities. There have also been improvements in hardware with the addition of ECG and EDA sensors.</li><li>In 2020, Apple Health added a subscription for <a href="https://www.apple.com/apple-fitness-plus/">Apple Fitness+</a> for Apple Watch (Series 3+) with a catalogue of workouts and in-session metrics that sync to iPhone, iPad, or Apple TV. The subscription can be bundled into other <a href="https://www.apple.com/apple-one/">paid Apple services</a>. Since its launch, Apple Fitness+ has seen a steady stream of improvements that enhance its accessibility, personalization, and integration with the Apple ecosystem. Features like group workouts via SharePlay, expanded workout types, improved music and playlist integration, and better Apple Watch integration have made the platform more engaging and comprehensive for users of all fitness levels.</li></ul><p>The pandemic highlighted weaknesses in areas such as supply chain management, data visualization, situational awareness, and telehealth that further innovation could continue to address. Technologies for better Bluetooth device integration options, additional standards, data stream analyses that are more useful to different consumers and institutions, and even public health education tools are also needed.</p><p>Can you contribute?</p><p><em>Originally published at </em><a href="https://mindsea.com/apple-health-android-health-connect-integration-platforms-for-health-wellness-and-fitness/"><em>https://mindsea.com</em></a><em> on April 10, 2025.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4d750815524" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moving Digital Health, Episode 32: Alex Mitchell]]></title>
            <link>https://medium.com/mindsea-development-inc/moving-digital-health-episode-32-alex-mitchell-97cd0a4e2174?source=rss-3b53535c9a60------2</link>
            <guid isPermaLink="false">https://medium.com/p/97cd0a4e2174</guid>
            <category><![CDATA[healthtech]]></category>
            <dc:creator><![CDATA[MindSea]]></dc:creator>
            <pubDate>Mon, 24 Mar 2025 19:36:39 GMT</pubDate>
            <atom:updated>2025-03-24T19:39:50.563Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*j70imEVbWHrqha-u.jpg" /></figure><p>Our guest this episode was Alex Mitchell, who joined Reuben Hall to discuss the role of artificial intelligence in improving mental health care. Alex shares insights on the current challenges within the mental health system, the inefficiencies of traditional intake and triage processes, and how AI-driven tools can help streamline access to care.</p><p>“Three years ago, nobody really wanted to adopt these technologies. Now, there are 10 new companies entering the space every week.” Alex Mitchell on the rapid shift from skepticism to competition in AI-driven healthcare.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fv5Z8NoOcHlc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dv5Z8NoOcHlc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fv5Z8NoOcHlc%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc636b8aafc6633447b523934571a56f/href">https://medium.com/media/bc636b8aafc6633447b523934571a56f/href</a></iframe><p>Find <em>Moving Digital Health</em> on <a href="https://podcasts.apple.com/us/podcast/moving-digital-health/id1610546047">Apple Podcasts</a> and <a href="https://open.spotify.com/show/0OXaAaHQkfa4cfUg1BKf4M">Spotify</a>, and <a href="https://share.hsforms.com/1EgOC1hDpQjmPHAmNnKQc5Q185gy?__hstc=71280975.d141b9bdeedddd7967e2f47b2e5014ca.1639602052475.1661870519476.1663607831453.158&amp;__hssc=71280975.3.1663607831453&amp;__hsfp=817607603">subscribe to the MindSea newsletter</a> to be notified about future episodes.</p><p><strong>Read Transcript:</strong></p><p>Reuben (00:01)<br>Welcome to the MindSea Podcast series, Moving Digital Health. Our guest today is Alex Mitchell, surgeon and chief operating officer at Brightlight Health. Thanks for joining us today, Alex.</p><p>Alex Mitchell (00:13)<br>Thanks for having me, Ruben.</p><p>Reuben (00:15)<br>Maybe you can start by telling us a bit about your background.</p><p>Alex Mitchell (00:19)<br>Sure. I’m a general surgeon by training, still practice part time.</p><p>During my surgical career, I got into healthcare leadership and into healthcare infrastructure. I spent quite a number of years in executive leadership in the healthcare infrastructure space in Nova Scotia. And in addition on the side, have also been a serial entrepreneur, real estate investor, and have started a couple of other small companies, and currently, one of my ventures is participating as the Chief Operating Officer at a company called Brightlight Health.</p><p>Reuben (01:08)<br>Cool, so practicing surgeon, serial entrepreneur, healthcare leadership, that’s a lot. You must be a busy guy. Maybe tell us what a typical day looks like for you.</p><p>Alex Mitchell (01:25)<br>Yeah, so now I left my former public service role so I don’t work for the province of Nova Scotia any longer. So since June, a typical day for me depends on whether it’s a clinical day or a non-clinical day. A clinical day is off to do things at the hospital. Non-clinical days are get up super early. I’m an early riser. I believe strongly in exercise and quiet time before my day begins. So usually I get up, quiet cup of tea and a solid work out and then start driving. I’ve got four kids. Everybody heads off in different directions and one of my kids is usually my responsibility to get them into town and I will either take him to school or come home and go to our Dartmouth office or I’ll come home and work from home online and juggle between the various different companies.</p><p>healthcare consulting company that I’ll spend a few hours with every single day and better part of half the day probably most days with Brightlight related activities and I’ve also got a septic engineering company that usually runs pretty smoothly but a few times a week needs a few hours a day.</p><p>Reuben (02:50)<br>Okay, I think I got all that. So how many days a week are you kind clinical versus non-clinical?</p><p>Alex Mitchell (02:59)<br>Presently about a day a week clinically and in the near future that’ll go up to two and a half days a week.</p><p>Reuben (03:06)<br>Okay, and maybe you could tell us a bit more about Brightlight Health, how that came to be and more what it’s all about.</p><p>Alex Mitchell (03:17)<br>Yes, so Brightlight Health, I’m not the founder. I came on, I think about 18 to 20 months after it was founded. Founded in 2019 by two individuals, one Grant Betts and Om Agarwal.</p><p>Grant and I actually are childhood friends and hadn’t seen each other in quite some time. Our kids ended up at the same school and we ended up connecting through the kids, which is where I discovered that he was working on machine learning solutions in mental health. And, you know, and we linked up and I saw what they were working on. And with my background in small business and in healthcare leadership and healthcare design.</p><p>There was an excellent alignment of what they needed at the time. They had some early machine learning solutions without much of a business model around it and were working to mature their solutions and start trying to become market ready with those. Brightlight initially was working with some early machine learning solutions, ultimately transitioning over to the large language model space as that space is matured. And Brightlight has been working with large language models to improve the provision of mental health care, really to improve access to care, reduce burdens to care, reduce documentation administrative burden to more efficiently streamline the mental health care workflow right across the entire continuum of care.</p><p>Reuben (05:05)<br>That’s a great story. It’s funny, as parents, how much of our social life, and even professional in some cases, can happen through the connections of our children. There’s one girl on my daughter’s basketball team that jokes that her dad would have no friends if it wasn’t for all the activities and sports she was involved in. It’s interesting how those connections can happen sometimes.</p><p>Alex Mitchell (05:38)<br>Yeah, definitely. I’ve got five kids and I’d say the majority of our social network and or everything else revolves around what they’re up to and who they’re up to it with.</p><p>Reuben (05:50)<br>Cool, so let’s talk about Brightlight Health a little bit more. I you mentioned the intake process for mental health is one of the solutions that you’re focused on. Maybe talk about what’s the status quo and how does Brightlight improve on the typical existing intake process.</p><p>Alex Mitchell (06:16)<br>Yeah, so I mean, I think we’ll go a little bit higher, you know, and just say like the status quo, I think most would understand is terrible. Right, that the overwhelming burden of illness globally is horrendous. Yeah, over a billion people on the planet with documented mental illness. In Canada, one in two by the age of 40 suffered with some form of mental illness and about half a million Canadians out of work every single week in Canada related to mental illness related disability or dysfunction. $51 billion hit on the Canadian economy each year.</p><p>And presently, the health system manages the mental health burden through a number of different ways. So on the private side, we have employee assistance programs, among other things, but they run relatively similar to the public side, where people are documenting and noting that they’ve got challenges, usually sent to a phone call center to be, you know, to undergo an intake interview with some form of health professional. Many people just simply directed to online self-help resources, not human-based. In the public health system, very similar. separate out mental health crisis, right? But still it’s a either see family physician or call one of the available intake phone lines usually leave a message and receive a phone call back whatever, it’s staffed by human beings, usually from eight till four p.m. local time, wherever you’re at, sometimes not every day, and no way really to triage who needs the call first, it’s sort of first in first out. And then so a really slow process of filtering everybody only to enter into a system that even if we did have everybody filtered, there’s really no, you know, there’s really no exit plan.</p><p>There’s really nowhere for everybody to land in a large volume of people sent to self-help. Mental health crisis, quite a different model of course, like still crisis help lines, but a whole variety of different doors into that system, which include emergency health services, police, other different elements to how patients access care. And we all know that a large amount of that is still driving through primary care, urgent care and emergency departments.</p><p>Brightlight and I guess in more in general terms, I think the advent of the large language models affords an incredible opportunity to offload and augment a lot of the human tasks. Artificial intelligence can work 24 seven. It doesn’t have to shut down at four o’clock. It can be making sense of information and having AI driven conversations with people at any time of day and collecting information, summarizing that information into efficient and compact stories and providing potentially an overlying triage layer and other things trying to streamline and make more efficient that intake process and augment the existing human staff and potentially allow for more highly trained healthcare professionals to get off the phone lines and to participate in active care of patients instead of just information collection. And that just as a starting, that’s just the first scratch. There’s so many other ways that the use of artificial intelligence can help streamline and make healthcare more efficient and free up those human resources to do the human elements of care.</p><p>Reuben (10:25)<br>Yeah, and there’s so many different humans or stakeholders involved here, right? There’s the patients and their family and supports. There’s the clinicians and then the administrators and other staff involved in providing care. Maybe let’s start with the patients. Like, how do you feel the patient’s attitude towards interacting with AI tools? Are they very receptive? Is there kind of resistance or mistrust there? What’s been your experience?</p><p>Alex Mitchell (11:00)<br>Yeah, think generally it’s early, right? I think the deployment of many of these technologies is still so early that it’s hard yet to tell. I think that outside of healthcare, the use of AI-driven trap bots, among other things, has had fairly wide adoption. And I think all the reviews are certainly not in, all the reviews are certainly not glowing.</p><p>What I would continue to challenge us on is not just the user experience at this moment, I believe it’s important, but I think we do need to compare it against the current contrast of just nobody to talk to. There’s no way to get my story in. so I think that clients, when given the opportunity, are very grateful for any opportunity to share their story in any means that helps move the needle and helps move their particular case and scenario and situation through the system towards a moment at which they might actually receive care.</p><p>Reuben (12:07)<br>And how about the administrators and staff and clinicians? What has there been response been to these types of tools?</p><p>Alex Mitchell (12:19)<br>Initially, healthcare has been terrified of the advent of AI. I heard a quote recently from a group of Canadian healthcare CEOs that when asked, openly admitted that they were standing on the sidelines waiting to see what was going to happen, which is unfortunate and concerning healthcare is a laggard when it comes to adopting new technological change and certainly Canadian healthcare has been slow in other technologies and will continue I believe to be slow in adoption of this. That said on a sort of more individual clinician and smaller divisional and group situation initially people are at first interested, curious, apprehensive</p><p>And then once they have an opportunity to see it work, to see the nature of it and to thoroughly understand that this is not full automation, handing the reins entirely over to a computer or software that this really is augmenting their usual work and trying to replace some of the functions that they know aren’t necessarily the most valuable things they do each day, we do get a fair amount of support and understanding and a willingness to use. I think part of the challenge we’ve had is really just deploying and letting people try it and use it. And once they do and see how helpful it can be, then they’re usually very excited to use it more and go deeper.</p><p>Reuben (13:59)<br>So with the Brightlight, I there’s a few different solutions or tools and integrations you’re working with. Where have you seen the biggest adoption from people being willing to try it out and make the transition?</p><p>Alex Mitchell (14:21)<br>Yeah, have two of the two easiest areas are the easiest first is AI scribe to deploy an AI scribe and have people try it and use it is a relatively straightforward low requires very little in the way of integration or other technology challenges and it’s been the easiest thing to get people to try and start with is the AI scribe technology. We also we have an EMR and workflow platform that works very well in allied health care and mental health care situations in those scenarios where we have private third party providers of allied health or mental health especially when they’re new and just opening and trying to decide on adoption of other platforms and that’s been an area where we’ve certainly had some strength. And now currently, you know, we think the largest impact area is on AI driven intake and triage and that is the area that’s most challenging to get approval to deploy and get people to consider.</p><p>Reuben (15:42)<br>So how does the triage part of the intake work? you know, let’s say I’m, you know, an administrator comes to my desk first thing in the morning, there’s been all this, you know, these calls, information that has come in overnight or off hours. You know, what does that look like to me from a workflow perspective?</p><p>Alex Mitchell (16:05)<br>Yeah, so I think the biggest difference is that, you know, from, I guess, you know, so if your call center finished at 4 p.m., so from 4 p.m. onwards through till 8 a.m. this morning, what happened is that, well, anybody that actually depends on whether they’re just coming through or whether we’ve actually deployed. So in some situations, some of our clients would identify potential clients, identify people who they need to collect information from and then deploy the intake chat bot to that individual specifically to then collect all of the information. Or in some situations, it may be the first pass digital front door and triage mechanism. In any event,</p><p>Reuben (16:44)<br>Right, like inbound versus outbound basically,</p><p>Alex Mitchell (16:47)<br>Yeah. In either circumstance, an AI driven chatbot, depending on the situation, would have its conversation thread at the way it speaks, ask questions, the kinds of questions it asks, the way it asks its questions has been co-designed with the client so that it is doing what they want it to do and want it to say. so that, you know, client engages with the chatbot after hours and, you know, it can take a 30 to 60 minute interview and a large amount of information and consolidate it down into a cohesive one to two paragraphs. We can tie that to the DSM-5 criteria or to ICD-11 criteria and pull out a variety of symptoms which can be highlighted and then we can overlay that whatever triage score the organization wishes to apply to it.</p><p>So if there’s particular things that they’re looking for that would trigger, hey, this is somebody I’ve got a call first thing this morning, this is somebody I want to send to this place, this is the information I think I want from that patient, whatever it is as part of the information gathering, we can pull that out, highlight it and allow to create a more streamlined bucketing of the various different cohorts of clients as they come through, know one particular One particular organization with a triage level of one through five five being, you know really acute mental health crisis requiring fairly urgent intervention and admission and one being people with very low level mental health issues who may be best directed at self-help and You know web-based self-help tools and it allows them to see the spectrum of what came in and meaningfully direct some of those low acuity stuff to self-help, medium acuity to licensed clinical therapy or clinical psychologists and those at the upper realm, know, fairly rapid contact and progress through the acute mental health system.</p><p>Reuben (18:59)<br>Sounds amazing to me and it would save a lot of time in the process for sure. So what does the onboarding experience look like for a new customer? Like for the intake solution for example, you know, they have their existing system, they want to try out Brightlight. How do they go from what they have now to migrating to a new solution?</p><p>Alex Mitchell (19:28)<br>Yeah, so I mean, I guess I challenged a caution to say it’s not really migration, right? It’s like very few organizations already have a chat bot or something else or even a web based forum at their front end. You know, it’s pretty much human driven. They’ve got usually people on the phone or providing virtual telemedicine care. What it would look like at first is we have a</p><p>mature, rapidly deployable intake chatbot. And I think one of our differentiators and value statements is we have an interesting user interface that allows for fairly rapid customization of the conversation threads of the way that the chatbot has its conversations that we don’t, you one size does not fit all. So.</p><p>you if you want to do a depression questionnaire, don’t have to take our, like, here’s our depression questionnaire. Our chat bot asks questions about depression this way every time. Well, no, you know, there’s a lot of different situations with a lot of different subtle needs. One group may be working predominantly with substance use issues and looking to triage people pre-detox treatment. Some people may be trying to better differentiate a PTSI population into who’s going to self-help, who’s going to licensed clinical therapy. So when we engage with a client, most importantly is try to understand what’s their business model, what’s their organization doing, how are they doing it, what’s the clientele that they’re targeting and who are they likely seeing.</p><p>and then work with them to try to understand, okay, what do you do today? What are the questions you ask? What’s the information that’s most important to you? And then we try to blend that and shape that into the way that our chatbot intake.</p><p>interviews so that really our chatbot is functioning as good or better as whatever the human being was doing eight till four for them on the front end. And that varies in many situations, but the first step is understanding who they are, who they’re seeing, what questions they typically ask and what information they really need. And then we make sure that our chatbot can do that.</p><p>Reuben (21:50)<br>And for those like frontline providers, do you find there’s much of a learning curve to working with the technology or is it pretty user friendly?</p><p>Alex Mitchell (22:00)<br>Yeah, the user interface for training it is very, very user friendly. So you do not need to be a software engineer or a coder or otherwise to manipulate this. There’s a few levels here where we do use some various prompt engineering steps that we would do ourselves internally with discussions, understanding that from the client, but it’s very straightforward.</p><p>Reuben (22:28)<br>Okay, and you mentioned a few of the team members that you work with there already. Maybe talk about some of the team at Brightlight and how you all work together to make this happen.</p><p>Alex Mitchell (22:44)<br>Yeah, so we have a fairly diverse background. starts with the two founders, Grant Betts, who one of the co-founders is an accountant by Original Training, also has a background in computer science and has been working in enterprise software support and development for much of his career. He co-founded and runs a enterprise software consulting</p><p>company in the US that helps large companies implement, make changes to and support their large, usually ERP platforms, SAPs, oracles, NetSuite, etc. Epicor, that sort of stuff. Agarwal is our other co-founder who was a young child prodigy who was doing machine learning coding and other interesting things.</p><p>you know in his early teens and he and Grant linked up during that time and Ohm is a know hardcore genius software engineer.</p><p>Reuben (23:53)<br>Well, it’s nice to have someone like that on your team.</p><p>Alex Mitchell (23:56)<br>Yeah, absolutely. Myself, we’ve already discussed. We also have Dr. Brydon Blacklaws, our Chief Medical Officer, who is a pioneer in the rural virtual emergency care sector and runs the rural virtual emergency care system in British Columbia and has had a lot of experience with telemedicine and provision of virtual care.</p><p>We also have Robert Zed, who’s a senior serial entrepreneur and consultant who functions as our board chair and Robert’s got</p><p>connections in both the private and public sector in healthcare leadership has started and exited a number of companies and provides us with ongoing governance oversight and also connection to a really large network of very successful businesses, business people and leaders that helps us along our way.</p><p>Reuben (25:02)<br>Excellent. Sounds like a pretty great team and a fun challenge to be working on, an important challenge to be working on. But we understand that as any startup, there are a lot of challenges and problems to solve on daily basis. What are the big challenges that Brightlight has to solve? Looking forward to really unlock the potential of the solution.</p><p>Alex Mitchell (25:35)<br>Yeah, I think that pendulum swings back and forth. Right, think on one day it’s all about trying to fertilize the field. It’s adoption of a very novel technology in a risk adverse sector that is slow to adopt technology. So it’s really finding those opportunities to deploy, to both prove its worth, but also to learn and adapt and fine tune.</p><p>And then the flip side of that is with each opportunity to deploy and successful opportunity to deploy for a small technology company is balancing the appropriate level of support, execution and whatnot to those deployments, making sure that they go well, that we meet the customer’s needs and that we take the opportunity to learn from each of those deployments and advance our knowledge and our process.</p><p>product. And you know, I think then the other pieces, this is a crazy moving space. So deployment and adoption might be relatively slow in this space, but the advancement and research and development of the products of the frontier large language models that underpin these is moving at light speed. So the technology is changing like really weekly,</p><p>like there are developments that occur almost every week that change how we see things working and how we might decide to, you know, to make our platforms work. And it also means that the space and the sector is filling up incredibly rapidly, you know, a space that we had no competition in. But we’re, you know, nobody really wanted to, you know, to adopt any of these technologies three years ago. We’re now in a space where there’s 10 new companies every week entering the space. So it’s a very, very interesting time.</p><p>Reuben (27:40)<br>Yeah, it really is an interesting kind of paradox, like you said, too, the slow movement in the sector and industry side and incredibly fast and changing technology on a regular basis. So I feel it’s like a fire hose sometimes trying to keep up with all the changes in AI and other</p><p>technology frameworks on a day-to-day basis. But as part of the fun of the field too is that there is really never a dull moment. It’s like constant challenges and I guess it’s what we live for at the end of it.</p><p>Alex Mitchell (28:23)<br>Yeah. And then, you know, I still love the book, The Lean Startup and the concept of innovation accounting and that it isn’t just about new customers and revenue and other things. It really is, how much did we learn? How fast can we learn and are we learning more faster? And that’s part of the game. if nothing else, part of the accounting that we do every day and every week is what we learn.</p><p>because this is a space where there is tons moving and tons to learn and adapt very quickly.</p><p>Reuben (29:04)<br>Yeah, it was a great way of looking at it and a good reminder of that perspective. I really appreciate your time today, Alex, joining me on the podcast. It was great to chat with you and hear about your stories from the frontier there.</p><p>Alex Mitchell (29:21)<br>Excellent, you’re very welcome. Thank you so much for having me. Always appreciate an opportunity to talk about artificial intelligence and healthcare and certainly any opportunity to tell everybody about Brightlight.</p><p><em>Originally published at </em><a href="https://mindsea.com/moving-digital-health-jennifer-zelmer-2/"><em>https://mindsea.com</em></a><em> on March 24, 2025.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97cd0a4e2174" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mindsea-development-inc/moving-digital-health-episode-32-alex-mitchell-97cd0a4e2174">Moving Digital Health, Episode 32: Alex Mitchell</a> was originally published in <a href="https://medium.com/mindsea-development-inc">Moving Digital Health</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moving Digital Health, Episode 31: Jennifer Zelmer]]></title>
            <link>https://medium.com/mindsea-development-inc/moving-digital-health-episode-31-jennifer-zelmer-2bc3175247e8?source=rss-3b53535c9a60------2</link>
            <guid isPermaLink="false">https://medium.com/p/2bc3175247e8</guid>
            <category><![CDATA[digital-health]]></category>
            <dc:creator><![CDATA[MindSea]]></dc:creator>
            <pubDate>Tue, 21 Jan 2025 17:46:58 GMT</pubDate>
            <atom:updated>2025-01-21T17:52:07.153Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9fU-YPAV92kACGSW.jpg" /></figure><p>Our guest this episode was Jennifer Zelmer, President &amp; CEO of Healthcare Excellence Canada. Jennifer joined Reuben Hall to discuss the integration and scaling of digital health innovations within the Canadian healthcare system.</p><p>“It’s rarely the technology on its own that is able to deliver the real value. So it’s that combination of technology in a really smart way of implementing to ensure that you get the value from it.” Jennifer Zelmer on maximizing technology’s potential through thoughtful use.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FW1nphjcp5c8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DW1nphjcp5c8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FW1nphjcp5c8%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7940ada764ee406e368af4c56dfa8791/href">https://medium.com/media/7940ada764ee406e368af4c56dfa8791/href</a></iframe><p>Find <em>Moving Digital Health</em> on <a href="https://podcasts.apple.com/us/podcast/moving-digital-health/id1610546047">Apple Podcasts</a> and <a href="https://open.spotify.com/show/0OXaAaHQkfa4cfUg1BKf4M">Spotify</a>, and <a href="https://share.hsforms.com/1EgOC1hDpQjmPHAmNnKQc5Q185gy?__hstc=71280975.d141b9bdeedddd7967e2f47b2e5014ca.1639602052475.1661870519476.1663607831453.158&amp;__hssc=71280975.3.1663607831453&amp;__hsfp=817607603">subscribe to the MindSea newsletter</a> to be notified about future episodes.</p><p><strong>Read Transcript:</strong></p><p>Reuben (00:01)<br>Welcome to the MindSea podcast series, Moving Digital Health. Our guest today is Jennifer Zelmer, President and CEO of Healthcare Excellence Canada. Thanks for joining us today, Jennifer.</p><p>Jennifer Zelmer (00:13)<br>Thanks for having me, so nice to be with you.</p><p>Reuben (00:16)<br>Maybe you could start by telling us a bit about your background.</p><p>Jennifer Zelmer (00:20)<br>Sure, so I grew up mostly in Edmonton. But from relevance for this podcast, moved to Victoria for university to take a health information science program and have been involved with digital health since then, both working in Canada and overseas. And about five years ago, landed in Ottawa to start working then with the Canadian Foundation for Healthcare Improvement that then amalgamated with the Canadian Patient Safety Institute and to Healthcare Excellence Canada. So that’s the whistle stop tour of how I ended up here today.</p><p>Reuben (00:56)<br>Okay, interesting. I actually grew up in Victoria and ended up going to University of Alberta and moving to Edmonton. So we’ve may have crossed paths and been in similar cities over the years.</p><p>Jennifer Zelmer (01:13)<br>Nice, we swapped locations.</p><p>Reuben (01:15)<br>Yeah, so did you go to University of Victoria or…</p><p>Jennifer Zelmer (01:18)<br>Yeah, I did.</p><p>Reuben (01:19)<br>Excellent. So maybe you could tell us a little bit more about Healthcare Excellence Canada and your role there.</p><p>Jennifer Zelmer (01:27)<br>Sure, so Healthcare Excellence Canada is a national charity working with folks across the country to shape a future where everyone in Canada has safe and high quality health care.</p><p>We’re pretty new organization, so formed from that amalgamation that I mentioned in the middle of the pandemic, and really focused on doing that work in four ways. So identifying people who are working on wicked problems and the innovations that they’re finding along the way. And once those innovations are proven, looking to spread and scale them to more people.</p><p>Recognizing though that if we work innovation by innovation, we’re going to be at this for a very long time. So also building capacity for change within the health system, things like leadership development, engagement capable environments. And last but not least, recognizing that local teams can do amazing work. But if they’re trying to do that work in a policy or a structural context that makes things hard, they’re pushing water uphill. So we also work to catalyze policy and structural change that makes the things that deliver value easier to do.</p><p>Reuben (02:35)<br>Excellent. And maybe you could dive into some of those big pillars a little bit, specifically around innovation. What are some of the initiatives that you’ve been part of or are trying to spearhead?</p><p>Jennifer Zelmer (02:54)<br>You bet. So that first pillar, identify innovators and innovations. We just finished a health workforce innovation challenge, recognizing that recruitment is obviously important, lots of people working on that side of things, but if we’re not supporting and retaining people who work in healthcare, then we’re not doing what we need to do.</p><p>So the Workforce Innovation Challenge invited folks from across the country who were interested in that support and retention challenge to come together to work with their innovations in their context, but then share knowledge about what was working, build capacity together to make those changes happen. And we saw a whole array range of innovations across. So everything from scheduling changes, in some cases supported by digital tools that enabled that to happen, to changes in roles, supporting folks in different ways with creating psychological safety in the workplace. creating the ability to feel that you can make changes in your workplace as well that we know is associated with retention and better quality of work life. So we had hundreds of folks across the country focused on that challenge sharing with each other. So that’s an example of that sort of first pillar identifying those innovations. If think about the second pillar, that’s spreading and scaling individual innovations.</p><p>So if I take a couple examples in the digital space that we worked on a few years ago was around e-consults. So recognizing that if we can connect primary care providers with specialists in a more dynamic way, that we can shorten the time for the consults and also in about half of the cases, there’s actually not a need for a consult at the end of the day. If there’s able to be a need for a formal referral, if there’s able to be a quick e-consult between the primary care provider and the specialist. And so we worked there with two different models, one from Ontario, one from BC as sort of the initial innovations, and then worked with folks across the country to spread and scale those particular approaches. And we did see that in the end about half of the time a formal referral was able to be avoided and the average time to get a response was one to two days. So you were able to get a much more much quicker access to specialist care through that process in a way that supported primary care providers to be able to deliver care directly to their patients.</p><p>Reuben (05:29)<br>Okay, and so what form did that tool take? Was it more of a digital tool or interface or was it more of like a process procedure change?</p><p>Jennifer Zelmer (05:40)<br>We actually had both as part of the process. I don’t know what your experience has been, my experience has been, it’s rarely the technology on its own that is able to deliver the real value. So it’s that combination of technology in a really smart way of implementing to ensure that you get the value from it. And different teams in that challenge use different specific technologies. So what we were looking to identify as we do in all of our work is what are the core elements of that innovation that you need fidelity to, to get the results that you’re looking for and where do you need to adapt to local circumstances to realize the outcomes that you seek. And it’s that balance between the two that allows us to move something from a pilot project to spreading across other settings and being able to understand those differences. Where do you need that consistency? Where do you need the variation that adapts locally that you’re really able to move to scale successfully at the end of the day?</p><p>Reuben (06:42)<br>Yeah, I was going to ask about that local adaptation and variations from province to province or health authority. How are you meeting some of those challenges? Or are you seeing that it is in that specific circumstance? Were things very different from location to location? Or did the same solution generally work in the different contexts?</p><p>Jennifer Zelmer (07:11)<br>On the tech side, the solutions were quite different. But the end outcomes were the same, so the goals were the same. And so it was about how do you really deeply understand the needs of the patients you’re serving, the needs of the providers you’re working with? What’s the nature of how that technology solution is going to embed within their workflow, is going to embed within their needs? So the needs of, for instance, a primary care practitioner who may be primarily serving patients in very rural and remote areas will be different than the needs of someone who’s in downtown Toronto, downtown Vancouver, and has easy access to specialists right around the corner. So recognizing that those circumstances differ, and therefore the needs of not just the specific technology solution, but also how you implement it are going to differ as well.</p><p>Reuben (08:06)<br>And who are some of the partners involved there? Like, is this a collaboration between private sector and public, or is it more kind of innovation from within?</p><p>Jennifer Zelmer (08:17)<br>Yeah, so we tended to work directly with care providers, whether they were in regional health authorities or primary care or specialist services. And then they were the ones who chose the tech solutions that were best in their circumstance. So we didn’t do a collective procurement of a tech solution. They decided what was going to be right for them within the context and concept and with support from coaches, with support from tools and resources that we had available to them, to help make that easier to do, to be able to benefit from also their shared learnings peer to peer.</p><p>So we often hear from folks who join our programs that initially when they join, they may be attracted by the seed funding opportunities, some of those kinds of things, but often where they actually find the most value is by working with coaches and by working with other people like them and being able to share those experiences and learn together as they move forward. Because chances are the particular thing they may be tripping over, somebody else has already dealt with it and has an ability to connect and be able to learn together. And we definitely found that we’ve more recently been doing a lot of work around appropriate use of virtual care in primary care. And we’re seeing that in spades, that there’s practices, there’s approaches, there’s shared learnings that apply and can be beneficial across multiple settings and can just save you that time in angst somebody has already been down this path before. Great. Let’s learn from their experience.</p><p>Reuben (09:48)<br>Yeah. And what are some of those learnings? I’m not sure if you can talk about anything specific around virtual care that you’re seeing or just improving the whole experience for everyone.</p><p>Jennifer Zelmer (10:01)<br>I mean, I think virtual care at the beginning of the pandemic got slammed in fast and hard in lots of places because it had to be. And thinking as it was, right, that was what we had available to us. So, you know, super grateful to everybody who took the plunge at that point. It didn’t necessarily get introduced out of necessity in the most thoughtful way or in the ways that we now know are most effective. So there’s an opportunity now to look at what do we want to do going forward? What does the use of virtual care look like going forward? Where does it really deliver value? And where are the areas where frankly we need to adapt and adjust? So we’ve seen, for example, the real importance of connecting with patients and providers, really deeply engaging around how do we design this virtual care service that’s really going to be effective in that particular context, particular care path for patients.</p><p>So if you think about something like remote patient monitoring, there’s different ways of introducing remote patient monitoring. There’s different ways of approaching what types of tech you have in the home. Do you need to train in person before you go home or can you do that training remotely? So it’s all those kinds of experiences that we can learn from and improve everything from the mechanics of the user interface on the tech itself through to something as simple as how do you the tech when you’re done with it. How do you make that easier for patients as well?</p><p>Reuben (11:35)<br>Yes, all the logistics around actually having these devices in your home and then the aptitude to be able to maybe even troubleshoot something if it doesn’t work perfectly, right? Like who has the skills to be able to do that? How do you support the patients in their home? So what does some of that look like? people going into homes and kind of more hands-on supporting people who might not be very technically proficient in teaching them.</p><p>Jennifer Zelmer (12:19)<br>it actually starts even way before that. So engaging patients right upfront to understand the context in which the technology will be used, to do some testing with patient partners so that you actually decrease some of those things that are going to be tripped over. So, you know, if for instance, when you have a couple of patients test things, you find, gee, you know, a key problem is that this particular step is being missed. It’s not obvious. Well, Is there something you can even do upfront to eliminate that step that pre does it so that people don’t trip up over it? Or that really highlights that step in a process to make sure it doesn’t get missed? So what are the things that we can make the thing that you need to do easier to do? So it’s that design phase upfront where it starts. And then absolutely, once you’re in process, how do you then make it easier to troubleshoot along the way? So what are some of the most common things that come up?</p><p>In some cases, we actually had peer-to-peer support, so patient partners helping other patient partners to be able to learn from each other about how to effectively use the tech. In other cases, it required some different types of approaches and thinking about who was really in the best position to be able to provide that support so that things would go smoothly.</p><p>Reuben (13:39)<br>Yeah, it’s just like the human-centered design process that we’re using on an everyday basis when we’re designing mobile applications or web applications for patients. Really thinking through that user journey step by step and involving the patient in the process. Asking them questions, showing them prototypes. How would you do this? observing and getting their feedback at every step of the process and designing the system around them instead of forcing them to adapt.</p><p>Jennifer Zelmer (14:20)<br>Absolutely. mean, in a way, none of it’s rocket science, right? Like we know these core principles, but it is about doing them consistently and doing them well and doing them with a range of different patients and circumstances. So you’re not just working with partners in the design phase who may already be tech savvy, for instance, but making sure we’re bringing in the full range of patients who are going to be actually using whatever the solution is.</p><p>Reuben (14:38)<br>Yeah, sometimes the main barrier can be convincing the stakeholders that this is the right way to go about to do things because it takes time and it takes resources and sometimes not everyone’s on board. Have you found that you have to really kind of sell it up the chain or to everyone involved or is it pretty? people kind of see the value and are willing to invest in it.</p><p>Jennifer Zelmer (15:20)<br>I think most of the time people see the sort of value in principle. Sometimes haven’t had experience doing that kind of work in practice. So there is a process of, how do you do this work? And there’s always that tension isn’t there between, as you said, you know, it takes time, it takes resources up front. So that tension between making sure that we’ve allocated the time, we’ve allocated the resource to do that step as part of the planning versus, you know, quickly diving in. which is so tempting to do, but then you end up spending the time one way or the other, right? You can either spend it upfront or you can spend it later. Just depends on whether you want to suffer the pain in the meantime of not having done it.</p><p>Reuben (16:03)<br>You mentioned scheduling as well, and I’ve heard this is a big one from many others, that every hospital system is using different ways of scheduling. A lot of it’s just like spreadsheets, and there’s so many last minute changes and swapping and rotations. It can become very complex and chaotic. Was it a very similar situation as to what you described with virtual health, or is there different challenges to solve?</p><p>Jennifer Zelmer (16:42)<br>I mean to some of the core principles like user-centered design, absolutely the same. you know, there’s definitely some of those common threads. I think where there can be some differences is some of the structural issues that you need to think about in scheduling are different than the ones you need to think about in terms of virtual care.</p><p>So for instance, what’s the relationship between scheduling shifts and existing collective agreements? How do you provide the flexibility that people are looking for while staying true to the commitments that have been made through those agreements? Or do you need to have conversations around the next round of adapting those agreements going forward to meet everybody’s needs more effectively? So there’s some of those kinds of broader considerations that would be different than with virtual care. Care where you may be more thinking about how does virtual care fit within a clinician’s workflow, how is virtual care compensated. All those kinds of issues are a bit different, but some of the same core issues on the sort of tech adoption side ring true still.</p><p>Reuben (17:51)<br>And how about rolling out a solution because, you know, it’s the kind of thing it’s tough to just do little pieces and improvements and iterative scheduling improvements without just kind of, you know, a complete new system. How did you tackle that?</p><p>Jennifer Zelmer (18:11)<br>So different teams who we’ve worked with have tackled it differently. There’s definitely not one size fits all. For some folks it has been more of a process leading up to a full implementation of a new scheduling solution. Others have decided to start with maybe one unit or one group of home care nurses or one particular area so that they have a chance to walk before they run and work in more of that iterative approach and incremental change. So we have seen both approaches being used. you can use some similar, there’s user-centered design applies to both, so it’s not like that’s necessity one way or the other. But it does mean that sometimes you don’t have a choice, right? Like the agreement may require you go all one way or all another and so you may have some particular structural considerations that you need to have in</p><p>Reuben (19:11)<br>So I love hearing about the success stories obviously like that it sounds like a lot of progress is being made here you know virtual health scheduling through other any other kind of examples or innovations you’d love to talk about.</p><p>Jennifer Zelmer (19:29)<br>Yeah, I we get, I feel so lucky in my job because frankly, I get to work with people across the country who are just fired up to fix healthcare. So, you know, nobody has to work with us really. So when you come to us, it means that, you know, the thousand teams across the country we worked with last year, all of them had that commitment many of them had a tech component because now we’re looking at healthcare in a digital world, right? And that’s the lens we tend to take. It’s not digital health first. It’s about what are the healthcare goals or the health goals that you’re aiming for? And then how do you best use all of the means at your disposal to get there? So some of the kinds of things that we’ve been done have been much more around models of care,</p><p>for instance paramedics providing palliative care in the home. Most people want to be at home in that situation. Most don’t want to be in hospital. But often home palliative programs aren’t available 24–7 and you can bet your boots that the crisis happens 2 a.m. on a Saturday, right? It doesn’t conveniently happen at 2 p.m. on a Monday. So what often used to happen is that paramedics who visited the home, because that’s who the call goes to, it goes to 911, all they could do was just transport the patient to hospital. And then they ended up in a merge, which is not the place where they wanted to be.</p><p>So by introducing new models of care that supported different scopes of practice for paramedics, also often had a back-end clinical solution, digital solution, that would allow them to connect in with the patient’s care plan from the palliative team, that would allow them to connect in with support that they might need to deliver the best possible care they were then able to provide care in the home. So about half of the time, actually, paramedics who’ve been trained in this approach and supported to deliver it no longer have to transport the patient to hospital, but they’re actually able to support them in their own home. And not only is that way better for the individuals and their families, paramedics find it really rewarding work because they’re able to provide that care and address the issue that folks call 911 and also we found that on average it saves half an hour on a paramedic call. Because many of our emergency departments paramedics have to wait for the patient to be admitted. So by being able to care for the patient in the home, they’re actually also saving time and then able to help more patients too.</p><p>Reuben (22:10)<br>Yeah, less waving around. Excellent. So it sounds like your team is very busy. Maybe tell me about the team at Healthcare Excellence and some of the people that are helping to move forward these innovations.</p><p>Jennifer Zelmer (22:14)<br>Exactly. Yet we do have an absolutely amazing group of just over 100 folks who work at Health Care Excellence Canada. And we’ve now got folks who work in every province across the country. Not yet in the territories, but I’m sure that’s coming soon. And so we as an organization work very virtually as well, although we do still have a physical office in Ottawa and the folks who work with us have a combination of backgrounds. Some of them have clinical backgrounds, some of have backgrounds in improvement, some of them have IT type backgrounds. So we’ve got the whole mix of folks who work together and that’s sort of our core on staff, but the team is actually broader than that. So we have coaches as well across the country who don’t typically work for us, but are partnered with us.</p><p>faculty for the different programs, and then patient partners also who work with us and provide advice both to HEC but also to those we work with. And then of course as I mentioned peer-to-peer support is an important part of our programs. So the teams we work with are also part of that team because they can provide support to the team next door or the team very far away. We find for instance we have a Northern and Remote Network that we host which is basically the Health Systems North of 60. And you can imagine that somebody in northern Saskatchewan probably has more in common with someone in Labrador than they do with someone in Regina in terms of the care setting and the context. creating those broader connections is an important part of what we do as well</p><p>Reuben (24:00)<br>Yes. And you talked about the coach role and that’s really interesting and can be really effective. So who are the coaches? Are they physicians themselves or is it just varied backgrounds again like the rest of the team?</p><p>Jennifer Zelmer (24:24)<br>Yeah, it is very background. So some of them do have clinical backgrounds and then provide coaching on those aspects. But we also need people with other backgrounds. So we need people, for instance, with an evaluation background who can support teams to understand how are the changes that they’re making changing the outcomes that they’re looking for or not, and how do you adjust? We have folks who have expertise in improvement science and in implementation science. So bringing that knowledge and set of skills in as well. So you have a whole range of with different backgrounds so that we can draw on them as we need to along the way.</p><p>And a really important part of our coaching team are expert patient partners and folks who have other types of lived experience because they can provide a very different perspective on things like how do you engage effectively? How do you ensure that you are being responsive to your community, that you’re really listening well? So we need that full range of skills in our coaching team just as we do in our core staff.</p><p>Reuben (25:31)<br>Excellent. Switching gears a little bit, I did notice that you recently graduated from Royal Roads University. Could you tell us a bit about the program there?</p><p>Jennifer Zelmer (25:46)<br>Yeah, so I took an executive coaching certificate actually. So to up my own skill level on coaching and get a different set of tools in my leadership toolbox was really the goal. And it was very much a learning by doing program, which is a way that I learn effectively. So it was the opportunity to really get skills and experience in how do you coach well. And how do you do that in a context where you may have technical expertise in a subject matter or you may not? And how do you support people to be their best selves and to achieve the things that they’re aiming for?</p><p>Reuben (26:29)<br>And was that a lot of in-person work or was it mostly remote and virtual?</p><p>Jennifer Zelmer (26:37)<br>it was no in-person work. It was all remote. So I met, I think, with one of my fellow cohort, there was quite a lot of us, once for coffee in person, because she happens to be in Ottawa, but otherwise it was all remote. But it was just such a fascinating mix of people across the country. in the team that I was working, for instance, with most directly, we had one person who was had a sales background on the commercial side, one person who was a master trades person, so brought that set of experience, a former Olympian who brought a sports background, someone who came from a real estate world and brought that perspective. So we had a whole range of different backgrounds, which meant that we were really able to focus on coaching competencies, because we did not have subject matter in common.</p><p>Reuben (27:12)<br>Okay, nice. Well, it sounds like a great group. And is that something you’ve you always been kind of kind of continuously learning and in addition to your career?</p><p>Jennifer Zelmer (27:48)<br>I love to learn how many of us, you know, don’t want to do that and try new things along the way. I think for anyone in digital health though, it’s kind of a requirement, isn’t it? You even if I think about where something like generative AI is today compared to where it was even a couple of years ago, you fundamental change. So I think early on, maybe it was some of the tech changes that sort of pushed me into that continuous learning. And now I just love to learn whatever the subject has to be.</p><p>Reuben (28:19)<br>Yeah, I think in my day job in technology, know, things are changing so fast. Every day is continuous learning for me. And I love it as well. I’m just always impressed when people can, you know, take courses on top of their regular duties and to kind of improve their knowledge and other subject matters. So good for you.</p><p>Jennifer Zelmer (28:44)<br>I was really fortunate I had two colleagues who forged the path a year ahead of me and showed me that it was possible. I was able to take the plunge based on those peer-to-peer learnings.</p><p>Reuben (28:55)<br>So when it comes to Health Care Excellence Canada, are there any new initiatives or events or exciting things coming up that you’d to share?</p><p>Jennifer Zelmer (29:10)<br>So we actually just launched a new initiative in long-term care focused on how do we improve person-centered care so that we reduce inappropriate use of antipsychotic medication. So antipsychotics are amazing if you have psychoses, but if you do not have that diagnosis, then they are not the right medication for you typically. but they are often prescribed to folks in long-term care. And so what we know is that reducing the use of those medications means that we need to look to what are the non-pharmacological approaches that are supportive of people where they’re at and the needs that they have.</p><p>So just to give you a concrete example, I remember this story that one of the teams that we worked with in an earlier program told me that one of the residents anytime there was a team meeting at the nursing station would come and would bang on the window. And it was quite disruptive to the meetings and it was one of the behaviors that meant that he was put on antipsychotic medication. And when they huddled with the family and they really looked at what the background, what his background was, he had been an executive for his career. And so he was used to being the person in the meetings making the decision, not the person excluded from the meetings. So they brought in an extra chair, they brought in a clipboard, they welcomed him into the meeting, and he was there. And the meeting proceeded as it would normally have, and he felt included in that process. There was no more banging on the window, obviously. so sometimes it’s those kind of concrete specific changes that allow you to get to a different place.</p><p>So that’s a program that we’ve just launched and then we’ve got more stuff coming up in the spring looking at how do we support high quality primary and community care that reduces the need for emergency department visits. Because about four in ten Canadians said they went to the emergency department for something that they didn’t need to if other care had been available in their community. So that’s a big effort that we’re going to be tackling in the spring.</p><p>Reuben (31:27)<br>Mm-hmm. And all very important places for improvement. And I love that story too. It’s a great way to kind of wrap things up. And I really appreciate you joining me on the podcast today, Jennifer.</p><p>Jennifer Zelmer (31:46)<br>Likewise, lovely to chat with you.</p><p><em>Originally published at </em><a href="https://mindsea.com/moving-digital-health-jennifer-zelmer/"><em>https://mindsea.com</em></a><em> on January 21, 2025.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2bc3175247e8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mindsea-development-inc/moving-digital-health-episode-31-jennifer-zelmer-2bc3175247e8">Moving Digital Health, Episode 31: Jennifer Zelmer</a> was originally published in <a href="https://medium.com/mindsea-development-inc">Moving Digital Health</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moving Digital Health, Episode 30: Vanessa Rokni]]></title>
            <link>https://medium.com/mindsea-development-inc/moving-digital-health-episode-30-vanessa-rokni-38881be8d8ac?source=rss-3b53535c9a60------2</link>
            <guid isPermaLink="false">https://medium.com/p/38881be8d8ac</guid>
            <category><![CDATA[health-technology]]></category>
            <dc:creator><![CDATA[MindSea]]></dc:creator>
            <pubDate>Thu, 28 Nov 2024 15:35:27 GMT</pubDate>
            <atom:updated>2024-11-28T15:40:51.545Z</atom:updated>
            <content:encoded><![CDATA[<h3>Moving Digital Health, Episode 30: Vanessa Roknic</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Zj1QCCsWc1OM1N0e.png" /></figure><p>Our guest this episode was Vanessa Roknic, Senior Commercial Innovation Executive &amp; Digital Transformation Leader. Vanessa joined Reuben Hall to discuss the intricacies of innovation in the pharmaceutical and digital health sectors.</p><p>“If we had done the right kind of quick testing and experimentation right at the beginning, that’s something that we could have found out, stop spending time, stop spending money and moved our resources to something that is going to be more successful both for the company, but also more importantly, the patients.” Vanessa Roknic on failing fast.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FW6qj_ZO4t9Q%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DW6qj_ZO4t9Q&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FW6qj_ZO4t9Q%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/eb2fe23e1c66494025971bf2f48b759a/href">https://medium.com/media/eb2fe23e1c66494025971bf2f48b759a/href</a></iframe><p>Find <em>Moving Digital Health</em> on <a href="https://podcasts.apple.com/us/podcast/moving-digital-health/id1610546047">Apple Podcasts</a> and <a href="https://open.spotify.com/show/0OXaAaHQkfa4cfUg1BKf4M">Spotify</a>, and <a href="https://share.hsforms.com/1EgOC1hDpQjmPHAmNnKQc5Q185gy?__hstc=71280975.d141b9bdeedddd7967e2f47b2e5014ca.1639602052475.1661870519476.1663607831453.158&amp;__hssc=71280975.3.1663607831453&amp;__hsfp=817607603">subscribe to the MindSea newsletter</a> to be notified about future episodes.</p><p><strong>Read Transcript:</strong></p><p>Reuben (00:01)</p><p>Welcome to the MindSea Podcast series Moving Digital Health. Our guest today is Vanessa Roknick, Senior Commercial Innovation Executive and Digital Transformation Leader. Welcome to the podcast, Vanessa.</p><p>Vanessa Roknic (00:15)</p><p>Thanks Reuben, nice to meet you.</p><p>Reuben (00:17)</p><p>Could you tell us a little bit about your background?</p><p>Vanessa Roknic (01:34)</p><p>Of course. So my background is primarily in front end R&amp;D. Originally I got my bachelor’s of science in medical microbiology and immunology. And while I started off working in a lab, I gradually found myself not feeling really fulfilled or challenged by that type of work. So I actually went on a working holiday visa over in London and fell into pharmaceuticals and just had a passion for it ever since.</p><p>I really struggled at first to understand why when I was working in a lab, things would take so long to get from the bench through to the market. And then when I got exposed to pharmaceuticals, I started to see the reasons why with the red tape and the regulations that surround it. And that I think is where the red thread for my career has really taken hold. It’s where I find these pockets of places that just</p><p>need to sort of have some way of challenging the status quo and trying to make things, you know, more efficient. And I think that’s what really drew me towards pharmaceuticals and particularly in the clinical trial space. And then it’s only in the recent years that I’ve started moving over into the more commercial side of the business to see how some of the works and the skill sets that I I leveraged in the clinical space can be transferred over into the commercial space and particularly in</p><p>innovation and digital transformation.</p><p>Reuben (03:07)</p><p>And you were at Nova Nordisk for about 10 years in various different roles. Maybe tell us where you started and kind of where your progression went.</p><p>Vanessa Roknic (03:18)</p><p>Yeah, well, so originally, if you can’t tell, I’m from Sydney, Australia, and that’s where I started with Novo. Back in 2014, I was there and I was working in the clinical trial space and I really, I really loved the company.</p><p>I really loved the work and it just so happened that there was some roles available over in the US and they transferred me over here back in 2016 and that was still in the clinical trial space and I really do enjoy that because knowing that you’re at the forefront of research and development with these new drugs that have been, you know, tested in people and, you know, you’re trying to find out whether they’re safe, whether they work.</p><p>it’s just it’s really exciting place to be. But I did that for many years and then I think when I came over to the States I was kind of exposed to…</p><p>a lot more of the different areas within the pharmaceutical industry. And I really started to try to branch out into different spaces. So while I was still working in the clinical trial area, I was in more of a business performance role, which was looking at data and trying to find insights from the clinical trials we were running and being able to use that data to share insights to our leadership team and allow them to be able to make more informed</p><p>decisions that we’re going to benefit the business, benefit our patients and our partners.</p><p>Reuben (04:53)</p><p>Maybe you could tell us a little bit more about your last role at Novo and what that entailed.</p><p>Vanessa Roknic (04:59)</p><p>Yeah, so more recently, once I was working in the clinical trial space and I was lucky enough to get a new role, which was in leading a new team for the organization. And it was what we called APIS Labs at the time. And it was actually driven by the executive office. They looked at how we were innovating, you know, I think it was back in 2018. And they just really thought that we could be doing it in a different way and a more accelerated way. And so they</p><p>did a current analysis of what the organization looked like at that time. What was probably a more organic next step and that was the lab. And we were in essence an internal incubator. And my role for that lab was to oversee the operations of it to sort of own the framework that we were using to drive the strategy forward. And so we had one of the interesting things that I really loved about the team is that we were product agnostic.</p><p>we weren’t there just to sell more product in the market. We were there to really understand what were the true pain points of our customers. And when we say customers, it could be patients, could be doctors, it could be payers, anyone that’s within that health care, the US healthcare ecosystem that’s having a pain point and really figure out how we can solve their problems that they were experiencing whilst creating a shared value for the business. Because obviously at the end of the day,</p><p>we are a business, we need to make money, but how do we do that while still keeping our customers at the forefront of what we were doing and what they’re experiencing? So that was really exciting. We had three experimentation teams that were working on different strategic focus areas at the time. And it was using combined methodologies like Agile, Lean, Design Thinking, all those sort of fun things that you’re hearing a lot more about now.</p><p>were just trying to pioneer this new way of working. We had no idea whether it was going to work and obviously there was a lot of bumps along the way but I think towards the end there we really were a high performing and high functioning team. So it was quite a journey to be a part of and to help drive for the organization.</p><p>Reuben (07:18)</p><p>For sure, innovating within a large organization can be very difficult. What type of frameworks were you using to make that possible?</p><p>Vanessa Roknic (07:29)</p><p>Yeah, well, I mentioned briefly those, those methodologies, but that’s not normally the thing in my opinion, that slows things down. It’s just the, the sheer size of an organization. When you’re talking about these big pharma companies, know, thousands of people, that’s like a huge machine to get moving. You’ve got a highly regulated space, you know, like pharmaceuticals, and I’m sure you experienced similar sort of red tape, sort of, you know, inhibitions, not inhibitions, that’s</p><p>not the right word, you experience a lot of regulation challenges, red tape and sort of barriers to innovation. And so what we did</p><p>on top of having a framework and a remit that we adhere to, we actually engaged with a lot of our regulatory partners, internal regulatory partners I’m talking about. we had every other week we’d bring together a group of people that included privacy experts, data privacy experts, ethics, compliance, safety, all these, all these.</p><p>really sort of high risk areas and we wanted to bring them in as early as possible and as transparently as possible so they could help us along the way build towards what we needed to build towards.</p><p>The reason why that’s important because a lot of the time because people see those areas as maybe barriers to innovation or barriers to progress, they don’t engage those partners until towards the end when they’ve got something that they really love but then it’s not going to be feasible in the market.</p><p>Reuben (09:09)</p><p>room.</p><p>Yeah, let’s build the product first and then worry about passing the regulations later, right?</p><p>Vanessa Roknic (09:19)</p><p>Exactly, exactly. And while it might seem like the right mentality to have around innovation because you have to be breaking down barriers.</p><p>there’s so much more you can do and do more constructively as well when you’re working with those people. for example, this was not something that we were working on, but if you, actually let’s look at something that people are probably familiar with, of glasses. People were looking at a lot of glasses that can have cameras in them and the issues with things like that in healthcare is,</p><p>compliance with privacy requirements. if you, if you have the potential to record someone else’s face, that face is considered private information. So you can’t share, you can’t share that. You can’t store that electronically. And so things like voices as well, that’s in some places considered personal identifiable information. So you can’t, you can’t record that either. If you’re, if your glasses, you’re walking with your glasses on and you’re recording,</p><p>addressed, that’s personal identifiable information. So you have to be aware of all those things that could be an issue down the line. And there are ways, it doesn’t mean that you can’t, for example, have the glasses, it just means that you might have to have some steps in place to prevent those kinds of things from happening. And the sooner you start making plans for that and designing features, so you achieve those goals, the less of a burden it’s going to be at the end when you’re just trying to get it on the, you know, get it out there in the market.</p><p>kit.</p><p>Reuben (10:58)</p><p>Yeah, that makes a lot of sense. It reminds me of Google Street View when you go in and they have the faces and certain things blurred out to avoid identifying individuals and using similar solutions to record the things that you wanted to record but obfuscate or remove the things that you’re not allowed to record.</p><p>Vanessa Roknic (11:26)</p><p>Yeah. Yeah, exactly.</p><p>Reuben (11:31)</p><p>So you’re a big proponent of failing fast. Can you tell us about some of the projects you’ve been part of that did fail?</p><p>Vanessa Roknic (11:42)</p><p>Yeah. I mean, I can definitely talk about the way that we define failing fast. And so I think you hear a lot of the time about failing fast, failing early and failing often. The reason being is…</p><p>If you, we just talked about a good example then with like maybe glasses or a product that you get all the way to the end and then you find out that it’s completely unfeasible within the market that you’re in. If we had done the right kind of quick testing and experimentation right at the beginning, that’s something that we could have found out, stop spending time, stop spending money and moved our resources to something that is going to be more successful both for the company, but also more importantly, the patients.</p><p>And so that’s the real reason why that’s important from a business sense. But when you’re talking about from an innovation perspective.</p><p>There’s so much happening. There’s so much changing all the time that you need to move fast in order to keep up with it. You you can think of all those graphs that they show where where technology is like moving exponentially or progressing exponentially. And so that’s the kind of pressure that you’re under with innovation. It’s not about trying to come up with the next shiny toy. It’s about how things are just constantly changing and how can we leverage some of those things to to benefit the patients in the pain points that</p><p>they’re experiencing. So one of the best examples that I have in regards to, you know, failing fast and failing often is this concept of, was it 3D glasses, 3D goggles, whatever you want to call them. And people trying to find ways to use them for Alzheimer’s or something like that. And</p><p>It sounds great in theory, it sounds great from the science, it can do all these really good things. But when you ask patients whether they’re willing to wear something like that, the answer will be no. And it’s been historically like that. And so I think that’s…</p><p>where we would go to first is the patient or the customer, what their problems are, and really understand what their needs are in order to move forward. If we’d find something that we thought was good and we believed in it, we’d go back and test it with the patient. If they liked it, we would continue. If they didn’t, we would probably just move it to the side.</p><p>So that’s how we would work with failing fast and failing often. We had a lot of projects that wouldn’t even get past the first phase of our research because we realized that it wasn’t a desire for the patient, even though the business was asking for it. When we’d go and test it with people, it would be, they’re just not interested. So I think sometimes that would be my message to your listeners out there is to really challenge yourself</p><p>about whether what you’re chasing that product at the end of the funnel is what your customers wants or whether it’s what you want as a business.</p><p>Reuben (15:28)</p><p>Mm -hmm. Yeah, you see it so often when people are jumping to solutions and they say, I have this great technology solution, this great application for a new technology, and it’s going to be perfect to change at XYZ. And they have that really clear vision in their head, and they just want to build that vision. But they haven’t.</p><p>gone back to the end user, whether it’s a patient or a clinician, to validate that hypothesis with them. You can spend a lot of time and lot of energy building the wrong thing, building a solution that doesn’t have that fit, that doesn’t solve the user’s needs. So we’re a big proponent of human -centered design.</p><p>and rapid prototyping to make sure the end user is always involved with the product development, not just at the beginning, but throughout the different phases.</p><p>Vanessa Roknic (16:35)</p><p>Hmm.</p><p>Yeah, I think that’s that’s one of the challenges when you look at a typical operation of these large, large organisations like pharmaceutical companies. They’re very much more used to the typical way of working, which is, you know, waterfall project management, you deliver the final product, and then you go take it to the market. Whereas what you were just talking about, and what we were working that sort of confines that our team were working within was, it’s a it’s that design thinking, it’s the</p><p>agile sort of iterative steps. So working on those small pieces, getting feedback, and then continuing to build and not just build that one thing and then hope that they like it at the end. So that’s how I think we were able to sort of challenge some of those barriers that you would normally see within a large organization like that.</p><p>Reuben (17:32)</p><p>Yeah, I think some people have this misconception of entrepreneurship that, you know, it is the great visionary like, you know, Steve Jobs, you know, people, people don’t know what they want until you until you give it to them and then they see what they want. Well, that’s great. But what’s the smallest, fastest thing we can build to put in front of people?</p><p>Vanessa Roknic (17:51)</p><p>Yeah.</p><p>Reuben (17:59)</p><p>to let them try it out and see if it works or not. Let’s not spend 12 months building that vision. Let’s build the smallest piece of that we can to test it and then continually test it out.</p><p>Vanessa Roknic (18:03)</p><p>Yeah.</p><p>Yeah and I think like I’ve used similar examples sometimes there’s that I’m not gonna I’m not gonna do it justice but the whole that whole sort of story around well people didn’t know they wanted a car until the car came along but people did know that they didn’t want to keep shoveling horse poo people did know that they wanted a faster horse like people did know that they didn’t want a horse that they had to continually feed and so</p><p>What I imagine, what I’m imagining in my mind is the person who invented the car was not just going, I’m, I’ve just come up with this idea for four wheels and blah, blah, blah. It’s like, I, there’s these pain points that people are experiencing with having a horse and buggy.</p><p>So how are we going to address those? And I guarantee you they went out there and sort of figured out what was the actual pain points and gradually were able to move things forward. Similarly to the iPhone, I’m sure they didn’t develop that in a vacuum. I’m sure they were going out there with some of the features that they have and testing them before they released the first one.</p><p>But I agree that people maybe can’t sort of visualize what it is that they need, but they know what they want.</p><p>Reuben (19:34)</p><p>Yes, and you mentioned the word pain points. I mean, that’s it, right? Like they want those pain points removed from their life. You know, whether it’s a symptom they’re dealing with, with a condition, an illness, you know, they want to get past that. Whether it’s you know, technological hurdle.</p><p>where they’re doing administration and they have to do the same 10 steps every time and they know they’re wasting their time and they know there’s a better way to manage this solution. It’s all about removing that pain.</p><p>Vanessa Roknic (20:05)</p><p>Yeah.</p><p>Yeah, absolutely.</p><p>Reuben (20:15)</p><p>So how many different projects do you think were going on at one time within the lab?</p><p>Vanessa Roknic (20:23)</p><p>Yeah. Well, so our lab.</p><p>I’ve mentioned before, we were about working very quickly iteratively. And so at any given time, we would try to be encouraging the teams to be working on four to six opportunities at a given time. And so for example, each pain point or problem statement of a customer was an opportunity. But each of those opportunities could, in theory, land you multiple solutions because they might not</p><p>be just one solution for multiple, for a problem there might be multiple solutions and we’d want to go out and test all of them.</p><p>But at the end of the year, our goal was to have around about 10 to 15 opportunities that we’ve worked on. I hope that one of those might make it through to the end of the funnel and be a successful solution that we could then use for the business or in the market. so it was all about, we put those goals, those sort of objectives to the team as sort of a target for them to aim towards, a way to encourage</p><p>them to move more quickly in the way that we needed them to because it’s so easy to think well I’ve just got this one project I’ve just got to really make sure that’s successful and we were trying to get past that idea that this is your baby this is something that you have to make successful it’s like no this is one project this might not be the most successful one that’s going to come out of your team so let’s make sure that you’re hedging your bets and you’re working across a breadth of opportunities rather than just that that one.</p><p>Reuben (22:00)</p><p>Yeah, don’t get too emotionally attached because we have to make some tough decisions about what goes on and what doesn’t. How did you involve academic researchers and academic institutions in that process?</p><p>Vanessa Roknic (22:17)</p><p>Yeah, so one of the barriers that we found or the challenges I would say is that</p><p>our team, because we were very small, we were about five people and we did move quickly, a lot of the time we had to be creative with how we worked more quickly. And so we were getting approached a lot by different academic institutes to see if we would sponsor maybe a capstone project or something similar. And we just, in the end, we started with one, I think it was the University of Washington.</p><p>And we just had a really good experience with them. And so started branching out into into other academic partnerships with one of my colleagues. He was the one that was leading, leading that work and.</p><p>It was just such, I mean, it was great from multiple angles. One, you’re at the forefront of technology, academia, they’re at the forefront of new technologies coming out, they’re developing in it. So it was really great to just listen and learn from them. You’re also getting students who have different perspectives than maybe someone who’s been a little bit jaded by the pharmaceutical industry. So they’re coming in fresh, fresh bright eyes. They don’t have the expertise.</p><p>Reuben (23:29)</p><p>Ha ha ha ha.</p><p>Vanessa Roknic (23:36)</p><p>bias that about what can and can’t be done. And, and so it was just a really great way for us to get not only I talked about the forefront of technology, but also this different kind of perspective. And then the last thing was just enabling us to move quickly they with the work that they would do on some of the concepts that we would provide them and deliver a tangible prototype.</p><p>Reuben (23:40)</p><p>Yeah.</p><p>Vanessa Roknic (24:03)</p><p>it was just, it was more than what we could have done in that time. And it was also just a lot different because of the different perspectives that they had. And so it was, that was really, when I look back, I think that was a great way for us to move more quickly in that we could focus on other things while they would then build the prototypes that we were looking to build. it was,</p><p>They would, it was just a really great experience from our side, I hope for theirs as well. But I do encourage, know, even for like, you know, future sort of lines is another angle that we would come at it from if there was an opportunity for them to be brought into the business as well, that would be even better. Because then you’re getting all these people with what I just talked about that they know about these upcoming technologies, they have these different perspectives,</p><p>life experiences that they can bring to the table that maybe our team just didn’t have.</p><p>Reuben (25:07)</p><p>Can you tell us about any of the other successful partnerships or projects that came out of the labs?</p><p>Vanessa Roknic (25:15)</p><p>I mean, there was a lot of partnerships because I think in innovation, you’re successful when you work with others. Innovation is not done in a silo. You need to collaborate because the skills that I have, the skills that our team has is not going to be the same as another team. So, for example, we had an internal team who were really great at scouting. And so we would leverage them if we ever needed a landscape analysis on a particular solution that we were thinking about.</p><p>they will go off and do some research in that space. So it’s like internal partnerships are critical.</p><p>But then also externally, yes, we did have a lot of different partnerships, you know, with the academic institutes that I just mentioned, but there was also some of in Boston, we were members of an organization called Farmstars, which is all about bridging the gap between big farm, the communication gap between big pharma and smaller enterprises that have a good solution to offer, but are struggling to sort of get it.</p><p>in there. So it’s teaching them about how do you, how does pharmaceuticals works, how does the industry work, how do you speak to the big executives, what are they going to be most interested in looking for. And so that was that was a really great experience, a really great partnership to be involved with.</p><p>Reuben (26:47)</p><p>Yeah, I’m sure like some of the projects you might not be allowed to talk about just because it’s, know, innovation in progress. But even in a generic way, are there any like product success stories where, you know, you were working on an innovation team that, you know, got out of that beta stage and into a live production environment and you got to see the impact on patients or clinicians and the</p><p>of that solution.</p><p>Vanessa Roknic (27:18)</p><p>Yeah, there was some one proof of concept that we worked on and the reason why I’m bringing it up because it was the first successful one that we had as a team. So it’s always like a very fond memory for me. But it was basically a predictive algorithm that we were working on in order to understand the risk of a patient that was presenting with certain symptoms of developing these adverse long -term health outcomes. So for someone living with</p><p>type 2 diabetes, what’s the risk of them at some point in their lifetime getting lower extremity amputations. And so we were working on that kind of model and it was actually just for our team at first. We were just seeing if it was something that we could predict and</p><p>But then through collaboration and trying to get feedback on it from our medical affairs partners, they actually really liked the tool and wanted it to be brought into a larger tool that they were developing. So we ended up handing off the algorithm. Actually, at first we were working with other teams. So we have these great data scientists that work within Novo. They were helping us build it and also data engineers as well. And eventually,</p><p>we were able to hand it off to medical affairs and it’s being used with them, engaging with their, through their medical liaisons with our healthcare professionals in the market. So that is something that I’m super proud of that we were able to deliver for the organisation and is actually delivering value for the relationship between the medical liaisons and the HCPs.</p><p>Reuben (29:09)</p><p>It’s always really rewarding to see a project go live in healthcare because sometimes it just takes so long. Like you said, the development process and ensuring that all the privacy and security is in place. And those are all very important to make sure the regulations are there.</p><p>Vanessa Roknic (29:28)</p><p>Yeah.</p><p>Yeah.</p><p>Reuben (29:36)</p><p>So when finally something is live and you see it out in the wild and it’s making an impact, yeah, must be a very proud moment.</p><p>Vanessa Roknic (29:46)</p><p>And I think what’s important to, I think, clarify with that is it wasn’t a one and done. When they released it and were testing it in the market,</p><p>They, was just on one therapeutic area and it was, you know, just trying to get feedback on whether it was useful or not. And, and now they’re looking to expand it into other therapeutic areas. So I think that’s, that’s also an important point to make is that you don’t, don’t need to boil the ocean. When you’re coming up with these ideas, you can start with something very small, just to test it out first and see whether it brings a value that you think it could. And that’s when you start expanding it. So you’re not investing like we were talking about before all this time.</p><p>effort and money into something that may not do exactly what you think it will do. And I was kind of alluding to this before, know…</p><p>Generally not just in pharmaceuticals and but across industries when you’re innovating properly You’d be expecting 90 % of what you’re working on to be failing if you’re doing it properly And so that’s why the volume and velocity is super important because if I was only working on one project a year There’s a 90 % chance that that project will fail so that’s why you need to kind of hedge your bets and and and work on more so that it’s kind of I like</p><p>to think of it from, I guess, my clinical trial days, when you think about you start with thousands of different molecules. And, you know, not all of those molecules make it to lab the lab bench, not all those molecules make it to pre clinical trials in animal studies, not all of those molecules make it to pre clinical and then clinical studies, you’re, you’re getting this big drop off along the way until at very end of the funnel, you get that</p><p>one product that’s going to make it to market that one molecule. And by that time, that’s probably like 15 years and billions of two point, I think the last time I looked at the metric, was two point one billion dollars that you spend on one molecule making it to the market. That’s just because you’re starting with so many, you’re spending so much money and time working on those, those, those thousands of molecules and eventually getting it down to the one.</p><p>Reuben (31:52)</p><p>Wow.</p><p>Vanessa Roknic (32:01)</p><p>and people don’t see that. And it’s the same with innovation. You need to sort of start really wide, cast a really wide net, and then gradually you get to that one opportunity that is going to be successful.</p><p>Reuben (32:16)</p><p>Yeah, it would be crazy to just have one molecule and expect that one to be successful and going through all the stages. And it goes to the point of failing fast as well. The less time you can spend on the things that aren’t gonna work gives you more time to spend on the things that are gonna work.</p><p>Vanessa Roknic (32:26)</p><p>Yeah.</p><p>Yeah, absolutely.</p><p>Reuben (32:43)</p><p>So what are some of the opportunities or innovations you’re most excited for in digital health?</p><p>Vanessa Roknic (32:50)</p><p>I like this is a bit of a cliche, I’m definitely, and I always do try to caveat with the, don’t be enamored by the shiny object, but I do really think there is going to be a lot of promise with AI. And, you know, even if it’s not for…</p><p>customers or patients, I’m super excited about what it can mean for the productivity within a company in terms of one thing that I found super helpful is the transcription of minutes from meetings. So like little things like that, I think I’m super excited about what that can mean for companies and customers.</p><p>And so that’s something that, mean, like I say, it’s cliche, but that’s one of the things that I’m, that I’m really excited to see the progression of. I, I try not to focus too much on just the tools themselves. What I try to encourage people is to think about the pain points because you, know, I mean, a lot of the, a lot of the innovation that we’re talking about is going to be in digital, but there’s always those customers that just are not going to have access to it. When you think about, technology deserts, internet.</p><p>deserts, just the rural locations where people live and just having access to physical locations. There’s just so many other limitations that are going to prevent digital from being a solution for them. So that’s where I think we need to start being more creative and going beyond just the digital and trying to think about innovations. just as an example, we talk about in terms of relationships, policies,</p><p>structural changes in a company, things like that. So, try not to limit myself to only those kind of perspectives.</p><p>Reuben (34:46)</p><p>Yeah, I 100 % agree. You know, AI is a huge opportunity and will be ongoing for the future for improvement of healthcare. I do feel like a bit of a broken record sometimes, be Like, well, yeah, of course, like we’ve been talking about this for a while, but it is ongoing and it’s interesting to see the…</p><p>the new use cases or the new applications of AI in different specific fields. But we can’t forget about, there are other ways to innovate beyond just AI and technology solutions. Like you said, there’s multiple things that need to be explored to solve those pain points. It’s not always technology.</p><p>Vanessa Roknic (35:41)</p><p>Yeah.</p><p>Reuben (35:41)</p><p>Technology is great, AI is great, but it’s not the only way to solve problems.</p><p>Vanessa Roknic (35:46)</p><p>Yeah, my boss used to say about, you know, could be low touch, high tech, high tech.</p><p>or sorry, high touch, low tech. So it could be either one of those combinations. And that’s the way I like to think of it. It’s always the option. And yes, there certainly are ways to use digital and technology to make life easier, but let’s not just automatically put our bias on towards that. it could be, you know, it could be AI and a new policy or it’s just maybe not as sexy to say it that way, but</p><p>It’s definitely an option.</p><p>Reuben (36:28)</p><p>Yeah, and how about yourself? Like what’s the next step for your career? Where do you see that going?</p><p>Vanessa Roknic (36:34)</p><p>That’s a good question. I am very passionate about innovation, I feel like that’s a bit of a, know, innovation can mean so many different things to different people and it’s more, I feel like it’s overused at the moment. I’m passionate about helping people that feel like they just can’t figure out their way around a wicked problem and trying to help them navigate that.</p><p>I think what I’ve learned throughout my career is you just need to keep things moving forward in any way you can. Like a little bit of momentum is better than none. So as long as you’re moving in the direction that you think you should be moving, whether it’s like a millimeter or whatever.</p><p>I think that’s what I love helping people figure out is realizing that they can achieve what they think is unachievable. And so that’s what I’m looking for in my next role is to, you know, still that innovation theme, but it can be, I mean, it can really be anywhere, right? It’s not just healthcare, it’s not just pharmaceuticals where that type of change is needed, but definitely prevalent.</p><p>you</p><p>Reuben (37:50)</p><p>Yeah, there are no shortage of problems to solve out there. So I’m sure you will find one to dig your teeth into and help solve it. It was great to hear your perspective and some of your experiences and share your knowledge today. Thank you so much for joining us on the podcast.</p><p>Vanessa Roknic (38:09)</p><p>Thank you.</p><p>Reuben (38:11)</p><p>And thanks to everyone listening. If you enjoyed the Moving Digital Health podcast, please go to movingdigitalhealth.com to subscribe to the MindSea newsletter and be notified about future episodes.</p><p><em>Originally published at </em><a href="https://mindsea.com/moving-digital-health-vanessa-roknic/"><em>https://mindsea.com</em></a><em> on November 28, 2024.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38881be8d8ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mindsea-development-inc/moving-digital-health-episode-30-vanessa-rokni-38881be8d8ac">Moving Digital Health, Episode 30: Vanessa Rokni</a> was originally published in <a href="https://medium.com/mindsea-development-inc">Moving Digital Health</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Academic Digital Health App Development: Overcoming Challenges]]></title>
            <link>https://medium.com/@MindSeaTeam/academic-digital-health-app-development-overcoming-challenges-94d1a0359416?source=rss-3b53535c9a60------2</link>
            <guid isPermaLink="false">https://medium.com/p/94d1a0359416</guid>
            <category><![CDATA[health-technology]]></category>
            <dc:creator><![CDATA[MindSea]]></dc:creator>
            <pubDate>Mon, 18 Nov 2024 18:50:39 GMT</pubDate>
            <atom:updated>2024-11-28T15:39:27.674Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*obYk9y1CW8rFNe1Rlupr-g.jpeg" /></figure><p>Digital health apps are reshaping healthcare and transforming patients’ lives with every download. Whether it’s through remote patient monitoring, collecting accurate health data, connection to other patients, improving workflow efficiency and experience to ease the burden on physicians, or even virtual consults, the possibilities these apps open up often seem endless.</p><p>Universities and academic institutions are a great starting place to test digital health interventions. You need the evidence that the intervention improves the standard of care before it can be widely adopted, typically in a research study or clinical trial. Digital health app development requires an approach that matches up with that. While some of the challenges remain the same, it just isn’t the same as working within a tech startup or private healthcare organization.</p><p>Drawing on our experience of working with academic institutions and universities to build healthcare apps, we’ve taken a closer look at the key challenges and offered potential solutions to pave the path for a successful academic digital health app development process and launch.</p><h3>The Challenges</h3><p>When we first start working with researchers and academics, we often find that they have tried to build a digital health app in the past. However, they’ve run into issues that stem from factors such as poor user experience, low adoption, lack of support, and data privacy concerns, as we explain below.</p><p><strong>Lack of Expertise Gives You the Jitters</strong></p><p>App development isn’t within the wheelhouse of most academics. It’s a specialist skill with many different facets that takes time to learn. It’s common for researchers to get the jitters on their digital health app development journey. They don’t know the jargon and they’re not sure what the process will look like. The path ahead seems confusing and marred with potential pitfalls.</p><p><strong>Technical Skills Alone Aren’t Enough</strong></p><p>One situation that we’ve encountered fairly often is academic institutions that have used student programmers within their own organization to help them build an app and it hasn’t worked out.</p><p>It might seem like a good idea at the time, but simply knowing how to write code or having a theoretical knowledge of software development principles doesn’t mean they can write commercial code or develop a digital health app. The end result is an app that isn’t user friendly, doesn’t scale, is glitchy, crashes, and is just cumbersome and awkward overall.</p><p>Students also have competing priorities like their course work and they come and go from semester to semester, which means there is a lack of consistent, reliable support. Finding the people with the right skills is time-consuming, and then getting everyone on the same page is another challenge.</p><p><strong>Fails to Meet User Needs</strong></p><p>The goal of digital health apps is to make life easier for patients or people struggling with health issues. An app shouldn’t feel like it’s placing an extra burden on patients’ shoulders. However, if the design is flawed due to the above issues and you haven’t carried out research to understand what patients really need, then adoption will be low, and the app won’t be able to fulfill its purpose.</p><p>Making sure the app hits the mark with the target audience through strategic, phased rollouts, such as beta groups, feedback collection, and continuous improvement work, is key, but it’s not easy to achieve, especially if you’re using in-house resources.</p><p><strong>No Post-Launch Support</strong></p><p>Building an app is just the first step, but what will happen once it is released? Who will maintain it, update it, and deal with bugs post-launch? Some companies build your app and leave you to support everything and figure it out, but a good digital health app development partner is willing to continue to be an extension of your team to help build successful products.</p><p>Researchers have a great clinical understanding, but they need help with not only designing the app, but figuring out how to roll it out and maintain it when it’s live. This kind of maintenance requires a deep understanding of the app’s underlying technology.</p><p><strong>Data Privacy and Security Concerns</strong></p><p>Health researchers have specific, stringent privacy and security requirements and compliance needs (HIPAA, PIPA, GDPR, PIPEDA, to name just a few). This includes holding data within the relevant country, which many digital health app developers don’t offer.</p><p>Alongside national legislation, researchers also have to consider institutional requirements. The app needs to meet the ethics requirements and other privacy and security standards set by their internal review boards. Currently, there is a lack of a standard approach to building an app and, with that, a lack of knowledge of standard processes and requirements.</p><h3>The Solutions</h3><p>Choosing a digital health app development company with experience in both technical and healthcare spaces gives you access to the necessary skills to overcome the above challenges.</p><p><strong>Don’t Underestimate Industry Experience</strong></p><p>Developing digital health apps in an academic setting is different to building the same technology for businesses, which is why you should work with a company with experience in working with academic institutions and within their frameworks and requirements. You also get a cross-functional team, including product managers, UX designers and QA testers (not just developers), that is forward thinking and a true extension of your vision.</p><p>A digital health app development company can offer regular project reporting, which provides information on factors such as progress and budget. This allows problems to be flagged early on.</p><p>Knowledge is power, your digital health development app partner will explain the process clearly to give you the information you need to make a decision. Instead of feeling like the whole app development process is a black box, you get clarity on what is happening at each stage to ease your jitters. You’ll also receive a realistic estimate of costs based on the many products the company has previously worked on.</p><p><strong>Agile Development Overcomes Perfectionism</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7-OqgLfWyoO3eWcU.jpg" /></figure><p>Researchers are often perfectionists, high achievers who want their app to be able to do everything they imagined before they launch it. But that isn’t always practical, which is why the agile development method is so important.</p><p>Maybe you’ve made a list of 20 features you’d like your app to have before you’ll consider showing it to users. But building all those features will take years, and you don’t want to wait that long before launch. An agile development method focuses on the most important features (say five to eight core features, as an example), makes sure those are perfect, and then launches.</p><p>Once you’ve launched, the digital health app development company will then work on adding in more features gradually and updating the app each time you’ve perfected the new functionality.</p><p><strong>Get To Know Your Users</strong></p><p>User story mapping helps overcome poor adoption by making sure the app meets the needs of your target audience. For example, how and when would they use the app? What features do they need? What layout works best? What are their unique needs?</p><p>User story mapping is a structured way of brainstorming what the product needs to do and putting the patients at the forefront of app development. It helps us get a well-rounded idea of what the prospective user base needs and what we need to know about them before we start with the development process.</p><p><strong>Develop a Prototype</strong></p><p>Developing a prototype for an app helps overcome the issues of lack of user adoption and poor usability. When we develop an app, we test all the features, main user flows, and overall journey based on real-world scenarios before we start to code and build it.</p><p>Once the prototype is ready and the researchers have signed off on it, we’ll conduct the usability testing.</p><p><strong>User Testing is Key</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m2ftWw791HGJeVR3.jpg" /></figure><p>When we get users to test an app, we can spend about an hour with them testing how everything works. We ask them to imagine they are in a situation relevant to the app’s purpose and then ask them what they think they need to do to complete the task. We watch them use the app, note if there are areas that they struggle with or if something doesn’t flow, and then document their feedback.</p><p>We sometimes have to hand this process over to the researchers to lead due to ethics board requirements.</p><p><strong>Take Development Onshore</strong></p><p>You may not be surprised to hear that a lot of app development companies aren’t local to your institution and may store your data outside your country. To overcome data privacy and security issues, choose an onshore app development company. For example, if your institution is located in Canada or the US, you can use exclusively onshore developers, the data is stored in Canada/US and secure for users, and it also meets local data privacy regulations. The data isn’t leaving the country and coming back again.</p><p>If the development team and the entire process can be conducted entirely within Canada/US that counts as an extra onshore resource that adds an extra layer of security.</p><p><strong>Ongoing Tech Support Service</strong></p><p>When you launch the app, you won’t be on your own if you’ve chosen the right app development partner. They will be able to provide an ongoing tech support service and post-launch support.</p><p>They also understand the technology inside out, so they can work within its potential as well as its limitations. This includes developing a product roadmap that takes into account the technical specs and long-term goals of your app.</p><h3>A Blueprint for Academic Digital Health App Development Success</h3><p>At Mindsea, we’ve worked on developing digital health apps for many universities and academic institutions., We use the insight gained from working with researchers and academic institutions to create a blueprint and a product roadmap that is built exclusively for your users. For example, we worked with the <a href="https://sunnybrook.ca/research/">Sunnybrook Research Institution</a> to <a href="https://mindsea.com/projects-halterix/">build an app</a> that evaluates and shares patients’ exercise data with practitioners through a smartwatch.</p><p>If you want a partner in your digital health app development journey, <a href="https://mindsea.com/contact/">get in touch</a> with Alex today.</p><p><em>Originally published at </em><a href="https://mindsea.com/from-research-to-reality-overcoming-challenges-in-academic-digital-health-app-development/"><em>https://mindsea.com</em></a><em> on November 18, 2024.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94d1a0359416" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moving Digital Health, Episode 29: Arjun Puri of Symbiotic AI]]></title>
            <link>https://medium.com/mindsea-development-inc/moving-digital-health-episode-29-arjun-puri-of-symbiotic-ai-701e159da6a3?source=rss-3b53535c9a60------2</link>
            <guid isPermaLink="false">https://medium.com/p/701e159da6a3</guid>
            <category><![CDATA[healthtech]]></category>
            <dc:creator><![CDATA[MindSea]]></dc:creator>
            <pubDate>Tue, 22 Oct 2024 14:38:33 GMT</pubDate>
            <atom:updated>2024-10-22T14:42:21.843Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VfgjDf8X3opvxhhf.jpg" /></figure><p>Our guest this episode was Arjun Puri, CEO &amp; Cofounder of <a href="https://www.symbioticai.ca/">Symbiotic AI</a>. Arjun joined Reuben Hall to discuss the importance of leveraging healthcare information to improve decision-making for both clinicians and patients in cardiology.</p><p>“it is a complex and difficult decision to make when the patient is sitting on the cath lab table and you have to make that decision with the information that you have at the table” Arjun Puri on decision making in cardiology.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FR0qxaT0P-j0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DR0qxaT0P-j0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FR0qxaT0P-j0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f9a2f06b6cf4fe2af0f5bf4744b5f6e4/href">https://medium.com/media/f9a2f06b6cf4fe2af0f5bf4744b5f6e4/href</a></iframe><p>Find <em>Moving Digital Health</em> on <a href="https://podcasts.apple.com/us/podcast/moving-digital-health/id1610546047">Apple Podcasts</a> and <a href="https://open.spotify.com/show/0OXaAaHQkfa4cfUg1BKf4M">Spotify</a>, and <a href="https://share.hsforms.com/1EgOC1hDpQjmPHAmNnKQc5Q185gy?__hstc=71280975.d141b9bdeedddd7967e2f47b2e5014ca.1639602052475.1661870519476.1663607831453.158&amp;__hssc=71280975.3.1663607831453&amp;__hsfp=817607603">subscribe to the MindSea newsletter</a> to be notified about future episodes.</p><p><strong>Read Transcript:</strong></p><p>Reuben (00:01)<br>Welcome to the MindSea podcast series, Moving Digital Health. Our guest today is Arjun Puri, CEO and co-founder of Symbiotic AI, a clinical decision support platform to improve heart care outcomes. Thanks for joining us today, Arjun.</p><p>Arjun Puri (00:17)<br>My pleasure. Thanks for having me.</p><p>Reuben (00:20)<br>Can you start by telling us a bit about your background?</p><p>Arjun Puri (00:31)<br>Yeah, happy to. So my background is in digital health innovation and clinical informatics. I started out my career really working on healthcare information and understanding how we could leverage that healthcare information to benefit clinical care and improve healthcare services for everybody in the world.</p><p>Reuben (00:44)<br>Cool. So what drew you to the digital health field?</p><p>Arjun Puri (00:49)<br>You know, my dad is an engineer. so I still remember stories of my dad coming home with old PCBs and circuits and saying, Hey, Arjun, go and work on these. And that only fueled my desire to learn more about information technology and how we use solutions and not just apps to solve problems. And that’s kind of where my journey began into digital health.</p><p>It was a perfect intersection of being able to have a positive impact in the world where the solutions that you create have the potential to impact lives, both patients, providers, and also the healthcare system that we all rely on every day. And that’s where my digital health journey began. fast forward to now, now I’ve had experiences with digital health innovation, with health systems commercializing and building.</p><p>digital health products in the medical imaging space and now in the clinical decision support space.</p><p>Reuben (01:50)<br>Cool. And so what was your first exposure into the healthcare field?</p><p>Arjun Puri (01:57)<br>Yeah, so after I finished my undergraduate degree, which was actually in sociology, so I was very interested in understanding, you know, the social aspects of how people operate. Initially, it was in the criminology field. Before, you know, getting into the healthcare space, I was really passionate about pursuing a career in the legal space. But as I started to learn more about clinical information, health informatics,</p><p>my attention really started to get piqued by how we use information to help make decisions. And after I finished my undergraduate degree, I actually ended up working with a organization in Ontario that evaluated the competency of healthcare professionals before they could practice in Ontario. So these organizations…</p><p>you know, primarily work with internationally educated graduates, whether they’re pharmacists, nurses, doctors, or specialist doctors, and want to ensure that they are ready to practice, you know, in the space that they’re entering into despite being trained elsewhere. And when I learned about, you know, the various challenges that physicians and other clinicians deal with on a daily basis and how similar they were, regardless of where the physician originated from,</p><p>that only further piqued my interest into understanding, how are we using the information that’s being collected by physicians? And that’s what led me to pursue a graduate degree in health informatics and clinical informatics. And that, you know, further fueled my interest and my intrigue. And, you know, I’m going to age myself now, but that was, you know, about 12 years ago or so now. So since then, the experiences that I’ve had and I’ve sought have all kind of</p><p>know, fueled that and added to that fire to get me to where I am today.</p><p>Reuben (03:59)<br>Interesting, yes. It is a field once you get into it. And your curiosity is peak, there’s infinite ways to take it. So now your latest venture, Symbiotic AI, maybe you tell us how that started.</p><p>Arjun Puri (04:17)<br>Yeah, you know, for a lot of innovators and entrepreneurs, their ventures start off with personal problems. And this was the case for me as well with symbiotic AI. Unfortunately, not too long ago, my mom had a heart attack and, you know, like others who are faced with that difficult challenge, you know, in the diagnosis of coronary artery disease, we tried our best to understand what this meant for my mother.</p><p>what it meant for our family, because your life changes. And then across the country, on the other side in the Western part of Canada, a colleague of mine, my co -founder, Dr. Jun Li, was doing research in coronary artery disease. And when we connected and shared some of the challenges that we were having on both fronts, whether that be about, you know, having access to the right information to make decisions or what sorts of</p><p>pieces of information would have been helpful for my mother and our family when we were making the decision about how to treat her condition. That’s what really gave rise to symbiotic AI. When we really decided to peer in to the domain of cardiology and have a better understanding of how decisions are being made currently and a realization that a lot of information can be left on the table.</p><p>while that decision is being made. And we may not be using the technological advances that we have access to, to their fullest potential. And that’s what gave birth to Symbiotic AI.</p><p>Reuben (05:56)<br>And why do you think, like you said, some of that information is being left on the table and not contributing to the decisions? it just, is it they’re in disparate locations? Is there too much information to consolidate? What’s the challenge there?</p><p>Arjun Puri (06:19)<br>Yeah, you’re hitting on some of the factors there. And I think there’s multiple layers, right? And you start finding this out as you start to talk to more interventional cardiologists, community cardiologists and surgeons. And this isn’t something, you know, specific to the domain of cardiology either. The reality is that our healthcare systems are becoming more strapped for resources year after year. The population growth and the aging population certainly does put</p><p>strain on the healthcare system to be able to provide, you know, support. And we do collect more information than we ever have today. You know, Canada has spent billions of dollars into the adoption and uptake of electronic medical record systems. And we’ve been working on this for well over decades now. But the benefits are still, you know, being realized as we speak today. you know, clinicians</p><p>have a tough time being able to access disparate sources of information at the point of care when they’re making these complex and challenging decisions. And because the information is located in disparate sources and the analysis of that information is tough in a short period of time, it can be challenging for you to not leave information on the table and take every data point into account.</p><p>And I think that’s the benefit of, you know, some of the data science and machine learning foundations that we’ve been able to, you know, advance as a society. know, artificial intelligence was made for this. It was made for us to be able to analyze thousands of data points in a matter of seconds, to be able to provide, you know, risk forecast predictions of what might happen in the future and actionable insights. So, you know, there’s multiple layers to it. But, you know, definitely the strained healthcare system.</p><p>along with the spread information of sources are strong contributors to that challenge.</p><p>Reuben (08:17)<br>Okay, and so what stage is Symbiotic in right now? Knowing that it is still a fairly young company. Yeah, tell us about the stage and then where you are in the journey to.</p><p>Arjun Puri (08:36)<br>Yeah, excellent question, Ruben. So if the listeners are familiar with technology readiness levels, I can state it that way and then I’ll give a more broad strokes picture of where we’re at as well. So we are at technology readiness level five, which means that we validated components of our solution in simulated environments. In fact, we’ve actually also validated the accuracy and effectiveness</p><p>of our core models and our AI algorithms retrospectively. That’s what gave us the confidence that there’s a potential for impact to patient lives, clinician lives, and healthcare system sustainability. So we’re progressing quickly and passionately towards advancing our readiness levels, but that includes continuous evidence generation, iteration on our user experiences, because</p><p>It is a partnership. You know, we hear the term user centered design in product management and in product development all the time. But what it truly means is that you have to move at the pace as your end users do. And, you know, our end users are interventional cardiologists, cardiac surgeons. So moving with them hand in hand, we want to make sure that we are relentlessly focused on their workflow. So as to not interrupt.</p><p>that workflow and instead be supportive of that workflow. So we’re continuously iterating on our user experience. And I think, you know, that iteration doesn’t stop ever because you’re always trying to create a better product for your end user. But we are, you know, at the stage where we’re starting to have trials and pilots of Revise AI, which is the name of the clinical decision support system. It’s a play on the word revascularization because that’s the decision that we help.</p><p>cardiologists make, how to revascularize a patient who’s had a heart attack and has had a diagnosis of coronary artery disease. Because usually cardiologists will have three treatment options. It’s not always the case, but sometimes they might treat the patient with medical therapy, send them home with medicine because they may think the disease is stable and not advanced to a stage requiring invasive intervention. Sometimes they could</p><p>treat that with a percutaneous intervention or more commonly known as the placement of stents to ensure that collapsed and stenosed vessels are able to function as best possible. And then the third option is usually a cabbage surgery or a coronary artery bypass graft or bypass surgery, which indicative from our data can often be better for long -term outcomes for patients as opposed to stents.</p><p>But it is a complex and difficult decision to make when the patient is sitting on the cath lab table and you have to make that decision with the information that you have at the table.</p><p>Reuben (11:41)<br>And what does the feedback from cardiologists been so far?</p><p>Arjun Puri (11:48)<br>Yeah, that’s an excellent question. You know, a lot of times entrepreneurs go out there and they create things that they think people want. But they’re not, you know, certain but it all starts with a catalyst, right? Steve Jobs used to say people don’t know what they want until you give them what they want, right? So a lot of that is catalyzed with designs and prototypes that you think would be compelling after discovery of, you know, features and</p><p>information that would be important to your end users. So, you know, because we’ve had the privilege of partnering with heart catheterization labs here in Alberta, we’ve been able to work hand in hand with interventional cardiologists to learn about what their information needs are, where in their workflow would they like that information. And that has led to a strong positive response. But you know what, when we started this journey,</p><p>and didn’t have a face to put to the product and user experiences to put that product, it can be ethereal, right? And clinicians may not know how they feel about the product, but now we’re at the stage of, you know, where we can actually demonstrate those user experiences, demonstrate the value propositions that we’re able to offer with the capabilities of the product. You know, the focus shifts from awareness of the product to consideration about the product.</p><p>and making more intriguing questions come to the forefront, such as, I think this could be helpful here, or this would be particularly helpful in this patient’s case. And it’s that light bulb and aha moment when you understand how it fits into your workflow that really leads to that positive response. So we’ve been privileged to get that positive response. But like I said, the iteration never stops because you’re trying to create something that’s going to</p><p>continuously improve that workflow and offer additional benefits. So there’s always more work to do.</p><p>Reuben (13:49)<br>Yeah, there’s a wide spectrum of preconceptions about AI, right? Like people range from being super excited and thinking it’s going to solve all the problems to very skeptical and fear of, this is scary and bad. But like you said, once people start to see how it can practically fit into their day -to -day job and the tasks they need,</p><p>done, then it starts to actually settle in. this is what AI is for. This is how it’s useful. It’s not some scary thing, or it’s not magic, but there are specific places where it really helps. And it is exciting to find those applications.</p><p>Arjun Puri (14:38)<br>Absolutely.</p><p>Reuben (14:40)<br>So you mentioned Revise and how it works with clinicians. There’s a patient -facing side to this as well,</p><p>Arjun Puri (14:49)<br>There is, you know, anytime you’re getting a surgery as a patient, you need to provide consent to receive that procedure. Now there’s obviously exceptions to that, you know, a rule that, or that statement that I just made where, you know, you may not be capable of making that decision or providing that consent. But generally speaking, if you have stable angina and stable coronary artery disease,</p><p>It is a shared decision between the patient, sometimes the family caregivers, as well as the interventional cardiologist who’s sharing the treatment plan that’s been designed for that particular patient. But without the patient’s consent, things can’t go forward. And it’s important for patients to be able to understand their treatment options. And you can imagine when you are going through symptoms of a heart attack and you’ve presented</p><p>you know, in the heart catheterization lab and you’re getting that heart cath and you know, the clinician comes back and says, okay, we found something, you know, this level of blockage and disartery or multivessel disease, it can be pretty overwhelming, right? And because the wait times for surgeries and a repeat procedure are fairly long, know, patients can sometimes feel compelled to make that decision in a very short period of time.</p><p>So we’re still learning, to be honest, Ruben, we’re learning and we’re engaging our patients and their family caregivers to understand what would be helpful for you to make your decision and what information would you want to be presented with. You know, the level of information, the detail that we offer, as well as the, you know, I guess, jargon of the nature of the information that we offer.</p><p>to clinicians may not work and probably won’t work as well for patients and their caregivers. So we wanna be really intentional with what we develop for our patient partners and for our family caregiver partners. We think a lot of what is being shared with the clinician should be shared with the patient as well, but how they would like it delivered, how much time they need to be able to analyze that information to make that decision.</p><p>is still something that we’re learning a lot more about. But it’s, in our case at least, it starts with the clinician because the clinician is the individual who has to consume those insights to understand whether there’s value of those insights and those risk forecasts to be presented to the patient. If it’s a clear cut decision that this patient should absolutely be going forward with a PCI and having some stents placed,</p><p>then that discussion may be shorter and you may not need a information package for patients and family caregivers to have to go through. Although the conversation may be fueled and pursued and assisted by other pieces of information. But the intention is for this to have a clinician facing component as well as a patient facing component that helps that shared decision making be more accelerated and more informed so that patients can think about the long -term health</p><p>Reuben (17:49)<br>Mm</p><p>Arjun Puri (18:05)<br>consequences of one treatment option over the other, whether that be the risk of a future heart attack, the risk of death, the risk of affecting their health related quality of life, how many medications they might have to be on for treatment A versus treatment B. A lot of considerations have to be taken into account. And we’re still analyzing that data and waiting to see exactly what our patients want before we go out and build it.</p><p>So there’s a lot of consultation happening with our patient partners. So I’ll do a quick plug. If there’s any listeners who are, you know, experienced with coronary artery disease as, you know, family caregivers or patients themselves, we’d love to hear from you and learn more about what would have been helpful in your coronary artery disease journey or what could still be helpful to you in your coronary artery disease journey.</p><p>Reuben (18:58)<br>Well, that’s excellent. I love the user -centered approach you’re taking to really bring the patients and clinicians into the process to really, really understand their needs. Now, maybe you could talk about how the AI insights are surfaced in the tool. Do you qualify or explain how symbiotic</p><p>came to that recommendation or insight and what the different factors are. I know there’s some problems with like black box AI that you get this insight, but a clinician has no idea why you’re getting that insight. then it can be mistrusted and kind of thrown out. like, that doesn’t make any sense to me. I’m just gonna go with my own knowledge and training here.</p><p>Arjun Puri (19:51)<br>Yeah, that’s an excellent question, Ruben. And I think you and I could probably talk about this for hours. But I’ll try to keep this succinct and say that you’re right. You’re right.</p><p>that needs to be built with AI solutions is certainly a challenge. And it’s not just a challenge in medicine, it’s challenge everywhere. And it’s appropriate for all of us to ask this question of what is the logic model and how is an algorithm or a solution preparing the information that it is? And a lot of the advancement that we’ve had in artificial intelligence solutions as of late,</p><p>sometimes can’t explain where that came from. Whether it’s the weighting of features, whether it’s the type of model that’s being developed, it all has an effect. So it’s up to companies like Symbiotic AI to put their best foot forward, to make sure that their systems are explainable, that their insights, origins have traceable steps. And that’s something that we’ve taken into account. So we are not a black</p><p>AI and trust with clinicians is very, very important. So to that end, what we do is we provide a variety of different features that explain how our algorithms and our solutions arrive at the insights that they do, whether they be specific patient characteristics that led to an increase of a risk in a particular event, whether that be monitoring our models over time.</p><p>as they’re ingesting new data and understanding how their accuracy, how their specificity and sensitivity has changed with new data or old data in there. These are all different aspects that are presented both to clinicians. And then there’s another aspect to Rubin, which is IT teams at enterprise institutions and hospitals, hard calf labs are going to be tasked with the implementation and monitoring of products that have artificial intelligence components built in.</p><p>There’s also a component in Revised AI that’s intended for IT administrators, chief information officers, chief technology officers, so that they have the confidence to understand that not only are our systems providing value to clinicians and providing that traceable logic model, just like the clinicians would have, okay, I’m analyzing this factor for this patient. I’ve read this randomized control trial. This is the case with a particular patient and this is how I’m arriving to my…</p><p>you know, a conclusion for the best treatment approach, they can trace that back in our system as well. And then for IT administrators, they can overall monitor the health and also have compliance, which is, you know, a big thing for artificial intelligence systems right now. You know, we operate in the software as a medical device space. So there can be, you know, although minimal risk to patients, they are real, which means that we must, and we do.</p><p>Reuben (22:49)<br>Mm</p><p>Arjun Puri (22:57)<br>ensure that we have quality management systems and risk management systems in place to ensure that what we are building has traceability as well. So for those requirements from the standard side, it’s essential that companies and clinicians alike are aware of what those requirements are, whether it’s maintenance of those systems or how to responsibly train models as they’re</p><p>heading into adoption of some of these solutions because they might not be mandatory requirements from regulatory organizations today. But my prediction would be that that’s not going to be the case for very long and that regulatory organizations will want to see responsibility from software as a medical device companies or medical device companies that leverage artificial intelligence to follow those standards to prove that they’re able to do this responsibly and ethically.</p><p>And that’s another place where symbiotic AI is differentiated in that the data that we have received access to to build our models is not just scraped off the internet without permissions or licensing. We have securely, ethically accessed data with appropriate licensing terms so that we can get to this stage. And that continues to be built into our terms and conditions and business agreements.</p><p>Reuben (24:20)<br>Mm</p><p>Arjun Puri (24:26)<br>You know, we do this responsibly moving forward as well.</p><p>Reuben (24:30)<br>Well, I love all of that and the approach you’re taking to really responsibly build this product. Obviously, it takes a lot of different skills and knowledge to make something like this come to life. Maybe you could talk a little bit about the team, of different roles and kind of how you’ve built up the team as you’ve built the product.</p><p>Arjun Puri (24:58)<br>Yeah, you you’re only as good as your team, right? And that’s where, you know, successful CEOs really prove their worth, right? How can they attract the right teammates who are driven by, you know, similar motivations and can support the unified mission of the company and the vision of the company and what you’re trying to do? And fortunately for us, we’ve been privileged that we’ve been able to find these teammates and work with these teammates, some from day one.</p><p>And we continue to add more teammates who are passionate about solving similar problems that we do. You know, we are trying to democratize precision heart health for as many people as we can around the globe. And that is what’s really kind of the unifying force between our team. So right now we’re small and mighty. We have my co -founder and chief technology officer who has a deep expertise in data science and machine learning. Dr. June Lee, who’s also a professor at the University of Calgary.</p><p>And that’s really how the company was initially kind of spun off and our foundations were in academic research. It came from an evidence -based foundation. So that way we could have some confidence in the fact that what we were creating is evidence -based, is going to lead to heavy impacts for the healthcare field. And then we added to that team by bringing on</p><p>talented and motivated teammates in the user experience design and development space, in the product management space. Because we’re building healthcare products and healthcare informatics products, information flow is very important. So we also have interface developers on our team who understand what it takes for information to flow from one information system to another information system.</p><p>how that information is passed back and forth securely and privately, because when you are dealing with personal health information, that is of utmost importance. And we have an advisory board that has interventional cardiologists with practice experience, both in Canada and the USA, which really adds a tremendous amount of value because it’s like having a resident end user who’s available.</p><p>for you to bounce ideas off of, for you to understand whether what you’re creating is truly of value. These components of the team have been massively helpful to help us accelerate our journey and our growth. We continue to be interested in bringing on additional individuals, of course, software developers. And because we’re working in the AI space, we’re also cognizant that the company has a, the team has a commitment and a responsibility</p><p>to AI ethics in the medical field. So we’re also inviting medical ethicists and data science ethicists to work with us and collaborate with us in that space. We also work with health economists as well as human factor specialists because what we’re creating has to be IEC compliant from a use case specifications perspective. unless you can quantify the benefits</p><p>of what your solution is able to provide through appropriate health economics forecasts. You’re not really able to accurately claim that this is what the potential of the product is with respect to a return on investment. So these are some of the critical components of the team at this stage and we’re privileged to have passionate and motivated people working with us.</p><p>Reuben (28:35)<br>Right.</p><p>next month. Well, it sounds like you have a great team around you and you’re solving an important problem. It might be too early to talk about like, you know, success stories for patient outcomes, but in your mind, like, you know, what’s a future ideal success story of how, you know, Revise AI has impacted patient outcomes?</p><p>Arjun Puri (29:08)<br>Yeah, so this is where you have to put on that future vision hat and look into the future and think about what would it be like if it was an ideal state and you were helping millions if not billions of people around the world. The reality is that coronary artery disease is a leading killer of individuals worldwide and it tends to be a strain on healthcare systems across the world. So for us, success is</p><p>you know, avoiding repeat procedures for patients who don’t need that repeat procedure. And the first decision is the appropriate decision for us, you know, avoiding future heart attacks or strokes is success for us clinicians spending less time behind the computer, documenting everything that they’ve, you know, received in terms of insights and automating that is important. And that’s success criteria. And then, you know, making the healthcare system and the</p><p>delivery of heart care more sustainable because you’re avoiding repeat procedures, because you’re being mindful about physician time is also a success metric. know, often in the healthcare space, you’ll refer to or hear about a framework called a quadruple aim or the triple aim. And, you know, that’s really what we’ve focused on. How do we improve the health of our populations? How do we improve the provider?</p><p>and patient experience and how do we make care more sustainable? And if we can have some of these impacts and these metrics, you know, with the revised data that we’re forecasting, we’re confident that we’ll get there. That’s what success would look like for us. And then there’s, you know, always opportunities to apply what you’ve learned and done in the cardiology space and discipline into other disciplines of medicine, right? So I think the, if we can,</p><p>transcend and transfer our learnings and the foundations that we’re building in the cardiology space to other disease spaces later on, you maybe long into the future, that would give us an opportunity to have an impact on more than one discipline in medicine and, you know, kind of grow our product offering at the same time. And, you know, at the same time, we want to make sure that our clinicians are happy, our patients are happy and living better lives at the end of the day, and the team is happy.</p><p>right, because the team’s got to be motivated and willing to come to work every day to build what we build. And a lot of that comes from one -on -one engagement with patient partners and physician partners. So we’re always seeking those opportunities that help propel that.</p><p>Reuben (31:48)<br>Well, I can certainly get on board with that vision Arjun. I appreciate that you’re putting all your energy and passion into this product. And thank you for joining me on the podcast today.</p><p>Arjun Puri (32:01)<br>It’s a pleasure. Thank you for having me. Fantastic questions. And I hope we were able to share information with your listeners that they found intriguing. If you want to learn more, visit our website, symbioticai.ca, or feel free to get in touch with me.</p><p>Reuben (32:17)<br>Thank you and thanks to everyone for listening to Moving Digital Health podcast. If you enjoy the conversation, please go to movingdigitalhealth.com to subscribe to the MindSea newsletter and be notified about future episodes.</p><p><em>Originally published at </em><a href="https://mindsea.com/moving-digital-health-arjun-puri/"><em>https://mindsea.com</em></a><em> on October 22, 2024.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=701e159da6a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mindsea-development-inc/moving-digital-health-episode-29-arjun-puri-of-symbiotic-ai-701e159da6a3">Moving Digital Health, Episode 29: Arjun Puri of Symbiotic AI</a> was originally published in <a href="https://medium.com/mindsea-development-inc">Moving Digital Health</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>