Mike,
Here's some information about the location of HealthFrame's database files.
HealthFrame Viewer was designed to support the exchange of clinical record information between patients and their healthcare providers.
Currently, it is rare for patients and providers to both have access to electronic medical record software. HealthFrame Viewer fills this void and makes it possible for individuals who do not own a clinical record application - such as HealthFrame Explorer - to still be able to view personal health record (PHR) data.
Given that HealthFrame Viewer provides a subset of the functionality available in HealthFrame Explorer, we did not initially consider the value in supporting access to the local databases. In other words, we thought that if one owned HealthFrame Explorer, why would one use the HealthFrame Viewer instead, given its limitations?
With that model in mind, the current implementation of the HealthFrame Viewer expects that the PHR data has first been exported. The reader can then open the exported file in HealthFrame Viewer. Future versions of the HealthFrame Viewer will likely remove this limitation and allow access to local databases, in addition to PHR exports and other data repositories.
Thank you for your interest in HealthFrame and please let us know if we can be of further assistance.
Support Team