Skip to main content

CALPADS error brief · MEET

MEET0598

Invalid Referring Party Code
Severity
FATAL error - Must be corrected in order to post the record and/or certify the data.
Error type MEET - Special Education Meetings
Record type MEET

Official CALPADS rule

What CALPADS is rejecting

Referring Party Code must only be populated when Special Education Referral Date is populated

Focus fields

Fields validated

24.10 - Special Education Referral Date 24.11 - Referring Party Code

Recommended correction path

Suggested resolution

Official rule in plain language

Severity: Fatal   Type: Input Validation

Fields validated

  • 24.10 Special Education Referral Date
  • 24.11 Referring Party Code

MEET0451 enforces the forward dependency—date requires party. MEET0598 enforces the reverse dependency—party cannot stand alone without its referral date.

The initial-evaluation sequence

1 · Referral24.10 records when the referral occurred.
2 · Referring party24.11 identifies the referral source.
3 · Parental consent24.12 records consent for the initial evaluation.
4 · Evaluation/meeting24.13 or 24.14 identifies completion or pending status.

Chronology rule: Referral must have occurred; referral source accompanies it; consent is the same date or later; the meeting/evaluation follows the applicable prerequisite dates.

Valid, invalid, and diagnostic examples

ResultExampleWhy
Valid Referral Date + Referring PartyThe paired referral facts are complete.
ValidNo referral event + both fields blankNo unsupported referral facts are submitted.
InvalidBlank Referral Date + Referring PartyThe source is reported without the event it describes.

Version 18 Referring Party codes

CodePartyUse when the documented referral came through
10ParentParent, guardian, or caretaker
15CDE WebsiteFamily received evaluation information from the CDE website
20TeacherCredentialed educator responsible for instruction
30Student Study/Intervention TeamSST or intervention team
40Other school/district personnelOther LEA employee or personnel pathway
42California State Preschool staffCSPP program
45Private preschool/childcare staffPrivate preschool or childcare program
47Early Head Start/Head Start staffEarly Head Start or Head Start program
50Early Intervention ProviderLicensed or certified early-intervention/service provider
60California Regional CenterRegional center
65Community/nonprofit organizationCommunity, family-resource, tribal, or similar organization
70Hospital/Medical ProviderHospital or medical provider
75Social WorkerSocial worker or Department of Social Services representative
80Family/Neighbor/FriendFamily member, friend, or neighbor
90OtherSource not described by another code

Use the current CALPADS definition and the documented referral source. Similar local labels do not automatically mean the same code.

Concrete checks

  • Determine whether the referral date was accidentally omitted or the party code was carried into a non-initial event.
  • Inspect source-to-extract rules that reuse the latest referring party on later meetings.
  • Confirm that a reevaluation or plan review was not incorrectly populated with initial-referral data.
  • Review adjacent MEET events before clearing either field.

Recommended correction path

  1. 1

    Preserve the rejected event

    Capture submission ID, SSID, Reporting LEA and SELPA, Academic Year, 24.10–24.14, 24.16, and the complete MEET history.

  2. 2

    Confirm the evaluation type

    Determine whether this is Initial Part B (10), Initial Part C (15), another evaluation, a plan review, or a different meeting event.

  3. 3

    Build the four-event timeline

    Place referral, referral source, consent, and meeting/pending evidence in chronological order. Keep documents from different evaluations separate.

  4. 4

    Verify authoritative evidence

    Use the referral/intake record, consent documentation, assessment workflow, meeting record, and current SEDS history. Do not infer a date or party from who entered the data.

  5. 5

    Correct the source and mapping

    If a documented referral exists, restore its date and validate the complete initial-evaluation sequence. If no referral belongs to this MEET event, remove the carried-forward party code from the authoritative source or mapping. Repair repeatable extract logic.

  6. 6

    Resubmit and reconcile

    Confirm acceptance, inspect the full MEET history, and review connected SWDS and PLAN records plus other students produced by the same workflow.

Official references