0.4.0 - ci-build
ONCOnnectTumorboardIG - Local Development build (v0.4.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
These define constraints on FHIR resources for systems conforming to this implementation guide.
| Comorbidities (Profile) |
Captures the comorbidities of a patient. |
||||||||||||||||||
| DocumentReference (Profile) |
Captures the metadata for a document or file. Files aren't included in the registration bundle. Instead they are uploaded afterwards. Check out the guide to learn more. |
||||||||||||||||||
| ECOG Performance Status (Profile) |
Captures the ECOG performance status of a patient, which is a measure of their functional status and ability to perform daily activities. |
||||||||||||||||||
| Family History (Profile) |
Captures the family history of a patient, including conditions and relationships to all family members. |
||||||||||||||||||
| Family History Member (Profile) |
Captures information about a family member's health history, including conditions and their relationship to the patient. |
||||||||||||||||||
| Karnofsky Performance Status (Profile) |
Captures the Karnofsky performance status of a patient, which is a measure of their functional status and ability to perform daily activities. |
||||||||||||||||||
| Oncological History (Profile) |
Captures the patient's oncological history, including conditions and events that are relevant to their health status. The resources that should be used to represent the different events are listed below.
Previous tumor conditions shouldn't be tracked here. Instead they have their own Previous Tumors list. In case it is not possible or requires significant effort to track the patient history in
a structured way, you should still use one base resource per event, but only use the |
||||||||||||||||||
| Oncological History Guideline (Profile) |
The guideline (Leitlinie) followed in the treatment of the patient. The profile currently only exists to differentiate between guideline and other observation types in the oncological history. |
||||||||||||||||||
| Patient (Profile) |
Captures the basic information about a patient. |
||||||||||||||||||
| Previous Tumors (Profile) |
A list of all previous tumors of a patient |
||||||||||||||||||
| Primary Diagnosis (Profile) |
Captures the primary diagnosis of a patient, including clinical status, verification status, associated codes and staging. If the primary diagnosis is a recidive, the original primary diagnosis should be captured in the previous tumors list. |
||||||||||||||||||
| Registration (Profile) |
The ServiceRequest is the central resource for capturing the registration of a patient in a tumor board. It maintains status information and links to all other relevant resources. |
||||||||||||||||||
| Registration CHARITE MTB (Profile) |
The specific ServiceRequest for the CHARITE MTB registration. |
||||||||||||||||||
| Registration WTZ MTB (Profile) |
The specific ServiceRequest for the WTZ Essen MTB registration. |
||||||||||||||||||
| Registration WTZ Sarkom (Profile) |
The specific ServiceRequest for the WTZ Essen Sarkom registration. |
||||||||||||||||||
| Requester (Profile) |
Captures the information about a requester and links to their role and organization. |
||||||||||||||||||
| Requester Department (Profile) |
Captures the information about a requester's department. |
||||||||||||||||||
| Requester Hospital (Profile) |
Captures the information about a requester's hospital. |
||||||||||||||||||
| Requester Role (Profile) |
Captures the role of a requester, including their contact information and associated organization. |
||||||||||||||||||
| Smoking Status (Profile) |
Profile based on the ISIK Raucherstatus, which is unfortunately non-functional. The profile captures the smoking status of the patient as a general category. |
||||||||||||||||||
| Smoking Status Pack Years (Profile) |
The profile captures the smoking status of the patient in pack years. |
||||||||||||||||||
| TNM Staging (Profile) |
Captures the staging (TNM) of a tumor using MII profiles. |
||||||||||||||||||
| Therapy Concept (Profile) |
Captures the therapy concept associated with the primary diagnosis. |
These define sets of codes used by systems conforming to this implementation guide.
| Document Type (ValueSet) |
ValueSet for the type of document attached to a tumorboard registration. |
| ONCOnnect OncoTree (ValueSet) |
ValueSet placeholder for tumor types based on the OncoTree classification. Includes all codes from the ONCOnnect_CS_TB_OncoTree code system. |
| Profile Version (ValueSet) |
ValueSet for the version of the profiles used in the tumorboard IG. |
| Request Outcome Error Details (ValueSet) |
Value set for capturing details about the outcome of a request, such as reasons for a request being rejected or not performed. |
| Requester Department Identifier (ValueSet) |
ValueSet for the departments of requesters. |
| ServiceRequest Category (ValueSet) |
ValueSet for the category of the ServiceRequest in the context of tumor boards. |
These define new code systems used by systems conforming to this implementation guide.
| ONCOnnect OncoTree (CodeSystem) |
CodeSystem placeholder for tumor types based on the OncoTree classification. The actual codes are fetched at runtime from the OncoTree API. There is also a human friendly search. Citation:
|
| Profile Version (CodeSystem) |
CodeSystem for the version of the profiles used in the tumorboard IG. |
| Request Outcome Error Details (CodeSystem) |
Code system for capturing details about the outcome of a request, such as reasons for a request being rejected or not performed. |
| Requester Department Identifier (CodeSystem) |
CodeSystem for the departments of requesters. Only contains placeholder values for now |
| ServiceRequest Category (CodeSystem) |
CodeSystem for the category of the ServiceRequest in the context of tumor boards. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.