Key points

  • A correct occurrence code with the wrong date is still an incorrect claim element.
  • Occurrence codes use standardized meanings.
  • When multiple occurrence events are reported, make sure each entry belongs to this claim period and patient.

Code and date are one data point

A correct occurrence code with the wrong date is still an incorrect claim element. Verify the event and date together.

Do not substitute a narrative

Occurrence codes use standardized meanings. If a payer needs a different explanation or attachment, entering a vaguely related occurrence code is not a substitute.

Check for repeated events

When multiple occurrence events are reported, make sure each entry belongs to this claim period and patient.

Institutional-claim review

  • Treat an occurrence code and its associated date as one data element.
  • Verify the event date from the source record instead of estimating it from the billing period.
  • Remove stale occurrence information from copied claims.

Occurrence code and occurrence date must travel together

An occurrence code describes a defined event and is paired with a date. A valid code with the wrong date is still wrong, and a copied date from an earlier stay can be especially difficult to notice. Review the source event, the code definition, and the date as a unit. If multiple occurrence events are present, verify each one independently against the current institutional record.

Sources and verification

Use the CMS institutional-claim sources below for current CMS-1450/UB-04 guidance, then apply the payer’s rules for the facility claim.

Related guides

Try UB-04 software

For offices that prepare institutional paper claims, MedClaimSoftware’s dedicated UB-04 / CMS-1450 program can save and retrieve claims, support printing and alignment, and keep facility claim preparation in a focused Windows workflow. The software is $99/year for up to 2 computers, with a free downloadable trial. View UB-04 software.

← Previous: Condition Codes on the UB-04Next: Value Codes on the UB-04 →