HealthVault application architecture - Quick notes

Image via Wikipedia

HealthVault application architecture primary revolves around the following:
- Where is data stored?
- When is data accessed?
- How is user authenticated?

Where is data stored?
#1 Stored only in HealthVault
#2 Most of the data stored in HealthVault and remaining in application data store
#3 Data duplicated in HealthVault and application data store

Among above, #1 and #2 doesn't require synchronization between HealthVault and Application data store. #3 does require synchronization between them, which makes the system either simple or complex.

When is data accessed?
- The application requires permission from user everytime accessing the data from HealthVault
- The application requires permission only once from user and can access HealthVault data anytime from then without requiring permission from the user

How is user authenticated?
- Require the user to authenticate every time the application is accessing HealthVault data
- Require authentication once and store the relevant information for authentication-free subsequent access

Conclusion:
Requiring permission from user everytime to access their health record would be an impediment to doctors or any health care staff for adopting EMRs. Also, this wouldn't work in times of medical emergency. On the other hand, given a free hand to EMR would make the system more user friendly by performing underlying authentication in a transparent manner. But, users should be cautious about such access requests.

For those interested in processes, CodePlex has a HealthVault solutions development framework here.