<?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>Jerry Fahrni &#187; Integration</title>
	<atom:link href="http://jerryfahrni.com/tag/integration/feed/" rel="self" type="application/rss+xml" />
	<link>http://jerryfahrni.com</link>
	<description>Pharmacy Informatics and Technology</description>
	<lastBuildDate>Wed, 23 May 2012 14:29:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Integration and standardization are still stumbling blocks in healthcare</title>
		<link>http://jerryfahrni.com/2009/08/integration-and-standardization-are-still-stumbling-blocks-in-healthcare/</link>
		<comments>http://jerryfahrni.com/2009/08/integration-and-standardization-are-still-stumbling-blocks-in-healthcare/#comments</comments>
		<pubDate>Wed, 19 Aug 2009 19:13:18 +0000</pubDate>
		<dc:creator>Jerry Fahrni</dc:creator>
				<category><![CDATA[Barcoding]]></category>
		<category><![CDATA[Pharmacy Informatics]]></category>
		<category><![CDATA[BCMA]]></category>
		<category><![CDATA[Integration]]></category>
		<category><![CDATA[Standardization]]></category>

		<guid isPermaLink="false">http://jerryfahrni.com/?p=1504</guid>
		<description><![CDATA[I spent a good chunk of my morning in meetings and workgroups for the implementation of our barcode medication administration system (BCMA). Most of these sessions are dominated by nursing as many consider BCMA a nursing system. The largest piece of the puzzle for pharmacy is getting the medications barcoded and ready for scanning prior [...]]]></description>
			<content:encoded><![CDATA[<p>I spent a good chunk of my morning in meetings and workgroups for the implementation of our barcode medication administration system (BCMA). Most of these sessions are dominated by nursing as many consider BCMA a nursing system.<br />
<span id="more-1504"></span></p>
<p>The largest piece of the puzzle for pharmacy is getting the medications barcoded and ready for scanning prior to dispensing. When the district wide barcode initiative was designed, the department of pharmacy evaluated various options, made a decision, installed a barcode system from Talyst (AutoPharm, AutoCarousel, AutoPack, AutoLabel ) and haven’t looked back. That was over 18 months ago.</p>
<p>Fast forward to today where our organization continues to wrestle with implementation of the “nursing” pieces of the puzzle. Most of the delay surrounds issues with policy and procedure. The meetings I attend are often “lively” as nursing units throughout the hospital debate the best way to handle certain issues. I am always surprised to hear the number of ways that nursing units interpret the medication administration process. Each unit thinks they are unique. In fact, that was the battle cry of the day; “we’re different”.</p>
<p>In addition to the range of ways to do things, many of our units utilize systems that are poorly integrated with the rest of the hospital. L&amp;D, ED and OR all use stand alone systems to document and chart patient information. Because these systems are not integrated with the rest of our systems, the information is not immediately retrievable from other areas of the hospital. Being the lone pharmacy representative, I had to ask how the information was made available to nurses and physicians when the patient was transferred. The answer was simple, yet staggering; they print the records out and send them with the patient. Huh? We pride ourselves on being on the cutting edge of technology (for hospitals), but provide paper copies of information that is already available in an electronic format. &lt;*sigh*&gt;</p>
<p>As we move in the direction of a complete electronic medical record, this becomes an unacceptable practice. Segregation of systems based on practice environment, i.e L&amp;D, ED, OR, pediatrics, etc., must be eliminated if we really expect to develop a universally accepted electronic medical record. Electronic records should contain all pieces of information and be readily accessible from any computer at any time. Access should be independent of operating system, browser, or device.</p>
]]></content:encoded>
			<wfw:commentRss>http://jerryfahrni.com/2009/08/integration-and-standardization-are-still-stumbling-blocks-in-healthcare/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Beyond patient safety with technology and automation</title>
		<link>http://jerryfahrni.com/2009/07/beyond-patient-safety-with-technology-and-automation/</link>
		<comments>http://jerryfahrni.com/2009/07/beyond-patient-safety-with-technology-and-automation/#comments</comments>
		<pubDate>Tue, 07 Jul 2009 02:35:53 +0000</pubDate>
		<dc:creator>Jerry Fahrni</dc:creator>
				<category><![CDATA[Automation]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Efficiency]]></category>
		<category><![CDATA[Integration]]></category>
		<category><![CDATA[Pharmacy Automation]]></category>
		<category><![CDATA[Pharmacy Technology]]></category>
		<category><![CDATA[Talyst]]></category>

		<guid isPermaLink="false">http://jerryfahrni.com/?p=979</guid>
		<description><![CDATA[I had reason to do some thinking about healthcare automation over the weekend, and after much thought decided that healthcare, specifically pharmacy, was a little strange in several ways. As an industry, healthcare rarely looks beyond patient safety when talking about technology and automation. Let&#8217;s face it, patient safety is the rally cry for any [...]]]></description>
			<content:encoded><![CDATA[<p>I had reason to do some thinking about healthcare automation over the weekend, and after much thought decided that healthcare, specifically pharmacy, was a little strange in several ways. As an industry, healthcare rarely looks beyond patient safety when talking about technology and automation. Let&#8217;s face it, patient safety is the rally cry for any department in need of a jumpstart to complete a project that has stalled for one reason or another. Unfortunately the investment of time, energy and capital resources typically stops immediately after implementation secondary to meeting the patient safety goal. However, this model seldom allows for technology and automation to be taken to the next logical step.<br />
<span id="more-979"></span></p>
<p>In general, technology is ideal for improving patient safety, but it can do so much more. Technology and automation offer several other benefits including:</p>
<li>Freeing up pharmacist&#8217;s time so they can move to the bedside. Technology can decrease time spent in the pharmacy by streamlining processes that require a pharmacist’s attention. In addition, technology like tablet PCs, mobile phones, and anytime/anywhere access to drug information and evidence based medicine resources via &#8220;the web&#8221; make the mobile pharmacist a reality. Literature has shown that a pharmacist at the bedside is better for the patient in several ways, including decreased drug related administration errors, fewer adverse events and more cost effective drug therapy. This is not only good for the patient, but can save thousands of dollars in avoided adverse events.</li>
<li>Enhanced workflow. Continued implementation and use of automated systems such as those available from <a href="http://talyst.com/">Talyst</a> (<a href="http://talyst.com/Products/Software/AutoPharm">AutoPharm</a>, <a href="http://talyst.com/Products/Hardware/AutoCarousel">AutoCarousel</a>, <a href="http://talyst.com/Products/Hardware/AutoLabel">AutoLabel</a>, <a href="http://talyst.com/Products/Hardware/AutoPack">AutoPack</a>), clearly impact the efficiency and standardization of workflow in the pharmacy. If you’ve ever been in an inpatient pharmacy, then you’ll understand the importance of workflow. Unfortunately system improvement typically stops immediately after implantation. It is often difficult to convince those in healthcare to continue developing these systems after deployment secondary to the “if it ain’t broke, don’t fix it” mentality. It is important for hospital administration to realize that an efficient pharmacy not only saves money in labor costs, but helps move pharmacists toward the bedside as mentioned above.</li>
<li>Inventory control and drug security. This may seem obvious to everyone, but often times continued development and advancements in technology are necessary to stay ahead of the “work-arounds”. Human nature and willful disregard for procedure frequently trump our technology. Doing the wrong thing needs to be harder than doing the right thing. This leads to better control of inventory and less diversion (i.e. it saves money).</li>
<li>Improved technology can lead to better integration of various healthcare systems. It seems like every department in the hospital has a system specifically designed for them and no one else. This leads to an increased need for support personnel in the IT department as well as resources dedicated to upgrading and maintaining those systems. Integration is a key component to decreasing healthcare costs, and one area that I believe is frequently overlooked.</li>
<p>While it may be important to think of patient safety as the primary reason for the implementation of new and advanced technology, one must not forget the fringe benefits that can save healthcares systems thousands of dollars both directly and indirectly through pharmacy intervention at the bedside, increased efficiency in the pharmacy, and integration with existing system resulting in less time required for maintenance and upgrades. Technology can do so much more.</p>
]]></content:encoded>
			<wfw:commentRss>http://jerryfahrni.com/2009/07/beyond-patient-safety-with-technology-and-automation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

