Hsc 2008 Day 2
•
0 likes•261 views
Microsoft HealthVault conference in June 2008. Source: http://msdn.microsoft.com/en-us/healthvault/cc627280.aspx
Recommended
Recommended
More Related Content
Similar to Hsc 2008 Day 2
Similar to Hsc 2008 Day 2 (20)
More from Mohammad Al-Ubaydli
More from Mohammad Al-Ubaydli (20)
Recently uploaded
Recently uploaded (20)
Hsc 2008 Day 2
- 4. Agenda • Basic Tenets • HealthVault integration options • Patient and provider workflows • Development models • Common data sharing scenarios 4
- 5. Basic Tenets • Patient’s HealthVault record is controlled by them/caregiver – They can create, read, update, and delete any data – Access to their data must be authorized by them – They can revoke someone’s access at any time • Patient’s clinical record is controlled by their provider – The provider is responsible for the data – The provider is responsible for determining the basis for medical decisions – The provider must adhere to relevant state and federal regulations with respect to the patient’s clinical information 5
- 6. A TALE OF TWO PRACTICES… 6
- 7. Practice A Practice #1 Practice B Microsoft Corporation 7 Confidential and
- 8. Practice A Practice #1 HealthVault Helps Patients Helps Providers Keep their health history all Get a comprehensive view of in one place & share their their patients’ histories & information with others deliver information to them Practice B Microsoft Corporation 8 Confidential and
- 9. Practice A EMR + PATIENT PORTAL 9
- 10. You already have… • A way for patients to authenticate online • A user interface for patients to interact with their clinical information • Data exchange between your portal and your EMR You’ll need to build… • A user interface for patients to authorize the practice to access their HealthVault information • Storage of the user’s HealthVault Person and Record IDs • The pushing/pulling of information to HealthVault 10
- 11. A HealthVault-integrated Patient Portal THE UX 11
- 12. Microsoft Corporation 12 Confidential and
- 13. Microsoft Corporation 13 Confidential and
- 14. 14
- 15. Microsoft Corporation 15 Confidential and
- 16. Microsoft Corporation 16 Confidential and
- 17. Practice B EMR ONLY 17
- 18. You’ll need a way… • For patients to authenticate online • For patients to authorize the practice to access their HealthVault information HealthVault’s new Patient Connect feature solves this. 18
- 19. To connect to HealthVault, you’ll need… • The patient’s HealthVault Person ID • The patient’s HealthVault Record ID Patients Table Patient_ID 123456 Name John Smith HV_Person_ID Null You’ll get this after the patient authorizes you HV_Record_ID Null 19
- 20. A quick walkthrough of the patient and provider workflow THE UX 20
- 21. Patient & practice discuss sharing information through HealthVault Dfsfd sfd dfdfd sfs XX-X XX 21
- 22. Dfsfd sfd dfdfd sfs A staff member XX-X XX creates and prints an ‘identity code’ for the patient, along with instructions on what to do at home 22
- 23. The identity code • Let’s you verify that the patient is who he says he is • Expose a user interface for practice staff to create and print this for patients • Call HealthVault API, and pass in… – Unique string representing “Patient_ID” Patients Table Patient_ID 123456 – Verification question and answer – Friendly name for the patient 23
- 24. Dfsfd sfd dfdfd sfs A staff member XX-X XX creates and prints an ‘identity code’ for the patient, along with instructions on what to do at home 24
- 25. Dfsfd sfd dfdfd sfs XX-X XX The patient goes to www.healthvault.com to authorize the practice 25
- 26. Microsoft Corporation 26 Confidential and
- 27. Microsoft Corporation 27 Confidential and
- 28. 28
- 29. 29
- 30. 30
- 31. Microsoft Corporation 31 Confidential and
- 32. Completing the connection • Check periodically for new patients • Call HealthVault API, and get back… – The “Patient_ID” string that you passed in Patients Table Patient_ID 123456 – Patient’s HealthVault Person ID – Patient’s HealthVault Record ID 32
- 33. Patients Table Patient_ID 123456 Name John Smith HV_Person_ID 1F5987G0-2F20-98B2-1C3B-9821C74C9273 HV_Record_ID 3F2504E0-4F89-11D3-9A0C-0305E82C3301 You can now… • Connect to the patient’s HealthVault record using HV_Person_ID and HV_Record_ID • Expose a user experience for practice staff to push/pull information to/from the patient 33
- 34. AUTHORIZATION 34
- 35. 35
- 36. 36
- 37. Data sharing scenarios • Lina, who has diabetes, monitors her blood glucose at home and gives her doctor access electronically • Mary builds an electronic medical record for her baby and uses a PHR to manage her family’s health • John receives a discharge summary in his HealthVault record after surgery • Cecilia, an elderly “snowbird” with doctors in different states, keeps track of her medication list in HealthVault • Kai moves to a new city with a full health history, and shares it with his new doctor 37
- 38. Resources • www.msdn.microsoft.com/healthvault – Stories – High-level workflows – Technical documentation – API documentation and samples – Growing data model • Let your HealthVault contact know if you have follow up questions or want to discuss your scenario in more detail 38
- 39. What about paper? 39
- 40. Q&A Kalpita Deobhakta Program Manager, HealthVault Partners Team kalpitad@microsoft.com 40