Health IT Project Management

Download Report

Transcript Health IT Project Management

Health IT Project Management
Indrek AIt
7/17/2015
Agenda
• Health IT Technologies
• Implementation Process
• Health IT Implementation Success Factors
The Technologies
Case Management
Clinical Data
Warehouse
Health Information
Exchange
Practice Management /
Electronic Health Record
Interfaces
Pharmacy, Dental and
other Systems
Telemedicine
IT Infrastructure
1) Have a plan
2) Follow the plan
• The purpose of project management is to
increase the likelihood of success
Implementation Process
Initiating
Planning
Executing
Monitoring and Controlling
Closing
Implementation Process:
Core initiatives
Initation and setup
Model System
Overview
Member Setup
Setup
Validation
Training
Change Management
Collaborative Participation
Workflow Development
Project Management
Final
Preparation
and Go Live
Support
Health Information Technology
Implementation Success Factors
• Strong Clinic Leadership
• Experienced Partners
• Time Invested on Workflow Design and
Training
• Change Management Planning
• Plan for Ongoing Support
• Understanding the Financial Commitment
1) Strong Clinic Leadership
•
•
•
•
•
Must have executive leadership throughout
Must have clinical leadership throughout
Great idea to have board leadership
Choose wisely, trust and empower your team
Be visible, supportive and unwavering in
commitment
• Expect the best, plan for the worst
• Recognize successes
2) Experienced Partners
• Look for experience
• Financial viability
• Regional market penetration (vendors
pros/cons)
• Reference checks /site visit (going to clinics,
how it is live and used in the system)
• Community
• Strong leadership team
3) Workflow and Training
•
•
•
•
•
Include all departments
Document workflows from multiple sources
Consider how appointments are scheduled
Do not discount anomalies
Opportunity to streamline and standardize work
processes
• Anticipate and embrace new methods (make sure
that old workflows are not created in the new
process)
4) Plan for Ongoing Support
•
•
•
•
•
Support at your site
Supporting for new programs
Managing infrastructure
Software updates
Ongoing training activities (once you go live, the
system is always changing, there will be updates.
There has to be a training plan how to adapt for
changes; webinars, on-person etc)
• Measuring and monitoring success metrics (what
does success mean for us)
5) Understanding the Financial
Commitment
• Staff time – training, extraction, novice to expert
• Productivity implications post go-live (for
inexperienced users, you want to get experience
for them now)
• Space renovation (reconvert some spaces that
might not be needed anymore)
• Hardware, software, connectivity (has to be
bought)
• Training and education
• Ongoing costs (maintainance costs etc)
Executing
•
•
•
•
•
Project team key qualities
Responding to risk
Cater to the physician
Make it personal
Phased approach
1) Project Teams Key Qualities
• Knowledge of department or function
• Trusted/respected, works well with other
departments
• Interest/enthusiasm
• Communicator/listener
• Organized/can meet deadlines
• Motivated
2) Responding to risk
• Get users up to speed (basic computer classes)
• Ask for what you need
• Avoid silos
3) Cater to the Physicians
• Device options
• Physician resource room (all the needs they
need; mandatory support)
• Intensive tracking and follow up on issues
4) Make it personal
• One-on-one training (anything less, less than
optional)
• Communication
5) Phased Approach
•
•
•
•
•
•
Viewing results, e-signature and entering notes
Procedure ordering
Medication ordering
Go paperless
Remove old forms from the area
Be available
Monitoring and Controlling: Continued
support
•
•
•
•
•
Daily staffing
Training on enhancements and upgrades
Training for new physicians
Continued communications
Monthly physician champion meetings
Tips and tricks
•
•
•
•
Train for patients-friendly use
Plan for quality reportng early
Revisit the vision and objectives
Become the tribal storyteller
Lessons learned
• Top down support is paramount to success
• Communicate the fact that this isn´t an
information systems driven initiative.
• If you aren´t moving forward, you are falling
behind
• Market your accomplishments
• Your vendor is your partner
• If it´s broke, fix it
• Exploit the software
• Be willing to beta things that are important to you
THANK YOU