Build and operate clinical workflows in days

Thomas Vande Casteele

Tech Brief

Competition in V1C is rising, markets are changing and the need of becoming profitable faster is more present than ever. The digital health winners of tomorrow will be those that have an agile way to build, measure and improve their care flows. Our platform is designed to help V1C to become agile. To create a healthcare learning system that will drive the best outcomes in the space. Some V1C use non-healthcare-specific workflow tools to manage their clinical workflows. But healthcare is complex. Healthcare needs a tool to build and operate care-specific clinical workflows. And that’s what we do. We help care organizations manage complex workflows for diseases like lung cancer, heart disease, and IBD. Besides, some EMRs (e.g Epic, Athena, Canvas Medical) also offer workflow-specific tooling. We see 3 big differences: - None of them offer a no-code platform. Building workflows in Canvas Medical for example is all done in Python. With Awell your clinical team can work directly and independently when designing or iterating care flows. Nothing is lost in translation between clinical, product & engineering. - The current EHR systems don’t offer easy-to-use APIs to connect with external tools that V1Cs are using every day. With Awell you can easily connect your workflows with external applications like Truepill, Getlabs, Calendly... - With Awell you can build flows where you can get everyone involved (care team and patients). Every flow is connected with the EMR and patient app using APIs. We are a 100% ‘headless’ solution–the V1Cs “own” the front-end / end-user experience.

Problem Tech Solves

Product & clinical teams at virtual-first care providers (V1C) design their clinical workflows in tools like Miro, Lucidchart & Word. These flows are then translated into code by their engineering team. Because of this archaic, tedious process, they end up with: 1. Stitched together point solutions that are hard to maintain 2. A monolith of custom-written code, the team is afraid that every release will bring new bugs 3. It takes significant time and resources from the engineering team to maintain and change existing care flows Besides these technical problems, the clinical team also experiences major downsides because of this process: 1. Clinical teams must work with unstructured, scattered data to demonstrate to customers that the care delivery process has a positive ROI (better outcomes at a lower cost). 2. The complexity of some care flows makes it difficult for engineers to translate them into digital programs. Due to this, care teams work with Word versions of the flow during treatment, causing variability in care delivery and clinical errors. 3. The vast majority of (simple) flows are not integrated with clinical tools since building and maintaining them requires a lot of engineering resources. As a result, care teams still have to perform a lot of repetitive, manual work that could be automated. This creates a lot of frustration.


In November 2021, research was published in the Lung Cancer Journal about the impact of the Awell platform on outcomes and costs. Results: - 221 lung cancer patients were included in the care pathway (over a period of 3 years) - 3091 weekly questionnaires were digitally collected. Compliance with the weekly digital follow-up was 92% - Patients in the care pathway had significantly less ED visits (3.5% vs 4.8%, p 0.04) and a shorter length of stay at the day clinic (2.5 h vs 4.1 h, p < 0,05) compared to routine clinical care In stage IV lung cancer patients, overall survival was significantly higher in the care pathway (447 days (95% CI 379-663)) compared to routine care (286 days (95% CI 191-400)) (p = 0,025) You can read the article here: