Stream: CARIN IG for Blue Button®
Topic: 11/18-19 CARIN Connectathon - Optum server
Chris Connor (Nov 18 2020 at 18:16):
Auth endpoints:
https://authz.flex-test.optum.com/oauth/authorize/optumid/rmhp
https://authz.flex-test.optum.com/oauth/token
FHIR endpoint:
https://fhir.flex-test.optum.com/R4
Let me know your redirect info and I can set you up with credentials. Contact me here, chris.connor@optum.com or in breakout room 5.
Chris Connor (Nov 18 2020 at 19:04):
EOB endpoints -
https://fhir.flex-test.optum.com/R4/ExplanationOfBenefit?patient=551261670
https://fhir.flex-test.optum.com/R4/ExplanationOfBenefit/551261670
Chris Connor (Nov 18 2020 at 19:10):
Auth endpoint:
https://authz.flex-test.optum.com/oauth/authorize/optumid/rmhp
https://authz.flex-test.optum.com/oauth/token
FHIR endpoint:
https://fhir.flex-test.optum.com/R4
Client Id - CONNECT
Client Secret - DEMOSECRET
Scopes - claims clinical demographics
Member Login credentials:
UserId: fhirfighters_01@optum.com
Password: CB7fC2x4
If prompted for colors, sports team or pet – black, panthers, dog
After acknowledging, Select Member access
If you're using postman, OAuth2 token request would look like this: image.png
James Kizer (Nov 18 2020 at 19:13):
Hi @Chris Connor CommonHealth would like to connect. We're a public oauth client and our redirect is https://appdev.tcpdev.org/m/phr/oauth/redirect
Michele Mottini (Nov 18 2020 at 19:14):
Scopes: claims clinical demographics
These are not valid SMART scopes
Chris Connor (Nov 18 2020 at 19:57):
@James Kizer the information posted previously has all the URLs and member login info. I created a set of credentials for you that is set up with that redirect url -
Client id - COMMONW
Client Secret - DEMOSECRET
Chris Connor (Nov 18 2020 at 21:08):
@Hari Makkala here's the stream with the connection info. Once you let me know your auth redirectURL, I'll set you up and provide a client id
Kate Skrocki (Nov 18 2020 at 21:32):
@Chris Connor do you have any plans to return patient id in the token response? It appears that the EOB resource is loaded based on the token passed in. We are used to having the patient id returned in the token response and passing that id in on subsequent FHIR resource requests. Thanks.
Chris Connor (Nov 18 2020 at 22:01):
Yes, it's planned. I'm told that if you add openid to the scopes, it will return an additional id_token with an identifier
James Kizer (Nov 18 2020 at 22:01):
Thanks @Chris Connor! I'm now trying to authenticate, but getting the following text in my browser:
Error Page
Status code: 404
Exception Message: N/A
Michele Mottini (Nov 18 2020 at 22:02):
...it should return the patient ID in the patient property of the token response (if the client requested launch/patient)
Last updated: Apr 12 2022 at 19:14 UTC
