fix: allow claims without appointment + support post/core multi-tooth input

- Make appointmentId nullable/optional in Prisma Zod schema via @zod rich
  comment so claims can be submitted without an existing appointment
- Convert undefined appointmentId to null in all claim form handlers and
  the backend claim creation endpoint
- Add AI classifier rule for expanding one procedure across multiple
  comma-separated tooth numbers (e.g. "post/core on #23, 24, 25, 26")
- Add "post/core" (slash) alias to CDT lookup maps

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-06-28 22:57:24 -04:00
parent c9d08028a9
commit e1fe4862d5
1613 changed files with 59200 additions and 422 deletions

View File

@@ -52,9 +52,11 @@ exports.PatientFindFirstResultSchema = z.nullable(z.object({
policyHolder: z.string().optional(),
allergies: z.string().optional(),
medicalConditions: z.string().optional(),
preferredLanguage: z.string().optional(),
status: z.unknown(),
userId: z.number().int(),
createdAt: z.date(),
updatedAt: z.date(),
user: z.unknown(),
appointments: z.array(z.unknown()),
procedures: z.array(z.unknown()),
@@ -62,5 +64,7 @@ exports.PatientFindFirstResultSchema = z.nullable(z.object({
groups: z.array(z.unknown()),
payment: z.array(z.unknown()),
communications: z.array(z.unknown()),
documents: z.array(z.unknown())
documents: z.array(z.unknown()),
conversation: z.unknown().optional(),
cloudFolders: z.array(z.unknown())
}));