Skip to content
MicrosoftTeams-image (6)


Patient 360


JC: Good Afternoon, everyone

Welcome to one of the first episode of our video hackathon series for Vlocity health, where we are showcasing some of the really brilliant work that our internal talent has done around spotting some of the biggest challenge in the health industry and solving for them through the use of technology. 

So, I’m going to immediately hand the torch over to our vice president of product development, Santosh, who is going to introduce us to the team and tell us a little bit more about what this hackathon entailed and what the goal was! 


Santosh: Yeah. Thank you, Jennifer. 

Hello everyone. This is Santosh Naladkar . I’m currently leading the vlocity CV practice for MASTEK. As part of our yearly hackathon, this year, we focused on HLS domain- healthcare and life science domain, where we wanted to leverage, also known as a Salesforce industry cloud and see how we can use out of the box feature to meet some of the use cases for HLS domain.

So in  this use case,  Patient Risk 360 Interoperability, where we tried to showcase how Vlocity’s out-of-the-box features can be leveraged to phase the data, real-time data of  the patient, from the other providers, EHR systems, which will help the providers to take care of a patient  in the critical.

With that team, who has worked very smartly and very hardly on this use case to make sure we are using a lot of out of the box features to meet the requirement for integration with other EHR systems. 

So, we are Thinu Ganesan, Kesavakumar Murugesan, Jegadeesh and Gobinath Srinivasan. And we’ll go through the presentation as well as the use case.

So Thinu, please take it forward.

Thinathayalan: Okay. Thank you.  Yeah, so, all right. 

So as part of this hackathon, so we tried to tackle a situation where an inter-operative makes more sense. So, as you know, the patient’s health records have providence over the years from papers over to electronic health records.

And when I’m in my electronic health records, there are various different types of electronic health records in different formats, different spectrum's. Some of them are HL7, some of them are FHIR revision forest, and even the appropriately health records that are very specific to each provider. And these make it very incompatible when you want to access data from across different service providers.

And those records even lose context when they get transferred over and it becomes really hard for a patient, when they go in an emergency situation in a completely different state that they live from.  And they don’t have all the background information for the service provider or there to actually look at their previous medical history.

And then it becomes hard for them to even come up with a care plan to immediately address the patient’s health needs.  

So, the solution is to have a more standard approach on the electronic health records, especially when you stick to the standards that are more industry wide acknowledged, especially HL7 FHIR.

But the challenge with this is that the structure around this is too complicated and most of the service providers hasn’t transitioned over to these standards. And that’s the major setback with service providers or the clinical/ medical providers. So, it’s because that the structure is complex and, it becomes really hard for them to even invest time and money in getting a system that is more standards oriented. So, if you don’t have these standards in place, you cannot even exchange data between your health information exchanges and that’s where the real challenge comes in, where you cannot access data for different states or providers.

So what we did is,  using  Vlocity , we actually  standardized some of these approaches to actually fetch this health information, especially using FHIR APIs. And we did that without using a middle-ware. And we did that without writing any line of code, which is basically out-of-the-box Vlocity Omni studio Data Raptors.  What, it does is, it actually involves various FHIR endpoints, FHIR data endpoints. Especially, various endpoints for allergy intolerance or immunizations or diagnostics data. And these are very different data structures that goes around it. Right? So, we, actually invoke those through a Vlocity Omni studio using Data Raptor. It performs what do you call as an ETL and extract transformation and load of the data; it is maps data pines with what’s on your Salesforce health cloud, and also it transforms it, the way it requires  for your UI or your flex cards that you’re using. And then it just loads it and then your UI judges it. So, it’s all done without writing a line of code. Let me transition over to Jegadeesh; he will show you a quick demo of this. And we’ll look at the technology that we use.

Jegadeesh: Thanks, Thinu!

The patient detail page that we have is something, and in this space, patient detail page, you could have a 360 degree view of the patient’s entire health, historical data. And each of these UI that you see here are different flex cards, right? And we are basically leveraging the Vlocity technology here and each information that we got from the different electronic health exchange records which belongs to particularly this patient. Okay. We have this allergy information, EHR and the recent immunization details got pulled for this patient. And what are all the recent medication that is undergoing? Okay.

These all a part of the FHIR data that we are pulling, particularly for this patient. Okay. So that when the doctor or nurse or care provider look into this patient detail page, right, he is already aware that he’s having the certain medical conditions, so that they can do their care plan accordingly. 

And here you could see the, all the recent lab that we are leveraging the same Vlocity flex cards and all these flex cards are powered by a Data Raptor behind the screen, just pulling all the FHIR data, particularly for this patient. Okay. And here you could see that as a sync button there, right. And then by clicking the sync, the entire flex card data related to his current health condition that we are putting from the EHR or from different health information exchanges, they are real time not stored in their hospitals patient database. Okay. At the moment when we click it, these real time data are getting stored under our Salesforce health cloud environment, so that  we are keeping the  health history of this particular patient. Either we can share it to another care provider, or we can use when the same patient gets admitted in the same hospital.

Let me show you how it works.

What we are using is, we are using the Salesforce health cloud to map all electronic health conditions to different set of objects that is provided by the Salesforce health cloud.

For example, you could see the EHR conditions from this flex card, right? These are the existing conditions. Currently they have a certain medical condition related to heart disease and kidney related diseases. Each data gets pulled  from different health exchange platform and get stored under this health cloud environments, different clinical data model.

Similarly, we have all the subset of models which are matching in this particular electronic health information standards.  So that, it is very flexible for us to keep the historical data of the patient so that we be getting that 360-degree view of the patient, current medical health condition.

Yeah. Let me stop here and let me switch over to Gobinath for additional benefits and advantages. Thank you.

Gobinath: So, we are going to see about the benefits of the health cloud model. So, the main advantage here is for both the doctors and the nurses.  It won’t increase the diagnostic cost and saves emergency time as well.  Additionally , it increases the overall organization’s reliability since it’s  interoperable and gives trustworthy with the help of using Salesforce health cloud with the integration of Vlocity health on top of it.

I’ll say it’s very fast once you enter into it. And we are very glad that it’s our MASTEK’s accelerator package, which we used for an accelerated integration with a middle-ware APIs.

And finally for customer satisfaction, we achieved that with the help of interoperability. And with the help of this, we did an estimation and based on this estimation, like whenever as Jegadeesh showed in the demo with that, like creating of flex cards using LWC and Apex. It consumes over an estimated time of 40 hours but when we’re using Omni studio for immunization medication and diagnosis and conditions. All the flex cards took only the minimum time and then like four hours importing FHIR data. It consumes only 8 hours -real actual time. So totally we designed this within the actual time of 22 hours, and it saved about 91% days of development time. And it’s one of the great achievements with the help of this Omni studio Vlocity. Yeah. Thank you.

That’s actually really brilliant. I actually, I only have a couple of questions, that came to me. The first one, I know Thinu you talked a little bit about this already in the middle, but, well, I want to kind of pull it out and put a spotlight on it. And it’s that normally for the kind of functionality you created some kind of middleware is needed to pull information across, reformat it if necessary and then deliver it, plunk it down into a different application where it’s needed.

You seem to have done that without middleware. And I I’m wondering if you could just give us an overall overview of how. 

Thinathayalan: That is correct. So, if you look at the Vlocity Omni studio, it comes with what are called Data Raptors and each Data Raptor has different kinds of actions; data transformed, data extract and data load or data sale, right?

It’s basically translating that as a middleware. So, you use that technology to actually call an endpoint, get the data and fit all those data points and map it to what’s required on your application and then use it as is on your UI, or just dump it in your database. So that’s the flexibility that Omni studio provides.

So, if there are small providers or small companies, if they don’t have the budget for a real middleware, like MuleSoft, they could use or go with this approach and get this implemented at a faster time.

JC: Right, right. Absolutely. So, you’re looking at a pretty significant, faster time to value. I imagine that also plays well into an incremental rollout of technology, because it allows you to just get functionally very, very fast.  From an administration perspective, does introducing Vlocity health, that data model into Salesforce health cloud make it easier to maintain and if so, how? 

Thinathayalan: Absolutely! So, all these are done without writing any code. And these are basically declarative programming where you actually go in with the omni studio, or the UI and start building your processes order, right? You would start building the mapping. You would start building the ETL process and all that.

It’s all basically done through a declarative or through the UI. So, there is no line of code, so it becomes easy to maintain and easy deployments without having to run all the unit guys, mess with the cord and breaking anything. 

JC: Right. Absolutely. And my last question, anyone can chime in, I was thinking Santosh, but getting this kind of really great glimpse into the work that you did.

I know as part of the hackathon, you had to create a scenario and you chose an emergency situation where every minute counts in treating someone or saving their life. And so, this kind of technology is amazing for bringing information fast when it’s needed. But I can also see that its easily adaptable to many other situations.

 And I’m wondering if the quickest of brainstorms is, it seems to me that what other places can we adapt something like this technology to Medicare comes to mind because they have accountable care organizations initiative that requires a team of doctors to coordinate together, to give the best care to someone.

This kind of technology could easily be adapted to that kind of a scenario.

Santosh: Yes. As I said earlier, right, our primary focus was on the health care and life science domain. So, before we started this hackathon, we talked to the industry experts as well as looked at what the client needs. Okay. And then we put down those use cases and see how we can benefit the client as well as their customers, nothing with the patients, to get the required, help and the required care.

And we see this, one of the challenges where, when patient goes from one provider to the other provider, then the provider doesn’t have the required data. And then they face the challenge, especially in case of emergency situations where the data is not available to the doctor, they can use this to phase the data and treat the customer, do the required checks.

JC: Yeah, absolutely.  I think that’s absolutely brilliant. And I want to thank you guys for coming in and just sharing.  I think it’s very clear to anyone seeing the video, how passionate we are about trying to use our expertise in system integration and what we’ve been doing since 2012 to the healthcare industry reach its own goals.

You know, we’re developers and administrators, programmers, architects, but we’re patients do sometimes. So, this kind of technology touches all of us. And I really appreciate you coming on here today to share this glimpse into what we’re doing and how vital it is. So, thanks very much. 

For the folks watching, we will have some additional resources below the video for you, if you want more details. And if you have any questions at all, there’ll be a contact box or a comment section below. You can go ahead and input your question and we will reach out to you with an answer. So, thanks for now and we’ll see you next time.



Back to Work