Solution Showcase | Epic EMR-to-Origami Incident Launch: Reducing Manual Entry to Improve Efficiency & Data Integrity

Hello, everyone. Welcome to our webinar and solution showcase, EPIC EMR to Origami incident launch, reducing manual entry to improve efficiency and data integrity. I’m Alina Feinberg, and today, we’re going to demonstrate how Origami’s new functionality creates a convenient way to save your provider’s time while increasing data quality when managing incident reporting. Before we get started, there’s a couple of housekeeping items we need to cover. First of all, participants are all listed in listen only mode. If you have any questions, please feel free to use the q and a button at the bottom of the screen. Also, be on the lookout for an email with an on demand recording of the showcase that will be in your inboxes over the next seventy two hours. Today, I am joined by Anuja Cannon and Bharat Valarou. Anuja has been instrumental in paving the path forward for this integration, and Bharat has worked closely with our health care market as a technical sales consultant, providing numerous solution demonstrations to our clients. I’ll pass it over to Anujia and Bharat now to walk us through the solution and demo the functionality. Thanks, Alina. We’re very excited to be presenting today’s solution showcase highlighting our new Epic EMR to Origami incident launch feature. This new feature allows clients who use Epic as their electronic medical record to launch Origami incidents directly through the Epic page. Upon doing so, you’ll see that the relevant patient demographic and encounter data from Epic is automatically captured onto the incident record within Origami. From here, users can complete their incidents, hit submit, and proceed with their existing workflows. We’re thrilled to provide this convenient integration to our clients. This solution enables care providers to initiate an incident report directly as part of their existing care flow. It eliminates the need to manually enter this key information into Origami, resulting in an increased accuracy and significant time savings for the individual reporting and also across the broader organization. The streamlined process can also help encourage patient safety reporting since it’s now easier for front end users to report events and near misses. Before we dive into the demo, I do wanna share a quick note. Typically, on our solution showcases, we prefer to share a live view into our system. Because of the unique nature of this integration, we have prerecorded this demo with a client. You’ll see an epic screen, but note that all of this is dummy data in a sandbox environment. No PHI is included in any part of this demonstration. Anything that has been blurred is simply to maintain client discretion. With that, I’ll go ahead and turn it over to Bharat for our demo. Alright. Let me start sharing my screen. Okay. So what we’re gonna be talking today on about in the showcase is the workflow from Epic, pulling over encounter details directly into Origami. What we’re seeing on the screen right now is Epic’s, a sandbox of Epic where we can select our patients, choose where we wanna keep that launch into Origami, whether it’s the toolbars or hidden kind of menu. In this case, we’ll go into the menu here, choose our patient. So clicking the menu, we’ll go into the drop downs, go into, the dropdown or location list. We’ll select the location where this patient is going to be residing. In this case we’re going to select Stephanie. Double clicking into Stephanie’s record is going to take us into the summary where in this case, the sandbox, we’ll again click into the menu bar, go into help, and choose launch Origami. This will bring another tab up with our portal, and we’ll choose follow here to go into. Once we choose our incident type, all the encounter details from the individual’s encounter will pull over. This will be the latest encounter or the current encounter that we’re running off of. So we’ll see the first name, last name, birth date, all the encounter details, the CSN, and the encounter start date. Now going back into the database, we’ll take a look at that November eighth. So when we go back into Epic and go into chart review, we’ll see this is the admission or the current one, again, November eighth here. Now in practice, you would click that button. All the stuff will come through, and then when it we’ll fill in the rest of this incident form and hit submit. So whenever we are done with everything in the system, like I said, we’ll hit submit, and the rest of Origami’s automations and workflow engines will take over, again, firing off emails and things like that. But, again, in short, this is the demonstration of that epic button, just going through epic, selecting where we want that launched origami to be, pulling over that current encounter, and then populating those encounter details directly within a selected incident type on the origami side. Alright. Hope you guys enjoyed. Thank you. Excellent. Thank you, Bharat and Anujia. So that concludes the demo portion of our session. We’re now gonna move over to the q and a. As a reminder, please drop any questions you may have into the chat below, and our team will address those questions as they come in. And I believe we had a few come in during that demo. So the first question we had was, our version of Epic looks slightly different from what’s been shared on screen. Does the launch menu look the same for everyone with this new feature? I’ll take that one. So the configuration of the menus is totally up to you guys, and it’ll vary based on client to client. In our situation, we just put it behind the menu bar, but you can have it on the top at the work bar, or you can even have it as a URL link that someone can click directly on the record. So it’s totally up to you guys. Excellent. Another question we got through the chat. Does the end user have to have an Origami login in order to use this feature? No. So once you launch from Epic, the portal that comes up on the Origami side, you don’t need a login to access that. It’s just the same as our anonymous collection links. So, basically, you choose the incident type and then go through. So no login needed on the Origami side for anyone to put in an incident. Then one other question I’m seeing, can I pick which incident type the button will launch, or is this limited to just one specific type of incident? Yeah. I can take that question. Great question. So actually, no, you can absolutely select which incident type this is going to route to. So as you saw in the demonstration, actually, this feature, once you’ve launched from Epic, takes you to your existing landing page or the entry to your incident reporting portal. So on that portal, you’ll see all of the different tiles for the incident types that you’ve configured as part of your implementation. So from there, you can select which one you want. During the demonstration, you saw that there were only two tiles that we had configured for this demo. But again, it will show all of the ones that are available to you. Alright. Another question we got. Does the epic encounter have to be current, or can we use this feature from a past encounter as well? Yeah. So we didn’t show that first half, but you could definitely go through the motions that we just did, but go through basically their whole list and choose a previous encounter. In this case, we just had the link go directly to their previous encounter and just autofill that, but you definitely can look through their history and on a specific patient chart and pick whichever encounter you wanna create it off of. Downstream, the same process happens. You click that link into Origami. It’ll pull over that specific encounter details and then map it over into whichever incident type you choose. So, yeah, you could do both. One other question I’m seeing is how will the provider know if they submitted an incident? Can they track it on their end, and does the patient record receive notification that an incident was submitted to Origami? Sure. So this is kind of a multilayered question. So for the provider knowing about the submission as well as the patient, that’s all done through data enter or workflows, basically. So as long as we have the patient identifier details, maybe like an email address or contact information, we can reach out or send a notification once incident’s been submitted. And same thing for the provider. As long as the provide we have their provider details, we can also send them a notification saying, hey. This incident was submitted either by you or on behalf of you since you’re associated with it. From a tracking perspective from the provider, if they have a login to Origami, they can always go into the system, track anything that’s been assigned to them or they’re affiliated with. If they’re don’t have a login, there’s alternative ways like grant access and things like that, or even like a dashboard. We can kind of give a read only view, quote unquote, to providers. That way they can access those kind of links and get a glimpse into the data in Origami without actually going in and interacting or moving data around, if that makes sense. So, again, they’ll have read only views if they’re not a user, but if they are a user, they can always go in and see anything, and those workflows will take over to, you know, send the correct information to the right parties. And that’s all configured by you guys on what gets sent out, how it gets sent out, and, whatever frequency it does. Right. Thank you, Bharat. I think that’s all the questions we’re gonna get to at the moment. But, unfortunately, although we don’t get to every question live, if you did submit a question and it wasn’t answered during this q and a, we will follow-up directly with you, based off of the name associated with your registration. If there were a couple of questions that I think came in anonymously, So if that’s the case, please send your information over to info at origami risk dot com, and we can address that question for you over email. If you’re currently a client and interested in next steps or how to implement this solution or wanted to discuss it further, please contact your account manager so they can schedule time with you to scope the path forward. Otherwise, if you wanna learn more about Origami or the solution, please go to origami risk dot com or visit us at origami risk dot com slash get demo. Alright. Thank you all so much for your time, and have a great day.