[Openid-specs-heart] FHIR patient ID question

Adrian Gropper agropper at healthurl.com
Tue Dec 27 21:28:30 UTC 2016


Michael says:

After dynamic registration, mdNOSH can make a FHIR call to
https://shihjay.xyz/nosh/fhir/Patient to get a list of all available
patients in the pNOSH; that's what it does to get the id which returns only
1.  For the demo (it just assumes that there is only 1 id and it is 1).
Any EHR can make the initial call to get a patient list, but it would be an
unnecessary/redundant operation.

Afterwards any FHIR calls for specific information ie
https://shihjay.xyz/nosh/fhir/Conditions?subject:Patient=1 based on that
patient ID.

On Tue, Dec 27, 2016 at 9:38 AM Michele Mottini <mimo at careevolution.com>
wrote:

> Sorry, I don't get it.
>
> For what I understand  mdNOSH register resource(s) as per
> https://docs.kantarainitiative.org/uma/rec-oauth-resource-reg-v1_0_1.html,
> and register itself as a client as per https://tools.ietf.org/html/rfc7591
> - but I don't see a way to ask for and get back the pNOSH FHIR patient ID
>
>   - Michele
>   CareEvolution Inc
>
> On Wed, Dec 21, 2016 at 1:30 PM, Adrian Gropper <agropper at healthurl.com>
> wrote:
>
> 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/
>
>
>
>
>
>
>
>
> _______________________________________________
>
> Openid-specs-heart mailing list
>
> Openid-specs-heart at lists.openid.net
>
> http://lists.openid.net/mailman/listinfo/openid-specs-heart
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-heart/attachments/20161227/7b646183/attachment.html>


More information about the Openid-specs-heart mailing list