Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • assertedLoginIdentity: containing the login identity token.

  • prompt (optional): optionally set to force a login prompt from the user.

Example: https://sandbox.patientsknowbest.com/listAppointments.action?assertedLoginIdentity=<sample-token>&prompt=none

The user will be automatically logged in via NHS using the token provided.

...

https://sandbox.patientsknowbest.com/otp.action?otpToken=gnUF6vXCWhZ9QgD4-7s6TE1bSiqfUniw&redirect_uri=%2Fauth%2FpatientSummary.action%3Ftab%3DpatientSummary%26contextUserEmail%3Dpatient@example.com

Prevent patient switching (In development)

If an organisation decides to prevent patient switching, professionals using our OTP solution to log in will not be able to change patient records within PKB. The professional must open each patient’s record in their local system in order to open their PKB record.

To prevent patient switching, an organisation will add an optional parameter in the redirection URL when implementing SSO:

  • lockPatient. When this URL parameter is set to true, the professional will not see links to the patient search page, to log out and to the help page. This parameter will be propagated to any pages opened from the patient record, e.g. if an image is opened in a new tab.

https://sandbox.patientsknowbest.com/otp.action?otpToken=gnUF6vXCWhZ9QgD4-7s6TE1bSiqfUniw&redirect_uri=%2Fauth%2FpatientSummary.action%3Ftab%3DpatientSummary%26contextUserEmail%3Dpatient@example.com%2flockPatient = True

Data availability check

For some use cases it can be helpful to indicate to the user of the external system whether any data exists in PKB for the patient in context which the user of the external system is unlikely to have seen in their own systems, e.g. data from other organisations.

...