[Openid-specs-heart] FHIR patient ID question

Adrian Gropper agropper at healthurl.com
Wed Dec 21 18:30:20 UTC 2016


Check out Figure 3 (corresponds to Demo 1).

The link between mdNOSH and pNOSH is made in the context of the patient as
established in Step 1. In Step 2, mdNOSH registers a resource that's
specific to the patient as established in the Step 1 context. Every
different patient is registered as a different resource with whatever AS
the patient has specified in Step 1. This not only solves the multiple
portals problem but it also solves the patient ID matching and consent
problems that bedevil today's HIEs.

If you would like help with the code, please let us know via GitHub.

Adrian

On Tue, Dec 20, 2016 at 6:39 PM, Michele Mottini <mimo at careevolution.com>
wrote:

> A question about the Demo 2 diagram at http://hieofone.org/#h.699g5755uivz
> :
>
> step 2 is a FHIR call to get MedicationStatement from mdNOSH to pNOSH,
> this requires mdNOSH to know the patient ID in pNOSH.
>
> When / where that patient ID was transferred / made known to mdNOSH ?
>
>    Thanks
>
>    - Michele Mottini
>    CareEvolution Inc
>
> _______________________________________________
> Openid-specs-heart mailing list
> Openid-specs-heart at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-heart
>
>


-- 

Adrian Gropper MD

PROTECT YOUR FUTURE - RESTORE Health Privacy!
HELP us fight for the right to control personal health data.
DONATE: http://patientprivacyrights.org/donate-2/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-heart/attachments/20161221/48532aff/attachment.html>


More information about the Openid-specs-heart mailing list