Configure GKV integration
Complete institution-level Krankenkassen Integration settings — Absendernummer, ITSG onboarding, Hochschuldatei confirmation, required role, and insurance start date — so Meldegrund notices can flow through Dakota.
Configure GKV integration is the one-time (and occasionally revisited) institution setup that turns the FuxamCMS health-insurance capability into a live Meldeverfahren. You complete it in Settings → Krankenkassen Integration before student insurance tabs and automated GKV exports become active. Until every required row on the checklist is satisfied and saved, Fuxam keeps the health-insurance integration switched off — even if the Health Insurance feature is already available for your institution.
Think of this page as the bridge between German statutory onboarding (Absendernummer, ITSG, Hochschuldatei) and Fuxam’s operational switches (required role, insurance start date). Staff and students cannot usefully open the Krankenkasse tab until both worlds are aligned.
Why it matters
German Hochschulen participate in the electronic Studenten-Meldeverfahren under § 199a SGB V. To exchange XML notices with Krankenkassen, the institution (or its Dienstleister) needs a gesonderte Absendernummer issued via ITSG and recorded in the Hochschuldatei. Without that identity, Dakota has no trusted sender; without a complete Fuxam configuration, the product will not expose student workflows or schedule outbound Meldegründe.
Completing configuration correctly:
- Unlocks the Krankenkasse tab for users who hold the required role.
- Switches the health-insurance integration on so background jobs and admin views treat the institution as live.
- Anchors outbound notifications to an insurance start date, so historical enrollments are not accidentally re-reported from day one of the platform.
- Creates a clear handoff into day-to-day work: study-timeline hygiene, role assignment, and monitoring of GKV notifications.
Before you start
Confirm the following before opening Settings:
| Prerequisite | Why |
|---|---|
| Health Insurance feature enabled | Without this FuxamCMS capability, the integration UI is not available for your institution. |
| Administrator with permission to change settings | Only users with this capability can change Krankenkassen Integration values. |
| ITSG / Absendernummer readiness | Know whether your institution already has an Absendernummer, or whether you must request one and wait for Hochschuldatei confirmation. |
| Decision on required role | Choose which institution role must complete student-side Krankenkasse steps — typically a student-facing role used for matriculated learners. See Roles and permissions. |
| Agreement on insurance start date | Coordinate with student services so the go-live date matches when you intend Fuxam to begin sending notices. |
How it fits
Related handbook pages after go-live: Manage insurance data, Export exmatriculations, Reporting reasons and lifecycle, User Management.
Key terms
| Term | In this configuration |
|---|---|
| Absendernummer | Sender ID for the Meldeverfahren (typically eight alphanumeric characters). Indicate whether you already have one; if yes, enter the validated number; if not, use the guided request flow (ITSG email template and Absendernummer request instructions). |
| ITSG email | Confirmation that you sent the onboarding email to ITSG when prompted by the checklist. |
| Hochschuldatei confirmation | Mark that ITSG has confirmed your institution in the Hochschuldatei — the register of Hochschulen participating in electronic exchange. |
| Required role | Institution role whose holders see the Krankenkasse tab and must complete student-side steps. |
| Insurance start date | Date from which Fuxam should begin sending insurance notifications for your institution. |
| Dakota | Middleware used after go-live for XML exchange; background jobs that process GKV notifications and import master data rely on a completed configuration. |
Domain deep dive: Absendernummer, ITSG, and Hochschuldatei
Under § 199a SGB V, Hochschulen must apply for a gesonderte Absendernummer to take part in the electronic procedure. The GKV-Spitzenverband has commissioned ITSG to:
- Receive Absendernummer applications (typically via the published application form and ITSG Hochschuldatei contact).
- Issue the Absendernummer to the Hochschule or its Dienstleister.
- Store the Absendernummer and application data in the Hochschuldatei, which Krankenkassen use daily for addressing.
If a computing center or Dienstleister sends and receives notices on behalf of the Hochschule, that provider usually needs an additional Absendernummer. Mixing another institution’s ID, or saving a provisional number before ITSG confirmation, is a common go-live failure mode.
Fuxam’s checklist mirrors this external dependency: you cannot honestly mark Hochschuldatei confirmation until ITSG has actually registered your institution. The Absendernummer is your procedural passport; Dakota credentials and connectivity are the secure channel that carries Meldegrund XML once you are live.
How to open integration settings
Go to Settings → Integrations → Krankenkassen Integration (labeled Health Insurance or Krankenkassen Integration depending on locale).
Review the page introduction describing the GKV-Schnittstelle workflow.
Administrators need permission to change settings to edit these values.
How to complete the configuration checklist
Work through the rows in order. Later steps unlock only after earlier ones are satisfied — this mirrors the real-world dependency between Absendernummer issuance, ITSG processing, and Hochschuldatei registration.
Absendernummer — Indicate whether your institution already has an Absendernummer. If yes, enter the validated number. If not, use the guided request flow (copy the ITSG email template and follow the Absendernummer request instructions).
ITSG email — Confirm you sent the onboarding email to ITSG when prompted.
Hochschuldatei confirmation — After ITSG confirms your institution in the Hochschuldatei, mark that confirmation as received.
Required role — Choose which institution role must complete student-side Krankenkasse steps. Only users with this role see the Krankenkasse tab.
Insurance start date — Set the date from which Fuxam should begin sending insurance notifications for your institution.
Select Save to persist settings. When all required fields are complete, Fuxam switches the health-insurance integration on and shows the Next steps panel.
After configuration
The Next steps section summarizes operational tasks: ensuring study-timeline data is accurate, assigning the required role to affected students, and monitoring incoming GKV notifications. Background jobs that process GKV notifications and import master data handle ongoing exchange with Dakota once you are live.
Recommended operational follow-through
| Task | Where | Why |
|---|---|---|
| Assign the required role | User Management — edit users or use bulk actions | Without the role, students never see Dashboard → Management → Krankenkasse. |
| Verify immatriculation and exmatriculation dates | Study plan / study timeline on the user (see Manage insurance data) | Meldegrund selection is driven by timeline status, not by the Settings page. |
| Align cohort membership | Study programs and cohorts | Cohort enrollment generates and updates study plans that feed the timeline. |
| Spot-check Sent notices after first exports | Per-user Krankenkasse tab | Confirms Dakota connectivity and that the insurance start date behaves as intended. |
| Share Meldegrund vocabulary | Reporting reasons and lifecycle | Helps staff interpret inbound 10–13 notices and outbound 20 / 30 history consistently. |
Best practices
- Coordinate Absendernummer ownership. If a Dienstleister or computing center sends on behalf of several Hochschulen, confirm which Absendernummer belongs in Fuxam before you save — mixing IDs breaks routing for every Meldegrund.
- Choose the required role deliberately. Prefer a stable student role used for matriculated learners, not a temporary admissions or applicant role, so the Krankenkasse tab appears when study actually begins.
- Set the insurance start date with student services. Too early can attempt notices for cohorts already reported in a legacy system; too late can miss first-semester Meldegrund 20 traffic.
- Document who completed ITSG steps. Absendernummer email threads often live outside Fuxam; keep a short internal note of ticket IDs or confirmation dates for audits.
- Do not confuse this with Statistics Center setup. Enabling GKV does not configure University Statistics or the Statistics Engine — those remain separate institutional reporting channels.
- Plan for master-data freshness. Once live, Fuxam relies on background import of insurer master data alongside notification processing — keep Absendernummer and contact data current with ITSG if your institution merges, renames, or changes Dienstleister.
Common pitfalls
| Symptom | Likely cause | What to do |
|---|---|---|
| Krankenkasse tab says “not configured” | Checklist incomplete or not saved; integration still switched off | Re-open Settings → Krankenkassen Integration, finish unlocked rows, Save. |
| Feature enabled but Integrations entry not useful | Health Insurance feature missing or incomplete institution setup | Confirm feature enablement with your Fuxam contact, then complete the checklist. |
| Students cannot see Krankenkasse | User lacks the required role | Assign the role in User Management. |
| Staff cannot open insurance data | Missing permission to view insurance data | Adjust permissions via Roles and permissions. |
| Jobs run but nothing useful exports | Insurance start date in the future, or study timelines incomplete | Review start date and timeline data before expecting Meldegrund 30 volume. |
| Absendernummer saved but exchange fails | Hochschuldatei not yet confirmed, or wrong Dienstleister ID | Verify ITSG confirmation and which Absendernummer your Dakota path actually uses. |
FAQ
Is enabling the Health Insurance feature enough to go live?
No. The feature makes the integration available, but Fuxam only switches the health-insurance integration on after you save a complete Krankenkassen Integration configuration.
Who can change Krankenkassen Integration settings?
Administrators with permission to change settings. Viewing per-student insurance data separately requires permission to view insurance data.
Can I toggle the Krankenkasse tab from a role profile?
No. The tab is not toggled from role profile settings. It appears automatically for users with the configured insurance role once the health-insurance integration is fully set up and switched on.
What happens after Save shows Next steps?
Operational work begins: keep study timelines accurate, assign the required role, and monitor incoming GKV notifications. Background jobs that process GKV notifications and import master data handle ongoing Dakota exchange.
How long does ITSG Absendernummer issuance take?
It varies. Treat Absendernummer request and Hochschuldatei confirmation as external lead time in your go-live plan — Fuxam cannot shorten ITSG processing. Keep the checklist accurate rather than marking confirmation early.
Related pages
Health insurance overview
Domain context for GKV Meldeverfahren and how this section fits OrgHub.
Manage insurance data
Per-student Krankenkasse tab, progress steps, and sent notices.
Export exmatriculations
Automated Meldegrund 30 processing after go-live.
Reporting reasons and lifecycle
Meldegründe and how timelines drive automatic notices.