|
Success in South Muskoka: A Messenger System Implementation Story
The Messenger LIS, through the advent of its Perfect
World Architecture, brings to the Research Community a unique system that
is platform, operating system and database independent. Messenger possesses
the distinct flexibility to evolve with technology rather than having changing
technologies contribute to its obsolescence.
Medical Technologists and system administrators
alike are discovering the dependability of this user definable product; and
the longevity of a system that is easily able to adjust to modifications
of procedure, workflow and technology. Some might say that the implementation
process for the Messenger System is demanding. Because Messenger is fully
customizable by the end user, the customer's business and medical workflow
process must first be defined and understood. In some cases, it may be easier
for the system to dictate the processes. Rob Liebeskind, founder and CEO
of Isys/Biovation, believes that the additional commitment on the front-end
yields some very valuable information, and will lead to a long-term benefit
of really knowing your business.
As implementation processes go, a shining example
is the installation of Messenger at South Muskoka Memorial Hospital in Bracebridge,
Canada. Project Manager and Technical Director, Dave Beal and staff completed
the task, from training to going live, in just under 8 months.
Having picked up the project from someone who had
already begun the process, Dave recalls there was a certain amount of the
workflow already defined. He in turn took to task the validation of that
workflow.
Over a two-week period, a short amount of time
Dave admits, he flowcharted the major processes and looked for places that
changes could be made. Dave took the Messenger Level I Training Course in
November of 2001, which he found helpful. But as he says the learning only
starts there, the rest is learned by doing and making mistakes along the
way.
What made this particular implementation so successful?
For South Muskoka Memorial there were three main components: Expectations,
Training, and Scheduling. Dave set his expectations and the expectations
of his staff beforehand. Knowing the implementation will be a time consuming
task, takes some of the stress out of the situation.
Dave also states with certainty, "You can't
spend enough time training your staff." Each person in his staff
got a total of 10 hours training in the first session, divided over three
days. Then, the week before going live he brought them back for another
3 hours each to update everyone's training.
He was also able to create his own implementation
timeline. Using the list ISYS provides with a schedule of things that are
to be done in a certain order, Dave says, "I tried to use this to
build my own personal implementation schedule, first looking at their list
of things to be done, then assigning windows of time to do each thing and
make it all flow. On Friday afternoons I would take stock of where I was
and redesign the next couple of weeks accordingly. It kept me in the right
direction."
The Messenger System under Dave's supervision continues
to lead him and his staff in the right direction. He notes, "I can
interact and make changes with the system and add sites. I think that probably,
I've only scratched the surface of the things that I can do [with the Messenger
System]. You can either be content with what you have, or you can push the
envelope once in a while and try to get things done that sculpt the system
to your needs."
Return to News
|
