<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Following the rewrite: COSMOS documentation</title>
    <link>http://rewrite.rickbradley.com/articles/2006/07/06/cosmos-documentation</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>A journey on Rails</description>
    <item>
      <title>COSMOS documentation</title>
      <description>&lt;p&gt;For those of you who are fans of Martin Fowler&amp;#8217;s &lt;a href="http://www.martinfowler.com/books.html#ap"&gt;&lt;em&gt;Analysis Patterns&lt;/em&gt;&lt;/a&gt; tome of wisdom, and who are curious about the &lt;span class="caps"&gt;COSMOS&lt;/span&gt; clinical process model project that inspired much of that book, you may be interested in reading the documents linked below.&lt;/p&gt;


	&lt;p&gt;When Charles and I went to RailsConf this year to speak about the success we&amp;#8217;ve been having building a comprehensive research-friendly health record, we were approached by Adam Cavan from the audience who was interested in our project.  He asked how much of the &lt;span class="caps"&gt;COSMOS&lt;/span&gt; documentation we&amp;#8217;d read before embarking upon our project.  We were sad to say that we&amp;#8217;d never been able to actually acquire a copy of the documents, as no one seemed to have kept them around, nor were they to be found online any more.&lt;/p&gt;


	&lt;p&gt;&amp;#8220;Oh,&amp;#8221; said Adam, &amp;#8220;I&amp;#8217;ve got a copy&amp;#8212;would you like to see them?&amp;#8221;  Would we ever.  And he was as good as his word.  Thanks to his kindness we&amp;#8217;re also making those documents, with all their amazing insights, available here. By the way, you can reach Adam here: acavan (at) suika (dot) com.&lt;/p&gt;


	&lt;p&gt;Note we don&amp;#8217;t pretend to own these documents, but given that they were at one time available on the web we hope our posting will be looked upon kindly as a service to the software and medical care communities.&lt;/p&gt;


	&lt;p&gt;Without further verbage, here are .doc and .pdf versions of the documents we received:&lt;/p&gt;


&lt;table&gt;
  &lt;tr&gt;
    &lt;th&gt;&lt;span class="caps"&gt;DOC&lt;/span&gt;&lt;/th&gt;&lt;th&gt;&lt;span class="caps"&gt;PDF&lt;/span&gt;&lt;/th&gt;
  &lt;/tr&gt;
  &lt;tr&gt;
    &lt;td&gt;&lt;a href="/files/ccpm2pt1_clean.doc"&gt;The Clinical View of the Common Basic Specification&lt;/a&gt; (CCPM2 Part 1 &amp;#8211; &amp;#8220;Clean&amp;#8221;)&lt;/td&gt;
    &lt;td&gt;&lt;a href="/files/ccpm2pt1_clean.pdf"&gt;The Clinical View of the Common Basic Specification&lt;/a&gt; (CCPM2 Part 1 &amp;#8211; &amp;#8220;Clean&amp;#8221;)&lt;/td&gt;
  &lt;/tr&gt;
  &lt;tr&gt;
    &lt;td&gt;&lt;a href="/files/ccpm2pt1.doc"&gt;The Clinical View of the Common Basic Specification&lt;/a&gt; (CCPM2 Part 1)&lt;/td&gt;
    &lt;td&gt;&lt;a href="/files/ccpm2pt1.pdf"&gt;The Clinical View of the Common Basic Specification&lt;/a&gt; (CCPM2 Part 1)&lt;/td&gt;
  &lt;/tr&gt;
  &lt;tr&gt;
    &lt;td&gt;&lt;a href="/files/ccpm2pt2_clean.doc"&gt;The Activity Diagram&lt;/a&gt; (CCPM2 Part 2 &amp;#8211; &amp;#8220;Clean&amp;#8221;)&lt;/td&gt;
    &lt;td&gt;&lt;a href="/files/ccpm2pt2_clean.pdf"&gt;The Activity Diagram&lt;/a&gt; (CCPM2 Part 2 &amp;#8211; &amp;#8220;Clean&amp;#8221;)&lt;/td&gt;
  &lt;/tr&gt;
  &lt;tr&gt;
    &lt;td&gt;&lt;a href="/files/ccpm2pt2_clean.doc"&gt;The Activity Diagram&lt;/a&gt; (CCPM2 Part 2)&lt;/td&gt;
    &lt;td&gt;&lt;a href="/files/ccpm2pt2_clean.pdf"&gt;The Activity Diagram&lt;/a&gt; (CCPM2 Part 2)&lt;/td&gt;
  &lt;/tr&gt;
  &lt;tr&gt;
    &lt;td&gt;&lt;a href="/files/ccpm2pt3_clean.doc"&gt;Glossary of Concept Names&lt;/a&gt; (CCPM2 Part 3 &amp;#8211; &amp;#8220;Clean&amp;#8221;)&lt;/td&gt;
    &lt;td&gt;&lt;a href="/files/ccpm2pt3_clean.pdf"&gt;Glossary of Concept Names&lt;/a&gt; (CCPM2 Part 3 &amp;#8211; &amp;#8220;Clean&amp;#8221;)&lt;/td&gt;
  &lt;/tr&gt;
  &lt;tr&gt;
    &lt;td&gt;&lt;a href="/files/ccpm2pt3_clean.doc"&gt;Glossary of Concept Names&lt;/a&gt; (CCPM2 Part 3)&lt;/td&gt;
    &lt;td&gt;&lt;a href="/files/ccpm2pt3_clean.pdf"&gt;Glossary of Concept Names&lt;/a&gt; (CCPM2 Part 3)&lt;/td&gt;
  &lt;/tr&gt;
&lt;/table&gt;

	&lt;p&gt;&lt;em&gt;&lt;span class="caps"&gt;UPDATE&lt;/span&gt;&lt;/em&gt;:  Added better versions of the &amp;#8220;clean&amp;#8221; PDFs&amp;#8212;also added attribution to our previously pseudo-anonymous friend who found these documents.  Tahnks Adam!&lt;/p&gt;</description>
      <pubDate>Thu, 06 Jul 2006 13:43:00 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:57e23ca6-9ad6-4b8c-8ea8-737700c08298</guid>
      <author>rick</author>
      <link>http://rewrite.rickbradley.com/articles/2006/07/06/cosmos-documentation</link>
      <category>cosmos</category>
    </item>
    <item>
      <title>"COSMOS documentation" by fesp21@yahoo.com</title>
      <description>&lt;p&gt;I am really interested in this my parents have been asking to put together a strong wap that willbe used in their medical industry.  I am somewhat still new to ruby on rails and programming in general.  I have taken a few courses in sql and I am pretty familiar with it but when it comes to rails.  I am lost in the understanding of active record with regards to defining functions.  I feel somewhat comfortable with ActionPak but outside of using validations and table relationships i get lost in understanding what other business logic needs to go with a model.&lt;/p&gt;


	&lt;p&gt;Is there anyway I can contact you about this design that I am trying to complete.&lt;/p&gt;


	&lt;p&gt;speezy&lt;/p&gt;


	&lt;p&gt;&lt;a href='mailto:fesp21@yahoo.com' rel="nofollow"&gt;fesp21@yahoo.com&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 02 Aug 2006 14:44:09 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:3d757acf-c215-4943-8400-d8de80e63cb9</guid>
      <link>http://rewrite.rickbradley.com/articles/2006/07/06/cosmos-documentation#comment-324</link>
    </item>
  </channel>
</rss>
