feat: chatbot rendering provider override and NPI provider ordering

- AI chat extracts 'with provider <name>' and routes claim to that provider
- Claim form reads provider from sessionStorage before any async effects run,
  preventing saved claim/procedure data from overriding the chatbot selection
- NPI provider settings table shows Provider #1 / #2 labels with up/down
  reorder buttons; Provider #1 is always the default for claims
- Default provider now uses sortOrder instead of hardcoded 'Mary Scannell'
- Added sortOrder column to NpiProvider schema with migration

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Gitead
2026-06-11 13:17:05 -04:00
parent d4b9c1b889
commit 75c49ab1df
77 changed files with 385 additions and 105 deletions

View File

@@ -9,6 +9,7 @@ import { AppointmentProcedureCreateNestedManyWithoutNpiProviderInputObjectSchema
const makeSchema = () => z.object({
npiNumber: z.string(),
providerName: z.string(),
sortOrder: z.number().int().optional(),
createdAt: z.coerce.date().optional(),
user: z.lazy(() => UserCreateNestedOneWithoutNpiProvidersInputObjectSchema),
claims: z.lazy(() => ClaimCreateNestedManyWithoutNpiProviderInputObjectSchema).optional(),