<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>On FOCUS&#187; Clinician&#8217;s View</title>
	<atom:link href="http://focusblog.iatric.com/category/clinicians-view/feed/" rel="self" type="application/rss+xml" />
	<link>http://focusblog.iatric.com</link>
	<description>MEDITECH supplies the FOCUS, we supply the perspective on Client/Server 6.x</description>
	<lastBuildDate>Mon, 24 May 2010 19:55:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Restricted View May Leave Them Wanting More</title>
		<link>http://focusblog.iatric.com/2010/03/11/restricted-view-may-leave-them-wanting-more/</link>
		<comments>http://focusblog.iatric.com/2010/03/11/restricted-view-may-leave-them-wanting-more/#comments</comments>
		<pubDate>Thu, 11 Mar 2010 19:38:31 +0000</pubDate>
		<dc:creator>michelleschneider</dc:creator>
				<category><![CDATA[Clinician's View]]></category>
		<category><![CDATA[Learning More]]></category>
		<category><![CDATA[MEDITECH]]></category>
		<category><![CDATA[6.0]]></category>
		<category><![CDATA[assessment]]></category>
		<category><![CDATA[chart view]]></category>
		<category><![CDATA[clinical decision making]]></category>
		<category><![CDATA[Clinical Panels]]></category>
		<category><![CDATA[data evaluation]]></category>
		<category><![CDATA[patient chart review]]></category>
		<category><![CDATA[restricted view]]></category>

		<guid isPermaLink="false">http://focusblog.iatric.com/?p=552</guid>
		<description><![CDATA[by Michelle Schneider I have really been diving into MEDITECH’s 6.0 Clinical Panels.  This is, after all, the latest MEDITECH has to offer for patient chart review and support for clinical decision making.   I find it very frustrating though, because it’s difficult to get a good flow of data evaluation.  In MEDITECH’s demonstrations, the data [...]]]></description>
			<content:encoded><![CDATA[<p><strong>by Michelle Schneider</strong></p>
<p>I have really been diving into MEDITECH’s 6.0 Clinical Panels.  This is, after all, the latest MEDITECH has to offer for patient chart review and support for clinical decision making.   I find it very frustrating though, because it’s difficult to get a good flow of data evaluation.  In MEDITECH’s demonstrations, the data is all perfectly placed in these narrow columns so that the user gets a wonderful vibe of an easy, relaxed chart review.  However, as soon as reality strikes, users realize that all responses are not less than 15 characters.  A user is notified of a longer response with an ellipsis after a truncated entry.  In order to see the  longer response, he must click once to open an additional screen, move the mouse to the bottom right of the screen, click close and then continue the chart review.  In the assessment below, which certainly represents a very limited assessment, the user cannot easily glean the patient’s status.  There are so many entries with the ellipsis after them that the user is forced to click on each to see the response.</p>
<p><a href="http://focusblog.iatric.com/wp-content/uploads/2010/03/ClinicalPanels1.png"><img class="alignnone size-full wp-image-554" title="ClinicalPanels" src="http://focusblog.iatric.com/wp-content/uploads/2010/03/ClinicalPanels1.png" alt="Clinical Panels" width="500" height="277" /></a></p>
<p>This results in a very clunky workflow.  If you count the keystrokes required to view the first (and shortest) entry in this example, the user would have to use 10 keystrokes.  This may irritate users and in some cases, the user may think the beginning of the entry is intuitive and assume the remainder of the response in order to save time. However, this represents bad practice and could result in compromised patient safety.  For instance, the “Gastrointestinal” entry has two responses, which are both truncated with an ellipsis.  They are “Bowel Soun…” and “Abdomen D…”  Upon clicking on the row, the user sees that the entry is “Bowel Sounds Hypoactive” and “Abdomen Distended.”  The user can then sweep the mouse to the bottom right of the screen, click close and return to the assessment.  To see all of the entries on this screen, the user will have to click 40 times.  That is not a typo.  FORTY clicks!  Wow.  There is no apparent method to widen the columns and no apparent method to use that blue space to the right of my last column.  It’s just sitting there, teasing me.  Sure would be a good place for the rest of my results.  Hmmmmm.</p>
<p>How do you think your clinicians will react to this method of chart review?  Can this, will this meet their needs?</p>
<p  class="related_post_title">Related Posts</p><ul class="related_post"><li>January 29, 2010 -- <a href="http://focusblog.iatric.com/2010/01/29/finding-your-way-around-6-x/" title="Finding your way around 6.x">Finding your way around 6.x</a> (0)</li><li>January 13, 2010 -- <a href="http://focusblog.iatric.com/2010/01/13/report-designer-part-2-a-detailed-tour/" title="Report Designer Part 2, A Detailed Tour">Report Designer Part 2, A Detailed Tour</a> (1)</li><li>December 4, 2009 -- <a href="http://focusblog.iatric.com/2009/12/04/all-show-and-no-go/" title="All Show and No Go">All Show and No Go</a> (1)</li><li>November 17, 2009 -- <a href="http://focusblog.iatric.com/2009/11/17/please-pass-the-ketchup/" title="Please Pass the Ketchup">Please Pass the Ketchup</a> (2)</li><li>November 9, 2009 -- <a href="http://focusblog.iatric.com/2009/11/09/focus-whenwhere/" title="FOCUS:  When/Where">FOCUS:  When/Where</a> (1)</li></ul>]]></content:encoded>
			<wfw:commentRss>http://focusblog.iatric.com/2010/03/11/restricted-view-may-leave-them-wanting-more/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nursing Documentation: It&#8217;s a Whole New World</title>
		<link>http://focusblog.iatric.com/2010/02/25/nursing-documentation-its-a-whole-new-world/</link>
		<comments>http://focusblog.iatric.com/2010/02/25/nursing-documentation-its-a-whole-new-world/#comments</comments>
		<pubDate>Thu, 25 Feb 2010 14:00:35 +0000</pubDate>
		<dc:creator>Janet Clarke</dc:creator>
				<category><![CDATA[Clinician's View]]></category>
		<category><![CDATA[FOCUS]]></category>
		<category><![CDATA[Learning More]]></category>
		<category><![CDATA[MEDITECH]]></category>
		<category><![CDATA[client server]]></category>
		<category><![CDATA[clinicians]]></category>
		<category><![CDATA[dictionary]]></category>
		<category><![CDATA[horizontal scroll]]></category>
		<category><![CDATA[interventions]]></category>
		<category><![CDATA[magic community]]></category>
		<category><![CDATA[magic users]]></category>
		<category><![CDATA[medications]]></category>
		<category><![CDATA[patient assignment]]></category>
		<category><![CDATA[patient care system]]></category>
		<category><![CDATA[patient data]]></category>
		<category><![CDATA[vertical scroll]]></category>

		<guid isPermaLink="false">http://focusblog.iatric.com/?p=495</guid>
		<description><![CDATA[by Janet Clarke When you consider the impact that a 6.x migration would have on your end-users, bear in mind that a significant amount of time will need to be arranged for the re-education of the clinicians who will be using the PCS (NUR) module. The documentation routines in 6.x will feel somewhat familiar to [...]]]></description>
			<content:encoded><![CDATA[<p><strong>by Janet Clarke</strong></p>
<p>When you consider the impact that a 6.x migration would have on your end-users, bear in mind that a significant amount of time will need to be arranged for the re-education of the clinicians who will be using the PCS (NUR) module. The documentation routines in 6.x will feel somewhat familiar to current Client/Server (C/S) users, but very different to those currently in the MAGIC community.</p>
<p>First off, there is a change in the lingo. For MAGIC users who are unaware, the NUR Module is called Patient Care System (PCS) in C/S and 6.x.</p>
<p>In C/S and 6.x, MEDITECH’s Status Board is required to access a nurse’s patient list. This functionality has been available for some time in MAGIC but is not required.</p>
<p>The 6.x Status Board has a different look and feel than its MAGIC and C/S predecessors. The new Status Board has two main sections. The top section displays a list of an individual clinician’s patients with a spreadsheet array. The patient assignment editing routines are available on buttons at the bottom of this screen. Access to alternate lists is set up in the PCS Access/User Preference dictionary.</p>
<p>The patient list may be set up with pinned columns and a horizontal scroll for data that does not fit within the initial display. The functionality is somewhat improved over earlier versions as users may use click functionality within this section to view more information such as interventions or medications that are due, or new orders or lab results.</p>
<div id="attachment_505" class="wp-caption alignnone" style="width: 510px"><a href="http://focusblog.iatric.com/wp-content/uploads/2010/02/4.01-Status-Board-Patient-List1.png" target="_blank"><img class="size-full wp-image-505" title="Status Board - Patient List" src="http://focusblog.iatric.com/wp-content/uploads/2010/02/4.01-Status-Board-Patient-List1.png" alt="Status Board - Patient List" width="500" height="356" /></a><p class="wp-caption-text">Click to enlarge</p></div>
<p>The second section of the Status Board displays below the first and is the source for further patient detail. This is a curious design because it requires the user to look in two different places on the same screen to view patient data. If the highlighted patient happens to be at the top of a lengthy patient list that requires a vertical scroll, then the user may not be able to visualize both sources of patient data on the screen at the same time!</p>
<div id="attachment_499" class="wp-caption alignnone" style="width: 510px"><a href="http://focusblog.iatric.com/wp-content/uploads/2010/02/4.02-Status-Board-Patient-List-Scrolled.png" target="_blank"><img class="size-full wp-image-499" title="Status Board - Patient List - Scrolled Down" src="http://focusblog.iatric.com/wp-content/uploads/2010/02/4.02-Status-Board-Patient-List-Scrolled.png" alt="Status Board - Patient List - Scrolled Down" width="500" height="356" /></a><p class="wp-caption-text">Click to enlarge.</p></div>
<p>This two tier Status Tier design could contribute to the user not having access to complete patient data at one glance – with ramifications in terms of clinical decision making.</p>
<p>More 6.x Status Board scrutiny with the next post &#8230;</p>
<p  class="related_post_title">Related Posts</p><ul class="related_post"><li>December 9, 2009 -- <a href="http://focusblog.iatric.com/2009/12/09/there%e2%80%99s-more-to-the-mis-story/" title="There’s More to the (MIS) Story">There’s More to the (MIS) Story</a> (0)</li></ul>]]></content:encoded>
			<wfw:commentRss>http://focusblog.iatric.com/2010/02/25/nursing-documentation-its-a-whole-new-world/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

