Form Capturing — AOE Modal

The AOE Modal (AOEModal) is the primary capture interface for Ask at Order Entry forms during the billing workflow. It handles multi-form, multi-section navigation, conditional skip logic, prefilling, confirmation messages, and validation.

6.1 AOE Modal Architecture

Component: src/components/reusable/Billing/components/AOE/AOEModal.tsx

Props:

• aoeForms: AOEForm[] — array of forms to capture
• oldPatientData: JsonObject — existing patient data used for prefilling
• closeHandler() — callback invoked on save/close

Redux State (from GENERIC slice):

• activeAOEFormIndex — which form is currently active
• activeAOEFormSectionIndex — which section within the active form
• activeAOEFormMeta — computed metadata for the active section: { process, subprocess, questions, testDetails }

6.2 Form Rendering Pipeline

aoeForms (source data)
    │
    ▼
prepareActiveAOEFormDetails()
    │ Reads activeAOEFormIndex + activeAOEFormSectionIndex
    │ Resolves active form → active subprocess → ordered questions
    │
    ▼
activeAOEFormMeta: { process, subprocess, questions, testDetails }
    │
    ▼
AOEForm component
    │ Iterates questions[]
    │
    ▼ For each question:
    │
    ├── getLabFormInputComponent(type, field_type) → React Component
    │     Priority: Date types → LabFormDatePicker
    │               Signature → CustomSignature
    │               Others → getInputComponent(field_type) via inputMapper
    │               Fallback → CustomInput
    │
    └── prepareLabFormFieldProps() → Full prop object
          Includes: type, label, value, onChange, validation, errors
          ▼
    <InputComponent {...fieldProps} />

6.3 Field Prop Preparation

prepareLabFormFieldProps() is the master prop builder that adapts each question's configuration into props for the input component:

onChange Callback Chain:

6.4 Value Storage

Values live in Redux.GENERIC.aoeFormValues with a nested structure:

aoeFormValues = {
  billLevel: {
    [processId: number]: {
      [questionId: number]: string | any
    }
  },
  testLevel: {
    [testId: number]: {
      [processId: number]: {
        [questionId: number]: string | any
      }
    }
  }
}

Determining Level:

• testDetails === null → bill-level → aoeFormValues.billLevel[processId][questionId]
• testDetails !== null → test-level → aoeFormValues.testLevel[testId][processId][questionId]

6.5 Prefilling

setPrefillingValue() runs on form initialization, iterating all questions:

1. Today's Date Prefill: If todays_date attribute is true → sets moment() formatted by the question's date format.

2. Source-Based Prefill: If allow_prefilling is true:

   • Reads prefilling_source (Patient, Bill, Home Collection)
   • Reads prefilling_options.source_field — a dot-path (e.g., "patient.dob")
   • Traverses the source data using the dot-path to extract the value
   • Handles date format conversion if the source value is a date
   • Falls back to default_value attribute if source value is empty

6.6 Skip-To Logic (Conditional Navigation)

The skip-to system allows questions to redirect form navigation based on the answer given.

Configuration (stored as a serialized string in question attributes):

{
  "skip_to_conditions": "[{\"value\": \"Yes\", \"skip_type\": \"Process\", \"target_id\": 42}]"
}

Skip Types:

Execution Flow:

Data cleanup during skip:

• Intermediate forms removed from aoeForms
• Intermediate sections removed from targeted forms
• Questions below trigger point removed from current section
• All affected values removed from aoeFormValues

6.7 Confirmation Messages

When a question has requires_confirmation_message: true and the user enters a value:

1. afterFieldOnChange() detects the flag
2. Shows AOEQuestionValueConfirmationModal with the configured message (HTML-rendered)
3. Confirm & Proceed → continues (triggers skip-to if also configured)
4. Cancel → removeQuestionValueOnCancelConfirmation() clears the entered value

6.8 Form-Level Validation

Field-Level Validation via labFormQuestionValidatorMapper(field_type, attributes):

Form-Level Validation via checkIsValidFormSection() / checkIsAOEFormValid():

• Iterates all questions in the current section (or all forms)
• For each question: checks if mandatory + empty, then runs the type-specific validator
• Returns false on first error → disables the Next/Save button

6.9 Multi-Section / Form Navigation

Navigation Functions:

Footer Behavior:

• Previous: Hidden on first section of first form
• Next: Calls handleNextClick(), which validates the current section before navigating
• Save & Close: Shown on last section of last form → calls closeHandler()

File Reference: src/components/reusable/Billing/components/AOE/utils.ts (1726 lines — navigation, validation, field props, skip logic, prefilling)