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

Was this helpful?

  1. POC (Walking Skeleton)

Proof Of Concept

Also known as the Walking Skeleton

PreviousDeveloper GuideNextJoining a domain

Last updated 8 months ago

Was this helpful?

Koppeltaal 2.0 has been developed by using an Agile methodology. The devised architecture is tested using POC applications. The applications used within the POC are not the applications that will ultimately be used when Koppeltaal 2.0 goes live.

Applications within the POC now often use Yivi (formerly known as IRMA) to identify the user and relate across systems. This is not part of the standard. It's likely that Koppeltaal 2.0 will not use Yivi in the production environment.

The POC consists of the following type of applications:

Application type
Description

System component

Applications that form the core of Koppeltaal 2.0.

Supplier

A supplier who uses their non-production platform together with the PoC Koppeltaal 2.0 Server.

Pseudo-application

Application that mimics an e-health application. These are removed from the list as they need to be updated with the latest changes in the specification

Additional service

Application that is not part of the Koppeltaal standard, but helps during the development.

The POC consists of the following applications:

Application
Type
Description

Koppeltaal Server

System component

A FHIR HAPI R4 implementation for Koppeltaal.

Domain Management

System component

Applications can register to join a domain. A role is also assigned to applications, which determines what actions the application is allowed to perform on the Koppeltaal Server.

Auth Server

System component

Here - after approval from Domain Management - applications can request an access token via the flow.

Koppeltaal IdP

System component

Identity Provider (IdP) used to validate that the launching user matches the logged in user. This essentially prevents tokens from being intercepted and executed.

Domain Access Test Tooling

Additional service

This test suite helps with the implementation of the .

Koppeltaal Test Tooling

Additional service

A rich test of tools that help developers implement Koppeltaal. Look at page for more information.

Backend Services Authorization
Backend Services Authorization
this