Comments on: Why vendors don't implement CCOW in legacy systems http://www.healthcareguy.com/2006/02/23/why-vendors-dont-implement-ccow-in-legacy-systems/ Shahid's healthcare IT, EMR, EHR, PHR, medical content, and document managment advisory service. Enjoy. Thu, 09 Feb 2012 13:50:00 +0000 hourly 1 http://wordpress.org/?v=3.1.3 By: Matt Hernandez http://www.healthcareguy.com/2006/02/23/why-vendors-dont-implement-ccow-in-legacy-systems/comment-page-1/#comment-164 Matt Hernandez Wed, 02 May 2007 17:24:58 +0000 http://www.healthcareguy.com/?p=209#comment-164 "I don’t believe they’ve ever been confronted with a legacy app they can’t integrate with their stuff." You would have to have been with them longer than 18 months to make that statement. We had a lot of problems trying to integrate only 3 major vendor apps at our shop. There was 1 CCOW (Cerner) and Sentillion built 2 bridge products that never quite worked. Also its main desktop context manager was not reliable over wireless. A one second disconnect would hang the system and require a reboot. This was a couple of years ago. Hopefully the products are more robust now. It probably works great with CCOW apps, but don't assume they'll be able to bridge legacy apps. Every situation is unique. “I don’t believe they’ve ever been confronted with a legacy app they can’t integrate with their stuff.”

You would have to have been with them longer than 18 months to make that statement. We had a lot of problems trying to integrate only 3 major vendor apps at our shop. There was 1 CCOW (Cerner) and Sentillion built 2 bridge products that never quite worked. Also its main desktop context manager was not reliable over wireless. A one second disconnect would hang the system and require a reboot.

This was a couple of years ago. Hopefully the products are more robust now. It probably works great with CCOW apps, but don’t assume they’ll be able to bridge legacy apps. Every situation is unique.

]]> By: Steve Early http://www.healthcareguy.com/2006/02/23/why-vendors-dont-implement-ccow-in-legacy-systems/comment-page-1/#comment-163 Steve Early Thu, 07 Dec 2006 14:05:23 +0000 http://www.healthcareguy.com/?p=209#comment-163 Regarding Sentillion: I have been doing consulting work with this firm for the past 18 months or so and while they did originally start as a "CCOW Vendor" they have mushroomed into much more. They used their original knowledge of CCOW to develop a robust set of products for healthcare companies to perform identity and access management functions (user authentication, single sign-on, automated user provisioning, single patient selection and more). Their original CCOW work has also lead to the development of an SDK to help companies CCOW-enable their apps. They also have developed a VERY cool wizard-like interface that allows their healthcare customers to develop simple software bridges that link non-CCOW apps into their single sign-on environment in a matter of minutes. (Thus the product name "BridgeBuilder"). This interface works extremely well for web-based and client-server apps where 'username/password' are what is required to sign on. For the old legacy "green screen" apps, Sentillion builds bridges for their clients using a scripting language. I don't believe they've ever been confronted with a legacy app they can't integrate with their stuff. I just didn't want your readers to be left with the impression that Sentillion is just a "CCOW vendor". They're much much more than that today. /s Regarding Sentillion: I have been doing consulting work with this firm for the past 18 months or so and while they did originally start as a “CCOW Vendor” they have mushroomed into much more. They used their original knowledge of CCOW to develop a robust set of products for healthcare companies to perform identity and access management functions (user authentication, single sign-on, automated user provisioning, single patient selection and more). Their original CCOW work has also lead to the development of an SDK to help companies CCOW-enable their apps. They also have developed a VERY cool wizard-like interface that allows their healthcare customers to develop simple software bridges that link non-CCOW apps into their single sign-on environment in a matter of minutes. (Thus the product name “BridgeBuilder”). This interface works extremely well for web-based and client-server apps where ‘username/password’ are what is required to sign on. For the old legacy “green screen” apps, Sentillion builds bridges for their clients using a scripting language. I don’t believe they’ve ever been confronted with a legacy app they can’t integrate with their stuff.

I just didn’t want your readers to be left with the impression that Sentillion is just a “CCOW vendor”. They’re much much more than that today.

/s

]]>