| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Buried in cloud files? We can help with Spring cleaning!

    Whether you use Dropbox, Drive, G-Suite, OneDrive, Gmail, Slack, Notion, or all of the above, Dokkio will organize your files for you. Try Dokkio (from the makers of PBworks) for free today.

  • Dokkio (from the makers of PBworks) was #2 on Product Hunt! Check out what people are saying by clicking here.

View
 

Work Group 2

Page history last edited by Christel Anderson 11 years, 8 months ago

Work Group 2

TIGER Usability & Clinical Application Design

 


 

Working together using this wiki

This wiki is a shared online whiteboard that allows the entire group to easily share information to each other and other TIGER collaborative team members. The material on the wiki should be considered to be in draft format and will be published on the TIGER website at www.tigersummit.com upon completion. 

 

Activities of Work Group 2 

This work group is collecting case studies and examples from the field that illustrate usability and clinical application design from various environments.  These resources are intended to demonstrate examplars as well as lessons to be learned that can help others to avoid common pitfalls and mistakes.  

 

Group members 

  • Denise Tyler - Co-Facilitator

  • Janey Barnes 
  • Ryan Bramhall
  • Peggy Esch
  • Kristenia Jones  
  • Angela Lewis 

  • Tim O'Connor 
  • Nancy Robinson
  • Patti Rogers - Co-Facilitator
  • Lee Stabler 

 

Meetings 

This team meets every other Monday at 1 p.m. EST/10 a.m. PST

 

Upcoming Meetings:

March 17, 2008 at 1:00 p.m. EST - please register at https://www1.gotomeeting.com/register/363976443

April 7, 2008 at 1:00 p.m. EST - please register at https://www1.gotomeeting.com/register/734361695

April 21, 2008 at 1:00 p.m. EST - please register at https://www1.gotomeeting.com/register/186612902

May 5, 2008 at 1:00 p.m. EST - please register at https://www1.gotomeeting.com/register/533307278

May 19, 2008 at 1:00 p.m. EST - please register at https://www1.gotomeeting.com/register/584246816

 

Case Study Templates

type_doc.gifTIGER_Request for Case Study FINAL.doc Ready to Use Case Study Template

 

Supplied by Patti Rogers on November 28, 2007

type_pdf.gifHFEinIH proceedings content.pdf 

 

Case Studies Collected

type_xls.gifUsability_CaseStudies.xls 

 

Case Study Analysis

 

type_xls.gifUsability_CaseStudies_compiled(5).xls Case Study summarizations for Final

 

 

Drafts 

 

11/15/07 - provided by Nancy Staggers (slide used with permission)

Axioms of usability include:  a) involving the end-user early in the design process, b) iterative prototyping and c) empirical testing.  The attached slide was developed by a Suzanne Miller, a nursing informaticist employed by Intermountain Health in the early 2000s.  She worked with interdisciplinary care providers to create an interdisciplinary care summary page.  She used MicroSoft Front Page to mock-up this application to present before clinicians and elicit comments.  She could easily modify the presentation to produce iterative designs based upon comments.  Over months, she presented to many groups of clinicians, so this design represents the culmination of extensive work with clinicians.  Rather than empirical testing, Intermountain Health used a systematic but less formal method to solidify its design.

 

Example of a good case study.

 

Strawman for case study outlines:

 

Author

Institution

Application or Function

Target users

Overview of the Process

Positive attributes of this case

Challenges and lessons learned

 

Picture1.png

 

11.15.07 - submitted by Lee Stabler

 

Case Study

Health First, Inc.

Selection of Electronic Documentation System

 

            This is the process used by Health First (HF) hospitals to select an electronic documentation system. Health First, Inc.  is comprised of three separate acute care hospitals, free standing clinics, Hospice, Home Care, and a health plans. Current state at HF was electronic documentation was being done by all clinicians in all departments, except physicians. We had several best of breed niche systems that were implemented during the late 1990’s and early 2000’s. At the time niche system were purchased and implemented technology did not provide one electronic system that fit the needs of all specialty areas such as L&D, ED and OR.

            The first step was to determine the mission and vision HF wanted for their move forward in utilization of an electronic health record. It was determined that we needed to find a solution that would allow all departments to utilize the same system, accommodate CPOE, provide documentation support for evidenced based practice and decision support at the point of care. Additionally, the system needed to have a balance of standardization as well as the ability to support individualization. A key component during this step is to establish executive buy-in and sponsorship.

            The second step was the evaluation process for several systems/vendors. Before the actual evaluations could be started there was a determination of who should be included on the team doing the evaluations and criteria for the evaluations. The team needed to include all stakeholders that the new system would have an impact to. We chose bedside clinicians from each of the three hospitals, all disciplines, IT and management from across the organization. Once the team and tool for evaluations where established, then vendors were scheduled to come in and demonstrate their products. At the end of the demonstrations utilizing an objective based evaluation tool the selection was made.

            Now it was time to do a crosswalk between the current system(s) and the new system. We had a dedicated team of clinicians and support persons who looked at each piece we documented and compared it to the new system to answer several questions.

1)         Why are we charting this?

2)         Is it required by regulatory agencies?

3)         Required by HF policy?

4)         Just because we always have?

5)         Standard of care?

6)         Is the current documentation included in the new system? If not, why not?

7)         Is this evidenced based practice?

8)         Will policies and procedures be impacted and need revisions?

A master spreadsheet was kept of the crosswalk findings; follow up needed, time line for follow up and person responsible. Once this was completed then the custom configuration needed was completed by IT.

            The next step was extensive testing of the content and functionality. Included in this team was Clinical Informatics, our clinical system educators and selected clinicians. After testing was completed and all issues resolved, then the training plan was put together.

The training plan included content, length of classes, documented competencies based on roles and schedules to accommodate the go-live schedules. At HF we have dedicated clinical system trainers, who train all associates on any electronic systems. This provides a consistent method and content for the classes. During the training period we made sure that the training environment was available on each unit for four to six weeks prior to go-live of the unit, allowing staff to have extra time to practice.

            Go-live was the last step in the implementation phases. Each unit/department was scheduled for their go-live to start on a Tuesday morning at 0700. This corresponded with shift change and allowed Monday for prepping. The prep involved Clinical Informatics being on the unit and working with staff to pre-build the patient’s chart in the new system with the basics. The individual clinicians would customize for details such as drains. During go-live week there was scheduled support from Clinical Informatics, Clinical Practice Coordinators, Superusers and management. This was tapered the second week based on needs.

            HF has several systems set up for on going support. There is Clinical Informatics associates assigned to each facility and they make daily rounds to answer questions about system functionality and computer issues. The Clinical Practice Coordinators are reasonable for process issues. The Help Desk is available 24/7. We have an established change management process that addresses any change requests.

            Today we have all nursing and ancillary departments within the hospitals using the system successfully. May 2008 our ED’s which currently use a niche system will move to new system. Our OR’s niche system is in partnership with the main system and is progressing with integration of the data. We have seen significant improvements in our quality outcome measures since adopting this system.

 ----------------------------------------------------------------------------------------------------------------------

11/15/07 Submitted by Angela Lewis

 

In a recent post to the CARING listserve (November 14, 2007) excellent points where made related to the clinical user being the driver in the system design process and thereby ensuring usability. The poster differentiated between “building” and “designing” and made an elequant case for the right way to do clinical application design.Reprinted with permission.  
 
 
“Can we discuss the difference between building and designing?
 
I am a nurse informaticist / analyst responsible for building and
maintaining clinical systems but only under the direct supervision of
clinical experts/users who design the flow of the on line documentation
and who are content matter experts in their particular clinical
specialty.
 
 
I then look at their documentation design through the eyes of a nurse
who may float to the nursing unit, or a student nurse and question them
if it contradicts the basic logic of the nursing process, or if the data
entry screens are not intuitive. (AKA "The Novice Nurse Test," where I
fulfill the role of the novice nurse.)
 
I also take into consideration how can we capture data elements in the
documentation that we will want to use when it comes time to compile
clinical reports about that particular patient population. For example
does the patient have a latex allergy? Response: Yes, No. But if the
patient is unconscious what does the nurse enter in the field? If the
nurse leaves it blank it appears as a documentation omission. Responses
need to be Yes, No, and Unable to Assess.
 
 
As a system expert I am also responsible for bringing to the clinical
design discussion options for expediting the documentation of patient
care through the deployment of system features and functionality that
would not be evident to the clinical content matter experts or end
users.
 
 
For example many years ago I was tweaking a traditional care plan module
of a nationally known hospital information system (components included
Patient Problems and Goals, Outcomes, and Nursing Interventions to
address the identified problems and to get the patient to the desire
outcome) so that it matched a 4 day long clinical path for a total hip
replacement that the Orthopedic nurse manager designed along with one of
the Orthopedic surgeons on paper.
 
 
I built the clinical path in the test environment, tested it and
demonstrated it to my clinical designers. The Orthopedic nurse manager
and surgeon approved it so I then moved the clinical path to the live
environment.
 
 
 
We were just planning the pilot launch of the automated clinical path
when I got word that an ICU nurse found it on line and implemented day
one of the clinical path as the plan of care for a fresh post-op total
hip patient. When I asked the nurse why he used it he said, "Everything
I needed was right there." All the nursing interventions required for
caring for his patient were in one place. The process was intuitive
because he knew how to activate the traditional care plan components in
the same module. And it made the patient care planning process a 10
second task. He loved it.
 
 
It was a very easy documentation process to introduce. And other
orthopedic surgeons in the group began demanding clinical pathways for
their top procedures too.   
 
 
Nurse informaticists / analysts can build wonderful stuff based on their
vision, but without the design input of the clinical experts and end
users don't be surprised if you have to undo it and re-build it multiple
times both before and after go live. (The real test of a system is when
it goes live.)”
 
 
Joan M. Smith, MSN, RN-BC
Clinical Project Leader
Doctors Community Hospital
Lanham, Maryland 
 
 
Usability References and Resources
 
 

 

Comments (1)

Anonymous said

at 2:02 pm on Nov 1, 2007

An excellent beginning effort!

You don't have permission to comment on this page.