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 Set Default

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

One or more KIOLA standard treatment plans might be set as default plans, to be preselected when registering a new patient.

This capability might be used by other systems (e.g. editors for standard treatment plans) to set some KIOLA standard treatment plans as default plans. Those default plans will then be preselected and eventually applied when registering a new patient.

Raw OpenAPI-Swagger Definition file | Download

KIOLA Standard Treatment Plan Set Default

  • 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

The $meta-add and $meta-remove operations might be used with the tag https://fhir.ehealth-systems.at/artifacts/PlanDefinition/tag#default to add or remove a standard treatment plan from the set of default plans. The read and search operations might be used to query all standard treatment plans and lookup default plans in the result. The $meta operation might be used to check if a specific plan currently is a default plan. When creating a new treatment plan, the meta tag might also be included to declare it as a default plan.

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, search-type.

Extended Operations
ConformanceOperationDocumentation
SHALL$$meta-add
SHALL$$meta-remove
SHALL$$meta