<?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"
	>
<channel>
	<title>Comments on: EHR System Modeling</title>
	<atom:link href="http://rdn-consulting.com/blog/2008/01/01/ehr-system-modeling/feed/" rel="self" type="application/rss+xml" />
	<link>http://rdn-consulting.com/blog/2008/01/01/ehr-system-modeling/</link>
	<description>Software Development and Biomedical Engineering</description>
	<pubDate>Thu, 20 Nov 2008 17:55:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Bob on Medical Device Software &#187; Blog Archive &#187; HIPAA and EMR Design</title>
		<link>http://rdn-consulting.com/blog/2008/01/01/ehr-system-modeling/#comment-414</link>
		<dc:creator>Bob on Medical Device Software &#187; Blog Archive &#187; HIPAA and EMR Design</dc:creator>
		<pubDate>Fri, 04 Jan 2008 05:19:40 +0000</pubDate>
		<guid isPermaLink="false">http://rdn-consulting.com/blog/2008/01/01/ehr-system-modeling/#comment-414</guid>
		<description>[...] last post prompted a comment from Mary Hawking which asked this question: How does the legal framework in the USA influence the [...]</description>
		<content:encoded><![CDATA[<p>[...] last post prompted a comment from Mary Hawking which asked this question: How does the legal framework in the USA influence the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mary Hawking</title>
		<link>http://rdn-consulting.com/blog/2008/01/01/ehr-system-modeling/#comment-412</link>
		<dc:creator>Mary Hawking</dc:creator>
		<pubDate>Thu, 03 Jan 2008 19:38:55 +0000</pubDate>
		<guid isPermaLink="false">http://rdn-consulting.com/blog/2008/01/01/ehr-system-modeling/#comment-412</guid>
		<description>Health records - electronic or otherwise - are held within organisational and legal frameworks which  define the professional and legal responsibilities of the people and organisations involved in maintaining and using those records.
I'm a GP in England, and paperless - i.e. the only record for my patients is in the EMR (EMIS - if anyone is interested!) 
How does the legal framework in the USA influence the design of US EMRs?</description>
		<content:encoded><![CDATA[<p>Health records - electronic or otherwise - are held within organisational and legal frameworks which  define the professional and legal responsibilities of the people and organisations involved in maintaining and using those records.<br />
I&#8217;m a GP in England, and paperless - i.e. the only record for my patients is in the EMR (EMIS - if anyone is interested!)<br />
How does the legal framework in the USA influence the design of US EMRs?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob</title>
		<link>http://rdn-consulting.com/blog/2008/01/01/ehr-system-modeling/#comment-411</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Thu, 03 Jan 2008 03:42:37 +0000</pubDate>
		<guid isPermaLink="false">http://rdn-consulting.com/blog/2008/01/01/ehr-system-modeling/#comment-411</guid>
		<description>@Werner: Thanks for the feedback. The openEHR concept of "semantic context" is certainly a good one.   Every model will need to evolve as more is learned about the nature of the real world it’s trying to represent.  One of the hallmarks of a good development framework is its ability to allow these types of changes to be incorporated into the model at minimum cost while maintaining backwards compatibility. This is not an easy task. Software modeling and development technologies have to continue to improve in order to meet these challenges.</description>
		<content:encoded><![CDATA[<p>@Werner: Thanks for the feedback. The openEHR concept of &#8220;semantic context&#8221; is certainly a good one.   Every model will need to evolve as more is learned about the nature of the real world it’s trying to represent.  One of the hallmarks of a good development framework is its ability to allow these types of changes to be incorporated into the model at minimum cost while maintaining backwards compatibility. This is not an easy task. Software modeling and development technologies have to continue to improve in order to meet these challenges.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Werner</title>
		<link>http://rdn-consulting.com/blog/2008/01/01/ehr-system-modeling/#comment-410</link>
		<dc:creator>Werner</dc:creator>
		<pubDate>Wed, 02 Jan 2008 20:19:30 +0000</pubDate>
		<guid isPermaLink="false">http://rdn-consulting.com/blog/2008/01/01/ehr-system-modeling/#comment-410</guid>
		<description>Bob,

With so many others, you seem to forget, or at least fail to mention, that a common information/behavior model is not enough to have interoperable systems that do more than just replicating the document-centered approach of paper-based EMRs in an electronic environment. You also need to have a common model of that what the information is about, i.e. of the entities on the side of the patient about which information is stored in information systems. Although the goal of HL7 RIM might be the same as for OpenEHR, it fails seriously in recognizing the distinction that I made. OpenEHR is at least aware of the distinction.</description>
		<content:encoded><![CDATA[<p>Bob,</p>
<p>With so many others, you seem to forget, or at least fail to mention, that a common information/behavior model is not enough to have interoperable systems that do more than just replicating the document-centered approach of paper-based EMRs in an electronic environment. You also need to have a common model of that what the information is about, i.e. of the entities on the side of the patient about which information is stored in information systems. Although the goal of HL7 RIM might be the same as for OpenEHR, it fails seriously in recognizing the distinction that I made. OpenEHR is at least aware of the distinction.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
