|
Search
You searched for the word(s):
Showing page 9 of 70 (700 total posts)
< 1 second(s)
-
Thank you for this suggestion.
Because this report is currently implemented as an OpenHealth service (external plugin report) - it cannot access the HealthFrameWorks reference content database which contains that mapping of brand names to generic names.
We've added a bug report to track this request and will likely create a new (builtin) report ...
-
Thank you for your follow up. I can now see even better how/why this would be useful.
Due to quirks of our development process (its easier to add reports after we release a product than other sorts of changes) - I cannot promise this will be addressed before HealthFrame v3 ships. We are anxious to ship as soon as possible.
However, I've elevated ...
-
There is currently no such report in HealthFrame v2. One could create an OpenHealth service plugin to create such a report, but it wouldn't be easy, because the XML data representation of calendar items is normalized, and doesn't redundantly include computed calendar entries which are typically the majority of entries.
This issue has been raised ...
-
Right now - our focus at Records For Living is finishing up the HealthFrame v3 release.
Once that is completed, we do have plans to introduce more 'web-based' solutions - allowing patients to store their records in a distributed fashion. In fact -much of that functionality is already in the HealthFrame v3 code base.
We have long considered doing
-
If you still have access to your old computer (not the backups - but the running computer system), the easiest way to transfer your data is to:
(1) Run HealthFrame on the old computer
(2) REPEAT ONCE FOR EACH PHR
(2A) Open the PHR
(2B) Select ''Save PHR Backup'' from the menu - AND REMEMBER WHERE YOU SAVED
(3) Take the backups ...
-
Before upgrading, we recommend making backup files for each of your PHRs, and saving them someplace.
Then on the new computer, you can re-install HealthFrame, and restore from those backups.
From your description, its unclear exactly what you've done. If you simply updated your copy of Windows in-place, then HealthFrame (and any other ...
-
This is a known problem with HealthFrames CCD support.
Really - its two problems - which is why there is no easy fix.
The first 'problem' - is that when running OpenHealthService plugins - HealthFrame has a TIMEOUT period. Since OpenHealthServices are plugins which anybody can write, HealthFrame cannot be sure if they take a long time that they ...
-
The HealthFrame v2 data model only supports tracking of medical expenses, and not tracking transfers into accounts (which is needed to compute some of the things you are talking about).
Future versions of HealthFrame will support a more elaborate data model, so you can track accumulation of funds in a health savings account, adjustments, etc. And
-
Please clarify exactly what report you are using, and what information is being cut off.
If you use the 'Susan Taylor' Sample file, you can generate the report below. Note the Home > Reports > ... 'bread crumbs' can be used by you to navigate down to exactly that report on your PHR.
-
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.
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
... 9 ...
|
|