One of the strengths of an online community is its collective knowledge — the collaboration and innovation of many that can accomplish far more than any one individual or organization. It’s an open-source culture that has expanded way beyond the software community.
At a conference in Kansas City last week, fusion-physicist-turned-farmer Marcin Jakubowski told about Open Source Ecology, a network of farmers, engineers and supporters designing and posting do-it-yourself schematics for what they see as the world’s 50 most important machines. At a 30-acre site in northwest Missouri, workers have prototyped the first eight modular machines in this collaborative Global Village Construction Set. They envision their designs being used to “lower the barriers for entry into farming, building and manufacturing” around the globe. Another conference speaker, crisis mapper Patrick Meier, talked about the open-source Ushahidi mapping software and legion of worldwide volunteers that have helped governments and the United Nations pinpoint particular people and areas devastated in such recent and ongoing crisis areas as Haiti, Libya and Somalia.
Our humble blog can’t boast such expansive life-saving work, but we’re glad to be a part of an online community working together to improve the world of healthcare IT (which actually can save lives). For the past several years, we’ve addressed many of your concerns with our practical advice for maintaining and troubleshooting your complex Cerner Millennium® EMR system. We’ve even compiled a number of these into in-depth papers on such topics as message log monitoring, tips for remote-hosted organizations and steps to minimize risks during upgrades. These and more are available on our website.
To help us continue to cover the issues affecting your organization, we’d love to hear from you. Where specifically are your pain points with your EMR? In what internal or external areas do you need more understanding? What creative solutions has your IT team found? We will endeavor to address whatever ideas you suggest.
Just click the Comment link below to get the conversation started.
Hi continue to enjoy your articles;
Love the articles, but off top of my head
MQ, how best to monitor, manage and get the best performance.
2010.01 the new code level, what are improvements, the new MQ settings, and other settings.
Maybe take a look Cerner settings files like system.cerner etc.. the hnaagent file, setting worth changing or reviewing (like preventing server 56 killing servers?)
Front End Citrix Server settings any that should be reviewed.
Cerner do a System Setting document on uCern, maybe talk about some of them why should we review settings on regular basis?
How to manage long running scripts, troubleshoot them
Use of tools such as MTA, Issue Collector, Crash Collector
Posted by: Roland | Sep 08, 2011 at 03:20 PM
Thank you for the great feedback, Roland.
Whew! It is quite a list. I will begin tackling some of these topics after CHC2011.
Just as a heads-up, some could end up in white papers because they are technical and very involved.
I look forward to any additional feedback from you or your co-workers on specific issues or problems you have had.
Posted by: David Hallberg | Sep 12, 2011 at 09:25 AM