Thursday, December 27, 2007

Predictions for 2008 (And beyond)

It's that time of year for resolutions and futurist's predictions. I am a frequent reader of Medinnovations blog by Richard Reese, M.D. Dr Reese is a far more eloquent and articulate writer than I could ever hope to be. As a retired pathologist he sees the big picture from afar.
Amongst his predictions at his website, www.medinnovationblog.blogspot.com/ are commentary about RHIOs and EMRs. Despite the fact that I have been a proponent for RHIOs, HIEs and the like I have seen little progress for connectivity. There has been slow adoption of EMR. Physicians do need portals to access lab and imaging results from other sources. No doubt the physician wannabees and other "controllers" of our medical destiny (as well as the health IT sector) want to see all of this put into place. Physicians, while attempting to remain proactive find themselves sadly far behind the power curve, and and most are certainly not in the position to invest in this technology for many reasons. While most if not all providers who have adopted EMR state "they would not go back", this is a very biased answer since they have invested thousands of dollars into their "systems". (would you negate your investment with a negative evaluation?) .

In an election year the politicians in either party will be jockeying regarding their positions in regard to health care funding. Implementing Health IT is a solution that on the surface is politically correct.

My evaluation is "the jury is still out" . It is far too early to sign the death certificate for RHIOs.

Happy New Year to all.

Sunday, December 23, 2007

THE STATE OF RHIO

In a recent article from "DATA WATCH"  Adler, et al have surveyed the activity, success and failure rate of RHIOs across the United States.  The article can be found at "Health Watch".

Electronic clinical data exchange promises substantial financial and societal
benefits, but it is unclear whether and when it will become widespread. In early 2007 we
surveyed 145 regional health information organizations (RHIOs), the U.S. entities working to
establish data exchange. Nearly one in four was likely defunct. Only twenty efforts were of
at least modest size and exchanging clinical data. Most early successes involved the exchange
of test results. To support themselves, thirteen RHIOs received regular fees from
participating organizations, and eight were heavily dependent on grants. Our findings raise
concerns about the ability of the current approach to achieve widespread electronic clinical
data exchange. [Health Affairs 27, no. 1 (2008): w60–w69 (published online 11 December
2007; 10.1377/hlthaff.27.1.w60)]

The appeal of electronic health information exchange (HIE) in general, and
RHIOs in particular, is evident. An electronic, interconnected regional infrastructure
represents the rational approach to handling the volume and specificity of
health-related information required to efficiently deliver optimal care, particularly
in information-intensive specialties

Monday, December 17, 2007

THE CHIEF MEDICAL INFORMATION OFFICER

clip_image002 CLINICAL INFORMATION EXCHANGE

A  White Paper on the rise and role of the CHIEF MEDICAL INFORMATION OFFICER

Clinical Information Exchange is pleased to present this timely review of the role of physicians in deploying EHR, EMR and clinical information systems such as CPOE, Lab reporting, and connectivity.

Physician leadership is a critical success factor for health information technology initiatives, but best practices for structuring the role and skills required for such leadership remain undefined. The authors conducted structured interviews with five physician information technology leaders, or Chief Medical Information Officers (CMIOs), at health systems which broadly used health information technology. The study aimed to identify the individual skills and organizational structure necessary to for a CMIO to be effective. The interviews found that the CMIOs had significant management experience prior to serving as CMIO and were positioned and supported within each health system similar to other executive leaders; only one of the five CMIOs had formal informatics training. A review of the findings advocates for the CMIO to have a strong background and role as a physician executive supported by knowledge in informatics, as opposed to being a highly trained informaticist with secondary management expertise or support.

Are you a highly computer-savvy physician? Well, now may be your golden hour, according to one blogger. The position of chief medical information officer (CMIO) is getting hotter by the minute, as hospitals seek doctors to manage their investments in clinical IT categories like EMRs, e-prescribing and clinical support systems. CMIOs often make $200K or more per year, with some enjoying much larger salaries than that. And this isn't a boring job--they get the shape the future of medicine, as defined by the new systems coming on board to manage data. Isn't this worth examining?

The presence now of the chief medical information officer title indicates its growing importance in healthcare. Organizations are likely focusing on the necessary integration of technology and medical applications, which requires significant physician input and leadership,

FROM: ADVANCE FOR HEALTH INFORMATION EXECUTIVES

Vol. 10 •Issue 2 • Page 64

A Place for the CMIO

By Betsy Hersher

The CMIO position got its start in marketing the value of clinical systems, but the role has grown in stature and is moving many health care organizations forward.

I t seems that we have been writing and talking about the emerging role of the chief medical information officer (CMIO) for many years now. We have monitored this growing trend since 1992.

The increase in the number of information technology (IT) physicians has been significant. If we view IT physician roles as an evolution, we can analyze this trend as a historically separate iteration. In the 1980s, as clinical systems started to appear, the first group of "in-house docs" built their own clinical systems. However, in the late 1980s, the CIO began working with clinicians to gain process understanding, credibility and buy-in during the selection and implementation of new clinical systems. The utilization of internal physicians who continued practicing 50 to 75 percent of their time served the purpose in the earliest iteration of a role with no title, little authority and no clear job description. Few educational programs supported those clinicians. Also, most of the clinicians had little experience in project management of clinical information systems.

The CMIO concept

The concept of the CMIO grew slowly, probably dating from 1992, until the present. The second iteration of this new role visibly changed. There was significant buy-in from peer clinicians and the executive team. The title of CMIO took shape with a large component of the job marketing the value of clinical systems in the delivery of care.

Job descriptions and accountabilities remained vague and time spent practicing decreased. The position reported to the CIO in most organizations. Vendors and consulting firms started hiring clinicians to support product development, customer service and marketing. In this vendor group of physicians, clinical practice for the most part stopped. Typically, the clinicians in those roles were passionate, although deliverables were vague, and success difficult to measure. Vendors and consulting firms used titles such as physician executive, vice president of transformation, and not CMIO, which seemed to be adopted by the health care delivery systems.

The reporting structure had little uniformity. Vendor jobs were vigorous with significant travel and little or no career path. Clinical systems evolved rapidly with a simultaneous need for physician involvement in quality, compliance, the electronic medical record (EMR) and computerized physician order entry (CPOE).

As the new century started, government, business and hospital boards of directors began demanding significant and costly clinical systems to meet their quality and cost expectations. The mandates came from so many arenas the demand for IT-experienced clinicians grew exponentially, following a similar growth pattern as the evolution of the CIO's role in the late 1980s. However that's where the similarity stopped.

The reporting structure

At the start of the decade, a few job descriptions, accountabilities and career paths applied to clinicians.

The title of CMIO on the provider side became a common denominator.

Still reporting to the CIO, the CMIO role became essential and recruitment from outside organizations became necessary. Until only recently, physicians continued to practice 20 to 30 percent, to maintain their credibility.

However, many events occurring simultaneously affected the CMIO role significantly. The Institute of Medicine's "To Err is Human" report got government and industry more involved, which also triggered board concern and action. Quality, safety and compliance began to move the CMIO reporting structure away from the CIO to the chief medical officer and chief operating officer. Some CMIOs also began reporting to the CEO, particularly if quality was part of their portfolio.

Physicians became project executives with little or no management experience. During this rapid change, the first and second group of physicians moved from vendors and consulting firms for a variety of reasons. They began leaving and going back "home" to the delivery systems. Thus was born the current and third iteration of IT physicians.

What was lost is found

The industry has realized that the practice of medicine one day a week does not define a respected CMIO. So, what defines the role? The CMIO role is growing so rapidly that support structures can hardly keep pace. Physicians have very full plates. Meanwhile, boards and executive teams are under great pressure to quickly deploy EMRs and CPOE.

During the last few years C-level suites have been entirely wiped out at some health care organizations. New executive teams decided that changing the CMIO reporting structure was a potential option. Today, government, business, boards and consumer pressure influence the physician roles. Boards and executive teams are panicking over the need to have CPOE, EMRs and complex clinical databases, with a corresponding demand for physician CIOs. Overly engineered organizational charts are the result, but will any over-hiring support the CMIO position and physician CIO?

Some executive teams have kept the current CIO and have hired a senior CIO. The concept of an "Office of the CIO" is gaining momentum. The Office of the CIO can include all of the senior IT leadership (the CIO, CMIO, chief technology officer and office of project management).

In many instances, the Office of the CIO is used extensively as an outsourced environment. Facilities are seriously considering hiring CIOs who are physicians. Those physician CIOs will need a strong operational support team outsourcing and/or creating a viable team by utilizing the Office of the CIO.

Hersher Associates, Ltd., conducted a survey of 246 facilities in November 2005. Of 100 respondents, 48 percent had hired a CMIO and 52 percent had not. In a similar Hersher Associates survey in 2001, 36 percent indicated having a CMIO and 59 percent had not hired a CMIO.

Those figures coincide with our national search assignment statistics. In 2001, Hersher Associates placed two CMIOs; in 2002 six CMIOs; in 2003 five CMIOs; and in 2004 six CMIOs. In 2005 Hersher Associates had completed or was engaged in ongoing searches for eight CMIO candidates.

Today, the demand is great for an experienced CMIO. What is driving the demand and what role should the third-iteration CMIO play?

Good for business

According to Tom Tintsman, MD, executive director for clinical information services at UCDavis Medical Center in Sacramento, Calif., "It is believed that the business boom of the 1990s was the result of automation increasing productivity in the United States. If one believes this, one believes that 'lubricating a process' using IT is good for business."

Tintsman said that health care speakers and writers casually accepted that the industry had not adopted process automation like other businesses. Imagine a businessperson sitting on a health care facility's board listening to that line of thinking. The board member would apply his/her personal business experience with information systems (IS) and ask IS to automate its processes. Health care management would agree that their processes should be automated but quickly add that automation is expensive and slow, and the risk of clinician resistance is high. The businessperson would persist and ask for a proposal to automate clinical care.

Tintsman continued, "To prepare such a proposal, large, high-level questions must be answered. What are we really attempting to do? Does it require new executive skills and knowledge? Should the organizational structure be changed? Automating the clinical care process is more expensive and challenging than building a new facility. The project changes everything and everyone in the organization. Changes of that magnitude must be supported by the board, sponsored by the CEO, and lead by the COO. The COO knows from experience the large risk of physician and/or nurse rejection. To mitigate that risk, the COO begins a search for a CMIO, not certain about reporting relationships, responsibilities or the EMR program process. Supporting this view in the last two years, we have seen reporting changes for both the CMIO and the CIO."

In order to accelerate new senior roles for physicians, we are beginning to see overly engineered organizational charts usually hiring skilled implementers. Some of the third-generation IT physicians have become disillusioned. If they work in complex health care delivery systems, their funding suddenly may disappear. If they work with a vendor or consulting firm, their roles are sometimes changed or eliminated.

It appears that the safest and most productive health care enterprise is on the delivery side for the physicians. One of the motivators for becoming a CMIO was to define and develop or install systems for delivery of patient care.

The majority of IT doctors have earned the right of passage so they can give 100 percent of their time and effort to their still relatively undefined job as they become key members of the executive teams.

Where from here?

The 2005 Hersher Associates, Ltd., survey shows a slight change in reporting structure.

Of the 48 respondents, 61 percent of the CMIOs report to the CIO, 20 percent report to the CEO and 8 percent report to the CMO. This is a clear shift reflecting some changes in responsibility mentioned earlier.

The following skills, attributes and areas of experience will support success for a clinician in an IT role:

�previous hands-on work in management, consulting, installation/project oversight;

�passion;

�ability to collaborate;

�leadership;

�ability to teach; and

�patience.

What are some of the common circumstances that can get in the way of an IT physician's success? Factors include:

�wrong job, wrong reason;

�no real authority;

�lack of managerial experience;

�lack of support;

�unrealistic or wrong expectations;

�few meaningful job descriptions.

How can a physician make himself or herself attractive to an organization, peers and the board? Consider the following:

�insist on management responsibility;

�budget responsibly;

�learn how politics work;

�attain or work toward an MBA;

�most import, cultivate the ability to explain technology-based business decisions to other stakeholders.

The continuing CMIO role

An increasing number of today's organizations see the need for CMIOs and vice presidents of quality and safety. Those roles are being filled by physicians. The hiring of physician CIOs is a trend receiving national attention in response to CPOE, EMRs and other significant issues and costly implementations. Significant new skills are needed for the CIO role, too. Physicians need to be careful to review the support systems available to manage their role. With IT clinical ambulatory and in-house implementation a scarce commodity, we perceive a potentially broader role for the CIO. This opens the door for other clinical leaders.

It appears that vendors are also seeing a renewed need for physicians to be available for a myriad of key responsibilities.

Arlene Anschel, senior vice president of Hersher Associates, who works with many CMIOs, said, "The marriage of the vendor and physician is one that provides a mutually beneficial working relationship. Vendors utilize systems physicians' expertise in sales, consulting, research and development, and education. Physicians who have minimal applied or operational experience can gain skills in implementations, consulting, project management and knowledge of software. Working in the vendor's client hospitals enables them to learn about clinical systems. They serve as consultants to the hospital physicians and provide education on the use of the vendor product. They become trained in a practical and hands-on way in the clinical systems arena."

Anschel continued, "Even if a physician has formal academic training, the vendor provides 'graduate school,' and prepares the physician for the next step into senior positions in health care delivery organizations. These can include CMIO, executive positions in information systems, senior roles in research and development, and even, perhaps, CIO.

The physician provides the vendor with a means to interact with clinicians and executives in their respective client organizations. Accordingly, the vendor can benefit from physicians who have good business and entrepreneurial skills. The physician and vendor serve as a resource for each other and create a win-win situation."

Nonetheless, physicians should exercise caution when reviewing the support and dollars available for any new position. An employment contract is essential to this relationship. Beware of taking a role that could become expendable in two years.

A technological management role

Most organizations have started or are actively planning to implement an EMR with CPOE. The CMIO is finally being recognized as an important role in many health care organizations. Some organizations are looking beyond the vendor implementation and asking how information systems can be used to improve the quality of care and the productivity of their clinicians. If organizations are struggling with the best structure, executive skill and knowledge for the implementation, adding those objectives will be even more challenging.

Once again, this raises the question of the CMIO's reporting structure and responsibilities.

Some new organizational charts show a potential partnership with the organization's current CIO. Based on our observations, the CIO's operational team reporting separately could cause havoc and project problems. Now that we have a large number of qualified CMIOs and more on the way, it is incumbent on the health care community to -understand that this is no longer an emerging role but one that is established and recognized as a key position.

Ms. Hersher is president and founder of Hersher Associates, Ltd., a Northbrook, Ill. executive search and consulting firm.

Editor's note: The author acknowledges the significant contributions to this article by Arlene Anschel, senior vice president of Hersher Associates, Ltd. and Tom Tintsman, MD, executive director for clinical information services at University of California Davis Medical Center in Sacramento.

Interested parties may contact :

Gary M. Levin MD, President, CIE, Clinical Information Exchange Tel: 951-530-1351; cell or SMS 951-746-9145

-

Happy Holidays to All

It's been some time since I last posted here. Busy season with other priorities have engulfed me.

I have been working on a white paper regarding the rise and role of the CMIO, Chief Medical Information Officer.  I have a deadline to post this before Christmas descends upon us.

Sunday, November 18, 2007

Recent Developments


Quote of the Day:
We are always getting ready to live, but never living.
--Ralph Waldo Emerson


 

Health Train Express has recently become acquainted with a Canadian solution to RHIOs search for the "ultimate" application for their interconnectivity needs.  It bypasses the problems of "governance issues" and the thorny issues of "who owns what".

Many of these issues ignore the primacy of information transfer, efficiency, accuracy, and quality of healthcare delivery in this country.  In addition to that concern, it is not necessary to re-invent a "wheel" that already exists.

What we need has been well established by many consortiums, RHIOs and health information exchanges.  Do we all need all of it? The answer is profoundly "NO".

What about those providers who do not have broadband internet connectivity?

There are many pieces in the mix for a RHIO or Health Information Exchange.  Some of these are already provided by proprietary systems, such as clinical laboratories, hospital portals, secure messaging systems, Hospital PAC systems,etc.

The California Regional Health Information Organization provides a well structured outline and roadmap for developing governance; and also a library,   HIE toolkit  of documents for RFIs, RFPs, and other essentials for vendors, hospitals, providers and IT departments.

Monday, November 12, 2007

SELF CERTIFICATION ???

Groups To Launch No-Cost EHR Interoperability Testing Software

A no-cost, open-source software tool for testing the interoperability of electronic health record systems will be available to vendors March 21, 2008, Government Health IT reports.
The tool, which is being jointly developed by the Certification Commission for Healthcare IT and Mitre, will allow vendors to ensure that their EHR systems can exchange information on patients treated by more than one provider.
The tool, called LAIKA, also will initially support testing of the Health Level 7/ASTM Continuity of Care Document, a core set of patient information including:

  • Name;
  • Address;
  • Health problems; and
  • Medications (Ferris, Government Health IT, 11/9).

Mark Leavitt, chair of CCHIT, said, "This project is an important first step in our journey toward testing and certifying the interoperability of health IT systems" (Merrill, Healthcare IT News, 11/9).
CCHIT and Mitre have undertaken this open-source project without government support, Government Health IT reports.
Developers will demonstrate the tool at the Feb. 12, 2008, CCHIT meeting (Government Health IT, 11/9).

Next Article Next Article

Readers are invited to send feedback to: ihb@chcf.org

Next Article

Sunday, November 11, 2007

RPM or Remote Patient Monitoring

Microsoft has launched it's Health Vault application.

With this announcement comes a large list of positive and negative reactions in the marketplace.  The most positive aspects are the "commodization" and accessibility of these devices to consumers at affordable prices.

 

RPM data can and should enter the consumer electronics mainstream.  In addition, RPM data should be viewed as just one more type of medical data, similar to lab data, pharmacy data, physician notes, etc., that is equally plug and play.

But...There are Tradeoffs

Depending on whether you are a user or a seller of RPM, you probably reacted differently when reading Bill Crounse's casual reference to devices and services becoming "commoditized".  Regardless of your reaction, he's right.  HV will hasten the already occurring commoditization of RPM devices.

When the RPM market started, many of the devices were priced in the $6-8 K range.  Today prices have dropped to $1-2 K, and will go lower. 

We have all heard stories where RPM devices eventually would become consumer purchases made at Best Buy and Circuit City, and that prices would be in the range of other consumer technology purchases.  That day will arrive in 2008 when Continua Alliance compliant offerings begin hitting the street.

The RPM market is moving from

  • High unit prices rooted in the industry's early focus on medical device markets and business models
  • Proprietary devices, proprietary IT,  non-interoperable data
  • Low unit volume, moderate margins per unit
  • Competition based on the vendor lock-in through high changing costs

To:

  • Low unit prices as the technology evolves toward consumer markets and consumer business models
  • Intereroperable devices, common IT platforms, and interoperable data
  • High unit volume, low margins per unit
  • Competition based on value and service

Where exactly commoditization and HV come together is not clear. The efforts of Continua will bring to market multi vendor interoperability, true plug and play connectivity. Microsoft can deliver plug and play interoperability with your personal computer, but little else.

 

What do you think?

Wednesday, October 17, 2007

Economic Advantage????

This news from iHealthbeat:

Do we have a choice about EHR?

 

October 17, 2007

Boston Health Network Requires All Physicians To Adopt EHRs by 2009

Partners HealthCare System in Boston is requiring all of the physicians in its network to adopt or agree to adopt electronic health records by Jan. 1, 2008, or else they will be removed from the network, Tom Lee, CEO of Partners Community HealthCare, said, Modern Healthcare reports.
Partners expects to lose between 15 and 20 primary care physicians this year because of the mandate, and it could lose some patients if those physicians stop referring patients to Partners hospitals, Lee said.
To retain their network status, about 5,000 physicians in the network will be required to adopt either Partners' or GE Healthcare's EHR or sign an agreement that they will adopt EHRs during 2008. However, by Jan. 1, 2009, any physician without a connection to the network EHR system will be removed from the network.
Mario Motta, a cardiologist in the network, said the mandate is a "two-edged sword" because the benefit of EHRs is higher reimbursement rates from insurers, although Partners is not providing any funds to help physicians adopt the systems.
Lee added that funds are available to improve Partners' EHR system and to train physicians on it (DerGurahian, Modern Healthcare, 10/15).

Thursday, October 4, 2007

Microsoft Health Vault

from iHealthbeat,

"Microsoft has launched its HealthVault program, which offers consumers online personal health records. The company hopes that individuals will let health care providers directly transmit prescriptions, test results and other medical information to their HealthVault accounts. PHRs will be stored in a secure, encrypted database, and patients will be able to set the privacy controls"

Seeing this post I raced to find the "Vault"... First of all, it is complicated to set up, requiring a download of the basic program, and then and number of "connect" interfaces.  It is not designed for patients to enter their medical history, so it is not a true PHR, or personal health record. In addition, the patient must download a number of drivers for "devices".. These devices, so far include

"Healthy Circles", icePHR (In Case of Emergency),  these also interface with a blood pressure transduce, glucometer, spirometer,

There are several other websites one must go to to setup, enter, and read the data. Microsoft has developed a number of  "partners", which I will not mention here, just advise the reader to go to www.healthvault.com  Microsoft also has an interconnect program called "connect IQ", a portal that almost looks like a HIE, or RHIO.

For the patient, especially an elderly patient this will be difficult to setup, and use.  It will require a nurse or technical assistant to set it up and make it operational.  There will also be considerable expenses for the remote monitors.  The site also states that providers will be able to transfer medical records to the PHR as well. If all of this can be managed it does develop some slick looking tables and graphs of blood pressures, glucose levels,pulmonary function tests, and probably eventually a probe that will report CBCs and blood chemistries.....all from home.

The big question is will payors reimburse for all of this...Will this become part of P4P ?

This is not a patient oriented design.  Even for me it was a long pathway to download and figure it all out.  Setting up the actual vault took some time to complete, and then it was still an empty shell.  But then again I am only a doctor......more later....

Tuesday, October 2, 2007

The "Monkey on your Back"

I think one of the issues most providers are grappling with in regard to HIT and EMRs in their office is not only the initial investment of capital, but the ongoing "relationship" between the practice and the vendor(s).  Will you have a "tiger by the tail?"

The daily operation of the practice will be entirely dependent upon your PMS and/or EMR system. Witness the recent "crash" of the entire West Coast VA CPRS system. A recent iHealthbeat article quoted that it was the worst incident effecting quality and safety of care in the VA system.

The vendors have their "business model" for profitability, and they are not about to let providers interfere with that fact.

Keep in mind we are in the early phase of EMR and  HIT "buildout"

There will initially be a "bubble" as providers invest in EHRs, RHIOS, etc  Eventually the acquisition rate will flatten out. With diminishing returns will the vendors jack up maintenance contracts and costs for updates.

About 18 months ago Allscripts began offering a  "free eRx system which operates as a portal application. It is necessary to enter patient information in the system the first time it is used for a new patient.  Allscripts now offers "a bridge" to connect it to your PMS. They don't say much about interfaces for  EMRs.  Most of the interfaces cost about 300 dollars initially and 240 dollars each year afterward.  One interface was quoted at 695 dollars. There  are  many with "custom" as the interface quote.  Now I can see an upfront charge for an interface, but an annual charge is something else, unless there are some other changes in software after the initial installation. (sounds like Microsoft)...Windows "Live". I wonder what the rest of you thinks about this?

Monday, October 1, 2007

Whose Network is it, Anyway??

The San Francisco Chronicle featured an article highlighting Health 2.0 and the wave of consumer (patient) oriented web sites.

DailyStrength.org people can choose among 500 support groups - from celiac disease to pulmonary fibrosis - create an online journal to chronicle their disease and send electronic hugs to other members.

ZocDoc.com lets patients book physician and dentist appointments online, similar to the way OpenTable.com allows diners to make online reservations for restaurants

RateMDs.com takes a page from consumer rating sites like Yelp and RateMyTeachers.com - a popular site that allows students to "grade" teachers and administrators - by allowing patients to anonymously praise or pan their doctors.

Dubbed the YouTube of health care, ICYou.com allows patients to share their stories through online video clips.

Other Web sites, such as PatientsLikeMe, offer people battling devastating diseases the ability to discuss and track in great detail the treatment options other patients in their disease group are trying.

OrganizedWisdom.com: Aligns doctor-reviewed and user-generated health content to help people make decisions.

ReliefInSite.comRelief in Site. com: Helps patients record and track their pain and medications and share it with their doctors, nurses, pain specialists, therapists, friends and family members

And I like this one the best:

NursesRateDoctors.com: Recruits nurses to give their candid assessment of doctors........for the surgeons who throw instruments.....

It seems Health Information Networks are developing in ways which we could not imagine.

 

Today  I came across a focused PHR solution for Lasik surgeons. Safeguard your Sight

Many times patients undergo refractive surgery on their eyes, and require enhancements or cataract surgery at a later date. Often times it is with a different ophthalmologist and the prior records are unavailable.  Ophthalmologists are able to upload their "data" before surgery, and after surgery. The data resides on a server. Patients can access this information for a fee and give the results to the new surgeon. 

Friday, September 28, 2007

Featured Interview

This week I had an unplanned interview with Heather McGuire of Within3.   It started out for me as a "show and tell" regarding RHIO development and my "new" self sustaining business model, which frankly still is not a proven model.  Heather reciprocated and introduced me to  Within3. The site is based upon social networking of research scientists and clinicians. In order to gain access one must be recommended by a peer.  Members are thoroughly vetted to be listed on their site.  You can see their site by clicking on Within3 above.  The site has a search function as well.  You can search by disease and it will take you to a number of authorities on the subject, not only that but it will search Pubmed and bring up their articles as well under their name. The site also has their curriculum vita and other interesting things about that person.  There is much more to the site, but I will point you in that direction to find out for yourself.  It is still in early beta....but the concept seems exciting.  If successful, this will continue the revolution in search methodology.

Thursday, September 27, 2007

Part II - Science of Spread Change

I left off last time.....

Sarah Fraser is a consultant to health care organizations in the U.K. She points out "that innovators are not normal people, and look for and enjoy change, while most people are wary of change. " For this reason innovators are poor messengers for spread change. The majority of the people are those that hold the organizaton together, go to work at 7AM and not to a conference. They care for patients from day-to-day. If innovators cast aspersions on this group, then spread change is dead. Spreading innovation must also reduce costs, and there must be a return on investment for the organization that is making change. The organization (or stakeholder) must see financial gain for adopting the "new thing".

The article (which I highly recommend to IT people, vendors, RHIO developers and the like) goes on to discuss

Pilotitis
Low Hanging Fruit Syndrome
Unworkable Universal Solutions
The fallacy of the "tipping point"
Accepting Roger's categorizations of people, ie early, late, laggards
Spreading improvement requires continuous measurement
Without leaders....there is nothing
Implement good ideas is better than spreading good practices

I highly recommend this monograph which can be found at:
http://www.chcf.org/documents/chronicdisease/TheScienceOfSpread.pdf

Tuesday, September 25, 2007

The Science of Spread


Quote of the Day:
Resentment is like taking poison and hoping the other person dies.
--St. Augustine

 

Batten down the hatches....this post is going to be rather long, not a sound byte.  Thomas Bodenheimer  M.D.wrote for the California Health Care Foundation a treatise on this subject which bears reexamination at this juncture in the development of Health IT and the proposed NHIN. Dr Bodenheimer is on the faculty at UCSF.

He summarizes the literature on "spread theory" by Everett Rogers (1962), and Malcom Gladwell's "Tipping Point" . Paul Plesk cites Rogers and Gladwell "to argue that once 10-20% of the target population has adopted an innovation the tipping point has been reached."  Plesk than goes on to discuss "stages of change", "precontemplation", contemplation and action, followed by maintenance.

It can be said that EMRs and RHIOs, and NHIN are in all phases of Plesk's analysis of "Spreading Good Ideas for Better Health Care"

He offers several tools that might help improvement champions that analyze the systems and individuals that make up the spread target population....more later

Sunday, September 23, 2007

Health 2.0 Conference Results

Three years ago I had no idea how blogging would provide a platform for everyone and anyone interested in health care. The spectrum of participants ranges from physicians, payors, patients, political pundits, and others.
This forum lies outside the framework of "officialdom"; It has become the water cooler and allows much intercourse. Early on there were some disputes and "retaliation" against employees when their opinions reached "management".....However I believe freedom of speech issues prevailed as long as there was no libel or slander involved.

This year's Health 2.0 was planned for 200 participants, and over 400 registered. The introduction piece was very impressive. I am providing the link here. Health 2.0 Intro-http://www.icyou.com/events/health-2-0-conference?folder=All

The video by scribemedia was truly impressive: http://www.scribemedia.org/2007/09/20/health-20-conference/


While most reporters waxed on enthusiastically, the San Jose Mercury News threw some cold water on Health 2.0, most of which was unwarranted. They criticized health 2.0 and the blogs as not being well grounded in 'business models'. While some blogs do generate revenue, most proponents of health 2.0 blogs or health blogs in general did not nor want to have a rigid business model....I am also sure some will develop entrepeneurial motives or at least there blogs will network them into "greener" pastures.

I also think that unrecognized is the fact that Web 2.0 applicatons are rapidly being deployed for EMRs, Practice management systems, and other applications for healthcare. These applications do away with the heavy cost of capitalizing for hardware, ie servers, etc. A monthly subscription fee covers maintenance, upgrades, and technical support.

Without a doubt the environment of health blogging is one of free speech, enthusiasm, and just plain "glory" at seeing one's words printed on the world wide web. It is a great "equalizer."

Saturday, September 22, 2007

Alternate Road to Health Information Exchange

Saturday, September 22, 2007

Roadmap (Alternate) to Health Information Exchanges
RHIO and HIE development is a highly complex undertaking and not for the weak of heart. As I was driving into Los Angeles the other morning I encountered one of the routine "sigalerts". For those of you who have never been in California and live in a rural area I will explain this is a system of alerts from the Callifornia Transit Authority whereby notifications are sent out by television, radio and internet about blocks in traffic due to "events" such as accidents, toxic waste, police activities, construction activites, etc. Recently my oldest son, who has rapidly passed me by in the world of high tech (he has smaller thumbs than I do) and I were in the car together and as we bogged down and did not move for several minutes, the GPS asked if we wanted to plot an alternate route, and suggested about five different ways around the thrombosed artery.
I believe that the current roadmap is flawed as designed and hoped for by several agencies with good intent. Our Health Train Express is now in a "sigalert status" The problems with "roadmap" is that requires funding from unknown or difficult and confounding sources such as grant making organizations ranging from county to state and federal and combinations thereof. Often times these grants are tied to the momentary "political expediency" of the moment, ie, Katrina, Homeland Security, Bioterrorism, and even "Global Warming"
Often and most of the time it is totally dependent on the whim of the moment of legislatures both federal and state, impacted by competing budgetary priorities of peace and war. education, immigration issues, and more.
The "road not taken" as Robert Frost so aptly stated requires a minimalist approach with obtainable goals that step through the process. Rather than swallowing the whole cow, we must take small bites, chew an digest each piece individually. This rather graphic and seemingly unrelated metaphor sums up a new roadmap.
It is difficult for providers and hospitals to grasp the RHIO concept because it is rather like dropping an Atom Bomb. It overwhelms most executives who are fully engrossed in just running their institutions on a day to day basis.
Developing one functionality that would maximize a return on investment in one area as a demonstration without disruptive technology gives an HIE a "foot in the door" When a user (provider or hospital) subscribes to this service for a relatively small sum the revenues derived and create cash flow for the HIE as a revenue cycle. The single functionality must demonstrate it's own cost effectiveness and ROI in less than one month. It must be demonstrated as successful in a regional pilot program. It must be self funding, elective and non binding without contractual obligation, and also offered as a 30 day free trial........more later

Thursday, September 20, 2007

The view from Here

Just a reminder to take a look at my "parallel blog" at http://anyviewfromhere.blogspot.com

Saturday, September 15, 2007

Health Train Express is Slowing Down

As I travel on the health train express I have noticed the "local trains" which are stopping along the way at each station. Of course I am on the express track, or the high occupancy vehicle lane. In my 'rush' to reach my destination I am missing a lot of interesting places.

I may be posting less here and if you miss my meanderings you may find me at my new blog,
The View from Here (http://anyviewfromhere.blogspot.com/ It seemed apropos for a name for an ophthalmologist's commentary about matters of "great significance"

For those of you going to Health 2.0 enjoy!!

And thank you to Dimitriy for his great expose on Google....

Sunday, September 9, 2007

Saturday, September 8, 2007

Roadmap (Alternate) to RHIO and HIE

 

RHIO and HIE development is a highly complex undertaking and not for the weak of heart.  As I was driving into Los Angeles the other morning I encountered one of the routine "sigalerts". For those of you who have never been in California and live in a rural area I will explain this is a system of alerts from the Callifornia Transit Authority whereby notifications are sent out by television, radio and internet about blocks in traffic due to "events" such as accidents, toxic waste, police activities, construction activites, etc.  Recently my oldest son, who has rapidly  passed me by in the world of high tech (he has smaller thumbs than I do) and I were in the car together and as we bogged down and did not move for several minutes, the GPS asked if we wanted to plot an alternate route, and suggested about five different ways around the thrombosed artery.

I believe that the current roadmap is flawed as designed and hoped for by several agencies with good intent.  Our Health Train Express is now in a "sigalert status" The problems with  "roadmap" is that requires funding from unknown or difficult and confounding sources such as grant making  organizations ranging from county to state and federal and combinations thereof.  Often times these grants are tied to the momentary "political expediency" of the moment, ie, Katrina, Homeland Security, Bioterrorism, and even "Global Warming"

Often and most of the time it is totally  dependent on the whim of the moment of legislatures both federal and state, impacted by competing budgetary priorities of peace and war. education, immigration issues, and more.

The   "road not taken" as Robert Frost so aptly stated requires a minimalist approach with obtainable goals that step through the process.  Rather than swallowing the whole cow,  we must take small bites, chew an digest each piece individually.  This rather graphic and seemingly unrelated metaphor sums up a new roadmap.

It is difficult for providers and hospitals to grasp the RHIO concept because it is rather like dropping an Atom Bomb. It overwhelms most executives who are fully engrossed in just running their institutions on a day to day basis.

Developing one functionality that would maximize a return on investment in one area as a demonstration without disruptive technology gives an HIE a "foot in the door"  When a  user (provider or hospital) subscribes to this service for a relatively small sum the revenues derived and create cash flow for the HIE as a revenue cycle. The single functionality must demonstrate it's own cost effectiveness and ROI in less than one month.  It must be demonstrated as successful in a regional pilot program.  It must be self funding, elective and non binding without contractual obligation, and also offered as a 30 day free trial.

More on this later........

Saturday, September 1, 2007

Surfing on the Labor Day Weekend

The long labor day weekend is upon us all. I plan to spend mine with my feet up, and with a cold drink sightseeing on the hot sands of the Southern California beach.  I even invested in a cell card, so I can now find the internet whether I am floating on my raft, in a dark hole, in a green swamp, or whatever. I realize I am surrounded by   the "can you hear me now" guy and the helicopter flying overhead (Verizon).

As far as health information exchange goes, this weekend, my network is down....

Thursday, August 30, 2007

The Caboose

I suppose the health train express should not have a caboose because that implies the end of the train. However I missed an important addendum from Mike Leavitt's blog which he writes as he travels through Africa, attempting to analyze Africa's challenges, clinical overload, a far cry from the paperwork overload providers face in our country. Mike makes some comments about HIE and RHIOs, the subject of which motivate my original blog. The post which follows here is an important link for you to understand what has been done and what will take place over the next five years. Don't miss the TRAIN !!!

http://www.hhs.gov/healthit/community/background/

from Mike Leavitt's blog:

"Today we had an important meeting at HHS related to electronic medical record standards. The development of standards for interoperable health information systems is one of my most significant goals. I believe the standards required to make this electronic medical records system work have to be collaboratively developed among various stakeholders. About two years ago we created the American Health Information Community for that purpose. Rather than try to write much about it I will ask one of my colleagues to insert a link here to the AHIC website: http://www.hhs.gov/healthit/community/background/
People have been talking about interoperable systems for years but the standards to make them work haven’t materialized. So, those who invest in electronic health records are isolated. Many others put investment off, waiting until the systems mature.
This is an extraordinarily complex problem but the biggest challenges aren’t technological; they’re sociological, i.e. conflicting economic interests and turf. AHIC has successfully created a place and process to sort through them in an orderly way. We are starting to make serious progress which you can read about on the website.
Our plan from the beginning has been to get the standards development process started inside the government and then once it is functioning create a non-profit entity that operates under a highly democratic governance system so the progress can be accelerated and perpetuated. I call the transition moving from AHIC 1.0 to AHIC 2.0.
The government will have to be the biggest participant in the process, but to get these things right, the entire health sector has to be at the table in a meaningful way. The federal government will not only be the biggest participant but we have also committed to use the standards developed there. The President signed an Executive Order last August making clear that all the federal agencies, including Medicare, Medicaid, the Veterans Administration, and Department of Defense etc. will adopt the standards. We need to insist those we pay do the same thing, over time.
Today we held a meeting with interested people and organizations to invite their help in creating the non-profit entity and its governance.
The last several years I have become rather interested in collaboration as a large scale problem solving tool. I’m persuaded skillful organization of collaborations is a 21st century skill set. It is a close cousin to network theory. In fact, I think collaboration is the sociology of network building.
Our world is intuitively organizing itself into networks. Networks require standards to operate. The skills to navigate the creation and governance of networks constitute the next frontier of human productivity. Organizations and societies that learn to solve complex problems using these skills will begin to out pace their competitors.
The development of AHIC 2.0 is a significant venture. I’m optimistic it can produce a vitally important institution but it will require our best statesmanship to overcome the natural tension of competing economic interests and turf.
If readers have a chance to look through the AHIC website, I’d be interested to hear your thoughts."

Wednesday, August 29, 2007

Hot Weather and HotTopics

Stop, don't click away just because you think you have arrived at the wrong site. As I promised there were going to be some fresh changes at Health Train Express. Not only has Elvis left the building, but so too has Health Train Express.

Every summer at this time of August I mention how fast the summer has gone by. Well, just when I think it's over...it's not. The forecast for the next week is 100-107 degrees. As Yogi Berra has said "It ain't over until it's over".



So too is my forecast about P4P, RHIOs, and EMRs. No one can easily predict the outcomes in this arena. However it certainly fuels entrepeneurial minded providers, third party administrators and a variety of industry vendors into a fury of Category 5 storms.



One of my favorite blogs is that of Phillipa Kenneally, The Entrepeneurial MD. She regularly hosts podcast interviews at her site, which can be found at http://trusted.md/ Her guests are often "out of the box" innovators with examples of where many physicians go when they are not seeing patients.



Richard Reece's blog, medinnovation now has a link on my site . This retired pathologist living along the banks of Long Island Sound will give you much food for thought from his experiences and knowledge base of 30 years of clinical pathology experience, much of which has nothing to do with looking through a microscope.



We will be taking a two week break until after Labor Day, when we will return to continue our new "look" to our blog.

Tuesday, August 28, 2007

Transitions

Fellow bloggers:

When I first began “blogging” about three years ago I intended it to be a newsletter for a RHIO that I was heading up in my area of the country. About a year ago I chose to rename it “Healthtrain Express”. The term recently coined by others came to my mind in 1989 (that definitely dates me) It was in the pre-DRG, pre RVU, pre managed care (ie, the “golden days”) that my residents often wistfully mention..
I often tell them that no “age in medicine” is trouble free. It’s the nature of the “beast”.

Healthtrain express conjures up the rapid changes that constantly occur in medicine. For those of you who have read “Future Shock “ by Alvin Tofler , this has always applied to medicine. I highly recommend this reading.

It also denotes a vehicle with a tremendous amount of inertia, barreling down a “track” . If you are on the track you had better be moving fast enough to stay ahead of the train. If you are stationery, then you must either move aside or be “smashed”.

Returning to more specifics of our “age in medicine” we see the predictions and evolution of pay for performance and reporting, health information technology, the methodology of reimbursement change, including CMS intention to not reimburse for “poor outcomes” or those due to “poor care”. Medicine will continue to be increasingly directed by third parties, consumers, and political and social planners. Most of whom have never treated a patient. This one issue frustrates most physicians, although it has become a fait acompli, I know it continues to “gall” most doctors.

Physician-hospital relations continue to be in a state of flux. Gone forever in most areas is the leadership of the medical staff as it pertains to the board of directors, or trustees of the hospitals. In some rural areas this may remain intact, unless the hospital is part of a larger financial “holding company”. Creative financing has allowed many hospitals to continue operations with “leaseback arrangements” for management, and other issues.

Looming on the horizon is radical change in hospital accreditation organizations.
The JCAH authority is about to be undermined by pending legislation and some hospitals chose to use alternative accreditation sources This may or may not be a good thing, given that operating requirements have radically changed for hospitals.

For those of my readers you may notice on the sidebar the expansion of medically related blogs. Over the next month this list will be expanded. This is going to involve a significant amount of my time selecting and moderating my personal favorites.

I am also extending a personal invitation for co-authors to contribute to “healthtrain express”. Please email me if you wish to do so. email gmlevinmd@gmail.com

GML

Sunday, August 19, 2007

Change in Direction

For the past three years I have been beating the drum about the development of HIE and RHIOs. I have not come to any final conclusions about the destiny of this "visionary" prospect. There are a great deal of positives and negatives regarding HIE and EMRs.
I will deal with some of the negatives first.

1. Most providers complain about the complexity and bureaucracy of practicing medicine, in regard to regulatory requirements, the hurdles of reimbursement, and exponential increases in business overhead.
2. The burden of Health IT may outweigh the benefits.
3. HIT is very expensive
4. Automation and the impersonal nature of IT does not really fit in to the paradigm of medical care. Despite patient enthusiasm for all things technical most providers are reluctant to introduce an infrastructure that will make them dependent on third parties.
5. Most physician providers operate on the basis of accountability, reliability, and a one on one relationship with each patient. IT is not going to improve the patient relationship.
6. Medical care has always been a unique portion of our economy, and recently outside forces have forced change, some good, and some very detrimental to patient care.

Positive:
1. The introduction of web 2.0 has greatly expanded patient education, and allows patients to ask more relevant questions.
2. Web 2,0 also introduces transparency and allow for "error checking" on the part of patients
3. Web 2.0 also increases the providers outreach for reliable information instantly at the point of care.
4. Most providers who have installed EMR speak positively about having it, and "would not go back to the old system" (my comments are that they could not even if they wanted to, because of their heavy investment in the system.

That's my meager summary after three years, it is not all inclusive.

Beginning next week Health Train Express will change direction. Look for a change in content first, then a change in the front end. I hope to maintain the title "Health Train Express" however our domain name may change.

Friday, August 17, 2007

Mike Leavitt Sec HHS joins blogger world

HHS Secretary Leavitt Launches Blog To Boost Health Care Discussion
HHS Secretary Mike Leavitt this week launched a blog to foster public discussion and exchange ideas on health care issues, The Hill reports."If I can do it justice, we will continue," Leavitt said, adding, "If not -- we won't." Leavitt, who plans to write all his blog entries himself and read "as many of the comments as time allows," said he will "wade in a little deeper into blogdom" this month.Unlike some blogs, all comments will be screened prior to being posted, The Hill reports.One day after his first blog posting, Leavitt already had received more than a dozen comments, including one that had to be removed because it was inappropriate or offensive, according to a spokesperson (Retter, The Hill, 8/15).

Tuesday, July 31, 2007

News from Rhode Island

Providence, RI —July 30, 2007—Rhode Island is now one step closer to implementing a health information system that will allow physicians, with their patient’s permission, to access important patient health data from a variety of sources when and where it is needed. The State has chosen Electronic Data Systems Corporation (EDS), and its subcontractor InterSystems Corporation, to build and integrate the necessary technology and software.
National and local efforts have been underway for the last several years to computerize medical records and develop secure methods to share records electronically. Governor Carcieri has prioritized making health information electronic for the majority of Rhode Islanders by 2010. “Anywhere, Anytime Health Care Information” is one of five elements that make up the Governor’s health care agenda.
“We can now begin the important work of building a secure Health Information Exchange, which will result in a more cost-effective health care system by reducing unnecessary tests and potential medical errors,” said Governor Carcieri.
The Rhode Island Department of Health (HEALTH), working closely with community partners, providers, and other key stakeholders, will oversee the development of this interconnected, interoperable system. HEALTH has engaged a wide range of consumer advocacy groups, health care attorneys, and others to ensure the system protects patients’ privacy and addresses the needs of both health care consumers and clinicians.
“With the creation of a statewide Health Information Exchange, doctors will be able to look up their patient’s critical health information, giving them a more complete understanding of their patients and allowing them to provide higher quality, safer, more coordinated care,” said Director of Health, David R.Gifford, MD, MPH.
Following an RFP process, HEALTH selected EDS as the technical vendor to build the system’s technology. EDS will subcontract with InterSystems Corporation for its HealthShare software. Through a three year, federally funded, $1.71 million dollar contract, EDS and InterSystems will build the core components of the system, including giving authorized health care providers access to comprehensive lab results and medication history for their patients. Initially these data will come from Lifespan, East Side Clinical Labs, the Department of Health State Laboratories, and SureScripts (a national company that administers the network connecting physician offices and pharmacies for e-prescribing). During the course of the contract, the system may be enhanced to include additional data sources and types.
EDS is a leading global technology services company, with a local office in Warwick. The company has extensive experience working for the State of Rhode Island, such as serving as Medicaid’s fiscal agent. For more information about EDS, visit www.eds.com
InterSystems Corporation, a software company headquartered in Cambridge, Massachusetts, provides software for connecting healthcare information. For more information about InterSystems Corporation, visit www.Intersystems.com.
Editorial Contact:

Sunday, July 29, 2007

One Step Forward Two steps Back

Report: Health IT Bills Will Not Affect U.S. Health Care
Congressional measures to boost health IT adoption would not go far enough to make a significant difference in U.S. health care, according to a Commonwealth Fund report released Thursday, Government Health IT reports.The report, which analyzed major health IT and other health-related bills introduced between 2005 and 2007, found that none of the bills "would commit the funds and central leadership required to realize the potential benefits of a health information system.""There's just not enough funding to get us to a paperless health system in five to 10 years, in my judgment," Commonwealth Fund President Karen Davis said, adding, "If the U.S. is to close the health information technology gap with other leading countries, it will need a strategy and commitment of requisite funds to achieve its promise."Davis said the federal government should subsidize health IT adoption for safety-net providers and the development of regional health information organizations. "The basic problem (with the legislation) is that giving small amounts of money -- compared to the $3 trillion in U.S. health care spending -- and setting standards is not going to be enough to accelerate the adoption of health IT," she said.Davis said the report's findings are applicable to the Wired for Health Quality Act of 2007.The bipartisan Wired for Health Care Quality Act of 2007 has won committee approval and is awaiting action from the full Senate. There is not yet a companion House bill, but Rep. Patrick Kennedy (D-R.I.) is planning to introduce a comprehensive health IT bill after Labor Day, according to his policy aide, Michael Zamore (Ferris, Government Health IT, 7/26).

Despite this bleak appraisal of federal mandates and lack of follow through we see progress in private entrepenurial ventures to fund HIE. Local initiatives and buy in by stakeholders remains the elemental ingredient for success. One has only to look at the success of Healthbridge in Ohio, which has been operational for almost a decade. The key ingredient is focus and dedication by those involved over the long term.

Thursday, July 26, 2007

Monday, July 16, 2007

The Train Coming Down the Track

Is your information technology structure from the ‘90s? 1890??

In the next five years we will see a catalytic innovation take hold, and I don’t just mean electronic medical records, personal health records, or web 2.0 applications.
In the past several months we have seen several states release morbidity and mortality statistics from hospitals performing certain procedures. Most of these were selected based upon their high per capita cost. The figures are prominently announced and displayed on easily found web sites. This of course is quite controversial and is resulting in angst of both hospital administrators and physicians alike. Payers want the most “bang” for their “bucks”, that is to say the best possible outcomes for beneficiaries. (i.e., they are not going to pay for “bad results”.
Providers and hospitals have seen this coming for quite some time, but the impact of seeing this data displayed publicly is immeasurable. For those providers and hospitals on the top tier, this gives them a significant advantage when contract talks begin.
Internal quality assurance, outcome measurements and daily updates will be necessary to stay even with
Change management is one key for successful transition to healthcare 2.0. The significance of the paradigm shift in the early 1990s is not lost on health care institutions or the establishment of the RVU for determining reimbursements for services by providers. The lag in understanding the “strategic” shifts which occurred then caused thousands of practice business failures and also hospital shut downs. Even the sea-change of practice management firms could not stave off bankruptcy and/or operational demise. The drive toward multiple levels of management, i.e., IPA, MSO, and HMO with all it’s subsets of responsibility between patient, provider and hospital serves as a rationing method. The new system will not allow for this paradigm.

Consumer advocacy groups have arisen, and are and will be playing significant roles in “health change”.

Perhaps California was the “poster child” for bad things, the emigration of thousands of providers to other states, the cacophony of IPA closures, health plan demise, and the changing nameplates of groups, hospitals and others in the health industry.
It is a fairly simple analysis. (The have’s and the have not’s) The have not’s will not be providing health care in five years.

Not only will having EMR be critical but also additional systems that will enable chronic disease management by “remote control’ and telemedicine. Leveraging the capability of the medical staff to care for SNF patients, and at home chronic patients will enable providers. Payers must come to terms with reimbursements for these modalities, since the ultimate outcome will be to reduce hospital in patient and readmissions as well as needless office calls. Remote telemedicine is here with devices that can provide audio visual contact using dial up technology. Remote sensing of BP, Pulse, and Glucometers is already available, and many more are in development. Other peripheral include the Prothrombin time Micro coagulation System, telephonic stethoscope, digital scale, and pulse oximeter.

Payers have been reluctant to share in the development costs of these systems. Change management must analyze the short term ROI, rather than long term ROIs. Most businesses want to see results in three months ( a business quarter).Successful transition therefore will require carefully focused change implementation in limited areas and progress as each gains ROI. (Randy Moore, American Telehealthcare)

Saturday, July 14, 2007

Reality Check

I recently navigated over to the "TOP 100 HEALTHCARE BLOGS" ranking, and found that my blog was down in the 300s. The top 3 were "Random Acts of Reality" "Medgadget" and "Bad Science"
I also noted that technorati seemed to play a significant role in popularity of the "winners"

In the past I have written a great deal about health information exchange and RHIOs. From what I learned in the past three years I have altered my course and given up on the idea of "warp speed" and will depend upon "Impulse engines".

There certainly appears to be no impuslivity as it pertains to EMRs nor HIEs.

I sent out letters this past week regarding the "NEW PLAN" to bring EMR and HIE to our region of Southern California. Today is a clear day and I can look out over most of it and see all the way from Mt Wilson to Mt San Gorgonio and San Jacinto. As an aviator I can say
"CAVU". A properly paced mirror or antenna on anyone of these peaks would serve as a "beacon" for the hub of a health information exchange. If TV and Radio stations can do that then why not health information? Would this be a "disruptive technology" or a "catalytic innovation"

Funding seems to be a barrier to implementation of EMR and HIE. Why not an excise tax like the 911 excise tax on phone bills to provide emergency services? Certainly health care is important enough to our society that there lies a real basis for this to fund EMR and health IT. It spreads out the fiancial support to almost everyone evenly.

For those of you in our local region who read this I hope you will respond to my letter and email regarding the HHS grant for HIE. Hopefully your administrative assistant did not file it in the round file. Personally I tire of the voicemail trees and the voicemail...

On another note. one of my colleagues wanted to test the capacity of his servers. He posted a comment about "Daniel Radcliffe Naked". Within one day Google had picked up this post and his site hits went up by 10000 hits/day.

The name of my new post shall be "Daniel Radcliffe Naked" in the Health Information Age.
BTW for those of you over age 40 Daniel is the actor who plays Harry Potter.

From the desert to the sea

Your willing sevant.

Tuesday, July 3, 2007

Google me

Google Health (GH) could be the event of the decade in advancing health care reform — not just healthcare information technology (HIT) reform,
The "ultimate" PHR????
Google Health (GH) could be the event of the decade in advancing health care reform — not just healthcare information technology (HIT) reform, but health care system reform. GH promises simultaneously to create AND dominate the market for next generation personal health records (PHRs). There is nothing else in our solar system or in the entire universe like it.
II. GH’s Anticipated Technology Model
We’ve been provided a number of clues about the technology model that GH is likely to develop:
Patient centric
A personal health URL
Automated data mechanisms to gather and store PHI
Interoperable technical standards: XML and the Continuity of Care Record (CCR) standard
A user interface
Appropriate security and confidentiality measures
Value added functionality (over time)
What do you think???

Sunday, June 24, 2007

THE GLOSSARY

My apologies for the delay in getting this posted. It is a rather long one, but contains a lof of information for "newbies" I suggest you copy and paste it into a word document.....then if you have google desktop you can search for "glossary".


GLOSSARY


Access:
The process of obtaining data from, or placing into a computer system or storage device. It refers to such actions by any individual or entity who has the appropriate authorization for such actions.
American National Standards Institute (ANSI):
ANSI is a broad based agency charged with overseeing voluntary standards development for everything from computers to household products. ANSI accredits standards development organizations (SDO) based on their consensus process, then reviews and officially approves the SDO recommendations.

American Society for Testing and Materials (ASTM):
American Society for Testing and Materials develops standards on characteristics and performance of materials, products, systems, and services. There are numerous standards-writing technical committees. E31 is the Committee on Computerized Systems and E31.28 is the subcommittee on Healthcare Informatics responsible for the Continuity of Care (CCR) standard.
Annual Support & Maintenance:
Costs that are typically 15-20% of the software license costs. Where the actual license is normally a one- time fee, the support and maintenance costs are renewed on a yearly basis. This yearly fee basically covers two areas: 1) any upgrades or new releases; and 2) customer service and support. It should be noted that both vendor EHR software and third party software will need support, so it is important to determine which components the support costs cover. Also, some vendors might have more than one service level agreement representing different support options at different costs.
Architecture:
The orderly arrangement of parts; structure.

ASTM:
See American Society for Testing and Materials.
Asymmetric Key System:
A system that uses different keys for encryption and decryption. Within such a system, it is computationally infeasible to determine the decryption key (which is kept private) from the encryption key (which is made publicly available).
Attribute:

A characteristic or property.

Audit trail:
Chronological record of system activity which enables the reconstruction of information regarding the creation, distribution, modification, and deletion of data.

Authentication:
Verification of the identity of a person or process.
Authorization: The role or set of permissions for information system activity assigned to an individual.

Biometric Authentication Technology:
Technology that uses some human biological feature (e.g. fingerprint, voice pattern, retina scan, or signature dynamics) to uniquely identify an individual.

CA (certification authority):
The entity providing third party trust within PKI.
Certification/Conformance Testing: Testing a product for the existence of specific features, functions, or characteristics required by a standard in order to determine the extent to which that product satisfies the standard requirements.

Chief Complaint Mapper: A software product that maps chief complaints, captured as text, and transforms them into useful digital data that can be used in functions such as public health outbreak surveillance.
Clinical Classification:
A method of grouping clinical concepts in order to represent classes that support the generation of indicators of health status and health statistics.
Clinical Data Repository: The data warehouse that contains clinical data (HL7 messages) centrally.
Clinical Messaging:
The communication among providers involved in the care process that can range from real time communication (for example, fulfillment of an injection while the patient is in the exam room), to asynchronous communication (for example, consult reports between physicians). Reference: Health Level Seven, Inc.
"HL7 EHR-S Functional Model and Standard." July 2004. http://www.hl7.org/ehr/downloads/index.asp)
Clinical Messaging #1:
Continuity of Care Data Exchanges
(Inter-Provider Communication):
Communication among providers involved in the care process can range from real time communication (for example, fulfillment of an injection while the patient is in the exam room), to asynchronous communication (for example, consult reports between physicians). Some forms of inter-practitioner communication will be paper based and the EHRS must be able to produce appropriate documents. Reference: Health Level Seven, Inc. "HL7 EHR-S Functional Model and Standard." July 2004. http://www.hl7.org/ehr/downloads/index.asp)
Clinical Messaging #2:
Secure Patient/Physician e-mail (Provider and Patient or Family Communication): Trigger or respond to electronic communication (inbound and outbound) between providers and patients or patient representatives with pertinent actions in the care process. Reference: Health Level Seven, Inc. "HL7 EHR-S Functional Model and Standard." July 2004.
Clinical Reminders (Clinical Guideline Prompts):
The ability to remind clinicians to consider certain actions at a particular point in time, such as prompts to ask the patient appropriate preventive medicine questions, notifications that ordered tests have not produced results when expected, and suggestions for certain therapeutic actions, such as giving a tetanus shot if one has not been given for 10 years. Reference: eHealth Initiative Foundation. "Second Annual Survey of State, Regional and Community-based Health Information Exchange Initiatives and Organizations." Washington: eHealth Initiative Foundation, 2005.
Clinical User Authentication:
The process used by the HIE to determine the identity of the person accessing the system with adequate certainty to maintain security and confidentiality of personal health information and to administer with certainty of identity a regulated process such as e-prescribing and chart signing.
Computerized Provider Order Entry (CPOE): A computer application that allows a physician's orders for diagnostic and treatment services (such as medications, laboratory, and other tests) to be entered electronically instead of being recorded on order sheets or prescription pads. The computer compares the order against standards for dosing, checks for allergies or interactions with other medications, and warns the physician about potential problems. Reference: United States Department of Health and Human Services. Office of the National Coordinator for Health Information Technology (ONC) Glossary: http://www.hhs.gov/healthit/glossary.html.
Confidentiality:
A 3rd party's obligation to protect the personal information with which it has been entrusted.
Controlled Clinical Vocabulary: A system of standardizing the terms used in describing client-centered health and health service-related concepts.
Conversion Services:
Consulting services offered by the vendor. These services will take your original data, either in paper or electronic form, and transfer the data into the EHR system database.
Data Center:
The physical space and hardware used by the HIE to house its operations if these assets are kept within the HIE.
Data Integrity:
The accuracy and completeness of data, to be maintained by appropriate security measures and controls. Preservation of the original quality and accuracy of data, in written or in electronic form.
Data Recovery Services:

A mechanism and process to safely store duplicate databases and recreate the data should a disaster occur.
Decision Support:
Computerized functions that assist users in making decisions in their job functions. In the practice of medicine, these functions include providing electronic access to medical literature, alerting the user to potential adverse drug interactions, and suggesting alternative treatment plans for a certain diagnosis.
Decryption:
The technique of using mathematical procedures to "unscramble" data so that an unintelligible (encrypted) message becomes intelligible.
Demographics: Information about name, address, age, gender, and role used to link patient records from multiple sources in the absence of a unique patient identifier.
DICOM (Digital Imaging Communications in Medicine): A standard which defines protocols for the exchange of medical images and associated information (such as patient identification details and technique information) between instruments, information systems, and health care providers. It establishes a common language that enables medical images produced on one system to be processed and displayed on another.
Digital Signature:
A string of binary digits which is computed using an encryption algorithm. Digital signatures enable signatory authentication, confirmation of data integrity, and non-repudiation of messages.
Doctor Matching:
The process of cross-linking the multiple provider identifiers in a community from a variety of provider identifier sources and creating a master doctor identifier with a key for cross-referencing the various community identifiers.
Document Review, Edit, Sign:
A software process that allows for the secure review, editing, and signature through electronic, distributed technology of electronic health record components, such as operative reports, discharge summaries, and consultations.
eLaboratory:
The electronic delivery of laboratory results to practices so that such data may be integrated into electronic patient records in a full EHR system, or used by a dedicated application to view structured, context-rich, and/or longitudinal laboratory results on a patient. eLaboratory includes closing the orders loop, documenting the review of results by clinicians, and documenting that the results have been communicated to the patient. The full benefits of eLaboratory are not achieved until the results are used as input into clinical decision support systems (CDSS).
Electronic Billing (Claims, Eligibility, Remittance):
The ability to contact the payer before the patient is seen and get a response that indicates whether or not the services to be rendered will be covered by the payer. Reference: eHealth Initiative Foundation. "Second Annual Survey of State, Regional and Community-based Health Information Exchange Initiatives and Organizations." Washington: eHealth Initiative, 2005.
Electronic Billing Support:
The ability to contact the payer before the patient is seen and get a response that indicates whether or not the services to be rendered will be covered by the payer. Reference: eHealth Initiative Foundation. "Second Annual Survey of State, Regional and Community-based HIE Initiatives and Organizations." Washington: eHealth Initiative Foundation, 2005.
Electronic Health Record: Electronically maintained information about an individual's lifetime health status and health care.
Electronic Imaging Results Delivery:
The ability to accept messages from radiology sources and integrate the data for presentation to a clinician. Reference: eHealth Initiative Foundation. "Second Annual Survey of State, Regional and Community-based Health Information Exchange Initiatives and Organizations. " Washington: eHealth Initiative Foundation, 2005.
Electronic Prescribing (Pharmacy Communication):
Provides features to enable secure bidirectional communication of information electronically between practitioners and pharmacies or between practitioner and intended recipient of pharmacy orders. Reference: Health Level Seven, Inc. "HL7 EHR-S Functional Model and Standard." July 2004. http://www.hl7.org/ehr/downloads/index.asp
Electronic Quality Data Submission (Performance and Accountability Measures): Support the capture and reporting of quality, performance, and accountability measures to which providers/facilities/delivery.
Electronic Referral Management:
The ability to generate and/or receive summaries of relevant clinical information on a patient that are typically transferred between healthcare providers when a patient is referred to a specialist or admitted or discharged from a hospital. Reference: eHealth Initiative Foundation. "Second Annual Survey of State, Regional and Community-based Health Information Exchange Initiatives and Organizations." Washington: eHealth Initiative Foundation, 2005.
Electronic Referrals and Authorizations:
The ability to generate and/or receive summaries of relevant clinical information on a patient that are typically transferred between healthcare providers when a patient is referred to a specialist or admitted or discharged from a hospital. Reference: eHI Foundation. "Second Annual Survey of State, Regional and Community-based HIE Initiatives and Organizations. " Washington: eHealth Initiative Foundation, 2005.
Electronic Signature:

A digital signature, which serves as a unique identifier for an individual. Reference:
Encryption: The process of enciphering or encoding a message so as to render it unintelligible without a key to decrypt (unscramble) the message.
E-Prescribing: Provides features to enable secure bidirectional communication of information electronically between practitioners and pharmacies or between practitioner and intended recipient of pharmacy orders. Reference: Health Level Seven, Inc. "HL7 EHR-S Functional Model and Standard." July 2004. http://www.hl7.org/ehr/downloads/index.asp
Health Information Exchange (HIE): The mobilization of healthcare information electronically across organizations within a region or community.
HIE provides the capability to electronically move clinical information between disparate healthcare information systems while maintaining the meaning of the information being exchanged. The goal of HIE is to facilitate access to and retrieval of clinical data to provide safer, more timely, efficient, effective, equitable, patient-centered care.
Formal organizations are now emerging to provide both form and function for health information exchange efforts. These organizations (often called Regional Health Information Organizations, or RHIOs) are ordinarily geographically-defined entities which develop and manage a set of contractual conventions and terms, arrange for the means of electronic exchange of information, and develop and maintain HIE standards.
Although HIE initiatives differ in many ways, survey results and eHI experiences with states, regions and communities indicate that those who are experiencing the most success share the following characteristics. They are:
Governed by a diverse and broad set of community stakeholders;
Develop and assure adherence to a common set of principles and standards for the technical and policy aspects of information sharing, addressing the needs of every stakeholder;
Develop and implement a technical infrastructure based on national standards to facilitate interoperability;
Develop and maintain a model for sustainability that aligns the costs with the benefits related to HIE; and
Use metrics to measure performance from the perspective of: patient care, public health, provider value, and economic value.
Reference: eHealth Initiative. "Second Annual Survey of State, Regional and Community-based Health Information Exchange Initiatives and Organizations." Washington: eHealth Initiative, 2005.
Health Care Interoperability:
Assures the clear and reliable communication of meaning by providing the correct context and exact meaning of the shared information as approved by designated communities of practice. This adds value by allowing the information to be accurately linked to related information, further developed and applied by computer systems and by care providers for the real-time delivery of optimal patient care.

Health Level Seven (HL7): An ANSI approved American National Standard for electronic data exchange in health care. It enables disparate computer applications to exchange key sets of clinical and administrative information.
ICD-10 (International Statistical Classification of Diseases and Related Health Problems, 10th Revision): The 1992 revision of the international disease classification system developed by the World Health Organization.
ICD-10-CM (International Statistical Classification of Diseases and Related Health Problems, 10th Revision, Clinical Modification): The American modification of the ICD-10 classification system, for field review release in 1998.
ICD-10-PCS (International Statistical Classification of Diseases and Related Health Problems, 10th Revision, Procedural Classification System): A classification system for reporting clinical procedures, to accompany ICD-10-CM, developed in the US, for 1998 field review release.
ICD-9 (International Classification of Disease, 9th Revision): The 1972 revision of the international disease classification system developed by the World Health Organization.
ICD-9-CM (International Classification of Disease, 9th Revision, Clinical Modification): The American modification of the ICD-9 classification system for both diagnoses and procedures.
Implementation Services: Consulting services offered by the vendor. These services will provide planning and actual implementation of an EHR system. It is important when comparing quoted implementation costs that physicians understand which detailed cost line items a particular vendor will be supplying. Also, make sure and take a look at their project plans.
Informatics: The application of computer science and information science to the management and processing of data, information, and knowledge.
Interface: Shared boundary between two functional units defined by various characteristics pertaining to the functions, physical interconnections, signal changes, and other characteristics as appropriate.

Interface to ADT System: The interface between an HIE and the systems that are sources for admission, discharge and transfer (ADT) of patients in the care delivery setting and that are resident within care delivery institution.

Interface to ASP EHR System: The interface between an HIE and Electronic Health Records (EHRs) that are maintained on ASP platforms (i.e. NexGen, AllScripts).
Interface to Claims System: The interface between an HIE and the systems that are sources for or routing pathways for claims data that are resident within health plans and claims clearinghouses.

Interface to EKG System: The interface between an HIE and the systems that are sources for EKG results that are resident within dispensing physician offices and hospitals.
Interface to Eligibility System: The interface between an HIE and the source data of which people have eligibility for which type of benefits that are resident within health plans and are not infrequently web-enabled.

Interface to Formulary System: The interface between an HIE and the systems that are sources for formulary status of specific drugs for specific health benefit designs and that are resident within pharmacy benefit management companies and hospitals.

Interface to Laboratory System: The interface between an HIE and systems that are sources of laboratory data.

Interface to Pharmacy System: The interface between an HIE and the systems that are sources for prescription data or that are resident within dispensing pharmacies, pharmacy benefit management companies and hospitals.

Interface to Practice Management System: The interface between an HIE and the systems that are sources for the financial management systems of physician practices.
Interface to Provider List System: The interface between an HIE and the systems that track the multiple providers and their identifying data that are resident within health plans, dispensing pharmacies, pharmacy benefit management companies laboratories, physician practices, and hospitals.

Interface to Provider Office EHR System: The interface between an HIE and EHRs that are maintained in practice-specific systems (e.g. EPIC).

Interface to Radiology System: The interface between an HIE and systems that are sources for radiological data.

Interface to Transcribed Reports System: The interface between an HIE and the systems that are sources for transcribed reports. Typically these systems are based at a transcription service or at a hospital and contain admission and discharge notes and consultations, operative reports, and pathology and radiology results.
Interoperability:
The ability of two or more systems or components to exchange information and to use the information that has been exchanged accurately, securely, and verifiably, when and where needed.

The International Organization for Standardization (ISO): It is a worldwide federation of national standards bodies from some 130 countries, one from each country. ISO's work results in international agreements which are published as International Standards.
Key Certificate: A data record that authenticates the owner of a public key for an asymmetric algorithm. It is issued by a certification authority and is protected by a digital signature allowing the certificate to be verified widely. The certificate may also contain other fields beside the value to the key and the name of the owner, for example an expiration date.
Keys: A sequence of symbols that controls the operations of encryption and decryption.
LOINC (Logical Observation Identifiers, Names, and Codes): The LOINC databases provide sets of universal names and ID codes for identifying laboratory and clinical test results. The purpose is to facilitate the exchange and pooling of results, such as blood hemoglobin, serum potassium, or vital signs, for clinical care, outcomes management, and research.

Medication Matching: The process of cross-linking the multiple possible medication identifiers naming conventions in a community from a variety of systems housing medication information and creating a master medication identifier with a key for cross-referencing the various community identifiers. For example there are hundreds of NDC codes for identical drugs as well as HCPCS codes that identify the same drug as NDC codes.
Medication Reconciliation: Alerts providers in real-time to potential administration errors such as wrong patient, wrong drug, wrong dose, wrong route and wrong time in support of medication administration or pharmacy dispense/supply management and workflow. Reference: Health Level Seven, Inc. "HL7 EHR-S Functional Model and Standard." July 2004. http://www.hl7.org/ehr/downloads/index.asp

Message Integrity: Protecting a message against its unauthorized modification, often by the originator of the message generating a digital signature.

Messaging to Pharmacies: The process of communicating electronically with pharmacies. This typically includes the cost of communication lines and processes between the HIE and pharmacies. This is necessary to support the e-prescribing function when that function includes the process of electronically sending a digital prescription to the pharmacy.

Messaging to Providers: The process of communicating electronically with providers. This typically includes the cost of communication lines and processes between the HIE and provider terminals.

National Health Information Network: An interoperable, standards-based network across the nation for the secure exchange of heath care information. Reference: HHS Awards Contracts to Develop Nationwide Health Information Network. 2005.

Network Connectivity: The process used for maintaining connection for communication between the HIE and a data source (laboratory, radiology practice, physician practice, or hospital) and data user (physician practice or hospital).

Network: A set of connected elements. For computers, any collection of computers connected together so that they are able to communicate, permitting the sharing of data or programs.
Order Entry: The process of communicating health care provider orders through electronic, computerized processes.

OSI (Open Systems Interconnection): An international standard for networking adopted by the ISO (International Organization for Standardization). This 7-layer model offers the widest range of capabilities for networking.

Outbreak Surveillance: Support clinical health state monitoring of aggregate patient data for use in identifying health risks from the environment and/or population. Reference: Health Level Seven, Inc. "HL7 EHR-S Functional Model and Standard." July 2004. http://www.hl7.org/ehr/downloads/index.asp

Parallel Pathways for Quality Healthcare: eHI has developed a set of principles and framework for alignment of incentives with both quality and efficiency goals as well as HIT capabilities within the physician practice and health information exchange capabilities across markets. This Framework—entitled “Parallel Pathways for Quality Healthcare” offers significant guidance to states, regions and communities who are exploring health information exchange as a foundation to address quality, safety and efficiency challenges.

Participant Roles: Examples of roles that may be recognized by the health system that participate in events affecting the health of people:
Provider
Governor
Manager
Recipient
Researcher
Educator
Worker
Family Member
Roles may be used to authorize an individual's access to information system functionality.
Patient Matching: The process of cross-linking the multiple patient identifiers in a community from a variety of patient identifier sources and creating a master patient identifier with a key for cross-referencing the various community identifiers. This is also referred to as a record locator service.

Pay-for-Performance/Quality Data Reporting: Supports the capture and reporting of quality, performance, and accountability measures to which providers/ facilities/ delivery systems/communities are held accountable including measures related to process, outcomes, and/or costs of care, may be used in 'pay for performance' monitoring and adherence to best practice guidelines. Reference: Health Level Seven, Inc. "HL7 EHR-S Functional Model and Standard." July 2004. http://www.hl7.org/ehr/downloads/index.asp

Record (PHR): An electronic application through which individuals can maintain and manage their health information (and that of others for whom they are authorized) in a private, secure, and confidential environment. Reference: United States Department of Health and Human Services. Office of the National Coordinator for Health Information Technology (ONC) Glossary: http://www.hhs.gov/healthit/glossary.html. 2005

Public Key Infrastructure (PKI): A conceptual framework that enables the encryption, decryption and electronic "signing" of data transmissions in a secure fashion within an open network environment.

Privacy: Right of an individual to control the circulation of information about him-/herself within social relationships; freedom from unreasonable interference in an individual's private life; an individual's right to protection of data regarding him/her against misuse or unjustified publication.

Private Key: In asymmetric cryptography, the key which is held only by the user for signing and decrypting messages.

Public Health Outbreak Surveillance: Supports clinical health state monitoring of aggregate patient data for use in identifying health risks from the environment and/or population.

Reference: Health Level Seven, Inc. "HL7 EHR-S Functional Model and Standard." July 2004. http://www.hl7.org/ehr/downloads/index.asp
Public Health Processor: A software product that processes extracted data from health care provider systems for the purpose of tracking, trending, and reporting for public health reasons.

Public Key Certificate: A data record that authenticates the owner of a public key for an asymmetrical key system. It is issued by a CA and is protected by a digital signature, allowing the certificate to be verified widely.

Public Key: In asymmetric cryptography, the key which is published by the user to encrypt messages and so that others may verify his/her signature.
Recommend Treatment and Monitoring: The basis of cost, local formularies or therapeutic guidelines and protocols. Reference: Health Level Seven, Inc. "HL7 EHR-S Functional Model and Standard." July 2004. http://www.hl7.org/ehr/downloads/index.asp

Registration Authority: An entity (group or agency) that has been delegated by a CA to perform a specific set of ‘trusted authority’ functions within PKI.

Results Answer Matching: The process of cross-linking the multiple possible answers to asking for a given result. For instance, asking for the results of a chest x-ray could yield a dictated report or a digital image of an x-ray. In any case, the case received must be matched across the type of result to a term identifying a common result.

Results Name Matching: The process of cross-linking the multiple possible names of data results that can contain the same information. For instance a blood glucose reading can be called up by a blood glucose test, an SMA panel, or a glucometer result.

Results Review (Alerts to Providers): The ability to interpret the clinical data that is entered about a patient using a set of rules or algorithms which will generate warnings or alerts at various levels of severity to a clinician. These are intended to make the clinician aware of potentially harmful events, such as drug interactions, patient allergies, and abnormal results that may affect how a patient is treated, with the intention of speeding the clinical decision process while reducing medical errors. Reference: eHealth Initiative Foundation. "Second Annual Survey of State, Regional and Community-based Health Information Exchange Initiatives and Organizations." Washington: eHealth Initiative Foundation, 2005.

Results Review: The ability to interpret the clinical data that is entered about a patient using a set of rules or algorithms which will generate warnings or alerts at various levels of severity to a clinician. These are intended to make the clinician aware of potentially harmful events, such as drug interactions, patient allergies, and abnormal results, which may affect how a patient is treated, with the intention of speeding the clinical decision process while reducing medical errors.

Risk Assessment: An evaluation of the chance of vulnerabilities being exploited based on the effectiveness of existing or proposed safeguards or countermeasures.

Risk: The chance of a vulnerability being exploited.

Rules Engine: A set of rules defined within a software process that converts clinical and administrative data streams into a meaningful representation of clinical quality markers to be used in functions such as pay for performance/quality data reporting.
Security: In information systems, the degree to which data, databases, or other assets are protected from exposure to accidental or malicious disclosure, interruption, unauthorized access, modification, removal or destruction.

Service Level Agreement-Compliance: A documented track record of how well the vendor is meeting it’s customer support commitments.

Service Level Agreement-Customer Responsibilities and Duties: The steps that the customer needs to take in order to ensure that the vendor has all the information they need to resolve an issue.

Service Level Agreement-Hours of Support: Methods that will be used for communicating and resolving issues. Typical methods are email, phone, and online chat. Ask whether remote diagnostics and/or on site visits by support analysts are available.

Service Level Agreement-Methods of Support: Will be used for communicating and resolving issues. Typical methods are email, phone, and online chat. Remote diagnostics can be available and, in some instances, it might be necessary to have a support analyst come on site.
Service Level Agreement-Problem Escalation & Triage: The mechanism that defines how a problem migrates through the support system and the different resources that get involved along the way. If a problem can’t be resolved in a certain amount of time, then it escalates until it is resolved.

Service Level Agreement-Response Times: Different functions of the system might warrant different response times based on severity level. There should be a schedule of response times for different types of problems, and the service level agreement should define this accountability.

Service Level Agreement-Severity/Priority Classification: Different types of problems have different levels of urgency and importance. The severity level of a problem is usually noted when a support ticket is opened up. Resolution guarantees are based on severity levels. For example, CPOE down would be a high severity level while a patient education database not working might be a lower level of severity.
SNOMED International: A nomenclature for use by all health services professionals developed in the US and updated at least semi-annually.

Stages of Health Information Exchange Development:

Stage One:
Recognition of the need for HIE among multiple stakeholders in your state, region, or community
Stage Two:

Getting organized by defining shared vision, goals, & objectives, identifying funding sources, and setting up legal & governance structures

Stage Three:
Transferring vision, goals, & objectives to tactics and business plan, defining needs and requirements and securing funding

Stage Four:
Well under-way with implementation – technical, financial, and legal
Stage Five:

Fully operational health information organization. Transmitting data that is being used by healthcare stakeholders Sustainable business model.

Stage Six:
Demonstration of expansion of organization to encompass a broader coalition of stakeholders than present in the initial operational model
Reference: eHealth Initiative Foundation. "Second Annual Survey of State, Regional and Community-based Health Information Exchange Initiatives and Organizations." Washington: eHealth Initiative Foundation, 2005.


Standard:

Documented agreements containing technical specifications or other precise criteria to be used consistently as rules, guidelines, or definitions of characteristics to ensure that materials, products, processes, and services are fit for their purpose. A standard* specifies a well defined approach that supports a business process and:
Has been agreed upon by a group of experts
Has been publicly vetted
Provides rules, guidelines, or characteristics
Helps to ensure that materials, products, processes and services are fit for their intended purpose
Available in an accessible format
Subject to ongoing review and revision process
*This differs from the healthcare industry's traditional definition of "standard of care."

Statistical Deviation Detector:

Identifies variances from patient-specific and standard care plans, guidelines, and protocols.
The International Organization for Standardization (ISO): It is a worldwide federation of national standards bodies from some 130 countries, one from each country. ISO's work results in international agreements which are published as International Standards.

Third Party-EHR Specific:

Applications that are essential to the basic infrastructure of the system. They are the building blocks, such as the technical platform upon which the EHR system is built (e.g.,Windows, Linux, or MacIntosh, etc.) Also what kind of database structure controls the system (e.g, SQL, Oracle, etc.). When comparing license costs, note if there are separate general system license costs or if these are rolled into the main cost. Also, ask whether there will be additional costs when the vendor upgrades their software and it becomes necessary to install a new version of the database or operating system. Make sure your infrastructure software will support any features you wish to add later on.
Third Party-General System: Applications that are essential to the basic infrastructure of the system. They are the building blocks such as the technical platform the EHR system is built on such as, Windows, Linux, or MacIntosh, etc. Also what kind of database structure controls the system – SQL, Oracle, etc. When comparing license costs note if there are separate general system license costs or if these are rolled into the main cost. Also, will there be additional costs when the vendor upgrades their software and it is necessary to install a new version of the database or operating system. Make sure your infrastructure software will support any features you wish to add later on.
Training Services:

Consulting services offered by the vendor. They provide hands on training for all aspects of the system.
UMLS (Unified Medical Language System):

A long-term research project developed by the US National Library of Medicine to assist health professionals and researchers to retrieve and integrate clinical vocabularies from a wide variety of information sources. The goal is to link information from scientific literature, patient records, factual databases, knowledge-based expert systems, and directories of institutions and individuals in health and health services.
Vendor Software Licenses: License cost of various modules. Typically, modules will be licensed on a concurrent or named user basis. For example, with a concurrent license, if there are 4 providers and 8 employees, a minimum of 12 concurrent licenses would be needed. However, if the providers were halftime [meaning, they only used the system half time] (and all 4 never used the system at any one time, only 10 licenses would be needed). If using a named user license under the same circumstances, 12 licenses would always be needed – as licenses are not shared among different people. There can be a provision though for “active” and “inactive” providers (which means they could look at information, but not enter it in the system). Under an ASP (monthly rental agreement), software licenses are not being purchased, but rented However, the same issues exist for determining number of ASP licenses as with a license purchase.
X12:

A committee chartered by the American National Standards Institute (ANSI) to develop uniform standards for inter-industry electronic interchange of business transactions—electronic data interchange (EDI).
X12N:

The principle responsibilities of ASC X12N Insurance Subcommittee are development and maintenance of X12 standards, standards interpretations, and guidelines for the insurance industry, including health insurance. Most electronic transactions regarding health insurance claims are conducted using these standards, many of which are mandated by HIPAA.
The website development and some of the content in the Toolkit have been made possible by grant number 1D1BTM00095-01 and 02, through the Health Resources and Services Administration HRSA Office of the Advancement of Telehealth (HRSA/OAT). The contents are solely the responsibility of the authors and do not necessarily represent the official view of HRSA/OAT.

 
Design by Free Wordpress Themes | Bloggerized by Lasantha - Premium Blogger Templates