There are really several issues here.
First, let me deal with the easiest (and most embarrassing). Internally, HealthFrame maintains a set<> ordered by ID of track locations associated with any contact (including the PHR Owner). So this bug should apply to ALL contacts (pharmacy, doctor, and YOU).
Fortunately, its not a data model error - just a very simple (I hope) to correct coding bug.
I've added a bug report to track this - http://bugzilla.recordsforliving.com/show_bug.cgi?id=1027
And I think we should be able to correct this in the not too distant future.
BTW - though this may seem crazy - as a temporary workaround, what you can do is randomly create new locations. Each new location will be assigned a random ID. That ID wont shift over time, so by trial and error you could get the ordering you want. Thats so bad, I'm not sure I should have even mentioned it ;-)
Hopefully we can squeeze that into v3.0.2?