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>
41 lines
3.1 KiB
TypeScript
41 lines
3.1 KiB
TypeScript
import * as z from 'zod';
|
|
import type { Prisma } from '../../../generated/prisma';
|
|
import { SortOrderSchema } from '../enums/SortOrder.schema';
|
|
import { SortOrderInputObjectSchema as SortOrderInputObjectSchema } from './SortOrderInput.schema';
|
|
import { PatientOrderByWithRelationInputObjectSchema as PatientOrderByWithRelationInputObjectSchema } from './PatientOrderByWithRelationInput.schema';
|
|
import { UserOrderByWithRelationInputObjectSchema as UserOrderByWithRelationInputObjectSchema } from './UserOrderByWithRelationInput.schema';
|
|
import { StaffOrderByWithRelationInputObjectSchema as StaffOrderByWithRelationInputObjectSchema } from './StaffOrderByWithRelationInput.schema';
|
|
import { NpiProviderOrderByWithRelationInputObjectSchema as NpiProviderOrderByWithRelationInputObjectSchema } from './NpiProviderOrderByWithRelationInput.schema';
|
|
import { AppointmentProcedureOrderByRelationAggregateInputObjectSchema as AppointmentProcedureOrderByRelationAggregateInputObjectSchema } from './AppointmentProcedureOrderByRelationAggregateInput.schema';
|
|
import { ClaimOrderByRelationAggregateInputObjectSchema as ClaimOrderByRelationAggregateInputObjectSchema } from './ClaimOrderByRelationAggregateInput.schema';
|
|
import { AppointmentFileOrderByRelationAggregateInputObjectSchema as AppointmentFileOrderByRelationAggregateInputObjectSchema } from './AppointmentFileOrderByRelationAggregateInput.schema'
|
|
|
|
const makeSchema = () => z.object({
|
|
id: SortOrderSchema.optional(),
|
|
patientId: SortOrderSchema.optional(),
|
|
userId: SortOrderSchema.optional(),
|
|
staffId: SortOrderSchema.optional(),
|
|
npiProviderId: z.union([SortOrderSchema, z.lazy(() => SortOrderInputObjectSchema)]).optional(),
|
|
title: SortOrderSchema.optional(),
|
|
date: SortOrderSchema.optional(),
|
|
startTime: SortOrderSchema.optional(),
|
|
endTime: SortOrderSchema.optional(),
|
|
type: SortOrderSchema.optional(),
|
|
typeLocked: SortOrderSchema.optional(),
|
|
notes: z.union([SortOrderSchema, z.lazy(() => SortOrderInputObjectSchema)]).optional(),
|
|
procedureCodeNotes: z.union([SortOrderSchema, z.lazy(() => SortOrderInputObjectSchema)]).optional(),
|
|
status: SortOrderSchema.optional(),
|
|
movedByAi: SortOrderSchema.optional(),
|
|
createdAt: SortOrderSchema.optional(),
|
|
eligibilityStatus: SortOrderSchema.optional(),
|
|
patient: z.lazy(() => PatientOrderByWithRelationInputObjectSchema).optional(),
|
|
user: z.lazy(() => UserOrderByWithRelationInputObjectSchema).optional(),
|
|
staff: z.lazy(() => StaffOrderByWithRelationInputObjectSchema).optional(),
|
|
npiProvider: z.lazy(() => NpiProviderOrderByWithRelationInputObjectSchema).optional(),
|
|
procedures: z.lazy(() => AppointmentProcedureOrderByRelationAggregateInputObjectSchema).optional(),
|
|
claims: z.lazy(() => ClaimOrderByRelationAggregateInputObjectSchema).optional(),
|
|
files: z.lazy(() => AppointmentFileOrderByRelationAggregateInputObjectSchema).optional()
|
|
}).strict();
|
|
export const AppointmentOrderByWithRelationInputObjectSchema: z.ZodType<Prisma.AppointmentOrderByWithRelationInput> = makeSchema() as unknown as z.ZodType<Prisma.AppointmentOrderByWithRelationInput>;
|
|
export const AppointmentOrderByWithRelationInputObjectZodSchema = makeSchema();
|