KIOLA 2024

Short Description

The purpose of this track is to get familiar with the KIOLA IG for telehealth systems, so you can learn how to integrate it with your own digital health solutions.

Long Description

KIOLA can be tailored to the treatment of specific diseases and customized for patients, using treatment plans. They support a range of different measurements, which can be automatically transmitted or manually entered using different devices. In the current version of the implementation guide it is possible to use FHIR for these customizations. Third party systems can use the API either as a way to orchestrate KIOLA instances as part of larger treatment programs or integrate into KIOLAs treatment plans to provide additional services on a patient-basis. In future versions, it will also be possible to upload and/or query any kind of data (observations, tasks, etc.) to/from the system.

Type

FHIR IG

Submitting Work Group/
Project/
Accelerator/
Affiliate/
Implementer Group  

HL7 Austria / TC FHIR

AIT Austrian Institute of Technology GmbH

Track Lead(s)

Beyer Stefan 

Track Lead Email(s)

stefan.beyer@ait.ac.at

Related Tracks

-


FHIR Version

FHIR R4

Specification(s) this track uses

KIOLA FHIR IG (Download, PW: fhirHackathon2024)

Artifacts of focus

  • PlanDefinition
  • ActivityDefinition
  • CarePlan
  • RequestGroup
  • ServiceRequest
  • DiagnosticReport

Expected participants


Date / Time

Monday March 11, 09:00am-03:30pm CET

Test Servers

https://staging-15.ehealth-systems.at/

Track Details

Prerequisites (recommended)
System roles
  • Coordinator (user1-5): can manage standard treatment plans and assign them to patients. Can also customize individual treatment plans.
  • Patient (patient1-5): can enter measurements.
Get started

To get started please select a user (1-5) and download the corresponding environment for the REST-client. Please communicate which user you are using to the other participants, to avoid conflicts. The password for all users is "fhirHackathon2024".

Scenarios

All of the scenarios consist of a FHIR part and a UI part using KIOLAs web interface, so you can learn how the FHIR API influences the UI and vice-versa.

1 - Upload and manage PlanDefinitions

Here you will learn how to create and manage standard treatment plans. You will learn how to add measurements to the plan and how to use advanced features, such as compliance or allowed modes of data entry.

  1. Upload a plan definition: at first you will upload a predefined plan definition. Afterwards you can log in to the UI and see and understand the content.
  2. Query plan definitions: you can also query which plan definitions are present on the system via the API. You might also delete a plan definition.
  3. Modify a plan definition: now you will learn about measurement definitions and how to add them to a plan definition and configure them for specific use-cases. Using the UI, you can observe the changes.
  4. Mark a plan definition as default: for newly registered patients, some plan definitions can be applied by default.
  5. Mark a plan definition as non-exclusive: plan definitions might also be combined, so you can select multiple definitions per patient.
2 - Apply PlanDefinitions and modify CarePlans

Now you will apply the plan definitions you created in the previous scenario to patients and create individual treatment plans for them. You will learn how the standard treatment plans are related to the individual plans and how conflicts are handled, if multiple plan definitions are applied.

  1. Query the active care plan: a patient might only have one active care plan. You will see how you can query this care plan via the patient user or the administrative user.
  2. Apply a plan definition: plan definitions can be applied using the API for existing patients or using the UI for new and existing patients. You will also see what happens if multiple plan definitions are applied and if conflicts occur.
  3. Upload a modified care plan: care plans can be modified using the API or the UI. You can use the UI to see how the changes affect the FHIR resources.
  4. View history of care plans: if changes are made via the UI, new care plans are usually created. You can query the history of all changes.
3 -  Upload a DiagnosticReport

In this scenario you can upload a diagnostic report to the system and see it appear as a measurement. This is a preview of the upcoming APIs, that will allow any kind of measurements or tasks to be uploaded or queried.