<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.3.3" -->
<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/"
	>

<channel>
	<title>Medical Connectivity &#187; Uncategorized</title>
	<link>http://medicalconnectivity.com</link>
	<description></description>
	<pubDate>Tue, 09 Feb 2010 17:31:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
	<language>en</language>
			<item>
		<title>Medical Device System Network Install Issues</title>
		<link>http://medicalconnectivity.com/2009/09/22/medical-device-system-networking-issues/</link>
		<comments>http://medicalconnectivity.com/2009/09/22/medical-device-system-networking-issues/#comments</comments>
		<pubDate>Tue, 22 Sep 2009 16:37:19 +0000</pubDate>
		<dc:creator>Tim Gee</dc:creator>
		
		<category><![CDATA[Healthcare IT]]></category>

		<category><![CDATA[Standards &amp; Regulatory]]></category>

		<category><![CDATA[Uncategorized]]></category>

		<category><![CDATA[Wireless Medical Devices]]></category>

		<guid isPermaLink="false">http://medicalconnectivity.com/2009/09/22/medical-device-system-networking-issues/</guid>
		<description><![CDATA[If a medical device system runs on a network (physically separate or as a VLAN on your hospital enterprise network) the network is part of the medical device.]]></description>
			<content:encoded><![CDATA[<p>Last week there was an interesting discussion on the Biomed Listserv about network installation for patient monitoring systems. Emphasis highlighting key issues and best practices are mine. The discussion started with a question from Scott Skinner:</p>
<blockquote><p>I&#8217;m curious if anyone has been successful using their own vendors to pull cables for monitoring installations.  With the monitoring OEM we work with, they simply get a local subcontractor to do the cable pulls.</p>
<p>So this would involve breaking future monitoring packages up into two quotes:  one for the actual technology itself (and associated installation and implementation), and then one for just the cable pull work.  The latter would get bid out, and the OEM could compete against other vendors.</p>
<p>Of course, the OEM can just take the profit they would have made on the cable pull and add that to the cost of the equipment bid.  One would need to find a way to watch that carefully.</p></blockquote>
<p>Which lead to a critical observation from Craig Muehling:</p>
<blockquote><p>We have started pulling our own cable for monitoring installations. I have one happening now and I&#8217;m not exactly pleased how it&#8217;s working out. I won&#8217;t mention and names, [vendor name removed] but they make their equipment charges per drop whether you have any drops or not.</p>
<p>I would still like our [networking] vendor to do the networking, ie: install and configure switches and physically plug patch cables into the switches. Seems easy, but the way they [the patient monitoring vendor] charge it&#8217;s really not much less than if they did the whole job. I think from now on, we will have to take on the entire networking job.</p>
<p>I have learned a lesson from this last installation and will scrutinize the quotes closer from now on, but with their charging structure<br />
(supposedly) there&#8217;s not a lot of options. Either we do the entire job, or they make lots and lots of money for relatively little work.</p></blockquote>
<p>Here&#8217;s how they do it at the Mayo Clinic, from Steve May:</p>
<blockquote><p>We have our own low voltage and high voltage contractors for all in-house cable pulling, to include data pulls and all project related work, so <em>cable pulling and wiring costs are never part of an installation package, but an infrastructure cost which we earmark as Capital expenditures and plan/budget annually.</em> Bids &amp; labor costs are renewed by Purchasing every 2 years and our preferred contractors are all able to bid on both project services &amp; time &amp; material services. <a href="http://medicalconnectivity.com/2009/09/22/medical-device-system-networking-issues/#more-1268" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://medicalconnectivity.com/2009/09/22/medical-device-system-networking-issues/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Market Trends Series: Wireless Connectivity</title>
		<link>http://medicalconnectivity.com/2009/09/17/market-trends-series-wireless-connectivity/</link>
		<comments>http://medicalconnectivity.com/2009/09/17/market-trends-series-wireless-connectivity/#comments</comments>
		<pubDate>Thu, 17 Sep 2009 22:34:45 +0000</pubDate>
		<dc:creator>Brian McAlpine</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<category><![CDATA[Wireless Medical Devices]]></category>

		<guid isPermaLink="false">http://medicalconnectivity.com/2009/09/17/market-trends-series-wireless-connectivity/</guid>
		<description><![CDATA[There are quite a few device manufacturers that offer wireless in their devices. However, there are really only a few vendors that have done wireless right.]]></description>
			<content:encoded><![CDATA[<p><!--[if gte mso 9]&amp;gt;           &amp;lt;![endif]--></p>
<p><!--[if gte mso 9]&amp;gt;     Normal   0               false   false   false      EN-US   X-NONE   X-NONE                                                                                                     &amp;lt;![endif]--><!--[if gte mso 9]&amp;gt;                                                                                                                                                                                                                                                                                                                                                                                                                                &amp;lt;![endif]--> <!--  /* Font Definitions */  @font-face 	{font-family:"Cambria Math"; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:1; 	mso-generic-font-family:roman; 	mso-font-format:other; 	mso-font-pitch:variable; 	mso-font-signature:0 0 0 0 0 0;} @font-face 	{font-family:Calibri; 	panose-1:2 15 5 2 2 2 4 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:swiss; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1073750139 0 0 159 0;}  /* Style Definitions */  p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-unhide:no; 	mso-style-qformat:yes; 	mso-style-parent:""; 	margin:0in; 	margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman";} .MsoChpDefault 	{mso-style-type:export-only; 	mso-default-props:yes; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} .MsoPapDefault 	{mso-style-type:export-only; 	margin-bottom:10.0pt; 	line-height:115%;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.0in 1.0in 1.0in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;} --> <!--[if gte mso 10]&amp;gt;   /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-priority:99; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin-top:0in; 	mso-para-margin-right:0in; 	mso-para-margin-bottom:10.0pt; 	mso-para-margin-left:0in; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:"Times New Roman"; 	mso-fareast-theme-font:minor-fareast; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin;}  &amp;lt;![endif]-->Fresh back from the <a href="http://medicalconnectivity.com/2009/09/17/medical-device-connectivity-conference-wrap-up/">MDC Conference</a> in Boston last week - great inaugural event and a perfect venue at Harvard Medical School. Thanks to Tim and the conference organizers &#8212; I personally heard many very positive comments from a number of attendees.</p>
<p>As the healthcare market continues to evolve, so do solutions related to medical device connectivity. I would like to invite you to join me in a dialog over the next several weeks - perhaps even on an ongoing basis - that will explore the trends that are affecting the market of medical device connectivity.  The idea is to have an open and interactive discussion on where the technology is today, where it needs to go, and what is driving the market.  Remember that this is just my viewpoint as I see things based on my experiences. Perhaps your experiences and perspective are similar or maybe they are completely different.</p>
<p>So, let’s begin.  The first trend I’d like to talk about is wireless medical devices and the impact on connectivity.  We all know that more and more medical devices are becoming wireless and therefore more mobile, for example more and more smart IV pumps (smart pumps) are being implemented every day. One key aspect of wireless technology is the fact that wireless enables devices to become untethered, and therefore a mobile use case is enabled. Wireless medical devices such as smart IV pumps and patient monitors add to the list of connectivity challenges because, from a pure connectivity perspective, they have basically eliminated one problem (the use of a serial data cable) and often create others. Once a medical device is no longer connected to something that facilitates data integration (like a bedside terminal server for example), then part of the connectivity and integration problem often shifts onto the manufacturer of the medical device.<br />
 <a href="http://medicalconnectivity.com/2009/09/17/market-trends-series-wireless-connectivity/#more-1265" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://medicalconnectivity.com/2009/09/17/market-trends-series-wireless-connectivity/feed/</wfw:commentRss>
		</item>
		<item>
		<title>The Connectologist is Out</title>
		<link>http://medicalconnectivity.com/2008/08/24/the-connectologist-is-out/</link>
		<comments>http://medicalconnectivity.com/2008/08/24/the-connectologist-is-out/#comments</comments>
		<pubDate>Mon, 25 Aug 2008 04:03:08 +0000</pubDate>
		<dc:creator>Tim Gee</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://medicalconnectivity.com/2008/08/24/the-connectologist-is-out/</guid>
		<description><![CDATA[I will be on vacation for the next 8 days, returning September 2nd.
]]></description>
			<content:encoded><![CDATA[<p>I will be on vacation for the next 8 days, returning September 2nd.</p>
]]></content:encoded>
			<wfw:commentRss>http://medicalconnectivity.com/2008/08/24/the-connectologist-is-out/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Connectivity - The Book</title>
		<link>http://medicalconnectivity.com/2008/03/03/connectivity-the-book/</link>
		<comments>http://medicalconnectivity.com/2008/03/03/connectivity-the-book/#comments</comments>
		<pubDate>Tue, 04 Mar 2008 04:07:52 +0000</pubDate>
		<dc:creator>Tim Gee</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://medicalconnectivity.com/2008/03/03/connectivity-the-book/</guid>
		<description><![CDATA[I can think of several terrific contributors.]]></description>
			<content:encoded><![CDATA[<p><img src="http://medicalconnectivity.com/wp-content/uploads/2008/Writer.jpg" alt="LibraryLindy as rich guy" height="186" width="200" />Last October I was asked if I&#8217;d ever written a book. The answer was, and remains, that I have not. But then I&#8217;m not aware of any else having written a book on medical connectivity. After some thought, it seems that the market may be ready for such a literary epic. (I&#8217;m going to have to start wearing turtlenecks or ascots and smoking a pipe.)</p>
<p>The past few weeks I&#8217;ve been talking to people asking about publishers and such. I&#8217;ve got a few leads, but if you can suggest anyone to contact please let me know.</p>
<p>Here&#8217;s what I&#8217;ve been able to noodle out: <a href="http://medicalconnectivity.com/2008/03/03/connectivity-the-book/#more-1157" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://medicalconnectivity.com/2008/03/03/connectivity-the-book/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Tuesday Morning at HIMSS</title>
		<link>http://medicalconnectivity.com/2008/02/26/tuesday-morning-at-himss/</link>
		<comments>http://medicalconnectivity.com/2008/02/26/tuesday-morning-at-himss/#comments</comments>
		<pubDate>Tue, 26 Feb 2008 13:05:12 +0000</pubDate>
		<dc:creator>Tim Gee</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://medicalconnectivity.com/2008/02/26/tuesday-morning-at-himss/</guid>
		<description><![CDATA["How would your marketing guy describe this?" His reply, "I am the marketing guy." ]]></description>
			<content:encoded><![CDATA[<p><img src="http://medicalconnectivity.com/wp-content/uploads/2008/Intellidot.jpg" alt="Intellidot" height="269" width="350" /></p>
<p>A bleary eyed day 3 of HIMSS. There&#8217;s a lot of energy at the show this year - the exhibit hall is full with both attendees and exhibitors. Many write about the theme or hot topics at events. HIMSS has gotten so big, with such depth, that its easy to find that your interests are the hot topic at HIMSS. There have been some interesting announcements, which I&#8217;ll post on in the coming days. Many vendors have refined or shifted their strategies in ways that will impact their future products and customers.Yesterday I caught up with a very old friend. We started attending HIMSS over 20 years ago. He observed that some things never change.</p>
<p>There&#8217;s still a tremendous amount of spin and vapor ware. Sure there are new vendors and fresh faces but an alarming number of vendors still can&#8217;t describe their product in understandable language or articulate their value proposition beyond an alphabet soup of acronyms, &#8220;glamor words&#8221; and jargon. In meeting with one vendor yesterday, I asked repeatedly, &#8220;what is this?&#8221; In frustration I asked, &#8220;how would your marketing guy describe this?&#8221; His reply, &#8220;I am the marketing guy.&#8221; Uh, open mouth, insert foot&#8230;</p>
<p>Pictured at top is the only mobile device at HIMSS (or anywhere else) purpose built for health care from <a href="http://www.intellidot.net/">Intellidot</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://medicalconnectivity.com/2008/02/26/tuesday-morning-at-himss/feed/</wfw:commentRss>
		</item>
		<item>
		<title>HIMSS Pre-show</title>
		<link>http://medicalconnectivity.com/2008/02/22/himss-pre-show/</link>
		<comments>http://medicalconnectivity.com/2008/02/22/himss-pre-show/#comments</comments>
		<pubDate>Fri, 22 Feb 2008 18:48:46 +0000</pubDate>
		<dc:creator>Tim Gee</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<category><![CDATA[HIMSS]]></category>

		<guid isPermaLink="false">http://medicalconnectivity.com/2008/02/22/himss-pre-show/</guid>
		<description><![CDATA[Come to Meet the Bloggers]]></description>
			<content:encoded><![CDATA[<p><img src="http://medicalconnectivity.com/wp-content/uploads/2008//himssladies.jpg" alt="HIMSS Greeters" /><br class="webkit-block-placeholder" />I&#8217;m on my way to HIMSS today, and really looking forward to this year&#8217;s conference and exhibits.There&#8217;s lots of interesting rumblings among the market segments that I follow.</p>
<p>There will be big news among RTLS/RFID vendors and I&#8217;m expecting some announcements from a number of connectivity companies.</p>
<p>As in years past, I&#8217;m attending as a contributing editor for MX Magazine. As such I&#8217;ve been inundated by PR folks for appointments. For the first time, I&#8217;ve used an <a href="http://http://planner.zoho.com/public/publicpage.jsp?PageId=207183">online schedule</a> to coordinate things. HIMSS only comes once a year, and I always try to make the most of it.</p>
<p>Meet the Bloggers</p>
<p>I&#8217;m very late with a post this year, but there <span style="font-style: italic" class="Apple-style-span">will</span> be a meet the bloggers gathering during the HIMSS opening reception - that&#8217;s Sunday between 5 and 8 pm (here&#8217;s a <a href="http://www.himssconference.org/networking/openingRec.aspx">link</a>).  Look for the big blue and orange sign with &#8220;Meet the Bloggers&#8221; and come by and say hi.</p>
]]></content:encoded>
			<wfw:commentRss>http://medicalconnectivity.com/2008/02/22/himss-pre-show/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Greetings</title>
		<link>http://medicalconnectivity.com/2008/02/20/greetings/</link>
		<comments>http://medicalconnectivity.com/2008/02/20/greetings/#comments</comments>
		<pubDate>Wed, 20 Feb 2008 14:57:46 +0000</pubDate>
		<dc:creator>Tim Gee</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://medicalconnectivity.com/2008/02/20/greetings/</guid>
		<description><![CDATA[A whole new look and feel]]></description>
			<content:encoded><![CDATA[<p>What you see today is the new design for the site. I&#8217;ve been contemplating this for some time. The biggest issue was getting the 1,100+ previous posts created using the old software into this system. That should be done in the next few hours.</p>
<p>Enjoy!</p>
]]></content:encoded>
			<wfw:commentRss>http://medicalconnectivity.com/2008/02/20/greetings/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Patient Flow Recommendations and Predictions</title>
		<link>http://medicalconnectivity.com/2007/10/08/patient-flow-recommendations-and-predictions/</link>
		<comments>http://medicalconnectivity.com/2007/10/08/patient-flow-recommendations-and-predictions/#comments</comments>
		<pubDate>Tue, 09 Oct 2007 03:28:39 +0000</pubDate>
		<dc:creator>Tim Gee</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://medicalconnectivity.com/2007/10/08/patient-flow-recommendations-and-predictions/</guid>
		<description><![CDATA[
Research firm Arketi sent me a survey on hospital patient flow. Sponsored by patient flow software vendor StatCom, the survey sought to quantify the patient flow problem (how many ED boarders, hours on divert, room turn over times, etc.) and identify the departments contributing to, or ameliorating hospital patient throughput. This will all be good [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://medicalconnectivity.com/gems/Blog%20Photos/StatCom-Hospital.jpg" alt="StatCom-hospital" align="right" border="1" height="246" hspace="4" vspace="4" width="200" /></p>
<p>Research firm <a href="http://www.arketi.com/">Arketi</a> sent me a survey on hospital patient flow. Sponsored by patient flow software vendor <a href="http://www.statcom.com/">StatCom</a>, the survey sought to quantify the patient flow problem (how many ED boarders, hours on divert, room turn over times, etc.) and identify the departments contributing to, or ameliorating hospital patient throughput. This will all be good marketing data once the study is compiled.</p>
<p><span style="font-weight: bold">Lack of Data</span><br />
I was struck by a couple things missing from the study. From my experience, the biggest challenge facing hospitals seeking to improve patient throughput is the near total absence of performance data. Unless an effort is made to manually log performance data - with the oversight to ensure it is accurate and complete - hospitals have little data available to them. Such manual data gathering operations are expensive, time consuming and hard to sustain on a broad basis or for an extended period of time.</p>
<p>As the canary in the coal mine, the Emergency Department is the most common source for any detailed data, and often the squeaky wheel pushing for patient flow improvements. Consequently, data about hours on diversion, ED patient flow metrics, patient boarding, and reasons for boarding frequently represent the best patient flow data in hospitals. Once you get beyond the ED, available data drops off quickly.</p>
<p>Frequently, the best data available is aggregate ADT data that shows length of stay (LOS), transfers and discharges among individual departments and the hospital as a whole. Have you looked at your ADT data lately? Found all those duplicate transaction codes for decommissioned units (still in use)? Does everyone who enters ADT transactions or uses the data have the same understanding of what all those codes and locations really mean and when to use them? If you;ve not addressed this issue (cleaning up your tables, training users, auditing data) in the past year or two, or don&#8217;t want to ruin your day (it is Monday after all) let sleeping dogs lie.</p>
<p>The paucity of detailed reliable data to gage patient throughput is a significant hospital need, and I think a key justification for buying a system like StatCom&#8217;s, that is not addressed in the survey. Having some quantitative market research as proof to this need would be something I&#8217;d want if I was a patient flow software product manager.</p>
<p><span style="font-weight: bold">Patient Care Methodologies</span><br />
The other thing that struck me was the lack of any questions about patient care methodologies that create patient flow bottlenecks. Most hospitals are structured and managed based on industrial principles from 30 or 40 years ago. Back in the 1980s before DRGs and prospective reimbursement when hospitals had excess capacity, setting aside a fixed number of beds (and equipment) for specific categories of patients worked pretty well - excess capacity hid a multitude of sins.</p>
<p>As falling reimbursement wrung out excess capacity, the fundamental weaknesses of allocating fixed resources on the expectation that a certain consistent number of patients will utilize those resources became evident. In manufacturing, just-in-time management tools were used to lower costs. The fact is there are no just-in-time patients. Just like manufacturers learned that market demand can&#8217;t be reliably forecasted, and implemented flexible manufacturing concepts, hospitals must move beyond rigid patient care strategies. Besides creating patient flow bottlenecks in units like critical care and telemetry, conventional care methodologies can result in unnecessary patient transfers (something else the survey didn&#8217;t explore).</p>
<p>The most common example of a patient care methodology analogous to modern manufacturing processes goes by various names: variable acuity units, flexible monitoring, or universal beds. Whatever you call it, it means providing patient care in one on-service unit and not transferring the patient every time their acuity changes. Patient transfers are bad; each transfer adds a day to the patients LOS, and represents an opportunity for adverse events resulting from less than perfect patient hand-offs. Manufacturing has developed many techniques to be more flexible, like <a href="http://en.wikipedia.org/wiki/Cellular_manufacturing">cellular manufacturing</a>, <a href="http://www.valuebasedmanagement.net/methods_kaizen.html">kaizen</a>, the <a href="http://medicalconnectivity.com/categories/patientFlow/2005/06/07.html">Toyota Way</a>, <a href="http://www.lean.org/">LEAN</a> and <a href="http://en.wikipedia.org/wiki/Six_Sigma">Six Sigma</a> - and many of these tools have been adopted by innovative hospitals.</p>
<p>The best way to minimize critical care and telemetry as patient flow bottlenecks is through variable acuity units, where patients receive the most appropriate level of care in the lowest cost setting. You will never be able to match the number of critical care and telemetry beds to the exact number of patients who need them. You can waste money building too many of these high acuity beds - and don&#8217;t forget that about 15% of the patients in your critical care and tele beds right now don&#8217;t meet admit criteria and should be in other units. Or you can continue to go on ambulance diversion. A patient flow system like StatCom&#8217;s can be a useful tool in implementing variable acuity care. Good acuity scoring tools like <a href="http://www.atstaff.com/">ClairVia</a> are also helpful.<br />
<br style="font-weight: bold" /><span style="font-weight: bold">Prognostications and Prevarications</span><br />
Let me close by offering some predictions. Thankfully, most of these predictions are perfectly safe because any outcome can&#8217;t be verified. First off, the StatCom survey will show that the two departments representing the biggest patient flow bottlenecks are critical care and telemetry.</p>
<p>I see solid growth and adoption for the patient flow application market. McKesson&#8217;s <a href="http://www.mckesson.com/en_us/McKesson.com/Our+Businesses/McKesson+Provider+Technologies/Newsroom/McKesson+Announces+Definitive+Agreement+to+Acquire+Awarix.html">acquisition</a> of <a href="http://awarix.com/">Awarix</a> is further validation of anticipated growth. The most important justification for a solution like StatCom&#8217;s is that you can&#8217;t manage what isn&#8217;t measured. The market right now is still an <a href="http://en.wikipedia.org/wiki/Crossing_the_Chasm">early adopter market</a> (that&#8217;s marketing-speak for those wild eyed innovators who will try anything). The generation of products coming to market now represents a big improvement over earlier solutions. These systems still require certain enabling technologies to work effectively in hospitals run by anyone but Jack Welch. These applications will provide a plethora of useful data, across the enterprise. As the market matures, hospitals will better learn to pick the good patient flow applications and get better at wringing the most value from them.</p>
<p>Oh, and donâ€™t throw six or seven figure consulting contracts at the problem. The 80/20 rule says that youâ€™ll get 80% of the value from only 20% of the patient flow issues excruciatingly documented by the hoard of fresh MBA graduates who descend on your hapless staff. Empower an internal champion and find someone (maybe even a vendor) who can quickly find the bottlenecks with the biggest impact. Buy a patient flow application, and converge your patient flow findings with your software implementation targeting the &#8220;big bang&#8221; opportunities. You&#8217;ll still spend six or seven figures, but most if it will be on a software application that will deliver real value for years - as opposed to the one-time shot of a big consulting gig.</p>
<p>As patient flow problems increase, hospitals will transition from boarding patients awaiting an inpatient room in the ED to placing them up on their on-service unit. There&#8217;s lots of rational patient safety and financial reasons to do this, and the outrage and consternation evoked by such a change will eventually give way to reason. And don&#8217;t get snowed by the &#8220;fire codes don&#8217;t allow us to leave patients in hallways&#8221; excuse. They&#8217;re in hallways in the ED, aren&#8217;t they?</p>
<p>Finally, the federal government&#8217;s double edged strategy for transforming health care (reduced reimbursement to drive change, and increased visibility of provider performance to increase quality) will eventually include public disclosure of ED waiting times, reporting of time on ambulance diversion, and statistics on the number of patients boarded. This will probably occur after vendors &#8220;cross the chasm&#8221; and the early majority of the hospital market starts to implement patient flow solutions. This visibility will eventually drive the market laggards to adopt.</p>
<p>Pictured above is the hospital illustration from StatCom&#8217;s home page - I like the 8-bit retro graphic design.</p>
]]></content:encoded>
			<wfw:commentRss>http://medicalconnectivity.com/2007/10/08/patient-flow-recommendations-and-predictions/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Reference Website: bmesource.org</title>
		<link>http://medicalconnectivity.com/2007/10/01/reference-website-bmesourceorg/</link>
		<comments>http://medicalconnectivity.com/2007/10/01/reference-website-bmesourceorg/#comments</comments>
		<pubDate>Tue, 02 Oct 2007 01:07:42 +0000</pubDate>
		<dc:creator>Tim Gee</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://medicalconnectivity.com/2007/10/01/reference-website-bmesourceorg/</guid>
		<description><![CDATA[The site bmesource.org is a compendium of web sites with the stated goal of, &#8220;sharing knowledge across the biomedical technology design community.&#8221; The site was started at Stanford University. In 2003 they opened it up to additional university contributors.
I stumbled across the sites via my server logs that showed a visitor who came from bemesource.org. [...]]]></description>
			<content:encoded><![CDATA[<p>The site <a href="http://171.65.102.151/%7Ebmesource/Start">bmesource.org</a> is a compendium of web sites with the stated goal of, &#8220;sharing knowledge across the biomedical technology design community.&#8221; The site was started at Stanford University. In 2003 they opened it up to additional university contributors.</p>
<p>I stumbled across the sites via my server logs that showed a visitor who came from bemesource.org. The sight is pretty cool, check it out.</p>
]]></content:encoded>
			<wfw:commentRss>http://medicalconnectivity.com/2007/10/01/reference-website-bmesourceorg/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Home Use of Medical Devices Challenges FDA</title>
		<link>http://medicalconnectivity.com/2007/09/27/home-use-of-medical-devices-challenges-fda/</link>
		<comments>http://medicalconnectivity.com/2007/09/27/home-use-of-medical-devices-challenges-fda/#comments</comments>
		<pubDate>Fri, 28 Sep 2007 01:34:43 +0000</pubDate>
		<dc:creator>Tim Gee</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://medicalconnectivity.com/2007/09/27/home-use-of-medical-devices-challenges-fda/</guid>
		<description><![CDATA[
Medical Devices Today has a good post on potential safety and effectiveness issues surrounding medical devices where home use by patients is outside the scope if intended use. &#8220;Although manufacturers need FDA approval to market a device
over-the-counter directly to a patient or specifically for home use,
there are few restrictions on whether a physician can send [...]]]></description>
			<content:encoded><![CDATA[<p><img alt="Baxter-Syndeo" src="http://medicalconnectivity.com/gems/Blog%20Photos/Baxter-syndeo.jpg" align="right" border="0" height="239" hspace="4" vspace="4" width="200"></p>
<p>Medical Devices Today has <a href="http://www.medicaldevicestoday.com/2007/09/home-use-of-dev.html">a good post</a> on potential safety and effectiveness issues surrounding medical devices where home use by patients is outside the scope if intended use. &#8220;Although manufacturers need FDA approval to market a device<br />
over-the-counter directly to a patient or specifically for home use,<br />
there are few restrictions on whether a physician can send a patient<br />
home with a device that is not specifically labeled for use in the home.&#8221;</p>
<p>One of the biggest issues revolves around older devices that have been replaced and become hand-me-downs for home health. Concerns include:
<ul>
<li>Neither devices or directions for use not designed for patient use</li>
<li>Hand-me-down devices frequently missing directions for use</li>
<li>Patient purchased devices, e.g., after the  reimbursed rental period, end up getting &#8220;recycled&#8221; through eBay  - with no safeguards for proper maintenance, operation or directions for use</li>
<li>Proper distribution channel safeguards to ensure safety and effectiveness when sold retail or through other resellers</li>
</ul>
<p>Besides contemplating new regulations or legislation, the FDA is making the following responses:
<div style="margin-left: 40px;">
<p>Meanwhile, in the next six months FDA hopes to invite manufacturers<br />
to participate in its new online labeling repository for home-use<br />
devices. The voluntary repository, which will initially focus on<br />
infusion pumps, will give consumers access to the most up-to-date<br />
instructions for specific models. </p>
<p>The agency is also preparing to launch a sub-network of its MedSun<br />
adverse event reporting program called HomeNet. Participating home<br />
health agencies will be encouraged to report to FDA adverse events,<br />
including close-calls, related to devices used in the home setting. </p>
</div>
<p>Be sure to read the <a href="http://www.medicaldevicestoday.com/2007/09/home-use-of-dev.html">whole thing</a>. Pictured right is a Baxter Syndeo pump - perhaps something that might be used in the home?</p>
]]></content:encoded>
			<wfw:commentRss>http://medicalconnectivity.com/2007/09/27/home-use-of-medical-devices-challenges-fda/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
