This announcement describes in detail the next step in the evolution of a great healthcare IT company.
This is a big day in Raleigh – and something I'm proud to be a part of .. and it's one of two announcements made this week. The other one is just as important and highlights how Misys "gets" health IT in a way that most companies don't yet take seriously.
Longtime readers of Docnotes understand that I say what I think – and nothing less. This isn't the company speaking – this is me. As an industry – we've been held back by the self-evident truths that turn out not to be so true. Misys is now in a great position to demonstrate the agility often seen in only small companies – with the integrity, depth, and strength that one only finds in large companies. Our elephant is beginning to dance!
Take a look here at this: this wonderful set of resources.
The argument that HL7RIM is incoherent is compelling. I'll admit that I've found HL7 RIM to be impossible confusing for years. The problem is that as a foundation for all-things-HL7, RIM causes a lot of trouble.
I've had some very interesting conversations recently with Neil Cowles – CEO of Tolven – where they have created TRIM – for the definition of RIM based templates. Neil argues that TRIM provides all of the functionality and interoperability of RIM without the complexity.
Our IS department didn't support Treo 700p or 755p and I suspected that it had to do with our security certificate. Versamail 3.5 is more careful about self-signed certificates than previous versions were – and since 3.5 is installed on the 700p and 755 – these devices won't work without installing the self-signed certificate. It's pretty easy. What you need:
b) The certificate from the company's exchange server. May need to get this from your IS department.
If you are a company IS person reading this – then you can do most of the work for your users. If you are one of those users – and the IS folks have done this for you – follow along from step #2.