Solution Showcase | Simplified Incident Intake and Processing

Okay. We’ll go ahead and get started. So hello, everyone. Thank you for joining part one of our REMS training day where we’ll be talking about simplified incident intake and processing with Origami Risk. My name is Trish Kelly, and we are so glad that you’ve joined us today. For our first solution showcase, we are going to demonstrate Origami’s intuitive incident intake system, which allows users across their organization to report accidents and injuries in real time, alert stakeholders, assign investigation action items, provide corrective actions based on root cause analysis. Before we get started, couple of quick housekeeping items. All of our participants are in listen only mode. If you do have questions, please feel free to use the q and a button at the bottom of the screen, and we’ll take as many of those questions as we can after the demo. Be on the lookout for a recording of the solution showcase via email within the next seventy two hours. We also invite you to register for our second part of the training day coming up right after the solution showcase at one thirty PM Eastern Standard Time. We’ll be covering our end to end claims management system. You can register with the QR code shown on your screen here. Today, I’m joined by Rosie O’Neil, one of our senior sales executives at Origami. And now I will pass it over to Rosie to cover the demo. Thank you for taking the time to learn about capturing incidents and claims inside of Origami. Right now, you are looking at a dashboard in Origami that gives you information about claims that are inside of the system. It’s just one example of a dashboard because we have the ability to basically create multiple dashboards for different purposes, but this just gives you an idea. In Origami, we actually have, two different, areas. We have the ability to track incidents, which is anything that happens whether you pay out money or not. And then a claim is anything where you’re gonna pay out money. And whether that’s that you self administer that claim, you send it off to a TPA or a carrier, or it’s some small claims that you pay yourself, all of that can be managed through Origami. Today, we’re gonna be focusing on incidents and how they can be reported into Origami. We have the ability for you to add incidents into the system in a number of ways. The first is a person who has access to the system can actually go up under incidents and click new incident, and it will bring up a screen that allows you to enter in incidents of different types. We allow you to create any types of incidents that you want. All of this is configurable, and the names can be renamed as you desire. There is also the ability to report incidents through what we call a portal. The portal is also known as an anonymous collection link. It does not require a user ID or a password. It’s a link that can be embedded on your Internet or your intranet, and then you grant people access through that link. So this is an example of a portal inside of Origami, and this portal can again, no user ID or password is required, can be used to add information into any area of Origami. Again, today, we’re really gonna focus on the reporting of incidents and claims, So we’ll start with that, but it really can be used to report that you have a new vehicle, request a certificate of insurance. It can be used for any number of things. This is also configurable. There’s a version where it looks like a slideshow. You could, you know, have it a little more gridular. Like, it’s totally up to you what this looks like. So I’m gonna go, to this create incident and hit create new, and it’s actually gonna take us to the screen that looks just like the one that I had access to as a named user. And like I said, you do have the ability to configure the different types of incidents. At the top are probably the ones that get used the most. So, reporting a an injured employee that turns into a workers’ compensation claim, an injured nonemployee that becomes a GL claim, damage to a company vehicle, damage to a noncompany vehicle, damage to your property, damage to somebody else’s property. We do, in origami, allow you to connect all of the related incidents in one occurrence. So if I go here to the create multiple incidents, it will then allow me to enter general information, and I can down here say, you know, so let’s say you have a vehicle that’s on the road and your driver, hits another vehicle, and your driver is injured, and then one dry one person in the other car is injured. There’s damage to your car, and there’s damage to their car. Through this, form, you can actually then connect all those things together, and all the information that’s shared can then be easily transposed to those four, different incidents, but then they can be linked together for reports, and then they can turn into one claim for an occurrence purpose. I’m gonna go back, and I am just going to select an injured employee as the type of illness that we want injury that we wanna report. So, in origami, there are a few things about the form that are of use, to you and that you’ll need to know. One is everything that has a red asterisk is a field that you’ve specified as required. Anything with the I is a tooltip where you can provide instructions. So if you open this up to, you know, people throughout your organization who normally don’t deal with insurance or claims, you wanna make sure that they understand what you’re looking for when you’re asking a question. You’ll also see all of these lookups. Origami is a relational database that we can actually connect the different areas together, to make it easier for the person to report claims. So we can get a feed from your HR system of all of your employees. It would not look like this in the real world. This is all fake data. But if I actually select an employee, it will now add in his information. And if I go down, it actually pulls over his demographic information from the HR system. So even if we had the supervisor in there, that would be populated as well. For any of the date fields, there is a calendar function to make it easier. So I could literally say when did this happen. We have the ability to make fields like the report date default to the current date so that they don’t have to rekey that information. And you’ll see it knew that he’s actually assigned to a a location in Atlanta. Then I can then enter in, like, the description fields, and I can type out exactly what happened. So I’m gonna just make them fall off of the ladder. And then I can also then tie this to an individual location as well. We have an integration with Google Maps where it will literally pop up on a map, and you can say exactly where they fell off of the ladder. So maybe it happened right here at this particular store. You can select that address, and it will pull back the actual latitude and longitude of exactly where it happened, and then that can be used in reports. One thing that we recommend is we work with you to kind of configure these forms. We’ll start with the forms that you’re already using, and then we’ll basically, add enhancement to it. We do have the ability to have dependent questions and dependent sections that can appear. And an example of that would be this. If I say that the employee is injured, we have a body part diagram that literally allows the person to select where the injury occurred. And then because there were multiple options there, they can say, oh, it was his left hand, and they can add that part. Then maybe it’s also his lower arm, and they can add that as well. So, again, if you think about the fact that the people who are reporting in the incident may not know all of the body parts, this gives them a way, to do it a little bit easier and to improve the quality of your information. For the cause, I had said he had, you know, fallen off of the ladder. I can then basically pick that, and then we have a choice that’s fall, slip, or trip off of a ladder. That is up to you how much detail you want, and we do have what we call a cause and a detail cause. So some people will say it’s a slip, trip, and a fall, and then the detail cause will be from a ladder, from a wet surface, all of those details. I can also put in the nature of the injury, or I can leave that information blank. And then once they are done completing the incident, they will just hit complete incident, and then they’ll say okay. And then they will have the ability to attach photographs, videos, witness statements, police reports, any documents that they want. All they have to do is upload a file, and they can upload an individual file, or they can upload multiple files. Just in the interest of time, I’m not gonna do that right now, but just know that is an option that is available. And when they say I’m done, that incident is added into Origami. Now I mentioned that we have a number of ways to report. So we talked about the fact that a named user can actually add an incident directly into the system, and that’s sometimes very useful because maybe you get it over a phone call or something like that. Then we’ve got the portal for the anonymous collection. We also have, and it’s become very popular, a QR code. And so literally that is a code that you can scan. You could actually scan it right now, and it would bring you to that screen where you can report in any of that data directly into Origami. We also have a corresponding mobile application that is literally an app that can be used on an Android or an iPhone device. It works off of a PIN for access, you can have a, PIN that’s appropriate for them. You can even have, different PINs for different purposes. So if, say, you were a city and you wanted the police department to have one PIN and the fire department to have another, they would then see different forms depending on their area of interest. And so that would work very similar to that. Once the incident is actually reported into Origami, it would show up inside of the incident area in the system. And we do have a number of ways for you to look, but there is a view that’s called recently reported incidents, and you can create views in Origami. And so now this will take me back to that incident I just reported. I can now edit this incident, add additional details, and go from there. I worked with a client of Origami that were wanted to keep the form very simple, so they literally asked less than ten questions. And they said, we don’t want them to fill out the cause or the body part or the nature. We’ll do that ourselves. We just want them to put it in the description, and then we’ll add that detail later. So we can even do things like that for you as well. And so now I have the ability to basically edit this incident and add additional details, and we can even have it where certain fields show up when you edit that don’t show up when during the intake portion. So, for example, I could say what type of incident it is. We can have a question like, does this need to be reported to the TPA? And then if that box gets checked after you’ve looked at it, we then can basically send that incident off to the TPA through a secure file, and then they can use that to create the claim. And that’s a little bit of an overview of incidents inside of Origami. Thank you, Rosie. So we are now gonna move into the q and a portion. If you do have a question, please feel free to drop it in the q and a box at the bottom of your screen, and we will get to as many questions as we can. If we don’t get to your question, we will follow-up with you afterwards directly. So, Rosie, we have our first question here. When selecting the location, if you are on a mobile device, do you have the option to grab the location of the device instead of finding it on the map? And so just like any other mobile kind of application, it will if you have shared your location, it’ll know exactly where you are. So it’ll actually have a pin that’s where you’re at so you can select it. But if, say, the accident happened and you moved fifty to a hundred feet away and you’re not quite there, you then can move the pin to exactly where it happened as well. Perfect. Alright. Next question, we’ve got here. Do you, require a username and password? So, no, we do not require a username and password. As we mentioned, a user with a license can add an incident, but we also have that anonymous collection link or the portal to be able to, report any incidents without a username or password. And, additionally, the mobile application does not require that at all. You provide a a PIN that they then use to access the system. Wonderful. Alright. Next question. How granular can the location be? Is there also satellite view available so they can see where exactly a slip and fall occurred, in the parking lot, for example? So they have the ability to expand it up, and, basically, they could pick exactly where it happened, like, you know, inside of it. What I would recommend is that you actually add a field for, like, secondary location, then you can have, like, a pick list. So, like, if it was, like, a warehouse, you could have different options for where it happened. And then that’s a little bit better for reporting purposes because then you’ll have the availability to select that. In terms of the satellite view, I’m not actually sure if that’s true. It is a Google integration. So we’ll check on that and get back with you on that one and just let you know for sure. Alright. When associating incidents with the eventual claim being sent by the TPA, is there a way to get around required fields in the claim form to successfully, save the association? No. If a field is is is marked as required inside of Origami, the user will not be able to get past it without saving. If they attempt to get past it without saving, it’ll actually say you’ve missed these required fields and they turn, like, this pinkish red color and it highlights them and they can go right to it and populate it. What you can do, though, is you can design the field so that you’re not asking them so many required fields that they’re not able to complete the form. So, really, that’s one of the things we work with you on the design process is to ensure that you’re really only making the things that truly need to be required required. Perfect. Here’s another one. So once the incident report has been created, can this information be uploaded and turned into a claim, with the insurance company? We’ve kinda gone gone over that a little bit, but if you wanna expand on it, Rosie. Yeah. So what we typically do is basically, the incident gets reported into Origami. A lot of our clients actually have someone take a look at it and decide, is this something we need to send to the TPA or the carrier? And then you basically have some type of acknowledgment that, yes, it needs to go, like, submit to TPA or create a claim. There’s a number of different ways to do that. But then what happens is we send that off, through an encrypted flat file to that TPA or carrier, and then they create the claim. And then we can get a feed of that data back, which we’ll talk about in the claim portion, where then that data comes back into Origami as a claim inside of the system. Yep. And as Rosie mentioned, the claim portion, so we’re doing second solution showcase immediately following this one on our claims management within Origami. So we’ll cover that a little bit more there. Another question about lines of coverage. Do you have an application for auto and general liability? Yes. So we can support any line of coverage, even crime and other things like that. Some of our clients use it for reporting security incidents. So we definitely can support both auto bodily injury, body auto physical damage, and general liability inside of the system. Alright. Can you use the system to report near misses? Yes. So the incidents, again, because it’s anything that that you’re not gonna pay out money, that, if you go back to that screen when you get the recording, you’ll you probably will see near misses in there. But, yes, it can definitely be used to report near misses. We’ve gotten a few questions about, receiving a copy of the screens that were showed and, a copy of the demo recording. So we are gonna be sending this out. You should receive a copy of the recording within the next two to three business days, so please be on the lookout for that. One more question here. Can a workflow be created to have additional people who are not licensed users review or add information to the incident? Yes. And and, actually, we have different licenses that can accommodate the, different users being able to review. So it’s sometimes common that an incident gets reported and maybe the supervisor needs to look at it or or a nurse or someone else. And those people actually sometimes can have access to the system, Or we have a feature called grant access where we can send a link to non named users, and they can basically have access granted for a temporary period of time where they can update information about that incident. K. Great. So I don’t think we’ll be able to get to the rest of the questions live. But, if you did ask a question, and if it was not anonymous, we’ll be able to follow-up with you directly. So if you are able to put your name, in there, that would be super helpful. If you’d like to learn more about Origami or the incident management solution, you can go to origami risk dot com or to explore or request a demo or feel free to shoot us an email there at info at origami risk dot com. And then as I mentioned, we have a second part of this training day covering claims management. So if you’ve registered for that, that’s coming up here just in a few minutes at one thirty PM Eastern Standard Time. And with that, thank thank you everybody for joining, and we hope to see you at the next showcase here in a few minutes. And hope you have a great rest of your day.