Skip to content
This repository is currently being migrated. It's locked while the migration is in progress.

Add JSON Schema for VA Form 10-5345#1175

Draft
tarratsco wants to merge 1 commit into
masterfrom
optimus/10-5345-schema
Draft

Add JSON Schema for VA Form 10-5345#1175
tarratsco wants to merge 1 commit into
masterfrom
optimus/10-5345-schema

Conversation

@tarratsco
Copy link
Copy Markdown
Contributor

⚠️ 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-5345

Summary

This PR introduces a new JSON Schema for VA Form 10-5345 (Request for and Authorization to Release Medical Records or Health Information). The schema is defined against the JSON Schema Draft-04 specification and covers the structured capture of veteran and patient identifying information along with medical records release authorization details.

Key schema characteristics include:

  • A reusable simpleAddress definition used for structured address capture, with fields for street, street2, city, state (exactly 2 characters), and postalCode (validated against a US ZIP+4 pattern: ^\d{5}(?:-\d{4})?$)
  • A buildDefinitionReference helper used to generate $ref pointers to shared definitions, promoting reuse across the schema
  • additionalProperties: false enforced at the top level and within definitions to prevent undeclared fields from passing validation
  • Field-level maxLength constraints and example annotations for documentation and validation clarity

The schema is intended to support the digital submission of VA Form 10-5345, enabling veterans to authorize the release of their medical records or health information to a third party.

Files

  • src/schemas/10-5345/schema.js

Notes for reviewer

  • Please ensure you have incremented the version in package.json
  • Please add backend-review-group as a reviewer
  • The postalCode pattern (^\d{5}(?:-\d{4})?$) supports both standard 5-digit and ZIP+4 formats — please verify this aligns with backend expectations
  • The state field enforces exactly 2 characters (minLength: 2, maxLength: 2) — confirm this is appropriate for all valid use cases, including territories such as PR, GU, etc.
  • The buildDefinitionReference helper is defined locally within the schema file — confirm this pattern is consistent with conventions used elsewhere in this repository
  • Review whether any fields beyond simpleAddress (e.g., veteran name, date of birth, SSN, facility information) have been omitted from the artifact preview and ensure the full schema is complete before merging

Pull Requests to update the schema in related repositories

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant