Stream: Da Vinci PDex
Topic: Implementers
Mark Scrimshire (Feb 24 2021 at 02:06):
Creating this stream to capture questions from implementers of the Payer Data Exchange (PDex) IG
Lloyd McKenzie (Feb 24 2021 at 03:48):
Can't implementers create whatever thread they like for questions here? That's the normal pattern in Zulip - one thread per question...
Anusha (Feb 25 2021 at 15:28):
Did I post my question about provenance in the wrong place? I'd just created a new topic for it.
Lloyd McKenzie (Feb 25 2021 at 15:29):
Creating topics is fine
Lakshminarayanan (Mar 26 2021 at 16:24):
In a payer to payer data exchange, when using the $everything operation on a member, what type of FHIR message exchange is preferred to enable offline transfer
NARASIMHA MURTHY (Apr 09 2021 at 03:55):
Hi @Mark Scrimshire ,
I have 2 questions related to Payer to Payer data exchange.
-
I read that using FAST/CAQH one plan can discover the other plans. Is FAST a specification to discover the Fhir end points of other payer plans?. I am not very clear on this, Please elaborate. What other information does FAST provide about a new payer plan apart from Fhir end point. Does it also provide AUTH and Token end points for OAUTH2.0? Please let me know where I can get more details about FAST spec. I think FAST and CAQH solutions are the core for payer to payer exchange to be successful. Please let me know, if there is any useful links or materials related to FAST and CAQH.
-
Assuming we discover the new plan using FAST/CAQH, how do we get the OAUTH2.0 access tokens for other plans. Because OAUTH2.0 requires initial registration post that only we get the client id and client secret which are required to get an OATH2.0 token. My question is how do we register and maintain so many payers for OAUTH2.0? Is FAST and CAQH is going help there as well. Please elaborate.
thanks,
Narasimha
Last updated: Apr 12 2022 at 19:14 UTC
