Believe it or not, you can actually build a website using Corepoint’s RESTful web services. Prior to REST’s availability, I had to run tests and look at logs to see messages. The real visual proof of success is another application’s screen being properly updated. Now, with building a website, I get visual confirmation that I made the HTML correctly. Using RESTful is a new interfacing method in healthcare that presents a brand new world of possibilities to improve workflows and exchange data – and now I have some simple HTML skills.
Here are some different website ideas that can improve your current workflows:
- A website that offers the ability to view and edit a correlation or code set that is stored in a database table. This provides non-Corepoint users the ability to update key data.
- A website that displays a team’s rotating on-call schedule. The site can provide info on who is on call and how to change the schedule, which allows Corepoint alerts to go to the right on-call person on the day they are scheduled.
- A page that allows users to see “held orders” and manually release them at the right time.
- A site with a worklist of error messages that were the result of missing or incorrect data for a particular application. The website could poll a database to see what errors have not yet been corrected so the team can find a solution and provide the ability to resend the message right from the webpage.
A Corepoint Health customer had a need for the last scenario:
We created a custom website that, after login, users could see a worklist of messages that needed correction. The list only contained the facilities each particular user had authorization to view. This web page is unlike Corepoint Integration Engine’s Error Log, which shows the errors from every interface and continues to display the error messages after a user has resolved the error. Corepoint Integration Engine has always had the ability to access databases, so this particular scenario was no different: it worked with database tables for login access and tables for storing errors.
This website was a huge improvement because it allowed users to view the list of errors in a browser instead of using Microsoft’s SQL manager. An integration engine always has access to clinical data and – by using REST to create websites – important data becomes readily available to end users without the need to know SQL or have access to Corepoint’s configuration.
Building custom web pages is not the only thing that can be accomplished using web services in Corepoint Integration Engine, but it is highly rewarding to provide end users unique workflows customized to their particular role. Depending on your web development skills, the possibilities are endless.
If you are interested to learn more about web services, I highly suggest enrolling in one of our web-based 😉 web services training classes to see all the things you can accomplish with this powerful feature in Corepoint Integration Engine.