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. Hackathon Use Cases
  2. Use-Cases
  3. Use-Case 1: Create a Task

Create an ActivityDefinition

PreviousUse-Case 1: Create a TaskNextUse-Case 2: HTI Launch

Last updated 8 months ago

Was this helpful?

Applications that can be launched MUST be the publisher of the ActivityDefinition.

Koppeltaal adds three to the ActivityDefinition resource:

Extension
Description

endpoint

Every ActivityDefinition must refer to an Endpoint Resource. The value of this Endpoint must be filled with the URL that the user is sent to while launching a Task that uses this ActivityDefinition

publisherId

A unique identifier for the client publishing the ActivityDefinition. This can be used to, for example, retrieve all Tasks that refer to any ActivityDefinition from publisher X. This can be very useful for subscribing to changes in Tasks that are relevant to your application. This value requires an id type value, allowing more freedom of "groups" than the resource-origin field.

resource-origin

Example ActivityDefinition

{
    "resourceType": "ActivityDefinition",
    "meta": {
        "profile": [
            "http://koppeltaal.nl/fhir/StructureDefinition/KT2ActivityDefinition"
        ]
    },
    "extension": [
        {
            "url": "http://koppeltaal.nl/fhir/StructureDefinition/KT2PublisherIdentifier",
            "valueId": "ID345900-002"
        },
        {
            "url": "http://koppeltaal.nl/fhir/StructureDefinition/KT2EndpointExtension",
            "valueReference": {
                "reference": "Endpoint/04230feb-8cf6-458b-bb46-409430f64701",
                "type": "Endpoint"
            }
        }
    ],
    "url": "http://Testtooling.com/ActivityDefinition/",
    "identifier": [
        {
            "use": "official",
            "system": "http:/vzvz.nl/Testtooling",
            "value": "Controlelijst voortgang"
        }
    ],
    "version": "1.1.0",
    "name": "Controlelijst",
    "title": "Controlelijst voortgang",
    "status": "active",
    "description": "Vul de controlelijst zo goed mogelijk in. Dit kost ongeveer 10 minuten."
}

A reference to the Device that created the Resource. This is set by the Koppeltaal server as it's used by the . This value cannot be set by the client while creating new Resources.

authorisation mechanism
extensions