<?xml version="1.0" encoding="utf-8"?><rss version="2.0">
<channel>
<title><![CDATA[Clinical Architecture Healthcare IT Blog]]></title>
<link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/?rss=blogs]]></link>
<description><![CDATA[Clinical Architecture Healthcare IT Blog]]></description>
<language><![CDATA[en-US]]></language>

<item>
  <guid isPermaLink="false">e3769401-8261-4661-8658-40dc3c09af7e</guid>
  <title><![CDATA[Number Please?  - The Inevitability of Automated Interoperability]]></title>
  <description><![CDATA[History teaches us why automation in clinical interoperability is inevitable.]]></description>
  <pubDate>Wed, 11 Apr 2012 12:21:35 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/april-2012/number-please-the-inevitability-of-automated-inter/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">0529fb7c-fca8-49a9-9f77-3aabae7a81b0</guid>
  <title><![CDATA[Have you Ever Wanted to be a Super Hero?]]></title>
  <description><![CDATA[Come visit Clinical Architecture at HIMSS - booth 4863]]></description>
  <pubDate>Wed, 15 Feb 2012 23:05:06 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/february-2012/have-you-everwanted-to-be-a-super-hero/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">ddce4b89-6bf1-4cd3-94fc-71d666ecafef</guid>
  <title><![CDATA[The Twelve Days of Christmas... with an Informaticist]]></title>
  <description><![CDATA[On the&nbsp;<strong>first</strong>&nbsp;day of Christmas, my informaticist gave to me<br />
<strong>A hyper-precoordinated key</strong>]]></description>
  <pubDate>Fri, 23 Dec 2011 15:13:17 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/december-2011/the-twelve-days-of-christmas-with-an-informaticist/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">0e8114ab-a4eb-4190-b62b-e9bb023a5525</guid>
  <title><![CDATA[Clinical Terminologies in Healthcare - Part Two]]></title>
  <description><![CDATA[I am a Star Trek fan (not a Trekkie... I don&#39;t wear a tunic around the office...if I did it would be gold to signify command... but I DON&#39;T). On Star Trek they had a piece of equipment called a&nbsp;<a href="http://en.wikipedia.org/wiki/Transporter_(Star_Trek)" target="_self" title="'transporter'">&#39;transporter&#39;</a>.&nbsp; It was the job of the transporter to teleport a person from point A to point B.&nbsp; It does this by converting a person to a pattern of information and energy (dematerializing them), sending them through a beam and rematerializing them on the other side, hopefully without turning them inside out.]]></description>
  <pubDate>Thu, 15 Dec 2011 14:02:38 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/december-2011/clinical-terminologies-in-healthcare-part-two/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">e6e08d62-c267-42c9-a9f0-818d61ca707c</guid>
  <title><![CDATA[Clinical Terminologies in Healthcare Applications - Part One]]></title>
  <description><![CDATA[Over the past&nbsp;two decades, I have been on the battlefield of Healthcare IT.&nbsp; Throughout this time, I have been in many roles, ranging from programmer and systems designer, to chief technology officer.&nbsp; During this time, I have had the opportunity to observe a number of applications in the healthcare space.&nbsp; Some of these applications have been simple and some complex; some dealt with administrative aspects of care and some that meant the difference between a safe patient and a patient that ends up in a statistic that gets quoted in an ISMP report.&nbsp; I have learned from my successes, my mistakes and the successes and mistakes of others (yes, I have been watching you).]]></description>
  <pubDate>Sat, 03 Sep 2011 15:26:28 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/september-2011/clinical-terminologies-in-healthcare-applications/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">00102341-c86c-44bf-a464-9bcdff7f901d</guid>
  <title><![CDATA[PSA: Semantic Identity Crisis]]></title>
  <description><![CDATA[Did you ever wonder what happens to a code when there is a lack of good semantic interoperability?&nbsp; If so, please watch the following cautionary tale about a well meaning medication allergy term &#39;Si Metadeen&#39;.]]></description>
  <pubDate>Fri, 05 Aug 2011 13:40:44 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/august-2011/psa-semantic-identity-crisis/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">68f36a01-32e3-4389-ab76-aa86b4406eb5</guid>
  <title><![CDATA[Clinical Architecture Releases SYMEDICAL Server]]></title>
  <description><![CDATA[I try to avoid sales pitches in this blog, but from time to time I want to make you aware of what Clinical Architecture is up to with our products, especially if it is something amazing.]]></description>
  <pubDate>Sun, 03 Apr 2011 01:00:29 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/april-2011/clinical-architecture-releases-symedical-server/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">6f0d3b09-bd48-4bc3-b0a7-eec851bacd3e</guid>
  <title><![CDATA[Lab Domain and LOINC Overview – Part III]]></title>
  <description><![CDATA[In this post we are going to start digging into LOINC.&nbsp; While this is meant to be a critical review, I need to say that I am a fan of LOINC and respect the amount of effort and discipline that is required to build and maintain a terminology. &nbsp;]]></description>
  <pubDate>Sun, 13 Feb 2011 14:46:40 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/february-2011/lab-domain-and-loinc-overview-–-part-iii/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">50adbbf4-3617-4a7c-a1d0-c131097c7cd7</guid>
  <title><![CDATA[Lab Terminologies and LOINC - Part II]]></title>
  <description><![CDATA[I was hired by Medi-Span in 1998 to run their software products team.&nbsp; In a meeting with product management someone was explaining a CDS module that involved lab results and proudly informed me that they had cross referenced their internal lab codes to LOINC codes.&nbsp; I said, &ldquo;That&rsquo;s great&hellip; what&rsquo;s a LOINC code?&rdquo;&nbsp;]]></description>
  <pubDate>Sun, 06 Feb 2011 21:47:19 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/february-2011/lab-terminologies-and-loinc-part-ii/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">d8f645d7-99ad-473e-ad1d-a260377af3a1</guid>
  <title><![CDATA[Lab Domain Terminologies and LOINC - Part I]]></title>
  <description><![CDATA[Whether you have been following the buzz related to the ARRA meaningful use criteria or you are involved in clinical information exchange, you have likely run across the acronym LOINC recently.&nbsp; A significant chunk of my career has been spent in the lab system environment, so I thought it might be useful for me to share my thoughts and experience on the lab domain and LOINC.]]></description>
  <pubDate>Wed, 02 Feb 2011 14:17:24 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/february-2011/lab-domain-terminologies-and-loinc-part-i/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">dd542a52-fb73-4d0b-8f7b-ac648527d2b2</guid>
  <title><![CDATA[ISMP Tallman and RxNorm - January Update]]></title>
  <description><![CDATA[Happy new year from Clinical Architecture!&nbsp; My goal this year is to be more prolific on the blog.&nbsp; There are a lot of interesting things going on in healthcare, so there is plenty to talk about.]]></description>
  <pubDate>Sat, 15 Jan 2011 01:12:30 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/january-2011/ismp-tallman-and-rxnorm-january-update/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">6d61aef0-5485-4f22-a6f9-d29ff1f04310</guid>
  <title><![CDATA[ISMP Tallman and RxNorm - Quick Freebie]]></title>
  <description><![CDATA[On the&nbsp;<a href="http://www.clinicalarchitecture.com/resources/" target="_self" title="resources page">resources page</a>, I have posted an&nbsp;<a href="http://www.clinicalarchitecture.com/Default.aspx?app=LeadgenDownload&amp;shortpath=docs%2fTallMan_RXCUI_082010.xls" target="_self" title="excel spreadsheet">excel spreadsheet</a>&nbsp;that includes ISMP Tallman drug names and the RxNorm CUIs they are directly and indirectly related to.&nbsp; The first tab is the ISMP Tallman names and the RxNorm ingredients (TTY=IN) and brand names (TTY=BN).&nbsp; The second tab&nbsp;lists the relationships between the ISMP&nbsp;Tallman names and more granular RxCUIs&nbsp;<strong>with the Tallman names incorporated into the descriptions as appropriate</strong>.&nbsp; This was done by creating links based on the RXNREL table from the ingredient and brand names to their related&nbsp;concepts, replacing the names and manually reviewing each item.&nbsp;]]></description>
  <pubDate>Sun, 29 Aug 2010 22:11:44 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/august-2010/ismp-tallman-and-rxnorm-quick-freebie/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">0e9a3d55-e026-4f84-bda2-e6de885fe334</guid>
  <title><![CDATA[A Primer on the Vocabularies of Meaningful Use - Procedure Vocabularies]]></title>
  <description><![CDATA[<strong>Its Just a Simple Procedure...</strong><strong>Current Procedure Terminology (CPT)</strong>The Current Procedural Terminology (CPT) code set is maintained by the American Medical Association through the CPT Editorial Panel. The CPT code set accurately describes medical, surgical, and diagnostic services and is designed to communicate uniform information about medical services and procedures among physicians, coders, patients, accreditation organizations, and payers for administrative, financial, and analytical purposes.All CPT Codes are 5 digits.]]></description>
  <pubDate>Wed, 30 Jun 2010 22:20:50 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/june-2010/a-primer-on-the-vocabularies-of-meaningful-use-pro/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">1691a308-7b0a-4c49-afdb-0ecfd74a380e</guid>
  <title><![CDATA[A Primer on the Vocabularies of Meaningful Use – Allergy Vocabulary]]></title>
  <description><![CDATA[The vocabulary chosen to represent patient allergies is the FDA Unique Ingredient Identifier or UNII (I guess &lsquo;UII&#39; would be a difficult acronym to use in casual conversation...).]]></description>
  <pubDate>Wed, 30 Jun 2010 11:49:09 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/june-2010/a-primer-on-the-vocabularies-of-meaningful-use-–-a/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">3af794a2-87a7-45a5-9124-83362cab8c1f</guid>
  <title><![CDATA[A Primer on the Vocabularies of Meaningful Use - Problem Vocabularies]]></title>
  <description><![CDATA[International Classification of Diseases is a publication from the World Health Organization (WHO) and it provides a number of vocabularies for expressing disease concepts.&nbsp;]]></description>
  <pubDate>Tue, 18 May 2010 09:51:49 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/may-2010/a-primer-on-the-vocabularies-of-meaningful-use-pro/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">c63db0b4-7e96-4658-a6a7-a32057d9e37d</guid>
  <title><![CDATA[A Primer on the Vocabularies of Meaningful Use - Introduction]]></title>
  <description><![CDATA[I recently had a request to create a post providing a primer on the vocabularies of meaningful use. &nbsp;]]></description>
  <pubDate>Mon, 17 May 2010 22:37:48 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/may-2010/a-primer-on-the-vocabularies-of-meaningful-use-int/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">fd77d565-539f-4f1a-aa40-02dda37c8191</guid>
  <title><![CDATA[Why Symedical]]></title>
  <description><![CDATA[We at Clinical Architecture have created a new suite of software tools with a unique focus on terminology mapping, Symedcial. &nbsp;You may be thinking that there are already a number of mapping tools out there and are wondering &#39;Why Symedical?&#39;. I created a four minute screencast to show you how Symedical is different.]]></description>
  <pubDate>Mon, 22 Mar 2010 15:15:51 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/march-2010/why-symedical/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">b498e617-bdd5-467a-adac-91aa42841915</guid>
  <title><![CDATA[Medication Concepts – Engineering Primer – [Part 3] - The Secret Ingredient]]></title>
  <description><![CDATA[When dealing with any terminology domain, to establish a working understanding, you need to get a handle on the anatomy of a term within the domain.&nbsp;&nbsp;For example, if you are looking at a catalog of automobiles you quickly see a pattern that revolves around the vehicle make, model, production year and other characteristics that identify the vehicle to the required level of granularity.&nbsp;&nbsp;Regardless of the domain, the pattern typically becomes broken down into primary characteristics, secondary characteristics and modifiers.&nbsp;]]></description>
  <pubDate>Mon, 08 Mar 2010 23:08:24 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/march-2010/medication-concepts-–-engineering-primer-–-part-3/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">3ec07aca-9dc4-4a00-971b-7270ad940e04</guid>
  <title><![CDATA[Medication Concepts - Engineering Primer [Part 2]]]></title>
  <description><![CDATA[<span style="color: rgb(65, 65, 65); font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 13px; line-height: 21px; text-align: left; background-color: rgb(255, 255, 255); ">In order to understand how a medication concept can be appropriately leveraged, you need to understand its characteristics and which are required to support a particular activity.</span>]]></description>
  <pubDate>Thu, 21 Jan 2010 00:04:27 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/january-2010/medication-concepts-engineering-primer-part-2/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">6bacfe8b-48bc-4268-8f5a-28bc1b216e9d</guid>
  <title><![CDATA[Medication Concepts - Engineering Primer [Part One]]]></title>
  <description><![CDATA[As we enter the second decade of the 21<sup>st</sup>&nbsp;century, we have been&nbsp;given a mandate to evolve our simplistic, episodic and transient patient records into the robust, longitudinal, and precise paragons of technology that has been promised in board meetings, speeches and science fiction movies. &nbsp;This can be accomplished.&nbsp; Like all good architecture,&nbsp;achieving this objective will require an evolution over time that starts with stable foundational concepts that support the goal.&nbsp; There are a number of domains of clinical terminology: problems, procedures, laboratory tests, nursing orders, etc.&nbsp; One of the most pervasive and complicated of these is medications.]]></description>
  <pubDate>Sun, 03 Jan 2010 23:13:48 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/january-2010/medication-concepts-engineering-primer-part-one/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">b27be704-4287-469b-b5e1-c51c2943e986</guid>
  <title><![CDATA[Mapping SNOMED-CT to ICD9 Screencast]]></title>
  <description><![CDATA[I have completed a new screencast that provides a&nbsp;17&nbsp;minute&nbsp;overview on how to leverage the ICD9 cross map files in the SNOMED-CT&nbsp;optional download.&nbsp; Grab a sandwich, MS Access and curl up by the monitor and see how this great resource from the NLM can save you some time and effort mapping SNOMED-CT terms to ICD9.]]></description>
  <pubDate>Tue, 27 Oct 2009 16:45:05 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/october-2009/mapping-snomed-ct-to-icd9-screencast/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">1cbdce89-3c5d-4539-a509-659877884c9d</guid>
  <title><![CDATA[SNOMED-CT Core Subset – Significant Changes in July File]]></title>
  <description><![CDATA[<div style="text-align: left;">
	For those of you evaluating the use of the SNOMED-CT Core Subset, you need to be aware that the NLM has made some non-trivial changes to the format and content of the subset file in the latest (second) release dated 200908 (July).</div>
]]></description>
  <pubDate>Mon, 12 Oct 2009 22:37:52 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/october-2009/snomed-ct-core-subset-–-significant-changes-in-jul/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">46dfca3b-a875-47dc-be1e-6e21d5b185ef</guid>
  <title><![CDATA[Problem Lists: The Cacophony of Concatenation]]></title>
  <description><![CDATA[I have spent some time recently looking into terminologies that are used to represent problem lists.&nbsp; Specifically the terminologies in question are the current de facto standard ICD-9, its successor ICD-10CM and the big Kahuna SNOMED-CT.]]></description>
  <pubDate>Sat, 12 Sep 2009 01:09:20 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/september-2009/problem-lists-the-cacophony-of-concatenation/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">f24da1d0-cb77-4218-a62c-b05496e381b2</guid>
  <title><![CDATA[SNOMED-CT Essentials and CORE subset screen cast]]></title>
  <description><![CDATA[I had a request to do a screen cast on the new SNOMED-CT CORE&nbsp;subset.&nbsp; In order to do it justice, I decided to provide an overview of the SNOMED-CT Essentials terminology and the CORE subset together to provide context for people that are new to both.]]></description>
  <pubDate>Mon, 17 Aug 2009 15:50:57 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/august-2009/snomed-ct-essentials-and-core-subset-screen-cast/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">4ceef405-8198-43ae-858f-5b147fd75ded</guid>
  <title><![CDATA[SNOMED CT - CORE Subset - Quick Overview and Impressions]]></title>
  <description><![CDATA[I recevied an email from the NLM UMLS Users listserv today&nbsp;with the following&nbsp;subject &#39;CORE Problem List Subset of SNOMED CT Now Available&#39;.&nbsp; Being a UMLS enthusiast, I quickly downloaded the data and&nbsp;scoped it out.&nbsp; I thought I would share what I found out with you.]]></description>
  <pubDate>Tue, 21 Jul 2009 15:39:02 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/july-2009/snomed-ct-core-subset-quick-overview-and-impressio/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">a78623a0-58d2-43d5-ae3d-b3da45bfd31f</guid>
  <title><![CDATA[Basic Interoperability with RxNorm]]></title>
  <description><![CDATA[As we here at Clinical Architecture have been developing our Symedical product, I have had the pleasure of spending some quality time with UMLS Metathesaurus and RxNorm.&nbsp; As I was going through this journey of discovery, I thought to myself that it might be a good idea to share my findings and experiences with others who might also be looking into using RxNorm and UMLS to enhance or improve their clinical interoperability.
<div>
 &nbsp;</div>
]]></description>
  <pubDate>Fri, 10 Jul 2009 13:43:06 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/july-2009/basic-interoperability-with-rxnorm/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">18c44ac0-5ceb-49a2-a004-92fd796d8c9a</guid>
  <title><![CDATA[What are the characteristics of a good terminology?]]></title>
  <description><![CDATA[When looking into what makes a good terminology, I would be remiss if I did not mention Dr. James Cimino&#39;s &lsquo;<a href="http://www.dbmi.columbia.edu/cimino/" mce_href="http://www.dbmi.columbia.edu/cimino/">Desiderata for Controlled Medical Vocabularies in the 21<sup>st</sup>&nbsp;Century&#39;</a>.&nbsp; Dr. Cimino&#39;s body of work is very enlightening and this particular publication started me on my personal journey into medical informatics.]]></description>
  <pubDate>Fri, 12 Jun 2009 21:56:39 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/june-2009/what-are-the-characteristics-of-a-good-terminology/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">a54a60fb-66a8-41bf-8833-10344cc51038</guid>
  <title><![CDATA[Medical Terminologies - What’s in a Name?]]></title>
  <description><![CDATA[If you are new to the wonderful world of Medical Terminologies, it can be somewhat confusing.<br />
<br />
This series of articles is designed to provide my perspective on what medical terminologies are, how they work, what&#39;s good about them and what can make them hard to use.&nbsp; I am a practitioner of guerilla informatics.&nbsp; Therefore, my thoughts and opinions may not be representative of the &quot;official&quot; informatics community.&nbsp; For the record, I think that the ongoing work of the &quot;official&quot; informatics community is important and vital to the evolution of healthcare.&nbsp; My objective here is to take a complex topic and&nbsp;try to make it more accessible. (So don&#39;t form a mob and come after me at the next AMIA conference...)<br />
]]></description>
  <pubDate>Thu, 14 May 2009 23:13:46 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/may-2009/medical-terminologies-what’s-in-a-name/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">bf073d4f-84fe-4de5-af9e-8e81a175c3a8</guid>
  <title><![CDATA[The Audacity of Scope : Project Execution Pointers #1]]></title>
  <description><![CDATA[Project Execution Pointers are my thoughts on why projects go astray and what prevents us, as faithful software professionals, from achieving our objectives in a swift and effective manner.&nbsp;]]></description>
  <pubDate>Thu, 23 Apr 2009 14:34:08 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/april-2009/the-audacity-of-scope-project-execution-pointers-1/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">f9cf2532-3904-4cfc-82f8-fcb94193c432</guid>
  <title><![CDATA[Rule of Thumb – Drug Allergy Alerts]]></title>
  <description><![CDATA[One of the most often implemented clinical decision support modules, across the spectrum of healthcare applications, is drug allergy checking.&nbsp; In drug allergy checking a patient&#39;s allergies, or prior adverse reactions, are noted. When a drug is prescribed, it is checked against the noted allergies to see if there is a possibility that the drug could induce a reaction in the patient.]]></description>
  <pubDate>Thu, 26 Mar 2009 22:51:38 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/march-2009/rule-of-thumb-–-drug-allergy-alerts/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">b0c52bdb-7b91-4e64-8fd8-0abf23f2d837</guid>
  <title><![CDATA[Clinical Interoperability - The Antics of Semantics]]></title>
  <description><![CDATA[Semantic interoperability deals with the actual &quot;language&quot; contained in the conversation between applications.&nbsp; Solving the syntactic interoperability issue by using a standard message format does not mean that the terms used by one application are the understood by the other.]]></description>
  <pubDate>Tue, 17 Mar 2009 14:10:05 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/march-2009/clinical-interoperability-the-antics-of-semantics/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">5b3cda9b-937c-40da-ab2f-0ebef17da1e9</guid>
  <title><![CDATA[Clinical Interoperability - Getting the message across]]></title>
  <description><![CDATA[As mentioned in the first article in this series, two critical parts of Clinical Interoperability are physical and syntactic interoperability. &nbsp;&nbsp;These two are essentially the first and second of what I consider to be the four laws of interoperability dynamics.]]></description>
  <pubDate>Sun, 08 Mar 2009 20:32:55 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/march-2009/clinical-interoperability-getting-the-message-acro/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">591cfaca-ea56-492a-a9b4-90aa79d8d45f</guid>
  <title><![CDATA[Why is Clinical Interoperability Important?]]></title>
  <description><![CDATA[Now that we have a documented definition for clinical interoperability and its macro components, the next reasonable question is: &quot;Why is clinical interoperability important?&quot;]]></description>
  <pubDate>Mon, 02 Mar 2009 09:57:10 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/march-2009/why-is-clinical-interoperability-important/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">7a881f40-b040-42d5-98bf-4173dd0139ef</guid>
  <title><![CDATA[What is Clinical Interoperability?]]></title>
  <description><![CDATA[If you have seen the movie&nbsp;<strong><em>Independence Day</em></strong>, you may recall that the nerd/hero of the movie, played by Jeff Goldblum,&nbsp;saves the day by interfacing with the alien mother ship and uploading a virus from the modem on his laptop. &nbsp;When I saw this the first time, I looked around at the other people in the audience to see if it was just me, or if they too wanted to walk out of the theater. &nbsp;I know that while watching a movie, especially about alien invasions, you are supposed to &lsquo;suspend your disbelief.&#39; &nbsp;At that point in the movie, I would not have had to suspend my disbelief any further if, in the next scene, he attacked the mother ship while riding on the back of a unicorn.]]></description>
  <pubDate>Mon, 23 Feb 2009 10:26:45 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/february-2009/what-is-clinical-interoperability/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">c1215e4a-aa27-4d78-8c53-bfd0beaafa09</guid>
  <title><![CDATA[Three Principles of Good Architecture]]></title>
  <description><![CDATA[The Roman architect&nbsp;<a href="http://en.wikipedia.org/wiki/Marcus_Vitruvius_Pollio" mce_href="http://en.wikipedia.org/wiki/Marcus_Vitruvius_Pollio" target="_new">Vitruvius</a>&nbsp;in his treatise on architecture, De Architectura, asserted that there were three principles of good architecture]]></description>
  <pubDate>Thu, 29 Jan 2009 16:06:16 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/january-2009/three-principles-of-good-architecture/?feed=blogs]]></link>     	
</item>
<item>
  <guid isPermaLink="false">40b8ca71-26d8-42be-b1e6-44287dcec7af</guid>
  <title><![CDATA[Architecture Happens]]></title>
  <description><![CDATA[As a technologist,&nbsp;one can be very tempted to use labels to deprecate something you don&#39;t agree with or don&#39;t understand.&nbsp; This happens with the term &lsquo;Architecture&#39; all the time.&nbsp; When asked about an older system that we inherited or an application we are tasked with renovating, it is easy shrug off the notion of an underlying architecture.&nbsp; I think when we do that, we short change our ability to understand how a system works and thus making our jobs more difficult.]]></description>
  <pubDate>Wed, 28 Jan 2009 13:03:43 GMT</pubDate>
  <link><![CDATA[http://www.clinicalarchitecture.com/blog/clinical-architecture-healthcare-it-blog/january-2009/architecture-happens/?feed=blogs]]></link>     	
</item></channel>
</rss>

