<?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/"
		xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: EHR wants #2</title>
	<atom:link href="http://www.optoblog.com/2005/07/05/ehr-wants-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.optoblog.com/2005/07/05/ehr-wants-2/</link>
	<description>Personal Opinion Blog of David Langford</description>
	<lastBuildDate>Tue, 10 Jan 2012 17:54:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: optoblog.com &#187; Blog Archive &#187; Optometric EHR wants #3</title>
		<link>http://www.optoblog.com/2005/07/05/ehr-wants-2/comment-page-1/#comment-42</link>
		<dc:creator>optoblog.com &#187; Blog Archive &#187; Optometric EHR wants #3</dc:creator>
		<pubDate>Wed, 03 Oct 2007 05:13:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.optoblog.com/?p=55#comment-42</guid>
		<description>[...] Here were EHR wants number one and two. [...]</description>
		<content:encoded><![CDATA[<p>[...] Here were EHR wants number one and two. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.optoblog.com/2005/07/05/ehr-wants-2/comment-page-1/#comment-41</link>
		<dc:creator>David</dc:creator>
		<pubDate>Mon, 18 Jul 2005 22:57:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.optoblog.com/?p=55#comment-41</guid>
		<description>Sweet!  This is what the &lt;a href=&quot;http://www.cluetrain.com&quot; rel=&quot;nofollow&quot;&gt;ClueTrain&lt;/a&gt; is all about.  First Insight (Maximeyes) appears to already be on board.  I am so glad to find out about this stuff.  My hope is that in the future, every ophthalmic equipment company will be part of the work group.
Sorry I missed the AOA convention.  I was going to go and blog the whole thing, but I&#039;m saving my money for Academy this year.</description>
		<content:encoded><![CDATA[<p>Sweet!  This is what the <a href="http://www.cluetrain.com" rel="nofollow">ClueTrain</a> is all about.  First Insight (Maximeyes) appears to already be on board.  I am so glad to find out about this stuff.  My hope is that in the future, every ophthalmic equipment company will be part of the work group.<br />
Sorry I missed the AOA convention.  I was going to go and blog the whole thing, but I&#8217;m saving my money for Academy this year.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nitin Rai</title>
		<link>http://www.optoblog.com/2005/07/05/ehr-wants-2/comment-page-1/#comment-40</link>
		<dc:creator>Nitin Rai</dc:creator>
		<pubDate>Mon, 18 Jul 2005 20:03:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.optoblog.com/?p=55#comment-40</guid>
		<description>I just wanted to respond to your issues regarding equipment integration. There are standard for imaging equipment (DICOM). There are already vendor committees and work groups out there working on standards for EMR interfacing. Canon, Zeiss, Topcon are already part of that committee. No need to form another group for this effort. MaximEyes has already integrated with Zeiss Humphrey visual fields in a prototype that was shown at the AOA Meeting in Dallas in June.  We expect this interface to available in the next few months. Almost every imaging vendor allows exporting of their data in a jpeg format. Some imaging vendors are developing software that allows import export thru a programatic interface (Zeiss). It will be very hard to standardize on the programmatic interface as that is entirely dependant on the equipment in question. But at worst you can export an image from an imaging system and link into Maximeyes (jpeg).

Wrto the 800X600 limitation in maximEyes, that is not really a limitation. You can run the demo at higher resolutions as well..

Nitin Rai
CEO, First Insight</description>
		<content:encoded><![CDATA[<p>I just wanted to respond to your issues regarding equipment integration. There are standard for imaging equipment (DICOM). There are already vendor committees and work groups out there working on standards for EMR interfacing. Canon, Zeiss, Topcon are already part of that committee. No need to form another group for this effort. MaximEyes has already integrated with Zeiss Humphrey visual fields in a prototype that was shown at the AOA Meeting in Dallas in June.  We expect this interface to available in the next few months. Almost every imaging vendor allows exporting of their data in a jpeg format. Some imaging vendors are developing software that allows import export thru a programatic interface (Zeiss). It will be very hard to standardize on the programmatic interface as that is entirely dependant on the equipment in question. But at worst you can export an image from an imaging system and link into Maximeyes (jpeg).</p>
<p>Wrto the 800X600 limitation in maximEyes, that is not really a limitation. You can run the demo at higher resolutions as well..</p>
<p>Nitin Rai<br />
CEO, First Insight</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.optoblog.com/2005/07/05/ehr-wants-2/comment-page-1/#comment-39</link>
		<dc:creator>David</dc:creator>
		<pubDate>Fri, 08 Jul 2005 03:33:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.optoblog.com/?p=55#comment-39</guid>
		<description>I also want the ophthalmic equipment companies to enable downloadable info into their instruments.  Example,  why should I spend forever entering in Rx, name, DOB, etc into the Humphrey Visual Field?  The EHR and the HVF should communicate with each other.</description>
		<content:encoded><![CDATA[<p>I also want the ophthalmic equipment companies to enable downloadable info into their instruments.  Example,  why should I spend forever entering in Rx, name, DOB, etc into the Humphrey Visual Field?  The EHR and the HVF should communicate with each other.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

