<?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: Why my Firefox browser is more advanced than our hospital’s HIS</title>
	<atom:link href="http://jerryfahrni.com/2009/10/why-my-firefox-browser-is-more-advanced-than-our-hospital%e2%80%99s-his/feed/" rel="self" type="application/rss+xml" />
	<link>http://jerryfahrni.com/2009/10/why-my-firefox-browser-is-more-advanced-than-our-hospital%e2%80%99s-his/</link>
	<description>Pharmacy Informatics and Technology</description>
	<lastBuildDate>Mon, 06 Feb 2012 16:39:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jerry Fahrni &#187; &#8220;What&#8217;d I miss?&#8221; &#8211; Week of October 25th</title>
		<link>http://jerryfahrni.com/2009/10/why-my-firefox-browser-is-more-advanced-than-our-hospital%e2%80%99s-his/comment-page-1/#comment-752</link>
		<dc:creator>Jerry Fahrni &#187; &#8220;What&#8217;d I miss?&#8221; &#8211; Week of October 25th</dc:creator>
		<pubDate>Fri, 30 Oct 2009 20:31:29 +0000</pubDate>
		<guid isPermaLink="false">http://jerryfahrni.com/?p=2107#comment-752</guid>
		<description>[...] - HER Bloggers: “One of the biggest challenges for linking together different health information systems is the inconsistency in referring to a given individual – be that a physician, a patient, or whomever. One system, for example a lab system, may refer to “Patient x” one way (using their own arbitrary internal patient identifier number), while a different system (for example, a hospital) may use a completely different identifier. Between ambulatory EHRs, each one will also likely refer to a given patient with different, internal methods. Cross-linking these systems so that a unified dashboard can be created that displays all the information from all these systems is made much more difficult as a result.” – Exactly! See my post on a similar issue from yesterday here. [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8211; HER Bloggers: “One of the biggest challenges for linking together different health information systems is the inconsistency in referring to a given individual – be that a physician, a patient, or whomever. One system, for example a lab system, may refer to “Patient x” one way (using their own arbitrary internal patient identifier number), while a different system (for example, a hospital) may use a completely different identifier. Between ambulatory EHRs, each one will also likely refer to a given patient with different, internal methods. Cross-linking these systems so that a unified dashboard can be created that displays all the information from all these systems is made much more difficult as a result.” – Exactly! See my post on a similar issue from yesterday here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jerry Fahrni</title>
		<link>http://jerryfahrni.com/2009/10/why-my-firefox-browser-is-more-advanced-than-our-hospital%e2%80%99s-his/comment-page-1/#comment-745</link>
		<dc:creator>Jerry Fahrni</dc:creator>
		<pubDate>Fri, 30 Oct 2009 02:04:20 +0000</pubDate>
		<guid isPermaLink="false">http://jerryfahrni.com/?p=2107#comment-745</guid>
		<description>Amen, brother!</description>
		<content:encoded><![CDATA[<p>Amen, brother!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pillguy</title>
		<link>http://jerryfahrni.com/2009/10/why-my-firefox-browser-is-more-advanced-than-our-hospital%e2%80%99s-his/comment-page-1/#comment-743</link>
		<dc:creator>pillguy</dc:creator>
		<pubDate>Fri, 30 Oct 2009 00:54:58 +0000</pubDate>
		<guid isPermaLink="false">http://jerryfahrni.com/?p=2107#comment-743</guid>
		<description>The simple answer is that the companies that have monopolies on Healthcare information systems are there because of opportunity.  They were there at a time when the industry needed something.  The sad part is that something was created without much of the development rigors we have seen in competent industries.  These might include financial or retail.  We have software that in many cases was initially created in someone&#039;s garage.  

My second point is open source.  The reason Firefox is such a great platform is because they design API (application programming interfaces) and give the code to everyone.  That allows cool things to happen, and we benefit from it.  Intellectual Property paranoia in the private sector for healthcare IT has left most hospitals with a stale, unsatisfactory product.  

Although I will say I have been very impressed with Epic in general.  They put more thought behind their decisions, and really listen to their customers.  It is by no means perfect, it is clear to me the leadership really wants to make it work.  Once they allow API type interfacing, I will know they are truly in it for the patient.</description>
		<content:encoded><![CDATA[<p>The simple answer is that the companies that have monopolies on Healthcare information systems are there because of opportunity.  They were there at a time when the industry needed something.  The sad part is that something was created without much of the development rigors we have seen in competent industries.  These might include financial or retail.  We have software that in many cases was initially created in someone&#8217;s garage.  </p>
<p>My second point is open source.  The reason Firefox is such a great platform is because they design API (application programming interfaces) and give the code to everyone.  That allows cool things to happen, and we benefit from it.  Intellectual Property paranoia in the private sector for healthcare IT has left most hospitals with a stale, unsatisfactory product.  </p>
<p>Although I will say I have been very impressed with Epic in general.  They put more thought behind their decisions, and really listen to their customers.  It is by no means perfect, it is clear to me the leadership really wants to make it work.  Once they allow API type interfacing, I will know they are truly in it for the patient.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

