Sunday, January 27, 2008

Electronic Records for Non-Owned Doctors

In my previous post The top 10 things that will keep me up at night in 2008, the number one project is providing electronic health records (EHR) to non-owned physicians.

This will be the first of a series of posts about this very complex project. My posts will detail the cost challenges, the partnership we've built to execute the project, and the technical approach we've taken. Since this is truly a work in process, I'll publish these posts each week over the next few months.

Since 2002, my IT teams have provided electronic health records to every owned/closely affiliated clinician of Beth Israel Deaconess, using our home built webOMR software. We even have a Medical Executive Committee policy mandating the use of electronic health records for owned clinicians by July 30, 2008. 'Use' is carefully defined, since we want all our clinicians to update the problem list, create an electronic note for each encounter, and perform all medication management (e-Prescribing, medication reconciliation, allergy documentation) electronically. Of interest, recent data collected by David Blumenthal of Massachusetts General Hospital concludes that only 4% of clinicians in the US have this level of use of fully functional electronic health records.

Since Stark safe harbors now enable hospitals to fund up to 85% of the non-hardware implementation costs of private practice electronic health records, my teams are now expected to provide EHR solutions for all the non-owned affiliated BIDMC affiliated physicians in Eastern Massachusetts. This is a very different project than providing applications and infrastructure to owned clinicians, which we manage, on a network, which we manage.

The planning for the project includes the following major issues:

1. Designing Governance – My typical steering committees are drawn from hospital senior management, employed clinicians and hospital staff. The governance of a community-wide electronic health record system must include members of the physicians' organization, private physicians, community hospital executives, and legal experts.

2. Modeling costs – The 'hydraulics' of the project budget are quite complex. The hospital wants to support implementation for as many physicians as possible but has limited capital. The physicians want as much implementation subsidy as possible since by Stark regulation they have to fund all hardware and ongoing support themselves. The number of doctors implemented, the level of subsidy and total costs for all stakeholders are interrelated but each party has different goals.

3. Planning for distributed users – These non-owned clinicians are widely dispersed throughout Massachusetts and New England in urban and rural settings. Bandwidth varies from 20 Megabit Verizon FiOS connections to 56K dialup. Technology sophistication varies from fully 'wired' clinicians to offices run on 3x5 index cards.

4. Managing the project – CIOs traditionally serve hospital-based customers. They may not have the bandwidth or expertise to serve non-owned geographically dispersed customers.

5. Building a scalable infrastructure - The architecture must be designed to minimize costs, maximize reliability and support a project scope that is continually evolving.

6. Deploying staff - The existing hospital IT staff is not optimized for supporting networks, telecom, desktop and application at hundreds of remote locations. The physicians' organization and clinician offices do not have the staff or expertise to execute this project.

7. Creating the Model Office – A clinically integrated network of providers in a community will want to adopt a standard EHR configuration with common dictionaries to support healthcare information exchange and continuity of care. Standardizing software configuration means standardizing workflow, which requires business process re-engineering. Practice consulting is needed to balance standardization with specialty specific processes, ensuring that providers buy into the new workflow and staff are appropriately trained.

8. Obtaining all the funding - Once the scope, architecture, staffing and cost modeling is completed, the funding must be obtained from all of the stakeholders. State and Federal governments are not likely to contributing anything. Payers may fund the outcomes of EHR use via pay for performance, but are unlikely to pay for implementation.

9. Specifying the order of implementation - How do we choose the most appropriate offices for pilots and once those pilots are completed, how do we place hundreds of clinicians in a well ordered queue for rollout?

10. Supporting the practices – Hospital support models depend upon standardized networks and desktops with end to end control over the quality of service. Supporting heterogeneous practices requires on site, high touch, higher cost service.

My goal is to create a blog entry for each of these issues. Next week, I'll publish the governance model. The following week, I'll post the detailed considerations we're using to develop the cost model (the finished models will be published under 'obtaining all the funding', since they are still evolving). By the time all 10 posts are done, we'll be live in pilots with 4 practices and I hope to be able to sleep again.

6 comments:

kerrie_morin said...

Can you give me the reasons why your organization decided to donate software to non-owned clinics? I'm trying to research theh expected benefits to the donating hospital? Any information that you can share will be most appreciated.

dan said...

Do you have a marketing plan in place yet for the non-affiliated physicians that captures the general terms of your offer to cover a percentage of applications and infrastructure? Working on a HIMSS presentation that includes Stark/Anti-kickback strategies. Thanks.

Debra said...
This comment has been removed by the author.
Debra said...

Do you have any experience on what is required (and legal) for a hospital/IDN to leverage their EMR into non-owned community hospitals. The EMR allows partioning so financial and clinical information would be separated by hospital.

平平 said...

^^Thanks!!

婚前徵信婚姻感情大陸抓姦外遇抓姦法律諮詢家暴婚前徵信尋人感情挽回大陸抓姦離婚工商徵信婚前徵信外遇抓姦感情挽回尋人大陸抓姦離婚家暴工商徵信法律諮詢跟蹤工商徵信婚前徵信感情挽回外遇抓姦法律諮詢家暴尋人大陸抓姦離婚大陸抓姦外遇尋人家暴工商徵信法律諮詢家暴感情挽回大陸抓姦外遇婚前徵信離婚尋人工商徵信外遇抓姦法律諮詢家暴婚前徵信大陸抓姦尋人感情挽回外遇抓姦婚前徵信感情挽回尋人大陸抓姦工商徵信法律諮詢離婚家暴工商徵信外遇抓姦法律諮詢家暴婚前徵信尋人感情挽回大陸抓姦離婚婚前徵信工商徵信外遇抓姦尋人離婚家暴大陸抓姦感情挽回法律諮詢離婚感情挽回婚前徵信外遇抓姦家暴尋人工商徵信外遇抓姦法律諮詢家暴婚前徵信尋人感情挽回">徵大陸抓姦離婚婚前徵信工商徵信外遇抓姦尋人離婚家暴大陸抓姦感情挽回法律諮詢

Affordable Luxurious Wedding Dress Blog said...

cheap wedding gowns,
discount bridal gowns,
China wedding dresses,
discount designer wedding dresses,
China wedding online store,
plus size wedding dresses,
cheap informal wedding dresses,
junior bridesmaid dresses,
cheap bridesmaid dresses,
maternity bridesmaid dresses,
discount flower girl gowns,
cheap prom dresses,
party dresses,
evening dresses,
mother of the bride dresses,
special occasion dresses,
cheap quinceanera dresses,
hot red wedding dresses