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: Participant.PrgID + Participant.PrgYear + Participant.ParticipantType + Participant.SiteID
Table validation check e.g. That the primary key is unique regardless of the letter case.
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
Please authenticate to join the conversation.
In Progress
Feedback
2026 Claim Spec Update Queue
2 months ago

Jennifer Scheuerell
Get notified by email when there are changes.
In Progress
Feedback
2026 Claim Spec Update Queue
2 months ago

Jennifer Scheuerell
Get notified by email when there are changes.