<?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>Password protection/encryption</title><link>http://community.recordsforliving.com/forums/thread/742.aspx</link><pubDate>Thu, 14 Jun 2007 22:41:03 GMT</pubDate><guid isPermaLink="false">acfe26b8-79fc-43e3-8be5-02be2b0ad202:742</guid><dc:creator>support@RecordsForLiving.com</dc:creator><slash:comments>0</slash:comments><comments>http://community.recordsforliving.com/forums/thread/742.aspx</comments><wfw:commentRss>http://community.recordsforliving.com/forums/commentrss.aspx?SectionID=8&amp;PostID=742</wfw:commentRss><description>In thread &lt;a HREF="/forums/thread/736.aspx"&gt;http://community.recordsforliving.com/forums/thread/736.aspx &lt;/a&gt;Ted asks&lt;br&gt;&lt;br&gt;&lt;blockquote&gt;&lt;font color="navy" face="Arial" size="2"&gt;&lt;span&gt;&lt;span&gt;5)&lt;font face="Times New Roman" size="1"&gt;&lt;span&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/font&gt;&lt;/span&gt;&lt;/span&gt;&lt;/font&gt;&lt;font color="navy" size="2"&gt;&lt;span&gt;Does the application
use any kind of password protection or encryption to prevent “visiting”
users from accessing the application with family records on it?&amp;nbsp; Or for
that matter to prevent children from altering records?&lt;br&gt;&lt;br&gt;&lt;/span&gt;&lt;/font&gt;&lt;/blockquote&gt;5) Yes, HealthFrame supports both password protection and encryption, including for HealthFrame backup files.&amp;nbsp; You should note however that "exports" are not encrypted, since they are designed to be exchanged via mechanisms that are encrypted themselves - for instance - when you exchange clinical information using HTTPS - an encrypted transport mechanism.&lt;br&gt;&lt;br&gt;&lt;br&gt;Thanks,&lt;br&gt;Support Team&lt;font color="navy" size="2"&gt;&lt;span&gt;&lt;/span&gt;&lt;/font&gt;&lt;br&gt;&lt;font color="navy" size="2"&gt;&lt;span&gt;&lt;/span&gt;&lt;/font&gt;&lt;blockquote&gt;&lt;font color="navy" size="2"&gt;&lt;span&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;/span&gt;&lt;/font&gt;&lt;/blockquote&gt;&lt;font color="navy" size="2"&gt;&lt;span&gt;&lt;/span&gt;&lt;/font&gt;&lt;br&gt;&lt;font color="navy" size="2"&gt;&lt;span&gt;&lt;/span&gt;&lt;/font&gt;</description></item></channel></rss>