Well we’re back here at HIMSS 2019, here at the UiPath booth, with another use case
for healthcare.
I have David with me to show us insurance and Eye Care and what are we showing?
Yeah so what we’re doing here is we’re logging into an insurance provider that’s
like for eye care so, think of like VSP, vision insurance where they have to log in, do a
claim and all that.
So I’m going to go ahead and start this up this is just a video I’m going to walk
you through it.
First thing I want to show you is how when we create different modules, we’re going
to be… here’s a log in piece here’s the claim piece, here’s the claim summary.
The reason why we do that is we want to sometimes reuse these over and over again right?
Ok so they’re different kind of pieces of the automation that you’ve segmented out.
Correct.
I have not seen that in studio yet.
So you might have A, B, C, and D, and you go you know what, A we might reuse over and
over again, B we might reuse over and over again, the information is always there so
that you can rinse and repeat some of the stuff and reuse your code.
New thing, I had not seen this this is good.
I’m learning something everyday.
So basically in this case it’s going to go ahead and run, it’s going to walk you
through a little bit of it, it’s going to show you the different pieces.
As you can see our layout, what it’s going to do.
In a second it’s going to go ahead and roll and run it alright, so but again you have
a log in, insurance claim, read summary, you name it.
So if I look at that right am I actually logging into four different kinds of systems at that
point or four different platforms?
It’s not so much four different systems but four different pieces of the pie if that
makes sense.
Ok.
Alright, so in this case there, he’s actually clearing the queue, making sure it comes back
to the screen.
They’re actually going to be logging in.
Ok at this point he’s going to go ahead, he’s actually in this case logging into
two different systems.
Ok.
One is, the log in for the Eye Med, one’s going to be the insurance, and he’s going
to be linking them together, to take information from one, and put it in the other.
Just like a person would do.
Just like a person would do exactly.
So really pushes our HIMSS interoperability message that we’re trying to push to everybody.
So basically they logged, you logged in to two different systems, now he’s going to,
he’s filing a claim, and this is where he’s logging back they’re logging back in to
see what the status of the claim is.
Ok.
Alright.
And in so basically in this case he’s there basically calling the claim status, they can
go ahead and sort by two weeks, three weeks, a month, you know it, and basically see what
of the outstanding claims are available.
So as a provider, like if you’re an Eye Care provider, this is something you’re
going to be doing all the time to say, “what’s the status of all my claims?
What are we waiting for?”
So in this case we’re going great here.
Here this is outstanding for… still needs SSN right, and so there, someone automatically,
in this case a robot’s going to be going needs SSN, it might be kicking off an email
to somebody to say, “hey go call the client and get the SSN,” things like that.
So again and I can just keep running this over and over again without having to have
a human in this process so it’s and unattended robot.
This is an unattended robot, always running in the background so it’s always updating
the claim status, logging in to file a claim and also find out what the claim status is.
Again in this case we’re logging in to two different systems, and at the end we’re
creating an Excel sheet to say, “here’s a report for the office manager, here’s
where we’re at with all the claim status.”
Which is very important.
Yeah and this saves a lot of time I’m assuming.
Not only that but they could be basically looking at that Excel sheet, and just look
at it.
From there, from that Excel sheet we could create a whole chart to say, “Hey, for some
reason, Jody, when she logs in people, there’s always errors.”
So maybe it might be like a, “Hey we need to retrain Jody in the front desk to make
sure she gets information,” you know a lot better information front end.
Now how did you create this, it looks, we have Studio, it looks pretty complicated.
How in creation of this, how complex was this from a creation point of view?
Yeah from a creation standpoint it’s pretty easy we’re going to activities so it might
be here, we’re going to do log in, so we’re going to create a sequence that says log in,
and there we’re going, doing a one step click, and so the we can use Recorder, do
a Selector, and say here’s the log in click on it.
It’s really plug and play, it’s really simple.
You don’t need to be a developer to do this, you just need to know what the existing human
process is and then go from there.
So you’re the person who knows the processes you’ve been doing these processes for a
long time, now we’re just bringing it, automating it into the system.
Absolutely.
Thank you David, thank you guys.
We’ll be back with you the rest of the week so continue to follow.