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:
@@ -4,7 +4,8 @@ import { SortOrderSchema } from '../enums/SortOrder.schema'
|
||||
|
||||
const makeSchema = () => z.object({
|
||||
id: SortOrderSchema.optional(),
|
||||
userId: SortOrderSchema.optional()
|
||||
userId: SortOrderSchema.optional(),
|
||||
sortOrder: SortOrderSchema.optional()
|
||||
}).strict();
|
||||
export const NpiProviderSumOrderByAggregateInputObjectSchema: z.ZodType<Prisma.NpiProviderSumOrderByAggregateInput> = makeSchema() as unknown as z.ZodType<Prisma.NpiProviderSumOrderByAggregateInput>;
|
||||
export const NpiProviderSumOrderByAggregateInputObjectZodSchema = makeSchema();
|
||||
|
||||
Reference in New Issue
Block a user