<?xml version="1.0" encoding="utf-8"?>
<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/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Dave Rowe's Blog &#187; design</title>
	<atom:link href="http://blog.roweware.com/tag/design/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.roweware.com</link>
	<description>Ramblings about things I think I know...</description>
	<lastBuildDate>Wed, 14 Jul 2010 17:45:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>DB Design &#8211; ICD9 Data</title>
		<link>http://blog.roweware.com/2009/12/01/db-design-icd9-data/</link>
		<comments>http://blog.roweware.com/2009/12/01/db-design-icd9-data/#comments</comments>
		<pubDate>Tue, 01 Dec 2009 23:02:48 +0000</pubDate>
		<dc:creator>Dave Rowe</dc:creator>
				<category><![CDATA[Database Design]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[db]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[ICD9]]></category>
		<category><![CDATA[medical]]></category>

		<guid isPermaLink="false">http://blog.roweware.com/?p=140</guid>
		<description><![CDATA[In today's Adventures in Database Design, we'll take a look at a relevant topic, ICD9 data.  ICD9 data is the diagnosis and procedure codes used by insurance companies to categorize, well, diagnoses and procedures to be determined / performed by medical professionals.  The design is simple, but very versatile, given the type of data we're storing.]]></description>
			<content:encoded><![CDATA[<p>ICD9 data are the diagnosis and procedure codes used by insurance companies to categorize, well, diagnoses and procedures to be determined / performed by medical professionals.  Typically, if you visit the doctor for an ailment and file insurance, your provider will list the reason for the visit, any diagnoses, and any procedures performed.  This is then sent to the insurance company for processing.  They can then use codes to indicate if the procedure is covered, as well as, (for example) determine if the diagnosis was a pre-existing condition.  The data is a simple hierarchical structure which is shown in the following diagram.</p>
<div id="attachment_139" class="wp-caption alignnone" style="width: 306px"><img class="size-medium wp-image-139" title="ICD9" src="http://blog.roweware.com/wp-content/uploads/2009/12/ICD9-296x300.png" alt="ERD for storing ICD9 data" width="296" height="300" /><p class="wp-caption-text">ERD for storing ICD9 data</p></div>
<p>We see that diagnoses can have sub-diagnoses, etc.  I used this simple structure, and added a qualifying column of &#8216;record_type&#8217; to indicate if the code listed was an actual diagnosis, or a section header.  Sections of diagnoses are part of the data, and can be used in searching the database.  This diagram offers a simple and quick design to handle the data given.</p>
<p>Comments are welcome.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.roweware.com/2009/12/01/db-design-icd9-data/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Adventures in Database Design</title>
		<link>http://blog.roweware.com/2009/11/23/adventures-in-database-design/</link>
		<comments>http://blog.roweware.com/2009/11/23/adventures-in-database-design/#comments</comments>
		<pubDate>Tue, 24 Nov 2009 03:39:56 +0000</pubDate>
		<dc:creator>Dave Rowe</dc:creator>
				<category><![CDATA[Database Design]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[workbench]]></category>

		<guid isPermaLink="false">http://blog.roweware.com/?p=137</guid>
		<description><![CDATA[I&#8217;ve long neglected this blog, and the power behind it to discuss my feelings toward database design.  Proper database design is the backbone to a solid application.  Failing to correctly normalize tables and enforce business logic with foreign key relationships can cause undue headaches. What I&#8217;ll be doing is going through some simple applications, and [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve long neglected this blog, and the power behind it to discuss my feelings toward database design.  Proper database design is the backbone to a solid application.  Failing to correctly normalize tables and enforce business logic with foreign key relationships can cause undue headaches.</p>
<p>What I&#8217;ll be doing is going through some simple applications, and start modeling the tables and relationships, and intersperse some commentary where useful.  The discussion depends on interaction, and I&#8217;m of the opinion that a &#8216;good&#8217; database designer can a) defend their design articulately and b) know when to concede a good point.</p>
<p>Database design is becoming organic.  Strict adherence to the normal forms isn&#8217;t required any longer.  Let me be clear though, denormalizing a table to make things easier for a developer is not a valid reason to denormalize.</p>
<p>The modeling tool I&#8217;ll be using for generating the images is <a title="MySQL Workbench" href="http://wb.mysql.com/" target="_blank">MySQL Workbench</a>.  Workbench is a very powerful tool, from the source of one of the most powerful (and used) databases today.  I cut my teeth on database design with DBDesigner4, whose creator went on to work for MySQL Workbench.</p>
<p>Stay tuned.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.roweware.com/2009/11/23/adventures-in-database-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
