MII IG Kerndatensatz-Modul Molekulares Tumorboard
2027.0.0-ballot.1 -
Germany
This page is part of the MII Implementation Guide Molecular Tumor Board (v2027.0.0-ballot.1: Release) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
| Official URL: https://www.medizininformatik-initiative.de/fhir/ext/modul-mtb/ImplementationGuide/mii-ig-mtb | Version: 2027.0.0-ballot.1 | |||
| Active as of 2026-09-15 | Computable Name: MII_IG_MTB_DE | |||
This specification describes the FHIR representation of the Core Dataset (CDS) module Molecular Tumor Board of the Medical Informatics Initiative (MII). It covers the module's use cases and the associated FHIR profiles, extensions and terminology resources in their normative form. The MII Core Dataset enables the standardized secondary use of routine clinical data for medical research.
The Molecular Tumor Board (MTB) module is based on the DNPM dataset (Deutsches Netzwerk für Personalisierte Medizin) and complements the MII CDS module Oncology. Additional data elements — and deliberate omissions — resulted from discussing the dataset with experts from medicine and bioinformatics, and findings from other research networks (e.g. nNGM) were integrated.
The module's main elements are the patient's treatment episode involving the Molecular Tumor Board and the follow-up.
The treatment episode contains MTB-relevant information on diagnoses, previous therapies and specimens as well as the bioinformatic data of the NGS report and the molecular pathology report, which are decisive for the MTB decision (therapy recommendations etc.). The patient's consent to the MTB, the ECOG performance status and the family medical history are also part of the treatment episode. The follow-up covers the documentation of the therapies actually implemented afterwards and their cost coverage (Kostenübernahme).
A detailed rationale for the modelling and the intention of each profile can be found on the individual artifact pages. The Molecular Tumor Board module is explicitly
| Publication | |
|---|---|
| Date | 2026-03-30 |
| Version | 2026.0.1 (CalVer YYYY.n.n) |
| Status | active |
| Realm | DE |
Data Integration Centers (DIC), software developers and system architects building FHIR-based solutions.
→ see Profiles and Logical Models.
Scientists using KDS data for medical research.
→ see Guidance for Researchers.
This module is part of the MII Core Dataset; the other KDS modules and their dependencies are described at medizininformatik-initiative.de.
This module builds on the MII CDS modules Oncology, Molecular Genetic Report (MolGen), Pathology Report, Study, Medication, Biobank, Consent and the MII base modules (Person, Diagnosis, Procedure), as well as the HL7 Genomics Reporting IG; the exact version pins are listed in the ImplementationGuide resource.
More FHIR implementation guides can be found in the official
FHIR IG Registry (source:
FHIR/ig-registry).
This guide was created within the Medical Informatics Initiative and is subject, by its governance process, to the coordination procedure of the Interoperability Forum and the technical committees of HL7 Germany.
Questions about this publication can be asked on the HL7 FHIR Zulip
chat.fhir.org in the german/mi-initiative stream, or
on the MII Zulip mii.zulipchat.com in the
MII-Kerndatensatz stream.
Comments and issues are welcome as Issues on
GitHub.
Domain contacts:
© 2024+ TMF e. V., Charlottenstraße 42, 10117 Berlin
The content of this specification is public (CC0 1.0 Universal); reuse and republication are not restricted.
For the usage rights of the underlying FHIR technology, see the FHIR base specification.
Some of the code systems used are published and maintained by other organizations; the copyright of the respective publishers applies.
The content of this document is public. Please note that parts of this document are based on FHIR version R4, which is copyrighted by HL7 International.
Although this publication was prepared with the greatest care, the authors cannot accept any liability for direct or indirect damage that may arise from the content of this specification.