Add JSON Schema for VA Form 10-0998#4
Draft
voidspooks wants to merge 1 commit into
Draft
Conversation
Generated by Optimus (https://github.com/aquia-inc/optimus). All files require human review before merging. Files: - src/schemas/10-0998/schema.js
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New schema — VA Form 10-0998
Summary
This schema covers VA Form 10-0998, the VA Health Care Benefits Decision Notice appeal form. The schema defines structured validation for claimant-driven appeal submissions, with the following key characteristics:
claimantTypeenum (veteran-beneficiary-payer,provider-not-under-contract,provider-under-contract) drives all conditional screen routing in the form experience. This field is central to the schema's conditional logic and should be treated as effectively required.date(ISO 8601,YYYY-MM-DD) andnullableDate(nullable ISO 8601), both using JSON Schemaformat: datefor validation.$refusing abuildDefinitionReferencehelper, consistent with patterns used across thevets-json-schemarepository.additionalProperties: falseis enforced at the root level, ensuring only declared fields are accepted.Files
src/schemas/10-0998/schema.jsNotes for reviewer
package.jsonbackend-review-groupas a reviewerclaimantTypefield drives conditional routing for all three claimant paths; please verify that any conditionalrequiredfields downstream of this value are correctly gated in the schema or documented as handled at the application layer.nullableDateallowsnullin addition to a valid date string — confirm this is intentional for optional date fields (e.g., decision notice date may be unknown at submission time).draft-04— confirm this is consistent with the consuming application's validator version before merging.requiredarray is visible in the artifact summary snippet; please confirm the full schema includes required field declarations at the root and nested object levels as appropriate.Pull Requests to update the schema in related repositories