The keypair used to sign the JWT must be an RSA keypair. A key size of at least 2048 bits is recommended, but the service also accepts 4096 bit RSA keys. More on this in the JWT (JSON Web Token) section.

Voorbeeld

{
  "sub": "profID1241",
  "jti": "550e8400-e29b-41d4-a716-446655440000",
  "profInfo": {
    "firstname": "John",
    "lastname": "de Vries",
    "email": "john.devries@praktijk.nl"
  },
  "treatmentRelationshipId": "1532",
  "patientInfo": {
    "bsn": "426308505",
    "firstname": "Peter",
    "lastname": "de Mol",
    "email", "peter@gmail.com"
  },
  "iat": 1516239022
}

Opbouw tokens

SSO-token

Name	Type	Count	Description
sub	string	1..1	The unique identifier for the professional that is logging in.
jti	string	1..1	The unique identifier for this specific JWT. Should be random each time, UUID recommended
iat	number	1..1	'Issued at' timestamp. The time this JWT was created (in unix time)
treatmentRelationship Id	string	0..1	A unique identifier for the relationship between this professional and the patient (if any). For more information, see note.
	ssoTokenProfInfo	0..1	Additional information about the professional that is logging in. For more information, see note.
patientInfo	ssoTokenPatientInfo	0..1	Additional information about the patient into whose context the professional is logging in.

treatmentRelationshipId: If multiple professionals share the same TR ID with a patient the professionals are enabled to work together and share data with eachother about this patient. If this field is given, the professional will automatically be logged in to this patient context. This field may also be unique for each patient/professional combination, to highlight simple prof/patient relationships. If this is not given but a bsn is provided in the patientInfo field, the SSO service automatically generates a unique professional/patient relationship.

profInfo: The information provided in this field will make the registration process of the professional easier, meaning they spend less time filling in information about themselves before they can get to work within Hinq.

ssoTokenProfInfo

Name	Type	Count	Description
firstname	string	0..1	The firstname of the professional that is logging in.
lastname	string	0..1	The last name of the professional that is logging in.
email	string	0..1	The email of the professional that is logging in.
agb	string	0..1	The AGB code of the professional that is logging in.

If the agb field is provided, the professional that is logging in is automatically matched to their existing Hinq account, if they have one.

If the firstname, lastname and email fields are all filled in, an account is automatically created for this professional if they do not already have one. This saves steps for the professional.

ssoTokenPatientInfo

Name	Type	Count	Description
bsn	string	0..1	The BSN of the patient in whose context the professional is logging in.
firstname	string	0..1	The firstname of the patient in whose context the professional is logging in.
lastname	string	0..1	The last name of the patient in whose context the professional is logging in.
email	string	0..1	The email of the patient in whose context the professional is logging in.

If the bsn field of this datatype or treatmentRelationshipId field of the container SSO Token datatype is provided, the professional is automatically logged in to the right patient context.

If the firstname, lastname and email fields are all filled in, an account is automatically created for this professional if they do not already have one. This saves steps for the professional.