18 October 2013


1. Single Sign-On (SSO) and common identity management with CCOW integration 
"Start to phase out all applications that cannot meet common identity or SSO requirements," said Shah. The benefits of SSO are many, and include end-to-end user audit sessions to improve security reporting and auditing as well as significant password help desk cost savings. Likewise, Clinical Context Object Workgroup (CCOW) was designed to allow information sharing between clinical and health IT applications, Shah wrote on his blog, adding that "if a hospital can get their labs,EMR, and CPOE vendors to become CCOW compliant, they can share patient context instead of the user having to log in and out of each application separately." 

2. Programmable and app-driven content management and document management systems 
Both should be "a core for electronic health records instead of special-purpose EHR systems written decades ago," said Shah. "For starters, EHRs should be connected to the right document and content management systems like SharePoint or Alfresco." And when an EHR vendor can't meet your requirements, said Shah, what should be encouraged is meeting the requirements in an adjunct system that works with the EHR. 

3. Virtualization. According to Shah, virtualization should be a priority 
"As soon as possible, make it so that no applications should be sitting in physical servers," he said. "Start to phase out those apps that cannot be virtualized. When apps are virtualized, they can easily be scaled and recovered." On his blog, Shah added that environments with a lot of legacy systems embrace virtualization since it allows them to maintain their software while significantly upgrading hardware. "In the past, we've not seen this happen in healthcare," Shah wrote. According to him, simple cloud adoption is next once virtualization becomes the norm. 

click here to view this article
itech solutions website

No comments:

Post a Comment