Compose a launch
The launch steps on this page are the same for HTI as SHOF
To perform the launch, the following steps must be performed for both HTI and SHOF:
1. Create HTI context claims
The HTI:core v2.0 profile describes the following claims:
resource
string
yes
The identifier of the task to be executed by the person in the sub field.
definition
url
no
sub
reference
yes
patient
reference
no
intent
string
no
An example of the resulting HTI claims:
2. Create the JWT
The HTI:core v2.0 profile also contains claims that are always set on a JWT:
Issuer
iss
The client_id van het portaal
Audience
aud
The device id of the module provider. This can be found via the ActivityDefinition.resource-origin extension.
Unique message id
jti
A unique identifier for this message. This value MUST be treated as a NONCE, a subsequent message with an identical jti MUST be rejected. The jti value must be a random or pseudo number, the jti MUST contain enough entropy to block brute-force attacks.
Issue time
iat
The timestamp of generating the JWT token, the value of this field MUST be validated by the module provider to not be in the future.
Expiration time
exp
The "exp" (expiration time) claim identifies the expiration time on or after which the JWT MUST NOT be accepted for processing. The value MUST be limited to 5 minutes. This value MUST be validated by the module provider, any value that exceeds the timeout MUST be rejected.
These two sets of claims should be combined to form a valid HTI v2.0 JWT. For example:
3. Sign the JWT
4. Launch
The signed token can now be launched to the client. To find the endpoint to be launched to, the ActivityDefinition.endpoint extension can be used. The correct ActivityDefinition can be found using Task.instantiates extension (see Retrieve specific Resource).
Topics
Last updated