Lewis Baybutt

In this next post within my series on solution architecture for the Power Platform we’ll move onto another consideration, focusing on environments and location. We’ll have a deep dive into what I mean by environments and location and we’ll look at some of the… READ MORE [https://lewisdoes.dev/bl

Call a Clinician is here! 🤩 I am now publishing the solution as a sample on my GitHub for you to download and import into your own Power Platform environments to play around with, allowing you to either use this in your organisations, or… READ MORE [https://lewisdoes.dev/blog/call-a-clinician-i

Final steps! In my last 3 posts we’ve been building a solution using Microsoft Graph for a healthcare scenario of needing to request assistance from other clinicians with specific skillsets who are available at the current moment in time without unnecessary manual steps. So… READ MORE [https://lowc

In this next post in my series on solution architecture we’ll start of the next chunk of posts in this series where we look at different considerations solution architects need to make when it comes to designing Power Platform solutions for implementations. In this… READ MORE [https://lowcodelewis.

Recently in this sub-series, part of my wider series on Microsoft Graph, and utilising contextual ecosystem data, we’ve been working on building a solution to save time in a healthcare scenario by being able to call a clinician based on skills and availability. Utilising… READ MORE [https://lowcode

Time to get presence information with a custom connector! If you read my blog post from yesterday you’ll know exactly what I’m talking about. If you didn’t make sure you read it first, before continuing with this post! In yesterday’s post, we started to… READ MORE [https://lewisdoes.dev/blog/cal