Addressing a PHR

1. Proposed Workitem: Addressing a PHR

• Proposal Editor: Charles Parisot
• Editor: N/A
• Date: N/A (Wiki keeps history)
• Version: 0.3
• Domain: IT Infrastructure

2. The Problem

A consumer/citizen would benefit from a “standard address” for his/her own PHR System. In IHE terms, a PHR System is either a Affinity Domain where the XDS Registry is grouped with the consumer PHR Systems (PHR centric Affinity Domain), or the PHR System is an edge system (doc source/doc consumer) in an Affinity Domain, through which the patient has access to the Affinity Domain health information. In either case, it would be effective that a Consumer/Citizen could give to any Doc Source/Doc Consumer the “electronic address” where his/her personal records may be accessed or contributed.

3. Key Use Case

A patient wants visits a physician office, provide his “electronic PHR address”, and associated “access control” token, so that the physician through his local EHR may query and retrieve documents shared by the patient from his/her PHR system, and at the end of the visit upload a set of documents to a proper repository (in the Patient PHR or shared in the Affinity Domain) to provide and register these documents.

4. Standards & Systems

Existing systems possibly involved in the problem/solution: XDS Affinity domains (Repository and Registry) and possibly any system allowing communication between two affinity domains (e.g. XCA gateway)

Standards possibly relevant to the solution: as for XDS profile (i.e.: ebRIM, ebRS, SOAP)

5. Discussion

There isn't any possibility to copy documents straight from one repository to another.

The existence of multiple Affinity Domains interconnected via XCA could be facilitated, if the consumer/citizen would be able to provide (smart card, paper card) simple addressing information to facilitate the access from the local affinity domain (where the patient is presently) to the affinity domain where the patients’ PHR usually operates.