FAQs - Single Sign-On (SSO)

Question

Response

Can we lock the session down to a specific patient record?

Yes, there is a parameter that can be used to prevent switching between patient records.

If this is used, the professional isn’t shown the “Back to My Patients” option within the patient’s record in PKB.  To view another patient’s PKB record, they’ll have to return to the source system to initiate another PKB session.

Can the PKB session be opened in an iFrame?

Yes, technically that is possible, but requires additional configuration on PKB’s side.

Can we choose which page the user lands on when jumping off into PKB?

Yes, you can configure the user to land in whatever page within PKB’s UI you’d like.  For example, a professional can land directly on the summary page or on the test result page.

Does the user have to grant permission every time they login to the source system?

No.  There are access/refresh tokens that are managed by the customer, and as long as there is a valid access token for the specific user, jumping directly into PKB can happen after the initial pairing.

We are outside of the UK and don’t hold NHS numbers for patients. What else can we use as a patient identifier?

If you cannot use NHS numbers, patient email addresses can be used as a patient identifier when directing users into patient records.

Can an SSO be used by both Clinicians and Patients?

Yes, it is possible to set up an SSO for clinicians or for patients. Configuration is performed by PKB to set which type of users can use your SSO workflow.

When the SSO session is locked down to a specific patient’s record, there’s no logout option. Do I need to worry about users remaining logged into their SSO PKB session in these instances?

No, the OTP launch will log out any existing user before it logs the new one in.