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.

Reports and coding (12)
Summarise findings and doctors' letters for documentation Quality here depends particularly on the AI model; we test this use case with you before you buy.Ready to go
Prepare ICD-O-3 coding from the pathology report Quality here depends particularly on the AI model; we test this use case with you before you buy.Ready after a short setup
Prepare ICD-10 coding of the reported diagnosis from the doctor's letter Quality here depends particularly on the AI model; we test this use case with you before you buy.Ready after a short setup
Transfer documented TNM details from the findings report and surgical report Quality here depends particularly on the AI model; we test this use case with you before you buy.Ready after a short setup
Capture molecular pathology findings in a structured way Quality here depends particularly on the AI model; we test this use case with you before you buy.Ready after a short setup
Transfer documented therapy details from doctors' letters Quality here depends particularly on the AI model; we test this use case with you before you buy.Ready after a short setup
Check free text and coding for contradictions Quality here depends particularly on the AI model; we test this use case with you before you buy.Ready after a short setup
Compare several reports of a tumour Quality here depends particularly on the AI model; we test this use case with you before you buy.Ready to go
Query to reporting physicians about missing detailsReady to go
Capture death certificates with text recognitionReady after a short setup
Show coding help in the registry softwareCustom project
Pre-process incoming reports as a batchCustom project
Documentation and onboarding (3)
Answer questions on coding rules and the manualReady after a short setup
Search documentation work instructionsAfter connecting your systems
Practice cases for new documentation specialistsReady to go
Reporter service and reporting fees (8)
Draft replies to enquiries from reporting physiciansReady to go
Answer questions on reporting obligations and reportable eventsReady after a short setup
Explain interface error messagesReady after a short setup
Draft e-mail replies from the mailbox and contextAfter connecting your systems
Pre-sort enquiries from reporting physicians in the ticket systemAfter connecting your systems
Answer queries on reporting feesReady after a short setup
Information e-mail and circulars to reporting physiciansReady to go
Create training materials for reporting physiciansReady to go
Feedback and quality conferences (4)
Comment on a feedback report from key figuresReady to go
Answer questions on guideline quality indicatorsReady after a short setup
Prepare the quality conferenceReady after a short setup
Create minutes of the quality conferenceReady to go
Analysis and reports (5)
Draft annual report texts from tablesReady to go
Write clear fact sheets on types of cancerReady to go
Write and explain analysis scripts Quality here depends particularly on the AI model; we test this use case with you before you buy.Ready to go
Answer enquiries about cancer clusters Quality here depends particularly on the AI model; we test this use case with you before you buy.Ready after a short setup
Draft a press release from bullet pointsReady to go
Research and data use (5)
Check data requests for completeness Quality here depends particularly on the AI model; we test this use case with you before you buy.Ready after a short setup
Draft a data use agreement from a templateReady after a short setup
Answer questions on the dataset for researchersReady after a short setup
Literature research with web searchReady to go
Draft a publication from your own results Quality here depends particularly on the AI model; we test this use case with you before you buy.Ready to go
Data protection and data subject rights (4)
Draft replies to requests for informationReady after a short setup
Draft confirmations of objectionsReady after a short setup
Patient information in Easy LanguageReady to go
Draft a data protection impact assessment Quality here depends particularly on the AI model; we test this use case with you before you buy.Ready to go
Administration and committees (8)
Answer questions on the state cancer registry lawReady after a short setup
Prepare a statement on draft legislation Quality here depends particularly on the AI model; we test this use case with you before you buy.Ready after a short setup
Meeting paper for the advisory board and shareholdersReady after a short setup
Prepare evidence of funding criteria Quality here depends particularly on the AI model; we test this use case with you before you buy.Ready after a short setup
Draft service specifications for tendersReady after a short setup
Draft a job advertisement for documentation specialistsReady to go
Search documents across departmentsAfter connecting your systems
Create meeting minutes from a voice memoReady to go

How well a use case works also depends on the AI model. We test your most important use cases with you before you buy. What this means →

“After connecting your systems” means: the use case works as soon as basebox is connected to the system.

Notifications on your server or in our cloud.

Where and how notifications are processed is governed by your state cancer registry act.

  • Server without 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 with a data processing agreementYour own environment, AI model at basebox in Germany, with a data processing agreement and an agreement under § 203 StGB. Whether your state law allows this for notifications, we clarify with you and your data protection authority.

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 or in our cloud. On the server, notifications do not leave your organisation, and basebox has no access without your instruction. In the cloud, basebox processes them on your behalf, in your own environment in a data centre in Germany, with a data processing agreement and an agreement under § 203 StGB. Whether your state law prescribes a location, a particular separation or requirements for processing on your behalf is something you check with your data protection officer.

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 the reliability of coding by basebox 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 basebox connector for registry software. You upload or paste findings and notifications. Connecting via the basebox interface is a separate project with the vendor or your IT.

Last updated:

Cookie settings

This website sets no cookies for analytics or advertising and embeds no tools from other providers. Your browser only stores what is needed to use the site. Privacy policy