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

feat: Select Procedures flow, batch-column NPI provider fix, auto PDF save

Browse Source 
- Add 'Select Procedures' right-click option on appointment page (separate from Claims/PreAuth)
- Select Procedures form saves CDT codes + NPI provider to AppointmentProcedure storage
- Remove Save button from insurance claim form; Claims/PreAuth opens for insurance submission only
- Claims/PreAuth auto-prefills from saved procedures including NPI provider
- Batch-column: procedures npiProviderId takes priority over stale claim npiProviderId
- Batch-column: auto-save PDF to patient Documents after successful submission (no socket needed)
- Add npiProviderId column to AppointmentProcedure table (prisma db push)
- Fix 'invalid db creation invocation': guard staffId, npiProviderId, procedureDate as Date object, totalBilled NaN guard
- Add full error logging to batch-column catch block

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Gitead
2026-04-27 00:25:24 -04:00
parent a279a3e7c1
commit 3e899376c3
838 changed files with 28488 additions and 773 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
packages/db/shared/schemas/objects/ClaimOrderByWithRelationInput.schema.ts
View File

@@ -6,6 +6,7 @@ import { PatientOrderByWithRelationInputObjectSchema as PatientOrderByWithRelati
import { AppointmentOrderByWithRelationInputObjectSchema as AppointmentOrderByWithRelationInputObjectSchema } from './AppointmentOrderByWithRelationInput.schema';
import { UserOrderByWithRelationInputObjectSchema as UserOrderByWithRelationInputObjectSchema } from './UserOrderByWithRelationInput.schema';
import { StaffOrderByWithRelationInputObjectSchema as StaffOrderByWithRelationInputObjectSchema } from './StaffOrderByWithRelationInput.schema';
import { NpiProviderOrderByWithRelationInputObjectSchema as NpiProviderOrderByWithRelationInputObjectSchema } from './NpiProviderOrderByWithRelationInput.schema';
import { ServiceLineOrderByRelationAggregateInputObjectSchema as ServiceLineOrderByRelationAggregateInputObjectSchema } from './ServiceLineOrderByRelationAggregateInput.schema';
import { ClaimFileOrderByRelationAggregateInputObjectSchema as ClaimFileOrderByRelationAggregateInputObjectSchema } from './ClaimFileOrderByRelationAggregateInput.schema';
import { PaymentOrderByWithRelationInputObjectSchema as PaymentOrderByWithRelationInputObjectSchema } from './PaymentOrderByWithRelationInput.schema'
@@ -28,10 +29,12 @@ const makeSchema = () => z.object({
updatedAt: SortOrderSchema.optional(),
status: SortOrderSchema.optional(),
claimNumber: z.union([SortOrderSchema, z.lazy(() => SortOrderInputObjectSchema)]).optional(),
npiProviderId: z.union([SortOrderSchema, z.lazy(() => SortOrderInputObjectSchema)]).optional(),
patient: z.lazy(() => PatientOrderByWithRelationInputObjectSchema).optional(),
appointment: z.lazy(() => AppointmentOrderByWithRelationInputObjectSchema).optional(),
user: z.lazy(() => UserOrderByWithRelationInputObjectSchema).optional(),
staff: z.lazy(() => StaffOrderByWithRelationInputObjectSchema).optional(),
npiProvider: z.lazy(() => NpiProviderOrderByWithRelationInputObjectSchema).optional(),
serviceLines: z.lazy(() => ServiceLineOrderByRelationAggregateInputObjectSchema).optional(),
claimFiles: z.lazy(() => ClaimFileOrderByRelationAggregateInputObjectSchema).optional(),
payment: z.lazy(() => PaymentOrderByWithRelationInputObjectSchema).optional()