Update ~ 10:00 AM PT: PassportMD’s server certificate expired more than a month ago and hasn’t been renewed, but I’m no longer receiving the SOAP-ERROR messages during log-in, which is much slower than earlier trials. However, attempts from the PassportMD HealthVault page to synchronize data from HealthVault: Passport’s new Thawte certificate is dated, a month after their original certificate expired. After a substantial delay, the login no longer shows a certificate error. However, a HealthVault representative requested me to retry signing on. Update 12:10 AM PT: My initial attempts to log in with secure HTTP (HTTPS) to my PassportMD account today () encountered a certificate error with an expired (on ) Thawte Server Certificate. Microsoft’s Sean Nolan says PassportMD’s problem was fixed on. Update : Sync operations with Microsoft HealthVault no longer fail with the error message below. My interest in this topic stems from my belief that PHRs will become one of the largest single consumer markets for public cloud-based Platform as a Service (PaaS) and Infrastrucure as a Service (IaaS) providers. I established an account for both of us about two weeks ago and made some initial entries. I’ve been experimenting with creating personal health records (PHRs) for my wife and me using Microsoft’s HealthVault as the primary cloud data store and PassportMD as an alternative UI.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |