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
  • CapabilityStatement
  • SMART on FHIR Conformance
  • Topics

Was this helpful?

  1. Technical HOW-TO

Request Koppeltaal server metadata

PreviousKoppeltaal Test ToolingNextConnecting to Koppeltaal

Last updated 7 months ago

Was this helpful?

Koppeltaal metadata resides at two places

CapabilityStatement

The Koppeltaal Server provides a . This statement contains useful metadata related to the Koppeltaal Server. For example, it indicates the supported Resource types and supported MIME types.

SMART on FHIR Conformance

Koppeltaal also makes use of the . This specifically contains metadata used whilst executing the . This conformance can be found <BASE_FHIR_URL>/.well-known/smart-configuration. This way, there is no need to configure hard-coded URLs. This configuration can be used to, for example, retrieve the Auth Server URL for the specific Koppeltaal server at runtime.

Topics

CapabilityStatement
SMART on FHIR conformance
SMART on FHIR specifications
TOP-KT-016 - SMART on FHIR Conformiteit