<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://community.recordsforliving.com/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>HealthFrame Discussion</title><link>http://community.recordsforliving.com/forums/8/ShowForum.aspx</link><description>Discussion about HealthFrame, including bugs, questions, feature suggestions, etc.</description><dc:language>en-US</dc:language><generator>CommunityServer 2.0 (Build: 60217.2664)</generator><item><title>Re: Code Sets - Application Change Request</title><link>http://community.recordsforliving.com/forums/thread/1600.aspx</link><pubDate>Mon, 26 Jul 2010 21:51:52 GMT</pubDate><guid isPermaLink="false">acfe26b8-79fc-43e3-8be5-02be2b0ad202:1600</guid><dc:creator>support@RecordsForLiving.com</dc:creator><slash:comments>0</slash:comments><comments>http://community.recordsforliving.com/forums/thread/1600.aspx</comments><wfw:commentRss>http://community.recordsforliving.com/forums/commentrss.aspx?SectionID=8&amp;PostID=1600</wfw:commentRss><description>Once we release HealthFrame v3 - we will release it with the latest version of the UMLS data sources. Our current development build is using the 2010AA release.&lt;br /&gt;&lt;br /&gt;The issue of more frequent releases however - we will need to continue to consider. I certainly appreciate your desire (and others) to see frequent updates. The problem is - with every new content update, we need to undergo significant analysis and regression checking. Just  because the NLM releases a new version of the UMLS content, doesn't mean their release is bug free, or that even if its bugfree from their perspective, that it doesn't cause some problem with how we are using it.&lt;br /&gt;&lt;br /&gt;So we test very carefully - examining all their changes for mapping issues.&lt;br /&gt;&lt;br /&gt;Right now - I'm working on ways to automate much of that validation, and if we can come up with reliable tools, we maybe able to go to semi-annual or even quarterly reference content updates.&lt;br /&gt;&lt;br /&gt;Certainly - we should be able to do better than we've done so far in keeping up to date ;-) Thanks for your patience and your feedback&lt;br /&gt;&lt;br /&gt;    Support Team.</description></item><item><title>Code Sets - Application Change Request</title><link>http://community.recordsforliving.com/forums/thread/1589.aspx</link><pubDate>Mon, 21 Jun 2010 11:24:32 GMT</pubDate><guid isPermaLink="false">acfe26b8-79fc-43e3-8be5-02be2b0ad202:1589</guid><dc:creator>Rob49</dc:creator><slash:comments>0</slash:comments><comments>http://community.recordsforliving.com/forums/thread/1589.aspx</comments><wfw:commentRss>http://community.recordsforliving.com/forums/commentrss.aspx?SectionID=8&amp;PostID=1589</wfw:commentRss><description>Redesign application (or provide a utility function) to allow more timely updates of medical information databases (e.g. UMLS, IDC-9, RxNorm, SNOMED CT, etc.).&lt;br&gt;&lt;br&gt;The medical databases, like UMLS, are update buy their owners multiple times per year but HealthFrame currently does not provide updates until a new version is released.&amp;nbsp; Even then, some of the application's code sets within HealthFrame appear to not have been updated since 2005.&amp;nbsp; The lack of timely updates of the code sets needs to be addressed.&lt;br&gt;&lt;br&gt;While HealthFrame does allow entries without a match from the included code sets, this does prevent the needed  coding for the CCR and CCD formatted files.&lt;br&gt;</description></item></channel></rss>