Category: Azure

What is Microsoft Cloud for Health Care…?

Hi Folks,

Have you heard about this before?

Microsoft Cloud for Healthcare provides capabilities to manage health data at scale and make it easier for healthcare organizations to improve the patient experience, coordinate care, and drive operational efficiency, while helping support security, compliance, and interoperability of health data.

Microsoft Cloud for Healthcare includes solutions that are built on capabilities within Microsoft Dynamics 365, Microsoft 365, Microsoft Azure, and Microsoft Power Platform.

This is an introduction blog post. Firstly, Microsoft Cloud for Healthcare solution should be installed from Microsoft Cloud Solution Center. To say about Microsoft Cloud Solution Center, it actually checks for requirements such as licenses, dependencies, and enables you to easily discover and deploy capabilities and solutions in Microsoft Cloud for Healthcare, there by simplifying the deployment process from a single location.

We will see what are the prerequisites.

Prerequisites

  • You must be a tenant admin, Dynamics 365 admin, or Power Platform admin to deploy Microsoft Cloud for Healthcare solutions.
  • You must have licenses for the Microsoft Cloud for Healthcare solutions and apps that you’re deploying. If your organization doesn’t have the necessary licenses, you’ll be notified during the deployment process in Solution Center.

Here are the solutions that are part of Microsoft Cloud for Healthcare, for each solution. We need to keep in mind that:

  • Some solutions have predeployment setup requirements.
  • Some solutions require configuration or have additional capabilities that you can set up after deployment.
SolutionDependencies
Patient accessPower Pages, Dynamics 365 Customer Service
Patient service centerDynamics 365 Customer Service, Digital Messaging add-on for Dynamics 365 Customer Service
Patient outreachDynamics 365 Marketing
Patient insight cardsDynamics 365 Sales Premium
Care managementDynamics 365 Customer Service*
Home healthDynamics 365 Field Service
Data integration toolkitPower Apps
Unified patient viewPower Apps
Patient trends (preview)Power Apps, Dynamics 365 Customer Insights
Patient population dashboard (preview)Power BI
Provider data modelPower Apps
Payor data model (preview)Power Apps
Life sciences data model (preview)Power Apps
Virtual VisitsMicrosoft Teams
Text analytics for healthAzure subscription
Azure IoT for healthcareAzure subscription
Azure Health BotAzure subscription
Azure Health Data ServicesAzure subscription
Healthcare database templatesAzure subscription
Health document intelligenceAzure subscription

There were a ton of Microsoft Azure capabilities to explore which I will do in my upcoming blog posts. So here, I am using a personal Azure subscription and rest everything I will try to keep using Trial accounts as long as possible. So, you don’t need to worry if you will charge just to try it out.

Also, with the advent of AI, health care industry is getting revolutionized.

Interested…? Then keep looking this space as I will explore more with all of you. Stay tuned…

Cheers,

PMDY

What’s Rebase and Merge in Azure Devops…Quick Recap

Hi Folks,

Yesterday I was working with Azure DevOps repository for my project. My local Develop branch is behind the Main branch by few commits, I want to get the latest commits into my local and include those from the Main branch also in to my Develop branch.

It is then I got to know whether to use GIT Merge Command or GIT Rebase Command. And here you go my findings on the same….

I got to know the details, official Git manual states that rebase “reapplies commits on top of another base branch”, whereas merge “joins two or more development histories together”. In other words, the key difference between merge and rebase is that while merge preserves history as it happened, rebase rewrites it. Let’s start with an illustration…for better understanding…followed by the differences…

MergeRebase
Git merge is a command that allows you to merge branches from Git.Git rebase is a command that allows developers to integrate changes from one branch to another.
In Git Merge logs will be showing the complete history of the merging of commits.Logs are linear in Git rebase as the commits are rebased 
All the commits on the feature branch will be combined as a single commit in the master branch.All the commits will be rebased and the same number of commits will be added to the master branch.
Git Merge is used when the target branch is shared branchGit Rebase should be used when the target branch is private branch

Actually talking both do mean the same purpose and have their own uses, but at the end of the day it is completely up to your ALM strategy/methodology. I preferred to use Merge instead of Rebase just that my branch is shared branch and for simplicity.

Hope this helps…

Cheers,

PMDY