<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Collaborative Flow</title>
	<atom:link href="http://healthcarecollaboration.com/collaborative-flow/feed/" rel="self" type="application/rss+xml" />
	<link>http://healthcarecollaboration.com/collaborative-flow/</link>
	<description>Improving Physician-Hospital Relations</description>
	<lastBuildDate>Tue, 31 Jan 2012 01:07:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Collaborative Stress Management: A New Book Review &#124; Healthcare Collaboration</title>
		<link>http://healthcarecollaboration.com/collaborative-flow/#comment-6875</link>
		<dc:creator>Collaborative Stress Management: A New Book Review &#124; Healthcare Collaboration</dc:creator>
		<pubDate>Tue, 30 Mar 2010 11:13:40 +0000</pubDate>
		<guid isPermaLink="false">http://healthcarecollaboration.com/collaborative-flow/#comment-6875</guid>
		<description>[...] absorption in their work, the flow state [...]</description>
		<content:encoded><![CDATA[<p>[...] absorption in their work, the flow state [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Collaborative Bidding</title>
		<link>http://healthcarecollaboration.com/collaborative-flow/#comment-24</link>
		<dc:creator>Collaborative Bidding</dc:creator>
		<pubDate>Tue, 15 Apr 2008 17:07:42 +0000</pubDate>
		<guid isPermaLink="false">http://healthcarecollaboration.com/collaborative-flow/#comment-24</guid>
		<description>[...] In a previous post, &#8220;Collaborative Error: The Day I Nearly Quit&#8220;, I wrote that the old paradigm of physicians and nurses taking care of clinical dimensions of care and administrators keeping finance and operations to themselves does not work any more.  The decision not to reimburse for never events, such as wrong-site surgery, falls, hospital-acquired infections, and bed-sores acquired during a hospital stay requires a collaborative effort among clinical, administrative, and board team members.  So does improving patient flow, as discussed in &#8220;Collaborative Flow.&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] In a previous post, &#8220;Collaborative Error: The Day I Nearly Quit&#8220;, I wrote that the old paradigm of physicians and nurses taking care of clinical dimensions of care and administrators keeping finance and operations to themselves does not work any more.  The decision not to reimburse for never events, such as wrong-site surgery, falls, hospital-acquired infections, and bed-sores acquired during a hospital stay requires a collaborative effort among clinical, administrative, and board team members.  So does improving patient flow, as discussed in &#8220;Collaborative Flow.&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Furst</title>
		<link>http://healthcarecollaboration.com/collaborative-flow/#comment-23</link>
		<dc:creator>Ian Furst</dc:creator>
		<pubDate>Thu, 28 Feb 2008 23:59:35 +0000</pubDate>
		<guid isPermaLink="false">http://healthcarecollaboration.com/collaborative-flow/#comment-23</guid>
		<description>I absolutely agree that we enable inefficient systems in our clinics.  I think that one of the problems of applying som of the standard queue models is that the natural variation in our systems is quite high and not always easy to control because of the nature of illness.  To make use of the data to change capacity.  I don&#039;t agree that you should match capacity to peak demand due to cost (although it would be nice).  Rather I think we need to make capacity flexible enough that large  variations in demand can be accomidated.  It&#039;s not ideal but it is more cost effective.  As an example, we have four clinics and watch the demand of patients being referred.  &quot;doctor days&quot; are moved from one clinic to another to match demand.  No office is staffed for peak or average, rather the system is built for flexability.  If you get a chance please check my blog and if you feel appropriate could you link it?  thx.
&lt;a href=&quot;http://www.waittimes.blogspot.com/&quot; rel=&quot;nofollow&quot;&gt;www.waittimes.blogspot.com&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I absolutely agree that we enable inefficient systems in our clinics.  I think that one of the problems of applying som of the standard queue models is that the natural variation in our systems is quite high and not always easy to control because of the nature of illness.  To make use of the data to change capacity.  I don&#8217;t agree that you should match capacity to peak demand due to cost (although it would be nice).  Rather I think we need to make capacity flexible enough that large  variations in demand can be accomidated.  It&#8217;s not ideal but it is more cost effective.  As an example, we have four clinics and watch the demand of patients being referred.  &#8220;doctor days&#8221; are moved from one clinic to another to match demand.  No office is staffed for peak or average, rather the system is built for flexability.  If you get a chance please check my blog and if you feel appropriate could you link it?  thx.<br />
<a href="http://www.waittimes.blogspot.com/" rel="nofollow">http://www.waittimes.blogspot.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

