Ballot#199 Nell Lapres, Epic, on behalf of Isaac Vetter, [email protected] | From: To learn more about the user, the app should treat the “profileâ€...

[jmandel]

Ballot Weight

NEG Enhancement

Where

Scopes and Launch Context :: http://hl7.org/fhir/smart-app-launch/scopes-and-launch-context/

What

Nell Lapres, Epic, on behalf of Isaac Vetter, [email protected]
From: To learn more about the user, the app should treat the �profile� claim as the URL of a FHIR resource representing the current user. This will be a resource of type Patient, Practitioner, or RelatedPerson.
To: To learn more about the user, the app should treat the �profile� claim as the URL of a FHIR resource representing the current user. This will be a resource of type Patient, Practitioner, Person, or RelatedPerson.
Comment: A SMART server should be able to represent the current user with the Person resource, in addition to Patient, Practitioner or RelatedPerson according to the schematic that Matt Randall laid out in https://groups.google.com/forum/#!msg/smart-on-fhir/1F0jcaKxGsg/3Ua3bRgqDAAJ. Documented in smart-on-fhir/smart-on-fhir.github.io#148
Summary: Allow Person resource to represent current user

Josh's Triage Notes

Merge witth theme:Person in OIDC?

Would be good to discuss this, based on feedback in GH.

Disposition

See disposition from theme: "Person in OIDC"

Vote Details

Pro-Con-Abstain:
Date: