Koppeltaal-2.0-Dev-Guide
  • Developer Guide
  • POC (Walking Skeleton)
    • Proof Of Concept
      • Koppeltaal Server
      • Domain Management
      • Auth Server
      • Koppeltaal IdP
      • Domain Access Test Suite
      • Koppeltaal Test Tooling
  • Domain access
    • Joining a domain
    • Role-based access control
      • Autorisation model
      • Creating a role
      • Search Narrowing
      • Revoke Permission
  • Technical HOW-TO
    • Koppeltaal Test Tooling
    • Request Koppeltaal server metadata
    • Connecting to Koppeltaal
      • Requirements
        • Create a key pair
        • Signing the JWT
        • JWKS setup
      • Access to Koppeltaal
    • Managing resources
      • Versioning
      • CRUD Operations
        • Retrieve all Resources
        • Retrieve specific Resource
        • Create a Resource
        • Update a Resource
        • Delete a Resource
      • Subscribing to changes
    • Launching
      • HTI Flow
      • SHOF Flow
      • Compose a launch
      • Initiating a launch
      • Receiving a HTI launch
        • Token introspection
      • Receiving a SHOF launch
    • Detailed technical guidance
  • Hackathon Use Cases
    • Requirements
      • Install and configure Yivi
    • Use-Cases
      • Use-Case 1: Create a Task
        • Create an ActivityDefinition
      • Use-Case 2: HTI Launch
      • Use-case 3: SHOF Launch
      • Use-case 4: Subscribing to changes
  • Useful Links
    • Simplifier Profiles
    • FHIR Docs
    • HTI documentation
    • GitHub
    • Koppeltaal 2.0 Specifications & Architecture
    • Koppeltaal 2.0 Implementation Guide
    • Koppeltaal 2.0 OpenAPI Specs
Powered by GitBook
On this page
  • Requirements
  • Information Flow
  • Topics
  1. Technical HOW-TO
  2. Launching

HTI Flow

Health Tools Interoperability

PreviousLaunchingNextSHOF Flow

Last updated 1 year ago

is a light-weight solution from to quickly implement client-to-client launches. In short, the HTI launch is simply a with HTI-specific claims that is sent from one client to another. A public key can be used to verify that the JWT comes from a trusted source.

Requirements

  1. A .

  2. The module provider uses OR must be able to relate the issuer to its JWKS endpoint.

Information Flow

The HTI launch can be done without an authentication server. Therefore, it is important that the module provider is in possession of the issuer and the related JWKS endpoint. This way it can be proven that the portal actually signed the JWT. A public key may also be exchanged, although there is a strong preference to use JWKS since applications must implement it to make a .

Topics

TOP-KT-007 - Koppeltaal Launch
TOP-KT-021 - Token Introspection
HTI
GIDS
signed JWT
JWKS endpoint must be available
Token Introspection
Connection with Koppeltaal
HTI Flow
HTI Flow