Business Insight and Improvement


The debate and discussion about electronic health records or patient records is getting louder than the noise Seattle SeaHawk’s 12th man can make during the home game.  Backed by both presidential candidates and some of the biggest technology companies like Google, Intel and Microsoft, it can’t get muzzled out that easily. So you might think that we are entering a breakthrough age led by these giants and finally the area of digital health care is dawning upon us. Hold your horses. It is not that easy as it seems.

The idea and motivation for the electronic health records or patient records or medical information system, whatever you call it, is to get the patient information  in digital format so that it can be shared by doctors, insurers and others easily. The benefits of such sharing or collaboration could be to cut time for finding cure, avoiding delivering wrong treatment and the mobility of the patient records.  It can also cut costs for maintain paper and the time for patients to wait to fill it out during visits.

The challenge is really simple: Trust. Confidentiality and privacy concerns are outdoing the chance to get on this bandwagon. Critics also point out that privacy violations; technology risks and potential of such data being used for promotional purposes are far too risky to enjoy the benefits.  Nobody wants to trust the corporate profit-mongers with the essential data about health and then see themselves getting hijacked by the keepers of the information. No one has forgotten hassles of do-not-call lists, spam is still not dead and hackers never go away. So much for giving away your telephone number or email, what will happen once your entire health history is online? Just shudder to think what will happen once someone out there on the crazy anarchic internet knows about your irritable bowel syndrome. You will soon be bombarded with ads promoting the cure or you will become an office joke if your team member finds about it. That google search can be nasty you know.  Additionally, the patient records should not be at the mercy of these business models but really should be decoupled to deliver the benefits without the profits.

One point being overlooked is the bottom-line in these discussions: Information.  It is all about the information. Information about the medical knowledge, ability to find such information in time, almost anywhere with security in place so that it could be used for proper diagnosis in due time and save lives. Information which hospitals, patients, insurers and governments can use in a better way to reduce the time taken for approvals and delivering patient care.  The right information at the right time can really make a difference between life and death.  

The power of information is really the victim in this clash of health care IT and the privacy concerns.  It is amazing that in such a information-critical area of practice, the medical information systems still lacks the modernization that can be delivered by the technological innovations available today. Health care industry will spend approximately 30 billion dollars in IT investments this year, about same they spent in 2007 and on par with estimated spending for 2009. This goes with the historical trend in healthcare IT.  While pharmaceutical companies spend billions of dollars way more than 30 billion in new drugs, hospitals don’t spend nearly enough to get enough information about these drugs at the first place. That is why the incidences of drug side effects, improper dosage guidelines and lawsuits for the advertised drugs are increasing.

The technology to deliver this power of information is available and has been implemented successfully by a lot of big corporate, US government, Pentagon and the likes. For health information, what is needed is a way to deliver it in a fashion that makes sense to all the stakeholders.  May be instead of the idea of Google Health, HealthVault (Microsoft) and Dossia (Intel) which gives patient information to a corporation’s data center; patient information should be owned by patients to start with. The patient records should be normalized to start with and the patients should be allowed to transmit these records electronically to the doctors prior to their visit. This can follow the model of tax preparation and filing to IRS.  Individuals are responsible for preparing their tax returns and submitting to IRS. You can take assistance from CPAs if you wish but ultimately IRS will hold you responsible. If we are comfortable submitting our vital financial information to CPAs, TurboTax.com and IRS; then similarly we would feel comfortable with our health information.

All hospitals and doctors can install kiosks at their lobbies to assist patients in creating such records and electronically submitting it to the doctor’s office. This would reduce the time for patients or at least make it predictable. This would also avoid all the hassles of maintenance and storage of the paper records. The electronic health repository would make the search for information easier and help doctors to submit claims to insurance agencies much faster.  This can spawn whole ecosystem of software, services and support for electronic health information or medical information systems.  This will lead and improve the collaborative healthcare between internal medicine practitioners, surgeons, radiologists, labs to deliver a comprehensive health care for patients.

So, pay attention Healthcare IT – adopt collaboration and improve the state of healthcare in US. 

Applied SharePoint Case: Dashboards

One of the very common and important “applications” or use of SharePoint is to use it as a Business Intelligence system. Basically a “View” which aggregates the information from various enterprise (or non-enterprise) sources and presents this information in an context.

One of the easiest ways to create a BI Dashboard on SharePoint (You would need Enterprise license of MOSS) is to use Excel web parts and Excel files.

Here are some of the dashboards we have created.

I attended Mark Logic User Conference last week in SFO. We are discussing a partnership with Mark Logic and so I thought I would go check it out. I was impressed with the user turnout and passionate support the attendees showed towards the Mark Logic Server.

I did get to attend a few presentations during this, particularly:

  • Exploiting Office and OpenXML with Mark Logic Server
  • Dynamically Integrating Event Data to Model and Analyze Business Processes
  • Keeping Users informed with Alerting
  • Launching Video Search at CQ

Though I need to bring myself upto speed with a lot of technical details about Mark Logic, I came away with appreciation for this XML based information storage and discovery product.

A lot of enterprises produce variety of content from brochures to legal documents and need dynamic information aggreation for various business needs. With OfficeXML paving way for Office intgeration with Line of Business systems, a content based intgeration can be made easier by looking at Mark Logic.

Advanced Analytics, MashUps and subject-centric portalsites are some of the applications which can benefit from this content-driven architecture.

Currently Mark Logic is being used by Media and Publishing industry which is often content heavy. But it can be extended to enterprise scenarios to give some help to marketing, engineering, PR, legal and HR departments in their content-hungry or dynamic publishing needs.

Food for thought.heh?

 

I am making available the PDF of our webinar “Maximize Your SharePoint Investments” here.

 

“If at first you don’t succeed, then skydiving is not for you.” (and so is MOSS)
 

The above quote is true for skydiving and some other extreme sports as is valid for enterprise SharePoint projects.  I have been involved in a lot of serious enterprise-level MOSS-based transformation projects from a small internetsite POC to a HUMONGOUS project which had intranet, applications, integration and BI facets. Offcourse I have seen a number of talented teams struggling with MOSS projects. More often than not that is the reason we (or other consultants like us) get invited to help, ya?

It does hurt me when I hear from CIOs and IT managers about how much time and money they spent “trying” to do something with MOSS.

One of my customers spent one and half years and nearly 250k in trying to create a small extranet portal on MOSS. They hired a developer who was not skilled in MOSS but knew .NET and allowed him to learn on the job. Voila, they ended up with a system which could not be deployed and which did not meet the requirements 100%.

One of our other customers tried “in-house” approach with inhouse skills for more than a year with a large MOSS farm and ended up with an unstable platform after all this time. Money spent was eaily around 500k when taken into all hardware, software, people salaries etc.

Some other customers, burnt by hardships, have lowered their bar and are just content with the scrappy out-of-the-box intranet.

It does hurt, doesnt it, to see and hear about these self-inflicted wounds by these companies. Yes, they do fall prey to some sales pitch that MOSS is so easy that even a monkey can do it. And what happens when they try it. They wish they did not have to hand a hammer to a monkey.

Would the same companies deal with  a SAP project the same way? Would they deal with a Tibco B2B project the same way? I bet not. Then why with MOSS, they make these decisions and get hurt?

I really think that IT and business decision-makers should start taking MOSS projects seriously and stop the “trial and error” approach. MOSS just like any other middleware is as complex and requires a skilled hand. Why waste the time and money in trying to do “something” with MOSS? Why “somehow” implement an OOTB MOSS feature set and not achieve an optimum ROI? and then complain about MOSS?

When properly architected and designed, MOSS can help you achieve optimum ROI from your investments. We are helping our customers with their first entry in SOA enabled enterprise clouds by using MOSS. We are using MOSS for rapid application development for their business apps. We are creating an integrated platform on MOSS which delivers consistent and controlled content to their internet,intranet and extranet properties. We are creating business LOB systems on MOSS. Thus we are helping our customers reap optimum ROI from their investments.

So I say, when in doubt, seek wisdom. Dont waste time and money with experimentation on MOSS. It is not worth it. More often than not, the next guy ends up cleaning up mess created by the first guy. Thus wasting more time and money for you. That is what I am currently doing at my current project.

MOSS just like SAP or Sieble, requires specialised skillset and you should seek it if you dont have it available inhouse. It requires same SDLC considerations, architecture thought and planning game.

So do yourself a favour and seek help when  you need.