Add new table and fields to track participant type and number of participants

Reporting at the program level is preferred over Claims as it’s less complex.

Unique Pop NMEC could also be reported.
Will be reported as a CSV zipped with the record-level downloads on the data tab

Inline guidance and user guide will need to be updated.

Design mockup - Draft

Table name: Participant

Primary Key

  • Primary key: Participant.PrgID + Participant.PrgYear + Participant.ParticipantType + Participant.SiteID

  • Table validation check e.g. That the primary key is unique regardless of the letter case.

Relationship validation

  • Participant.PrgID must match a ProgramCost.PrgID

  • Participant.SiteID, when populated, must match a Site.SiteID


Fields

  • PrgID
    Data type: Text (up to 255 characters)

    Required: Y
    Description: The unique program identifier; joins to the ProgramCost table.

  • PrgYear

    Data type: Integer

    Required: Y

  • ParticipantType
    Data type: Text

    Required: Y

    Valuelist

  • ParticipantCount
    Data type: Number (Up to 15 decimal places)

    Required: Y

  • SiteID

    Data type: Text

  • EquityTargeted

    Data type: Number (Up to 15 decimal places)

    Required: Y

  • DAC

    Data type: Number (Up to 15 decimal places)

    Required: Y

  • HTR

    Data type: Number (Up to 15 decimal places)

    Required: Y

  • Underserved

    Data type: Number (Up to 15 decimal places)

    Required: Y

  • Comments

    Data type: Text

    Required: N

Select the module in CEDARS
Claims

Please authenticate to join the conversation.

Upvoters
Status

In Progress

Board
📨

Feedback

Tags

2026 Claim Spec Update Queue

ETA
Jun 09, 2026
Date

2 months ago

Author

Jennifer Scheuerell

Subscribe to post

Get notified by email when there are changes.