Manage insurance data

Use the Krankenkasse user tab to track insurance progress, inbound GKV notifications, sent Meldegrund 20 and 30 notices, and study-timeline dates that drive statutory reporting.

Once the health-insurance integration is fully set up and switched on, manage insurance data means working on a student’s Krankenkasse tab: tracking insurance progress, inbound notifications, and sent Meldungen (M20 / M30 notices). This is the operational heart of GKV work in Fuxam — where student services verify that statutory steps completed, that Krankenkasse responses arrived, and that outbound Meldegründe match the academic reality on the study timeline.

Admins work from OrgHub → User Management; eligible students (or staff acting on their own profile) complete a shorter checklist on Dashboard → Management → Krankenkasse. Both views depend on the same prerequisites: a complete integration configuration, the configured required role, and accurate study-plan dates.

Why it matters

Statutory Meldeverfahren fails quietly when data is incomplete: a missing KV number blocks student onboarding; a wrong exmatriculation date can trigger Meldegrund 30 too early or too late; an unnoticed inbound arrears notice can leave enrollment decisions unresolved. The Krankenkasse tab concentrates those signals on the same identity record used elsewhere in OrgHub, so insurance status stays aligned with User Management and with cohort-driven study plans from study programs and cohorts.

Use this tab when you need to:

• Confirm a student finished provider-notification steps before relying on automated exchange.
• Inspect Insurance notices for Krankenkasse responses processed via the GKV interface.
• Audit Sent notices for Meldegrund 20 (immatriculation) and Meldegrund 30 (exmatriculation), including correction workflows when something was sent incorrectly.
• Trace problems back to Study timeline dates instead of guessing from separate spreadsheets.

How it fits

Key concepts

How study status drives what you see

In the statutory procedure, Hochschule Meldegründe follow academic facts — not a separate insurance calendar. In Fuxam, those facts live on the study timeline:

How to open the Krankenkasse tab (admin)

You need permission to view insurance data to view the tab.

How to review admin sections on the tab

Work top to bottom when investigating a student case: progress and status first, then inbound traffic, then what you already sent, then whether the academic dates justify those Meldegründe.

Admin sections at a glance

Reading inbound Insurance notices

Inbound notices are how Krankenkassen talk back to your institution. Common patterns (domain context):

Full code reference: Reporting reasons and lifecycle.

Student self-service steps

Students (or staff acting on their own profile) with the required role see a simplified checklist on Dashboard → Management → Krankenkasse:

1. Enter and validate their KV number (Krankenversichertennummer).
2. Copy the provider request message email template.
3. Confirm the notification email was sent to their Krankenkasse.
4. Confirm the insurer’s response was received.

These steps mirror the admin progress indicators but are limited to the logged-in user’s own data. In the statutory process, students typically ask their Krankenkasse to report insurance status to the Hochschule before or during enrollment; the Fuxam checklist captures that provider-notification loop so staff can see completion without collecting paper certificates.

Worked example: first-semester onboarding

1. Admissions assigns the required insurance role when the applicant becomes a matriculated student.
2. The student opens Dashboard → Management → Krankenkasse, enters the KV number, and emails the provider using the template.
3. The Krankenkasse sends Meldegrund 10 to the Hochschule; it appears under Insurance notices.
4. Staff confirm Study timeline immatriculation dates match reality.
5. Outbound Meldegrund 20 (when transmitted for this student) appears under Sent notices for audit.

If step 3 never arrives, do not assume Fuxam is broken — the student may not have asked the fund, or Absendernummer / Hochschuldatei addressing may still be wrong. Check configuration and the student’s provider confirmation first.

Best practices

• Fix the study timeline before re-sending. If Meldegrund 30 looks wrong, correct Study Plan dates first, then use review / correction workflows on Sent notices — do not treat Sent notices as the master academic record.
• Read inbound notices in context. Contribution arrears or fund-change notifications can explain why enrollment or re-enrollment is blocked even when the student believes they are insured.
• Use Send notification sparingly. Prefer automated jobs for routine Meldegrund 30 traffic (Export exmatriculations); reserve manual Send notification for documented exceptions when the dialog is available.
• Keep role assignment in sync with cohorts. When you add users to a cohort, confirm they also receive the required insurance role if your process expects every matriculated student to complete Krankenkasse steps.
• Do not use Statistics Center as a substitute. Cohort rosters and statistics exports help you find who is enrolled; they do not replace per-user Meldegrund history on the Krankenkasse tab.
• Separate leave from exmatriculation in conversation with insurers. Leave statuses on the timeline are academic; Meldegrund 30 is end of study. Mislabeling leave as exmatriculation creates wrong outbound notices.

Common pitfalls

FAQ

Related pages