IPeople - Interface in a day?

by Ryan Dickerson on November 5, 2021

Hey there,

Ryan Dickerson, CEO of IPeople here, and I want to share with all of you about the time IPeople was able to write an inbound interface for an existing client in a single day from addendum signature to delivery.

The primary purpose of the integration of any kind is to automate something, saving the unfortunate person in your staff from having to manually key in hundreds or thousands of records - or even worse, to key the same thing into multiple places to keep two different systems in sync. This does not always have to be something that is going to remain ongoing forever. Many times, IPeople will scope and perform interfaces that are a one-time run to achieve a very specific task. From synchronizing dictionaries between MEDITECH Test & Live rings to UNV security scripts. Thinking about it this way, interfaces can and often are, written for any and every application MEDITECH currently offers. One module that we have not frequently gotten requests for is UNV interfaces. 

For this client, they were consolidating a recent acquisition into their network and MEDITECH Client Server 5.67 system. Their challenge was two-fold, they needed to add all users from their new acquisition into the existing MEDITECH platform, and they needed to update all existing users to their new, consolidated domain - all while not affecting ongoing patient care - meaning, they couldn't bring down the system to do it. While this process was being done, they needed the existing users to continue to be able to sign on from their old domain, until the new domain went live. 

They did their research, and in checking the number of existing users who had active access to MEDITECH combined with the new users that would need to be added - there were THOUSANDS of users that were going to have to be modified. The hospital was faced with a challenge - do they manually do this, or look for some help? As a test, we asked how long this process would take to do manually - for a single user. Now, the UNV application is well written and straightforward to use. But even something as simple as adding a domain to an existing user, the results were staggering. Not even counting the time it took to log into the MEDITECH system, navigate to the UNV User menu, the hospital found that it would take over a full minute to check the consolidated spreadsheet they created and find the first user ID, type it into the UNV User screen, navigate to the UNV Security tab, check if the user already had the new domain needed, and if not - then add the user's NEW username and domain. One full minute. That doesn't sound too bad on the surface, now let's multiply that times, say, 5,000 users. That is a grand total of 300,000 seconds, 5,000 hours, or 208 days. 208 days IF that person was superhuman and never slept, ate, or had to go to the bathroom. 

So, what kind of value does this bring? Many hospital systems simply do not have an extra person to spare for the next 5,000 hours - but even if they did, what is the average cost for an employee? Let's take our most entry-level IT staff member, unfortunately, he or she was the unlucky individual to draw the short straw and is now being requested to add all these users to the system. Luckily for the hospital, since he or she is entry-level, they are also the most affordable. BLS.gov states an average of all computer-related professionals at $43.87 an hour, so let's round down and call it $35.00 per hour - if we take that number and simply multiply it by the estimated time to perform this task manually - you are looking at an astounding $175,000 in labor alone! So how much did IPeople charge to automate this process for the hospital?  $1,600.

IPeople is built for this. Indeed, the second product the company wrote was a proprietary, built-for-MEDITECH scripting solution to automate repetitive tasks solving exactly the problem like the hospital above. The hospital reached out to IPeople, and after a 30-minute scoping call, our technical sales folks had a scope of work and work effort already written out, and our account executives presented it to the hospital. After a quick review (I am assuming the hospital had already done the math above), the hospital signed off and we were ready to begin work. 

Now, in this case, the stars did certainly align. This was a hospital that IPeople had previously done work for, so we had already established connectivity and had a server that was not currently at the capacity that could be used for this. In addition, an existing integration team member had just wrapped up a prior project - they were ready to begin immediately. On the next business day, within the first 30 minutes, the integration team had IPeople's scripting tool, IPeople Script, installed on the identified server. By 2:00 PM CST, the initial logic for the interface had been developed. By 4:00 PM, the proof of concept and testing had been complete. By 5:00 PM the site had verified the first five accounts to be added to the new domain and less than two weeks later, all 5,000 user accounts had been set up and completed. 208 days down to 14, 5,000 hours down to 333. 

This is the power of the IPeople Script technology, and this was the story of how we were able to successfully develop an interface for a hospital in a day, saving them over $173,400.00 in the process.

IPeople would love for our next success story to be YOU. Click the following link to set up an absolutely free 30-minute scoping session to see how we can automate your next challenge.

 

Topics: Interoperability, Interface, MEDITECH, Automation