Fix incorrect resourceSubType filter applied to ServiceRequest charge items #15113

yash-learner · 2026-01-12T19:41:01Z

Proposed Changes

This pull request introduces improvements to how charge item resources are categorized and handled across billing components. The main change is the addition and propagation of a new resourceSubType prop, allowing for more flexible and explicit assignment of resource subtypes when adding or displaying charge items. This refactor enhances code maintainability and enables future extensibility.

Charge Item Resource Subtype Handling

Added the resourceSubType prop to the AddMultipleChargeItemsSheet component and its TypeScript interface, allowing parent components to specify the subtype dynamically. [1] [2]
Updated the usage of AddMultipleChargeItemsSheet in both ChargeItemsSection and BedChargeItemsTable components to pass the appropriate resourceSubType value, making the resource subtype assignment explicit and context-aware. [1] [2]
Refactored the internals of AddMultipleChargeItemsSheet to use the passed-in resourceSubType prop instead of hardcoding the value for bed charges, improving flexibility for different charge item types.

Type Imports

Added imports for ResourceCategorySubType in relevant files to support the new prop and ensure type safety. [1] [2]

Tagging: @ohcnetwork/care-fe-code-reviewers

Merge Checklist

Add specs that demonstrate the bug or test the new feature.
Update product documentation.
Ensure that UI text is placed in I18n files.
Prepare a screenshot or demo video for the changelog entry and attach it to the issue.
Request peer reviews.
Complete QA on mobile devices.
Complete QA on desktop devices.
Add or update Playwright tests for related changes

Summary by CodeRabbit

Refactor
- Enhanced the charge item system to support flexible categorization of different charge types, improving system maintainability and extensibility without changing user-facing functionality.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

…rgeItemsTable components

netlify · 2026-01-12T19:41:07Z

✅ Deploy Preview for care-ohc ready!

Name	Link
🔨 Latest commit	`8b10c77`
🔍 Latest deploy log	https://app.netlify.com/projects/care-ohc/deploys/69654e50a8a4120008d7a7d0
😎 Deploy Preview	https://deploy-preview-15113.preview.ohc.network
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

coderabbitai · 2026-01-12T19:41:14Z

Walkthrough

This change introduces a new optional resourceSubType prop to the AddMultipleChargeItemsSheet component, allowing callers to specify the resource category subtype. The prop is threaded through to ChargeItemDefinitionPicker. Two consumers are updated to pass the appropriate subtype values.

Changes

Cohort / File(s)	Summary
Component Definition `src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx`	Added optional `resourceSubType?: ResourceCategorySubType` prop to `AddMultipleChargeItemsSheetProps` interface and component destructuring. Replaced hardcoded resourceSubType value with the new prop when passing to `ChargeItemDefinitionPicker`.
Component Consumers `src/components/Billing/ChargeItems/ChargeItemsSection.tsx`, `src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx`	Added `ResourceCategorySubType` imports and updated `AddMultipleChargeItemsSheet` usage to pass `resourceSubType` prop with appropriate subtype values (`ResourceCategorySubType.other` and `ResourceCategorySubType.charge_item_definition_location_bed_charges` respectively).

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: fixing incorrect resourceSubType filter applied to ServiceRequest charge items.
Description check	✅ Passed	The description is comprehensive, covering all major changes with references to specific files and lines, though most merge checklist items remain unchecked.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

📝 Generate docstrings

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch fix-ci-filter-in-sr

📜 Recent review details

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 331df8e and 8b10c77.

📒 Files selected for processing (3)

src/components/Billing/ChargeItems/ChargeItemsSection.tsx
src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx
src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx

🧰 Additional context used

📓 Path-based instructions (13)

**/*.{ts,tsx}

📄 CodeRabbit inference engine (.cursorrules)

**/*.{ts,tsx}: Write concise, technical TypeScript code with accurate examples
Use TypeScript for all code; prefer interfaces over types
Avoid enums; use maps instead
Use TanStack Query for data fetching from the API along with query and mutate utilities for the queryFn and mutationFn
Use raviger for routing

**/*.{ts,tsx}: Use TypeScript with strict mode and ES2022 target
Use interface for defining object types in TypeScript
Avoid explicit any type in TypeScript
Use proper nullability annotations in TypeScript types
Use dedicated error handlers and TypeScript strict null checks

**/*.{ts,tsx}: Use TypeScript for all new code
Prefer interfaces over types for object definitions in TypeScript
Avoid using any type; use proper type definitions in TypeScript
Use type inference where possible in TypeScript
Use TanStack Query for API data management
Prefer React Context for global state management

**/*.{ts,tsx}: Use TanStack Query with the query and mutate utilities from @/Utils/request/
Use appropriate query keys following the resource pattern for TanStack Query
Leverage TanStack Query built-in features for pagination and debouncing
Implement proper error handling using the global error handler for TanStack Query operations
Use useQuery hook with queryKey and queryFn parameters, where queryFn wraps the API route with the query() utility
Use useMutation hook with mutationFn parameter wrapping API routes with the mutate() utility, and implement onSuccess callbacks to invalidate related queries
Support path parameters in TanStack Query using the pathParams option in query/mutate utilities
Support query parameters in TanStack Query using the queryParams option in query/mutate utilities
Use the silent: true option to suppress global error notifications when custom error handling is needed

**/*.{ts,tsx}: Use TypeScript with strict mode and ES2022 target
Use interface for defining object types
Avoid explicit any types and maint...

Files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx
src/components/Billing/ChargeItems/ChargeItemsSection.tsx
src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx

**/*.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (.cursorrules)

**/*.{ts,tsx,js,jsx}: Use functional and declarative programming patterns; avoid classes
Prefer iteration and modularization over code duplication
Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError)
Use the "function" keyword for pure functions
Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements

**/*.{ts,tsx,js,jsx}: Use path aliases for imports from src (@/*)
Use double quotes for strings
Semicolons are required at end of statements
Order imports as: 3rd-party → library → CAREUI → UI → components → hooks → utils → relative
Use PascalCase for component and class names
Use camelCase for variable and function names

**/*.{ts,tsx,js,jsx}: Use path aliases @/* for imports from src directory
Use double quotes for strings
Require semicolons at end of statements
Order imports: 3rd-party → library → CAREUI → UI → components → hooks → utils → relative
Use PascalCase for component and class names
Use camelCase for variable and function names

Files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx
src/components/Billing/ChargeItems/ChargeItemsSection.tsx
src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx

**/*.{tsx,jsx}

📄 CodeRabbit inference engine (.cursorrules)

Use declarative JSX

Files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx
src/components/Billing/ChargeItems/ChargeItemsSection.tsx
src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx

src/**/*.{ts,tsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

src/**/*.{ts,tsx}: Use strict TypeScript configuration for medical data safety in all TypeScript source files
All literal strings must use i18next for multi-language support in healthcare interfaces
Use comprehensive error boundaries and user-friendly error messages for medical workflow debugging without exposing PHI
Follow ESLint configured rules for React hooks, accessibility, and code quality
Use @tanstack/react-query for server state management in API client code
Localize date and time formats for medical timestamps using locale-aware formatting functions
Use date-fns for date handling and manipulation with locale awareness for medical timestamps

Files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx
src/components/Billing/ChargeItems/ChargeItemsSection.tsx
src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx

src/**/*.{ts,tsx,css}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Use Prettier for consistent code formatting across the healthcare application

Files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx
src/components/Billing/ChargeItems/ChargeItemsSection.tsx
src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx

src/pages/**/*.{ts,tsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Use raviger for application routing in page components and route definitions

src/pages/**/*.{ts,tsx}: Keep page components in src/pages/ organized by feature
Use descriptive file names that reflect the page purpose
Export page components as default exports
Co-locate page-specific components and utilities with page components
Use raviger router for navigation (existing dependency)
Implement proper route parameters and query string handling
Handle navigation guards and authentication checks in page components
Implement proper loading states and error boundaries in page components
Use semantic HTML structure for accessibility in page components
Use @tanstack/react-query for API state management in page components (existing dependency)
Implement proper loading, error, and success states for data fetching
Handle pagination and infinite scroll patterns appropriately
Cache data appropriately in page components based on usage patterns
Use controlled components for form inputs in page components
Implement proper form validation with zod schemas in page components
Handle form submission states (loading, success, error) in page components
Use React hooks for local page state
Minimize unnecessary re-renders in page components
Implement proper authentication checks in page components
Handle different user roles and permissions in page components
Redirect to login when authentication is required in page components
Show appropriate UI based on user permissions in page components
Set appropriate page titles and meta descriptions in page components
Handle OpenGraph and Twitter card meta tags in page components
Implement structured data where applicable in page components
Implement code splitting for large page components
Use lazy loading for heavy components within page components
Optimize bundle size with proper imports in page components
Handle image optimization and lazy loading in page components
Implement comprehensive error boundaries in page components
Handle API e...

Files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx
src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx

src/**/*.{tsx,ts}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

src/**/*.{tsx,ts}: Use React 19.1.1 features and patterns following React 19 Documentation for healthcare application development
Use shadcn/ui as primary component system and CAREUI for healthcare-specific components
Use framer-motion for animations in healthcare UI interfaces

Files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx
src/components/Billing/ChargeItems/ChargeItemsSection.tsx
src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx

src/**/*.{tsx,css}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Use Tailwind CSS 4.1.3 utility classes with custom healthcare-specific design system for styling

Files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx
src/components/Billing/ChargeItems/ChargeItemsSection.tsx
src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx

**/*

📄 CodeRabbit inference engine (CLAUDE.md)

Use 2-space indentation

Files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx
src/components/Billing/ChargeItems/ChargeItemsSection.tsx
src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx

**/*.tsx

📄 CodeRabbit inference engine (.cursor/rules/02-coding-standards.mdc)

**/*.tsx: Use functional components with proper type definitions in React
One component per file is preferred
Prefer default exports for React components
Follow the component naming pattern: ComponentName.tsx for React components
Use Tailwind CSS for styling
Use Shadcn UI components when available
Use local state for component-specific data
Use PascalCase for component file names (e.g., AuthWizard.tsx)

Files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx
src/components/Billing/ChargeItems/ChargeItemsSection.tsx
src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx

**/*.{tsx,ts}

📄 CodeRabbit inference engine (.cursor/rules/04-ui-components.mdc)

**/*.{tsx,ts}: Use Shadcn UI components as the primary component library
Follow the component documentation for proper usage
Customize components using Tailwind CSS
Use navigate and useRedirect from raviger for navigation and redirects
Use Tailwind's responsive classes and follow mobile-first approach
Implement proper ARIA attributes for accessibility
Ensure keyboard navigation works in components
Define component props using TypeScript interfaces
Use translation keys from src/Locale/ for internationalization
Support RTL languages in components
Use proper date/time formatting for multiple language support

Files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx
src/components/Billing/ChargeItems/ChargeItemsSection.tsx
src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx

**/*.{ts,tsx,js,jsx,json,css,scss,html}

📄 CodeRabbit inference engine (AGENTS.md)

Use 2-space indentation

Files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx
src/components/Billing/ChargeItems/ChargeItemsSection.tsx
src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx

src/components/**/*.{ts,tsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

src/components/**/*.{ts,tsx}: Implement WCAG 2.1 AA accessibility compliance in medical applications with screen reader compatibility and keyboard navigation
Include medical use cases, accessibility notes, and WCAG compliance documentation in component documentation
Follow established React component patterns and folder structure organized by feature and domain

src/components/**/*.{ts,tsx}: Use path aliases: @/components/, @/types/, @/lib/, @/pages/ for imports
Follow import order: External packages → @/components/ui/ → @/components/ → @/CAREUI/ → @/types/ → @/lib/ → relative imports
Use named exports from lucide-react for icons (e.g., import { SettingsIcon } from "lucide-react")
Import useTranslation from react-i18next for internationalization
Use React 19.1.1 hooks pattern - Functional components only
Always define TypeScript Props interfaces (e.g., PatientInfoCardProps) for component props
Use handle prefix for event handlers (e.g., handleSubmit, handleTagsUpdate, handlePatientSelect)
Use shadcn/ui components as primary UI system (Button, Card, Badge, etc.) from @/components/ui/
Use healthcare-specific CAREUI custom components (Calendar, WeekdayCheckbox, Zoom) from @/CAREUI/
Use buttonVariants from @/components/ui/button with CVA patterns for button styling
Follow <Card><CardHeader> pattern for consistent card layouts
Use PatientRead type from @/types/emr/patient/patient for patient data handling
Implement TagAssignmentSheet with TagEntityType for patient/facility tags
Use PatientHoverCard for patient info overlays
Use Badge components to display patient status, facility capacity, medication dosage with color variants
Use cva() from class variance authority for variant-based component styling
Use cn() from @/lib/utils for conditional class composition
Follow Tailwind CSS 4.1.3 color system: primary-700, gray-900, red-500 pattern with dark mode variants
Use Tailwind shadow system: shadow-sm, shadow-xs for el...

Files:

src/components/Billing/ChargeItems/ChargeItemsSection.tsx

🧠 Learnings (8)

📚 Learning: 2025-11-25T13:52:51.914Z

Learnt from: CR
Repo: ohcnetwork/care_fe PR: 0
File: .github/instructions/react-components.instructions.md:0-0
Timestamp: 2025-11-25T13:52:51.914Z
Learning: Applies to src/components/**/*.{ts,tsx} : Implement `TagAssignmentSheet` with `TagEntityType` for patient/facility tags

Applied to files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx
src/components/Billing/ChargeItems/ChargeItemsSection.tsx
src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx

📚 Learning: 2025-11-25T13:53:20.837Z

Learnt from: CR
Repo: ohcnetwork/care_fe PR: 0
File: .github/instructions/typescript-types.instructions.md:0-0
Timestamp: 2025-11-25T13:53:20.837Z
Learning: Applies to src/types/**/*.{ts,tsx} : Define healthcare-specific utility types as union types: EmergencyPriority ('critical' | 'urgent' | 'semi-urgent' | 'non-urgent'), BedStatus, and MedicationRoute

Applied to files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx

📚 Learning: 2025-11-25T13:50:46.407Z

Learnt from: CR
Repo: ohcnetwork/care_fe PR: 0
File: .github/instructions/careui.instructions.md:0-0
Timestamp: 2025-11-25T13:50:46.407Z
Learning: Applies to src/CAREUI/**/*.{ts,tsx} : Integrate CAREUI components cleanly with healthcare data sources and support live data updates for critical medical information

Applied to files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx

📚 Learning: 2025-11-25T13:50:46.407Z

Learnt from: CR
Repo: ohcnetwork/care_fe PR: 0
File: .github/instructions/careui.instructions.md:0-0
Timestamp: 2025-11-25T13:50:46.407Z
Learning: Applies to src/CAREUI/**/*.{ts,tsx} : Use CAREUI imports for medical-specific functionality and shadcn/ui imports for standard UI components - CAREUI for medical interactions/workflows/data, shadcn/ui for buttons, forms, modals, tables, navigation

Applied to files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx

📚 Learning: 2025-11-25T13:51:23.408Z

Learnt from: CR
Repo: ohcnetwork/care_fe PR: 0
File: .github/instructions/context.instructions.md:0-0
Timestamp: 2025-11-25T13:51:23.408Z
Learning: Applies to src/context/**/FacilityContext.tsx : Implement Facility Context for department location and resource availability

Applied to files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx
src/components/Billing/ChargeItems/ChargeItemsSection.tsx

📚 Learning: 2025-12-17T19:47:58.152Z

Learnt from: AdityaJ2305
Repo: ohcnetwork/care_fe PR: 14821
File: src/components/Location/LocationNavigation.tsx:161-163
Timestamp: 2025-12-17T19:47:58.152Z
Learning: To ensure the remove-unused-i18n.js cleanup script detects i18n keys, avoid wrapping keys inside a ternary expression passed directly to t(). Instead, call t() separately in each branch of a conditional, e.g. condition ? t("key1") : t("key2"), or compute the key in a variable before passing to t(). For LocationNavigation.tsx (and similar TSX files in the repo), prefer explicit separate i18n calls per branch or a shared precomputed key to guarantee all keys are statically detectable by the script.

Applied to files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx
src/components/Billing/ChargeItems/ChargeItemsSection.tsx
src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx

📚 Learning: 2025-12-22T10:16:36.690Z

Learnt from: Jacobjeevan
Repo: ohcnetwork/care_fe PR: 14804
File: src/pages/Facility/services/pharmacy/DispensesView.tsx:117-135
Timestamp: 2025-12-22T10:16:36.690Z
Learning: In the care_fe repository, prefer the native HTML title attribute for simple tooltips over using shadcn/ui Tooltip components. Use Tooltip components only when the tooltip requires richer content, interactivity, or accessibility enhancements that cannot be achieved with a plain title. For simple cases, add a title attribute to the element (e.g., <span title="...">). If a Tooltip is used, ensure it is accessible and necessary, and avoid duplicating content available in the title attribute.

Applied to files:

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx
src/components/Billing/ChargeItems/ChargeItemsSection.tsx
src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx

📚 Learning: 2024-12-10T02:49:05.600Z

Learnt from: Jacobjeevan
Repo: ohcnetwork/care_fe PR: 9062
File: src/Routers/routes/ResourceRoutes.tsx:19-21
Timestamp: 2024-12-10T02:49:05.600Z
Learning: In the `ResourceCreate` component, `facilityId` can be optional.

Applied to files:

src/components/Billing/ChargeItems/ChargeItemsSection.tsx

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)

GitHub Check: build
GitHub Check: Redirect rules - care-ohc
GitHub Check: Test
GitHub Check: CodeQL-Build
GitHub Check: Header rules - care-ohc
GitHub Check: Pages changed - care-ohc
GitHub Check: Cloudflare Pages: care-preview

🔇 Additional comments (3)

src/components/Billing/ChargeItems/ChargeItemsSection.tsx (1)

13-13: LGTM!

The import is correctly placed with other type imports, and explicitly passing ResourceCategorySubType.other ensures the correct subtype filter is applied for service request charge items, fixing the issue described in the PR.

Also applies to: 183-183

src/pages/Facility/billing/account/components/BedChargeItemsTable.tsx (1)

50-50: LGTM!

The import is correctly placed, and passing ResourceCategorySubType.charge_item_definition_location_bed_charges is semantically appropriate for bed-associated charge items. This makes the subtype assignment explicit for the bed charges context.

Also applies to: 295-297

src/pages/Facility/services/serviceRequests/components/AddMultipleChargeItemsSheet.tsx (1)

48-59: LGTM!

The new optional resourceSubType prop is correctly added to the interface and threaded through to ChargeItemDefinitionPicker. The optional typing ensures backward compatibility for any callers not yet updated. ChargeItemDefinitionPicker accepts this prop with the matching ResourceCategorySubType type.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Copilot

Pull request overview

This PR fixes an issue where the incorrect resourceSubType filter was being applied to charge items, specifically affecting ServiceRequest-related charge items. The fix makes the resource subtype explicit and configurable rather than hardcoded.

Changes:

Added resourceSubType as a configurable prop to AddMultipleChargeItemsSheet component
Updated parent components to pass appropriate resourceSubType values based on their context
Removed hardcoded bed charges resource subtype from the sheet component

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
`AddMultipleChargeItemsSheet.tsx`	Added `resourceSubType` prop to interface and replaced hardcoded bed charges subtype with the prop value
`BedChargeItemsTable.tsx`	Explicitly passes bed charges resource subtype when using the sheet component
`ChargeItemsSection.tsx`	Passes generic "other" resource subtype for service request charge items

github-actions · 2026-01-12T19:58:56Z

🎭 Playwright Test Results

Status: ❌ Failed
Test Shards: 3

Metric	Count
Total Tests	251
✅ Passed	250
❌ Failed	1
⏭️ Skipped	0

📊 Detailed results are available in the playwright-final-report artifact.

_{Run: #4571}

fix: update resourceSubType handling in ChargeItemsSection and BedCha…

8b10c77

…rgeItemsTable components

yash-learner requested review from a team and Copilot January 12, 2026 19:41

ohc-project-manager bot assigned yash-learner Jan 12, 2026

Copilot AI reviewed Jan 12, 2026

View reviewed changes

ohc-project-manager bot added needs testing needs review labels Jan 12, 2026

yash-learner requested a review from amjithtitus09 January 12, 2026 19:46

Jacobjeevan approved these changes Jan 13, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Fix incorrect resourceSubType filter applied to ServiceRequest charge items #15113

Fix incorrect resourceSubType filter applied to ServiceRequest charge items #15113

yash-learner commented Jan 12, 2026 •

edited by coderabbitai bot

Loading

Uh oh!

netlify bot commented Jan 12, 2026 •

edited

Loading

Uh oh!

coderabbitai bot commented Jan 12, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

github-actions bot commented Jan 12, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Fix incorrect resourceSubType filter applied to ServiceRequest charge items #15113

Are you sure you want to change the base?

Fix incorrect resourceSubType filter applied to ServiceRequest charge items #15113

Conversation

yash-learner commented Jan 12, 2026 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Proposed Changes

Charge Item Resource Subtype Handling

Type Imports

Merge Checklist

Summary by CodeRabbit

Uh oh!

netlify bot commented Jan 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for care-ohc ready!

Uh oh!

coderabbitai bot commented Jan 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

github-actions bot commented Jan 12, 2026

🎭 Playwright Test Results

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

yash-learner commented Jan 12, 2026 •

edited by coderabbitai bot

Loading

netlify bot commented Jan 12, 2026 •

edited

Loading

coderabbitai bot commented Jan 12, 2026 •

edited

Loading