• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Ehrdt 14 the overview by-category design pp
 

Ehrdt 14 the overview by-category design pp

on

  • 15,796 views

 

Statistics

Views

Total Views
15,796
Views on SlideShare
1,226
Embed Views
14,570

Actions

Likes
1
Downloads
5
Comments
0

9 Embeds 14,570

http://histalk2.com 14545
http://www.hitsphere.com 12
http://hitsphere.com 6
http://abtasty.com 2
http://www.newsblur.com 1
http://elsevierbiz 1
http://10.140.30.109 1
http://sn137w.snt137.mail.live.com 1
http://www.365dailyjournal.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Ehrdt 14 the overview by-category design pp Ehrdt 14 the overview by-category design pp Presentation Transcript

    • In the Overview-by-Category design above, a summary of the patient’s EHR data is displayed in a singlescreen view, organized by category (CC and History of Present Illness, Previous Assessments and Plans,Allergies, and so forth).Each category of data is presented in a separate pane or table.
    • These mockups present the EHR data for an elderly woman with glaucoma in her right eye. In constructingthem, I used exactly the same patient database I used for the Snapshot-in-Time mockups in my last post.
    • The rows within the tables contain data from encounters on different dates or display the onset and enddates associated with events.
    • The tables tend to take up a lot of screen real estate because they are designed to display both present andpast information and because the fields within them can contain redundant, overly-detailed, or null data.As a result, the design shown here, based on a widely-used EHR, requires you to scroll or page down (seeblue arrows) just to view the lower half of the overview screen.
    • As you scroll or page down, the information in the upper half of the screen disappears from view. Hence,you have to use working memory to keep that information in mind, as opposed to retrieving it with a glance.Even with paging down, this overview screen omits four data elements displayed in the Snapshot-in-Timedesign (the visual field, the description of the optic disc, the family history, and the social history).
    • Suppose you notice that this patient’s intraocular pressure in the right eye (OD) was extremely high on5/27/2012 (green arrow) and you want to make sense of the clinical situation at that point in time.
    • First you have to remember the date 5/27/2012 and then visually scan each of the other tables to findrows with a match (green arrows). In the top two tables, however, the complete entry for 5/27/2012 is notvisible without scrolling.
    • For these top two tables, you need to use the scroll bars (blue arrows) to display the full 5/27/2012 entry.In doing so, however, you have shifted the position of the 5/27/2012 data to the top of each table,interfering with your ability to keep track of it visually by its screen location.
    • When you scroll down to the bottom half of the screen, the task of keeping track of what happened on or around5/27/2012 becomes even more difficult. After scrolling down within the Medications pane, you see that the status of theglaucoma drop Alphagan changed on 3/05/2012 and the status of Lumigan changed on 5/28/2012. You need to do aquick calculation to figure out that the patient was off Alphagan but still on Lumigan as of 5/27/2012. But unlike theSnapshot-in-Time design, there is no place in this design for the most important data field – the one noting that, in fact,she was not taking Lumigan on that date.
    • On looking over the Problem List and the Ocular Procedure History tables, you see that a new diagnosis ofdepression was added on 5/27/2012 and that the patient had glaucoma surgery on 5/28/2012. While youpresume that all these events are inter-related, you can’t know for sure because of the fragmented way theinformation is presented.
    • So in theory, the Overview-by-Category design allows you to reconstruct the patient’s state of health at a past time.In practice, it’s difficult because of the cognitive effort (green arrows) and mouse/keystroke effort (blue arrows)required.In my opinion, the Overview by Category design is useful mostly for seeing the present state of a patient’s health orfor scanning the tables for out-of-range values.
    • Many EHRs based on this design do provide an expanded or maximized view for some of the datacategories.In particular, many EHRs provide an expanded view of the Assessments and Plans pane.By clicking on an ‘expand’ button, the user can . . .
    • . . . navigate to a new screen. The screen above displays, as a date-sorted list, the fullAssessment and Plan data from previous encounters.The question is whether an expanded view of a single category of data is a useful interfacedesign.
    • For me, trying to comprehend a patient’s story by viewing a single category of data over time is alittle like trying to solve a Sudoku puzzle.Sometimes it’s easy and sometimes it’s difficult or impossible, but in either case, doing so requirescognitive effort that could be better spent on patient care issues.
    • It’s interesting to note that both the Overview-by-Category design (left) and the Snapshot-in-Time design (right)use exactly the same patient database, down to the level of individual data fields. The Overview-by-Categorydesign, however, requires us to make sense of temporal information using relatively slow, cognitive processing.In contrast, The Snapshot-in-Time design allows us to comprehend the same information using our very fast,high-bandwidth visual processing system.
    • Perhaps because of the cognitive burden imposed by the Overview-by-Category design (shown above),most EHRs that employ it also provide a workaround solution.Unfortunately, the workaround is non-interactive, not organized by screen location, and is of exceedinglow data density. More on this in my next post . . .