Gitead/DentalManagementMH07
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add Provider field to appointment form, drive AI claim automation

Browse Source 
Adds an optional Provider (NPI) select to the Edit Appointment form,
sourced from Settings > NPI Providers. The AI "Claim for Column" batch
flow now prefers the appointment's own provider when resolving which
provider Selenium should select on the insurance site (e.g. MassHealth
rendering provider dropdown), falling back to the existing per-procedure
selection, active claim, or first configured provider.

Also resyncs packages/db's committed compiled schema/client artifacts
with their .ts sources — they had drifted out of sync (some untouched
since July), which was silently stripping the new npiProviderId field
via stale .strict() zod schemas.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
ff
2026-07-20 23:07:10 -04:00
parent ca568de817
commit b1932fa3d6
1285 changed files with 21237 additions and 4432 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
packages/db/shared/schemas/objects/NpiProviderOrderByWithRelationInput.schema.ts
View File

@@ -5,7 +5,8 @@ import { UserOrderByWithRelationInputObjectSchema as UserOrderByWithRelationInpu
import { ClaimOrderByRelationAggregateInputObjectSchema as ClaimOrderByRelationAggregateInputObjectSchema } from './ClaimOrderByRelationAggregateInput.schema';
import { PaymentOrderByRelationAggregateInputObjectSchema as PaymentOrderByRelationAggregateInputObjectSchema } from './PaymentOrderByRelationAggregateInput.schema';
import { CommissionBatchOrderByRelationAggregateInputObjectSchema as CommissionBatchOrderByRelationAggregateInputObjectSchema } from './CommissionBatchOrderByRelationAggregateInput.schema';
import { AppointmentProcedureOrderByRelationAggregateInputObjectSchema as AppointmentProcedureOrderByRelationAggregateInputObjectSchema } from './AppointmentProcedureOrderByRelationAggregateInput.schema'
import { AppointmentProcedureOrderByRelationAggregateInputObjectSchema as AppointmentProcedureOrderByRelationAggregateInputObjectSchema } from './AppointmentProcedureOrderByRelationAggregateInput.schema';
import { AppointmentOrderByRelationAggregateInputObjectSchema as AppointmentOrderByRelationAggregateInputObjectSchema } from './AppointmentOrderByRelationAggregateInput.schema'
const makeSchema = () => z.object({
id: SortOrderSchema.optional(),
@@ -18,7 +19,8 @@ const makeSchema = () => z.object({
claims: z.lazy(() => ClaimOrderByRelationAggregateInputObjectSchema).optional(),
payments: z.lazy(() => PaymentOrderByRelationAggregateInputObjectSchema).optional(),
commissionBatches: z.lazy(() => CommissionBatchOrderByRelationAggregateInputObjectSchema).optional(),
appointmentProcedures: z.lazy(() => AppointmentProcedureOrderByRelationAggregateInputObjectSchema).optional()
appointmentProcedures: z.lazy(() => AppointmentProcedureOrderByRelationAggregateInputObjectSchema).optional(),
appointments: z.lazy(() => AppointmentOrderByRelationAggregateInputObjectSchema).optional()
}).strict();
export const NpiProviderOrderByWithRelationInputObjectSchema: z.ZodType<Prisma.NpiProviderOrderByWithRelationInput> = makeSchema() as unknown as z.ZodType<Prisma.NpiProviderOrderByWithRelationInput>;
export const NpiProviderOrderByWithRelationInputObjectZodSchema = makeSchema();