Add JSON Schema for VA Form 10-2850e

[tarratsco]

⚠️ AI-Generated PR — This pull request was automatically generated by Optimus. All code requires human review and testing before merging.

New schema — VA Form 10-2850e

Summary

This PR adds a new JSON Schema (Draft-04) for VA Form 10-2850e, the Application for Associated Health Occupations. The schema covers the full set of sections required for healthcare practitioner credentialing and appointment at VA facilities, including:

• Application type — enumerated values for initial, reappointment, transfer, and temporary appointment types
• Personal information — required fields for lastName, firstName, dateOfBirth, and ssn, with string length constraints
• Contact information — applicant address and communication details
• Professional licenses — licensure data supporting credentialing workflows
• Employment history — prior employment records relevant to the appointment process
• Professional references — reference contact details
• Adverse history — disclosure fields for adverse actions or disciplinary history
• Appointment details — specifics of the requested VA appointment
• Attestation — applicant certification and signature acknowledgment

All top-level sections listed above are marked as required. The schema enforces additionalProperties: false at the root and nested object levels to prevent undeclared fields. String fields use minLength/maxLength constraints throughout. The optional occupationalCategory field (max 100 characters) allows classification of the applicant's healthcare role without being required for submission.

Files

• src/schemas/10-2850e-schema.json

Notes for reviewer

• Please ensure you have incremented the version in package.json
• Please add backend-review-group as a reviewer
• The occupationalCategory field is defined but not included in the top-level required array — confirm with form stakeholders whether this field should be required for any specific applicationType values, as conditional required logic may be needed
• The ssn field is present in personalInformation; confirm that appropriate pattern validation (e.g., "pattern": "^\\d{9}$") is applied in the full schema and that PII handling complies with VA data standards
• Verify that the adverseHistory section's boolean disclosure fields align with the most current version of the printed 10-2850e form, as this section is subject to periodic regulatory updates
• Confirm whether transfer and temporary application types require any conditionally required fields not reflected in the current shared required array

Pull Requests to update the schema in related repositories

• vets-api: pending
• vets-website: pending