<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0">
<channel>
<title>Reports</title>
<copyright>Copyright (c) 2013 Dublin Institute of Technology All rights reserved.</copyright>
<link>http://arrow.dit.ie/teapotrep</link>
<description>Recent documents in Reports</description>
<language>en-us</language>
<lastBuildDate>Wed, 15 May 2013 12:28:42 PDT</lastBuildDate>
<ttl>3600</ttl>








<item>
<title>Terminology Enhanced EHR: integration of archetypes and terminology, an implementation experience</title>
<link>http://arrow.dit.ie/teapotrep/3</link>
<guid isPermaLink="true">http://arrow.dit.ie/teapotrep/3</guid>
<pubDate>Wed, 12 Jan 2011 06:45:03 PST</pubDate>
<description>
	<![CDATA[
	<p>The integration of terminology and EHR information models is an important step in the journey towards semantic interoperability. Archetypes and two-level models for EHRs provide a mechanism that not only applies constraints on clinical content but also ensures effective terminology binding. However the lack of a standardised mechanism to bind terminology to the EHR and the difficulty of systematically coding clinical content, has led to a number of possible implementation choices.   This study presents a review of the problems that may occur when working with modern terminology systems and discusses some related state of art technologies. The paper aims to share the experience of prototyping a minimum terminology integration service. A set of tools utilising medical text processing and a customised SNOMED-CT data source are the output of prototyping that enables quick processing of archetypes and automatic link suggestions to SNOMED-CT. The elaboration of prototypes of this sort can be used as components of an integration engine.</p>

	]]>
</description>

<author>Sheng Yu et al.</author>


</item>






<item>
<title>MirthConnect howto document</title>
<link>http://arrow.dit.ie/teapotrep/2</link>
<guid isPermaLink="true">http://arrow.dit.ie/teapotrep/2</guid>
<pubDate>Wed, 12 Jan 2011 06:01:07 PST</pubDate>
<description>
	<![CDATA[
	<p>This document aims at describing the steps involved in installing and configuring Mirth Connect so as to produce an EN13606-compliant record extract from an HL7v2 message using the LinkedEHR- produced xquery.</p>

	]]>
</description>

<author>Sebastien Pardon et al.</author>


</item>






<item>
<title>Use of OIDs and IIs in EN13606</title>
<link>http://arrow.dit.ie/teapotrep/1</link>
<guid isPermaLink="true">http://arrow.dit.ie/teapotrep/1</guid>
<pubDate>Wed, 12 Jan 2011 05:35:30 PST</pubDate>
<description>
	<![CDATA[
	
	]]>
</description>

<author>Damon Berry et al.</author>


</item>





</channel>
</rss>
