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

Home

Official URL: https://fhir.ccc-onconnect.de/ImplementationGuide/tumorboard				Version: 0.1.0
Draft as of 2025-09-04				Computable Name: ONCOnnectTumorboardIG

ONCOnnect Tumorboard IG

Welcome to the ONCOnnect Tumorboard Implementation Guide (IG). This IG is designed to provide a structured approach to managing tumorboard registrations and related data using the FHIR standard.

The IG is still in development. Expect changes and updates as we refine the content and add new profiles.

Overview

The most important resource that forms the center of every registration is the Registration profile which is based on the ServiceRequest resource. It tracks the status of the registration and is linked to all other connected resources through the supportingInfo field.

To get an overview of all existing resources, check the Table of Contents, where all profiles and examples are listed.

In general, profiles are based on MII profiles where possible and further constrained to fit our use case.

Submitting a Registration

Before you can submit any registration, you need to get an API key from the ONCOnnect team. Please get in contact with us for this. You should also register for a user account on the ONCOnnect communication platform, which then allows you to view the status of your registrations in the Tumorboard App.

To register a new patient for a tumorboard, you first need to create a FHIR Bundle containing the necessary resources. Start with the Registration (ServiceRequest) and include all relevant and available resources.

When your Bundle is ready, you can submit it to the staging ONCOnnect Tumorboard API endpoint, which you can reach at https://tumorboards.staging.test.ccc-onconnect.de/api/fhir/register/<location>/<tumorboard>, where <location> is the hospital, e.g. wtz-essen, and <tumorboard> is the name of the tumorboard you want to register for, e.g. mtb. Include your API key in the request header as Authorization: Bearer <your_api_key>.