For the cancer registries of the German federal states
Findings summarised, coding prepared.
On your registry’s server, checked by your documentation team.
- No access by basebox
- Operation without internet
- Every answer with its source
- Permissions from your directory
- ISO 27001 certified
Help from the notification to the annual report.
Examples from four areas.
- Notifications and coding
- Summarise findings for documentation
- Prepare ICD-O-3 coding
- Compare notifications on one tumour
- Reporter service
- Answers to reporters’ enquiries
- Explain interface error messages
- Questions on reporting fees
- Analysis and reports
- Texts for the annual report
- Write analysis scripts
- Fact sheets on cancer types
- Administration and committees
- Information on the state cancer registry act
- Papers for the advisory board
- Evidence for the funding criteria
49 use cases for cancer registries.
Each one checked, with the point from which it works.
No use case matches this selection.
Reports and coding (12)
Documentation and onboarding (3)
Reporter service and reporting fees (8)
Feedback and quality conferences (4)
Analysis and reports (5)
Research and data use (5)
Data protection and data subject rights (4)
Administration and committees (8)
“After connecting your systems” means: the use case works as soon as basebox is connected to the system.
Notifications stay in the registry.
Where and how notifications are processed is governed by your state cancer registry act.
- No processing on your behalfYou operate the server. basebox only has access for remote maintenance, and only on your instruction.
- Trust centre kept separateThrough separate groups or a separate server. We clarify with you which separation your state law requires.
- Cloud only without personal dataFor example for published figures, circulars and coding rules. Notifications belong on the server.
What basebox does not do.
Responsibility for the registry and its data remains with you.
- Not a medical devicebasebox does not interpret findings, makes no diagnosis and suggests no therapy.
- Nothing adopted without reviewWhat basebox prepares, your documentation team enters into the registry database.
- No record linkageMatching and merging identities stays in your procedure with control numbers.
- No assessment of reportersFeedback per institution, yes; assessment of individual physicians, no.
A server with you in three weeks.
Fully set up, with installation in the data centre and an introduction.
Frequently asked questions
On your registry’s server. There, notifications do not leave your organisation, and basebox has no access without your instruction. Whether your state law prescribes a location or a particular separation is something you check with your data protection officer. Notifications do not belong in the cloud.
No. basebox does not interpret findings, makes no diagnosis and suggests no therapy. In the registry, basebox helps with documentation and administration: it summarises, prepares coding and drafts texts. Your documentation team checks every result.
You measure that before you start, using your own findings that have already been coded. The suggestions are based on the coding rules you store once in the app. Only what your documentation team confirms is adopted.
Not directly. Section 393 of Book V of the German Social Code (SGB V) is addressed to healthcare providers and to health and long-term care insurers. Cancer registries are governed by Section 65c SGB V and your state cancer registry act.
There is no ready-made connector. You upload or paste findings and notifications. Connecting via the basebox interface is a separate project with the vendor or your IT.