<?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: Relationships broken during export/import in Healthframe format</title><link>http://community.recordsforliving.com/forums/thread/1959.aspx</link><pubDate>Tue, 07 Aug 2018 00:55:48 GMT</pubDate><guid isPermaLink="false">acfe26b8-79fc-43e3-8be5-02be2b0ad202:1959</guid><dc:creator>dealio</dc:creator><slash:comments>0</slash:comments><comments>http://community.recordsforliving.com/forums/thread/1959.aspx</comments><wfw:commentRss>http://community.recordsforliving.com/forums/commentrss.aspx?SectionID=8&amp;PostID=1959</wfw:commentRss><description>&lt;div&gt;Thanks for the warning about relationships being lost. I've not run into that yet, but now I know to be wary of it.&lt;/div&gt;&lt;div&gt;&lt;br&gt;&lt;/div&gt;&lt;div&gt;To your additional point about the apparent profound lack of support and the software's abysmal update curve, (despite positive reaction to suggested enhancements and additional features) I am disheartened as well. In a market where we have to be our own health advocate, this software and what it could become is an indispensable aid. Because support for it is all but non-existent (it's been 2 years since version 3 came out), I'm forced to consider other options for my health records -- perhaps building my own solution in Microsoft Access until another company sees the potential that this kind of software has and creates something similar but with a modern interface, the option not to store information in the cloud, adequate support and a reasonable update (bug fixes, minor changes) and upgrade (new features) schedule.&lt;/div&gt;&lt;div&gt;&lt;br&gt;&lt;/div&gt;&lt;div&gt;Good luck to you.&lt;br&gt;&lt;/div&gt;</description></item><item><title>Relationships broken during export/import in Healthframe format</title><link>http://community.recordsforliving.com/forums/thread/1954.aspx</link><pubDate>Sat, 09 Jun 2018 13:17:52 GMT</pubDate><guid isPermaLink="false">acfe26b8-79fc-43e3-8be5-02be2b0ad202:1954</guid><dc:creator>Mindsurfer</dc:creator><slash:comments>0</slash:comments><comments>http://community.recordsforliving.com/forums/thread/1954.aspx</comments><wfw:commentRss>http://community.recordsforliving.com/forums/commentrss.aspx?SectionID=8&amp;PostID=1954</wfw:commentRss><description>&lt;div&gt;Beyond the relationship between contacts and contact types being broken during migration from one machine to another, I've just discovered that all Relationships were wiped, too. The data is still there - Tests, Concerns, Treatments, etc.- but the relationships linking the data are gone, except for Vital Statistics on the Visit records, themselves. Grateful the data wasn't lost, but a tremendous amount of work to re-create the relationships.&lt;/div&gt;&lt;div&gt;&lt;br&gt;&lt;/div&gt;&lt;div&gt;Since Novemeber 2017, I've dealt with multiple hospitalizations, over 120 outpatient visits to multiple organizations and over 15 doctors. Healthframe has been invaluable in pulling that information together. While I do not regret purchasing the product, given Records For Living's aspirations for the product, the lack of response on the support forum to reported issues and suggestions for enhancements, and the problems that have emerged, are discouraging.&lt;/div&gt;&lt;div&gt;&lt;br&gt;&lt;/div&gt;&lt;div&gt;Healthframe has a lot of potential and fills a much-needed gap in PHR products. It is among the only PHR products that doesn't rely on Internet-based storage while offering the option. That said, the product needs a development team actively interested in the product and engaged with its users. There are many excellent features in this product, and response to the one email I sent to support was immediate, however the unexplained delay in release of an announced interim release (v3.0.2) with another theoretically already in the works (v3.0.3), and the complete lack of engagement in the support forum and the Facebook account, suggest to potential customers, existing customers, and the public, that the product is moribund.&lt;br&gt;&lt;/div&gt;</description></item></channel></rss>