User Profiles in Corepoint Integration Engine
User roles in Corepoint Integration Engine give administrators the ability to filter or control interfacing activities that other users can perform. The administrator can determine what user rights each user should have, including access to start/stop interfaces or permission to view log files.
User profiles enable administrators to assign access rights to users or groups so they can monitor connections pertinent only to their workflows—empowering colleagues to be proactive with connections to their own equipment.
- Customize and designate user privileges, including access to start/stop and view message log files.
- Assign access rights to an individual or a group of user profiles to monitor designated interface connections.
- Audit logs provide added security by tracking who has signed into the system and when, including what date they viewed the data and what they did with the data
With user roles in place, a set of connections might look like Figure 1. In this example, some of the permissions granted for users of the two connected systems overlap and some do not.
User roles allow designated users to view and troubleshoot certain portions of the interface without the ability to modify the engine configuration. This relieves the interface team from the responsibility of being the first point of contact when interface issues arise.
User roles are particularly useful if a problem occurs in the workflow or with interface data for a connected system. A person with the appropriate user role can investigate the issue rather than immediately contacting the interface team. Examples of issues include:
- A user cannot find a patient in the database. What happened to the message?
- An order comes in and contains incorrect information, such as the wrong ordering physician, a bad priority, or a bad date or time. Did something happen to the message in the engine, or did a user simply enter the data incorrectly?
- A system is not receiving data. Is the connection still up and running?
Two systems are exchanging messages when the lab technician notices that the LIS system is no longer receiving data.
As shown in Figure 2, without user roles in place, the first course of action would be for the lab technician to contact the interface team to check on the issue. The interface team would go into Corepoint Integration Engine to identify the problem. Noticing that the connection is down, they would restart the connection and then notify the lab technician that the issue was resolved. A minor issue, with a simple solution, required interface team involvement to get data flowing again.
With user roles in place, shown in Figure 3, the interface team can create unique permissions for the lab technician, granting full access to view her or his particular connection status, history, and alerts. Additionally, the technician is granted the ability to stop and start the connection. The technician is given no other permissions in Corepoint Integration Engine.
In this scenario, the lab technician logs into Corepoint Integration Engine to check the status of the connection. Seeing that the connection is down, the technician restarts the connection, logs out of Corepoint Integration Engine and the data is now flowing to the LIS. The issue was resolved without needing to contact the interface team.