KIOLA Implementation Guide
0.1.0 - STU1

KIOLA Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

CapabilityStatement: KIOLA Standard Treatment Plan Management

Official URL: https://fhir.ehealth-systems.at/artifacts/CapabilityStatement/kiola-standard-treatment-plan-management Version: 0.1.0
Draft as of 2023-01-11 Computable Name: KIOLAStandardTreatmentPlanManagement

KIOLA standard treatment plans might be managed by another system. Existing plans might be queried, new KIOLA standard treatment plans or updated versions of existing plans might be uploaded to the server. Also the status of existing plans might be changed.

This capability might be used by other systems (e.g. editors for standard treatment plans) to upload new or updated KIOLA standard treatment plans.

Raw OpenAPI-Swagger Definition file | Download

KIOLA Standard Treatment Plan Management

  • Implementation Guide Version: 0.1.0
  • FHIR Version: 4.0.1
  • Supported Formats: application/fhir+json
  • Supported Patch Formats:
  • Published on: 2023-01-11
  • Published by: null

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as "SHALL NOT". A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

FHIR RESTful Capabilities

Mode: server

A KIOLA standard treatment plan can be uploaded to the server, by simply using the create operation. Similarily, plans might be updated by using the read operation and a successive update operation with the modified plan. In the case of an update, existing instances of standard treatment plans (treatment plans in KIOLA care plans) are not upgraded. This might be done manually, e.g. by reapplying the treatment plan to the respective patients.

Summary of System-wide Interactions

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

  • The relevant profiles (if any)
  • The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
  • The required, recommended, and some optional search parameters (if any).
  • The linked resources enabled for _include
  • The other resources enabled for _revinclude
  • The operations on the resource (if any)

Resource Conformance: supportedPlanDefinition

Interaction summary
  • Supports read, create, update.