Product EngineeringFeaturesOrder SplitFrontend

Overview

Overview of UI architecture, modal workflow, Redux dependencies, and split interaction behavior in Order Update.

👤 Sachin Sharma, Nilesh Bhusari📅 Updated: Mar 24, 2026🏷️ feature🏷️ frontend🏷️ react🏷️ redux

Overview

This section describes frontend behavior for Order Split in livehealth-frontend.

Frontend implementation focuses on:

  • Entry point action in Order Update footer.
  • Split modal selection and API submission flow.
  • Client-side guards before split submit.
  • Redux state refresh after successful split.

Core responsibilities

Split entry and user interaction

  • Exposes split action from BillUpdateFooter.
  • Opens SplitOrderModal using existing footer modal lifecycle.

Selection and request construction

  • Allows selection of test rows to move.
  • Accepts optional destination source.
  • Sends bill_id, test_ids, and new_source to backend.

Result handling and refresh

  • Shows success/failure user alerts.
  • Refreshes billed-user test list.
  • Updates Redux bill data and closes the split flow on success.

Frontend pages in this section

Scope and Gaps

Confirmed implementation decisions, out-of-scope areas for V1, and known backend gaps.

Entry and Flow

Split entry points, modal sequence, and response handling in the frontend workflow.

On this page

OverviewCore responsibilitiesSplit entry and user interactionSelection and request constructionResult handling and refreshFrontend pages in this section