Thanks for your suggestions.
>1) remove reason for visit from preparation and post visit, and have it be its own subcategory
Please clarify why you think this would be a good idea. We've already made significant changes to the content of the 'visit' page for 2.0 (mostly surrounding the issue of links to related information).
We have not changed this particular section at all, but do have significant improvements planned to this area for 3.0 (relating to integration with other major new planning features). Our inclination would be to address this issue with 3.0, but if you can clarify now - within the framework of how 1.0 works - why 'reason for visit' would be best off its its own collapsable area, we will consider it for 2.0.
> 2)combine organizations and individuals together into one group
This is already part of our plan for our 3.0 product cycle.
>3)re-define drop down lists to more common names and have lesser knowns
>be use-defined or enable the user to add/remove items to suit thier
needs.
This too is already on our list for our 3.0 product cycle, but its less clear if it will be done for 3.0.
>4)remove start and end dates. most surgeriesand treatments and etc. start and end on the same date
Perhaps most do, but how does the user enter information about those that do not? Many treatments last months or years.
I believe we've made it easier and clearer in 2.0 that these 'end date' fields can be left blank (and what that means).
We do want to make HealthFrame both simple and easy to use, and flexible enough to accomodate all the various things a user might want to keep track of. These interests often pull our user interface in opposite directions.
We welcome your suggestions if you have ideas how we can accomodate the flexability some treatments require, while making it easier for users to handle the most common cases.
Thanks kindly for your suggestions and feedback.
Support Team.