Nowadays, rather than actually talking to each other, Google Calendar has become the first place my wife and I go to see each other’s availability. This is particularly interesting since her work schedule can vary from week to week. Some days she may need to be up earlier for work, and on others she may work in the afternoon.
Previously, she might verbally remember to tell me at the beginning of the week about her work schedule and even ask for some assistance waking early on Wednesday, for example. And, as any good husband would do, I would plan accordingly.
So Wednesday would come around and, being the good husband, I decided that she deserved extra rest and needed to sleep in a bit longer that morning. …I’m sure you can imagine the tone of her texts to me later that morning.
After a few of these “incidents,” I asked her to keep her work schedule on a shared Google Calendar, rather than on the native calendar app on her device. Now, rather than needing to wake her up every morning to ask her schedule, I just have to remember to look at the shared calendar on my own smart phone.
Somewhat similarly, the Corepoint Integration Engine Administration console is a web-hosted application (they typically don’t allow me to discuss marital issues on the company blog without some sort of helpful product tie in. 😉 ). This means that any computer or device with access to the network where Corepoint Integration Engine is running can be granted access to monitor interfaces in production.
It’s quite simple: If someone in another department regularly asks about the state of a connection, give him or her the server address to check at any time. No more pesky phone calls that interrupt your daily work and you’ve made a colleague a more-informed and a de facto member of the interfacing team!
However, because sensitive patient data runs through the engine, it would be a risk to grant access to every connection and log in the engine. This is one reason we created unique User Profiles.
User Profiles (see video demonstration at the end of this post) determine what information each user has permission to access in the Administration console. Administrators of Corepoint Integration Engine have the ability to restrict access to certain controls in the Administration Console, like being able to start and stop the engine service or to purge messages from connection queues. Log viewing access can be restricted to only specific connections as well. It’s also possible to disable access to the Configuration application altogether.
Creating specific User Objects for each individual allowed to log in to Corepoint Integration Engine allows for certain interactions to be tracked with an audit trail. In Configuration, this is particularly useful for seeing who made each commit in the repository. In the Administration Console, this is used in the Audit Log to show when a user viewed data that could contain PHI, which also happens to be a requirement for Meaningful Use.
Of course this only touches on a few of the settings available through the User Profiles feature in Corepoint Integration Engine.
Granting colleagues access to information relevant to their daily activities can provide peace of mind and a greater feeling of control over the data needed to adequately care for their patients. As for improving the plight of not-so-helpful husbands… that’s a job best left to shared Google calendars and surprise deliveries from your local FDA florist.
