After witnessing several family members with chronic health care "mysteries" bounce from physician to specialist, it became apparent that if all the physicians and specialists had met briefly to discuss the case (a "scrum", if you will), the solution could have been identified within hours instead of within months.
One loved one with a chronic health "mystery" went to the Mayo Clinic in Rochester where exactly this kind of care was administered and within 2 hours, 4 physicians and specialists had identified the root problem and the long-term solution. The loved one has not had a relapse of this condition since the Mayo Clinic "Scrum". The Mayo's physician teamwork correctly identified the issue in record time - reducing patient suffering as well as medical costs.
To support a new approach to healthcare, there will be the need for reform in how physicians and specialists interact, but also a new approach to managing the healthcare data. Tooling to support reform includes dashboarding, data integration, business intelligence/analytics, and updated health privacy policies. It's also my opinion that an overall case management methodology based on Scrum Agile would also improve patient care accuracy and improve solution delivery times.
A white paper written recently highlights the need for integration of health care across health silos and the increased collaboration of a team of physicians to create a holistic medical solution for each patient. Visit Healthcare Reform and Master Data Management at Perficient's published whitepaper website (whitepaper by Perficient's Lisa Morris and KEMH LLC's business partner, Linda Lyons, as contributor).
Monday, November 16, 2009
Thursday, November 5, 2009
If the framework fits...
To those in the know, there are general frameworks and concepts that hold true (with perhaps minor modification) regardless of the industry.
Enterprise Content Management and creating data portals/business intelligence reports are among the concepts that can be easily ported from one company to the next with minimal modifications based on industry. When trying to create flow of data through the enterprise to teams upstream and downstream, the need is the same though the content may be different.
Based off my consulting experiences in various industry, including manufacturing, marketing, health insurance, insurance, travel, financials, among others, the enterprise overview graphic I've created below depicts a standard flow of how I've seen data flowing across heterogeneous enterprises. This is how organizations can leverage the benefits of best practices in reusing tested frameworks across industries and companies, lowering risk and short- and long-term costs, while leveraging a wider pool of knowledge and lessons learned.
Enterprise Content Management and creating data portals/business intelligence reports are among the concepts that can be easily ported from one company to the next with minimal modifications based on industry. When trying to create flow of data through the enterprise to teams upstream and downstream, the need is the same though the content may be different.
Based off my consulting experiences in various industry, including manufacturing, marketing, health insurance, insurance, travel, financials, among others, the enterprise overview graphic I've created below depicts a standard flow of how I've seen data flowing across heterogeneous enterprises. This is how organizations can leverage the benefits of best practices in reusing tested frameworks across industries and companies, lowering risk and short- and long-term costs, while leveraging a wider pool of knowledge and lessons learned.
Why Risk the Requirements?
Requirements Risk Management (RRM) is the best way the industry has to eliminate the 90% of product defects introduced in the Requirements phase.
Some methodology, such as Scrum Agile, are designed with RRM in mind. Early learning is key to getting it right before getting it wrong costs the organization budget, credibility, and morale.
Please click here to see the Requirement Risk Management presentation I prepared and delivered to a Project Management 101 group, with references to industry experts, in November 2007.
Some methodology, such as Scrum Agile, are designed with RRM in mind. Early learning is key to getting it right before getting it wrong costs the organization budget, credibility, and morale.
Please click here to see the Requirement Risk Management presentation I prepared and delivered to a Project Management 101 group, with references to industry experts, in November 2007.
Subscribe to:
Posts (Atom)
