PayerConfigurationReviewReason

Type com.regiocom.healthcare.model.types.PayerConfigurationReviewReason Why a migrated payer configuration needs a PDL's review (#3322 step 3). Legacy data holds contradictions the old flat record could express and the new model cannot, and values the new model has no source for at all. Nothing is discarded over one of these: the slice is migrated with a documented default and carries the reason, so the affected clients stay findable long after the migration run's log lines are gone.

enum PayerConfigurationReviewReason {
  AKTENZEICHEN_MISSING
  BEIHILFESTELLE_INCOMPLETE
  BEIHILFE_PERCENTAGE_CLAMPED
  BEIHILFE_PERCENTAGE_MISSING
  CONTRADICTORY_SOURCE_RECORD
  DIVERGING_FUND_NOT_EXPRESSIBLE
  DIVERGING_SOZIALHILFETRAEGER
  NO_FUND_RECORDED
  ODOO_PARTNER_DISCARDED
  PRIVATE_RECIPIENT_CONFLICT
  SELBSTBEHALT_ON_BEIHILFE_DROPPED
  SOZIALHILFETRAEGER_INCOMPLETE
  SUPPLEMENTARY_ON_HEALTH_RECORD_DROPPED
  UNMAPPABLE_RECORD
}

Values

`PayerConfigurationReviewReason.AKTENZEICHEN_MISSING`

The Aktenzeichen has no source field in the legacy data and was left blank.

`PayerConfigurationReviewReason.BEIHILFESTELLE_INCOMPLETE`

The Beihilfestelle's name or address was missing, so the Beihilfe's share is migrated but cannot be addressed yet.

`PayerConfigurationReviewReason.BEIHILFE_PERCENTAGE_CLAMPED`

The Beihilfe percentage was outside 0-100 and was clamped into range.

`PayerConfigurationReviewReason.BEIHILFE_PERCENTAGE_MISSING`

A Dienstbereich carried a Beamtenbeihilfe answer with no percentage anywhere to take it from, so it was defaulted to 0.

`PayerConfigurationReviewReason.CONTRADICTORY_SOURCE_RECORD`

The legacy record contradicted itself — a privateInvoice flag beside a funding agency, or a hasSupplementaryInvoiceRecipient flag disagreeing with the recipient type.

`PayerConfigurationReviewReason.DIVERGING_FUND_NOT_EXPRESSIBLE`

A Dienstbereich named a different Kasse than the one that became the Beteiligter. Only the Krankenkasse may legitimately differ (SGB V); anything else is not expressible as a deviation, so the Dienstbereich was left coupled to the Beteiligte.

`PayerConfigurationReviewReason.DIVERGING_SOZIALHILFETRAEGER`

The Dienstbereiche named Sozialhilfeträger that disagree on name, address or Kostenzusage. The most frequent one became the Beteiligter.

`PayerConfigurationReviewReason.NO_FUND_RECORDED`

The legacy record named no Kasse, or named one without an insurance number. Every Dienstbereich resolves to "no coverage" until a PDL enters one.

`PayerConfigurationReviewReason.ODOO_PARTNER_DISCARDED`

An Odoo partner id on the legacy record has no equivalent on the new Beteiligter and was discarded.

`PayerConfigurationReviewReason.PRIVATE_RECIPIENT_CONFLICT`

The LTCI and health-insurance branches implied different private recipients for the same interval. The LTCI one was kept, as it covers more Dienstbereiche.

`PayerConfigurationReviewReason.SELBSTBEHALT_ON_BEIHILFE_DROPPED`

A sozialamtDeductible was set on a Beamtenbeihilfe record. A Selbstbehalt only caps what a Sozialhilfeträger takes over (question 2), never a Beihilfe share (question 1), so it was dropped.

`PayerConfigurationReviewReason.SOZIALHILFETRAEGER_INCOMPLETE`

The Sozialhilfeträger's name or address was missing, so no Sozialhilfeträger could be recorded and the client keeps the Eigenanteil for now.

`PayerConfigurationReviewReason.SUPPLEMENTARY_ON_HEALTH_RECORD_DROPPED`

Beihilfe or Sozialamt data sat on a health-insurance record. Those Beteiligte are recorded once for the whole client, from the LTCI record, so the health-insurance copy was dropped.

`PayerConfigurationReviewReason.UNMAPPABLE_RECORD`

The legacy record could not be mapped at all and was migrated as a client-pays-everything configuration.

Member Of

PayerConfigurationReviewNote object

Values​

Member Of​

Values

Member Of