{"action":"created","issue":{"url":"https://api.github.com/repos/smart-on-fhir/smart-on-fhir.github.io/issues/76","labels_url":"https://api.github.com/repos/smart-on-fhir/smart-on-fhir.github.io/issues/76/labels{/name}","comments_url":"https://api.github.com/repos/smart-on-fhir/smart-on-fhir.github.io/issues/76/comments","events_url":"https://api.github.com/repos/smart-on-fhir/smart-on-fhir.github.io/issues/76/events","html_url":"https://github.com/smart-on-fhir/smart-on-fhir.github.io/issues/76","id":101100700,"number":76,"title":"Do EHRs need to be OIDC Identity Providers?","user":{"login":"jmandel","id":313089,"avatar_url":"https://avatars.githubusercontent.com/u/313089?v=3","gravatar_id":"","url":"https://api.github.com/users/jmandel","html_url":"https://github.com/jmandel","followers_url":"https://api.github.com/users/jmandel/followers","following_url":"https://api.github.com/users/jmandel/following{/other_user}","gists_url":"https://api.github.com/users/jmandel/gists{/gist_id}","starred_url":"https://api.github.com/users/jmandel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jmandel/subscriptions","organizations_url":"https://api.github.com/users/jmandel/orgs","repos_url":"https://api.github.com/users/jmandel/repos","events_url":"https://api.github.com/users/jmandel/events{/privacy}","received_events_url":"https://api.github.com/users/jmandel/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/smart-on-fhir/smart-on-fhir.github.io/labels/specification","name":"specification","color":"5319e7"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":16,"created_at":"2015-08-14T20:49:24Z","updated_at":"2015-09-02T00:52:08Z","closed_at":null,"body":"> Are we requiring EHRs to be identity providers, thus requiring them to implement section \"15.1.  Mandatory to Implement Features for All OpenID Providers\" for OpenID Connect?  This adds quite a bit to the EHR's requirements, and will require running EHRs through the OpenID Connect conformance features.  This also gets QUITE complicated if the EHR itself is an OpenID Connect relying party... it has to pass-through much of the functionality to the upstream OIDC IdP.\r\n\r\nIn-context at: http://fhir-docs.smarthealthit.org/argonaut-dev/specification/#q-issue-76"},"comment":{"url":"https://api.github.com/repos/smart-on-fhir/smart-on-fhir.github.io/issues/comments/136904440","html_url":"https://github.com/smart-on-fhir/smart-on-fhir.github.io/issues/76#issuecomment-136904440","issue_url":"https://api.github.com/repos/smart-on-fhir/smart-on-fhir.github.io/issues/76","id":136904440,"user":{"login":"bakerdb","id":10760477,"avatar_url":"https://avatars.githubusercontent.com/u/10760477?v=3","gravatar_id":"","url":"https://api.github.com/users/bakerdb","html_url":"https://github.com/bakerdb","followers_url":"https://api.github.com/users/bakerdb/followers","following_url":"https://api.github.com/users/bakerdb/following{/other_user}","gists_url":"https://api.github.com/users/bakerdb/gists{/gist_id}","starred_url":"https://api.github.com/users/bakerdb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bakerdb/subscriptions","organizations_url":"https://api.github.com/users/bakerdb/orgs","repos_url":"https://api.github.com/users/bakerdb/repos","events_url":"https://api.github.com/users/bakerdb/events{/privacy}","received_events_url":"https://api.github.com/users/bakerdb/received_events","type":"User","site_admin":false},"created_at":"2015-09-02T00:52:08Z","updated_at":"2015-09-02T00:52:08Z","body":"Thank you @whitehatguy for getting us back to the issue at hand.  I don't think our profile should dictate EHR architecture.  "}}