Why

...

• This one off process is done in order to ensure the user of the application is linked to their record in PKB and avoid the need for them to grant the application access to their PKB record every time they want to use it.

• This process allows the app to determine the patient’s demographics, including identifiers stored within PKB, enabling further interaction with PKB’s APIs for that patient.

How to:

...

Prerequisites

• The patient already has a PKB record they can access.

• If the patient doesn’t have access to a PKB record, the app will need to guide them on how to create one.

How to

Account Creation

• Patient creates an account on the partner app.

• The app ensures the patient login is associated with a unique app_user_id.

...

• The app exchanges the authorization code for an access and refresh token which enable interaction with the PKB APIs specifically for that patient.  

  • Using the authorization code as a parameter, you’ll swap it for an access / refresh token pair.

  • Further details with parameters and example call and response are here.

  • The patient will only do this authorization one time.

  • The app will need to maintain, manage, and associate tokens with the corresponding patient record in the app.

Patient Detail Retrieval

• Using a valid access token, the partner app pulls the patient’s details. There are a few options, two of which are outlined below, and the best option depends on what the partner use case is.

  • PKB public id using the FHIR Purview operation on PKB’s Facade FHIR API. Example is here.

  • Demographic details, including any identifiers (national/local) in the PKB record, using a valid access token and PKB’s REST API. Example is here (/users/self).