• No results found

2011 Capstone Project

N/A
N/A
Protected

Academic year: 2021

Share "2011 Capstone Project"

Copied!
23
0
0

Loading.... (view fulltext now)

Full text

(1)

2011 Capstone Project

(2)
(3)

Capstone

 

Purpose

To align with organizations involved in efforts to support 

id  i  b i   i f l    f HIT b  

providers in becoming meaningful users of HIT by 

creating a registry of EHR vendors in major health care 

facilities in Washington State and by sharing that 

facilities in Washington State and by sharing that 

(4)
(5)

Capstone Key Informants

Capstone Key Informants

(6)

Capstone

 

Project

 

Scope

Project Kickoff:  CHITA board meeting April 13, 2011.  

Keyy Informant Interviews and Contacts

 CEO, Foundation for Health Care Quality

 Vice President and Chief Technology Officer, Group Health Cooperative

 Senior Policyy Analyst,y , Washingtong  State Health Care Authorityy

Executive Director, Health Information Program, WSHA

(7)

We defined our scope to include Washington State hospitals and group 

practices with 50+ healthcare providers.  This map from AHRQ’s 

website shows the number of hospital beds in Washington clustered in 

(8)
(9)

W   t d   d t  t bl   ith   t t f iliti   d 

We created a data table with 124 target facilities and 

(10)

W   i d  bli h d i f ti  f  f ilit   d 

We reviewed published information for facility and 

contact information:

Washington State Health Information Exchange: 

Washington State Health Information Exchange: 

Strategic and Operational Plans

2011 WSHA Membership Directory

Physician Group Practices, Health Care of the Future 

Puget Sound Business Journal, April 2010

Billian’s Hospital Blue Book

(11)

 We composed survey questions to elicit vendor and 

product data, implementation challenges and 

t t  EHR  j t    t t i f ti

status, EHR project manager contact information.

Q1 Does your facility use an EHR?

Q3. Is your EHR solution comprised of a single vendor or multiple vendors?

Q7. What is the most significant challenge you face in the EHR acquisition and/or

Q9 Please provide the name and address of Q1. Does your facility use an EHR? Q2. Does your facility contract with an EHR

vendor or multiple vendors?

Q4. Please list your facility EHR vendor(s)? face in the EHR acquisition and/or

implementation process?

Q9. Please provide the name and address of your organization.

vendor?

Q5. What is your estimate of your organization’s progress implementing a complete EHR?

Q8. Who is the EHR implementation project manager?

Q10. How may we contact you?

(12)

C

l

S

T l

Catalyst

 

Survey

 

Tool

We developed a Catalyst survey to elicit EHR vendor 

We developed a Catalyst survey to elicit EHR vendor 

information from our target facilities, with questions about 

(13)

S

Q

ti

L i

(14)

EHR

 

Vendor

 

Registry

 

Inputs

Catalyst  Target  WSHIMA  E‐alert WSHA  EHR  V d   Survey  results facility  database WSHA  contact  emails Vendor  Registry

(15)

Challenges

 

and

 

Course

 

Corrections

 Defining  the scope and scale of our project

 Validating table data with  Billian’s Hospital Blue Book

 Cold calls to facilities time consuming

 Catalyst survey target contacts difficult to obtain

 WSHIMA E‐Alert distribution

 Targeted email recipient distribution list from WSHA

(16)

Barriers to Success

Barriers

 

to

 

Success

(17)
(18)

Target

 

Facilities

 

with

 

EHR Vendor Data

EHR

 

Vendor

 

Data

 

Vendor name or NONE is 

l d i   d    d  fi ld f  

populated in vendor 1 data field for 

64 of our 124 target facilities

Because some facilities utilize 

multiple EHR vendors our data 

multiple EHR vendors, our data 

table relationship between facility 

(19)

EHR

 

Vendor

 

Query

 

Results

Facility EHR Vendor Data

For 64 facilities with vendor data, 

5 8%

5. 8%

Facility EHR Vendor Data (n=64)

Figure 3 shows how many of the 64 

target facilities specified particular 

EHR vendors: EPIC 24. 37% 5. 8% 5. 8% EPIC 24.37%  MEDITECH 16.24% 16. 24% 10. 15% CERNER 10.15%

NB:  Some facilities have more 

than one EHR vendor.  

EPIC MEDITECH CERNER

MCKESSON GE N  V d

EHR vendor data is incomplete and 

not validated at this time.

(20)

Next

 

Steps

 Delete the survey from Catalyst

 Share our project findings with sponsors 

 Share our hospital and group practice database with 

fellow HIHIM students to aid their job search

Th k      d i f

 Thank our sponsors and informants

(21)

Capstone

 

Lessons

 

Learned

 Documentation on EHR vendors is not widely 

available

D i  h l h    i  i lid  

 Dynamic healthcare  environment invalidates 

published information only a few years old

 Survey respondents appreciate incentives

 Survey respondents appreciate incentives

 Accountable Care Organizations  may impact group 

practice choice of EHR vendors and products –

practice choice of EHR vendors and products 

Swedish is providing Epic and associated systems 

(22)

Resources

 Gretchen Murphy,  MEd, RHIA, FAHIMA, Director, Heath Informatics and Health Information Program, 

School of Public Health, University of Washington

 Kelly Llewellyn, MHA, Senior Policy Analyst, Washington State Healthcare Authority

 Bob Perna, MBA, FACMPE, Director, Healthcare Economics, Practice Resource Center, WSMA

i  C   i   i   l h  f i     S A

 Jim Cannon, Executive Director, Health Information Program, WSHA

 Joyce Duffy, Central Office Program Director, Washington State Health Information Management Association 

(WSHIMA)

 Kathleen Peterson, MS, RHIA, CCS, Professor, Health Informatics and Health Information Management, 

School of Public Health, University of Washington

 Washington State Hospital Association (2011) 2011 WSHA Membership Directory Seattle:  WSHA

 Washington State Hospital Association. (2011). 2011 WSHA Membership Directory.Seattle:  WSHA

 Puget Sound Business Journal. (April 2010). HealthCare of the Future: Physician Group Practices.

 eHealth Collaborative Enterprise, OneHealthPort. (July 2010). Washington State Health Information 

Exchange: Strategic and Operational Plans.Washington State Healthcare Authority. Olympia, WA: eHealth 

Collaborative Enterprise.

Billian's hospitalp  blue book. (2002).( )  Atlanta,, GA: Billian Pub.

 MGMA. (2011). Electronic Health Records: Status, Needs and Lessons: 2011 Report Based on 2010 Data,

Medical Group Management Association, 16‐17. 

 HIMSS Foundation. (2006) The Clinical Systems Hospital IT Market, 1998‐2005. Chicago: The Dorenfest Institute.

 http://www.wsha.org

h // h / / i h / l / l h

(23)

References

Related documents

In 2011, the FBI’s Criminal Justice Information Services Division (CJIS) issued the CJIS Security Policy, a set of standards for organizations that access criminal

Regulatory Data BUILD A SHORT LIST OF  EHR VENDORS VERIFY REFERENCES &  EHR  VENDOR VIABILITY Regulatory  Reporting Data  Security EVALUATE LIVE EHR  

Quality Insights of Delaware initially worked with physician practices interested in using their current EHR system with a CMS-qualified EHR-direct vendor to submit for the 2011

The system integrates with a patient portal allowing patients to verify their medical record, access billing status, review test results, and communicate to the physician via

An integrated hybrid email security solution from a single vendor is less expensive than either a hybrid solution comprised of an on-premise infrastructure layered with a

If the system includes third party software and/or content, the contract should spell out the associated costs, who is responsible for those costs, who is responsible for support,

If the system includes third party software and/or content, the contract should spell out the associated cost, who is responsible for those costs, who is responsible for support,

– ArcObjects : A rich set of GIS Software Components that ArcObjects : A rich set of GIS Software Components that can be used to build Web and Enterprise Applications. can be used