Overview
I want to confirm whether this is the intended product behavior or a functional limitation.
It may need to configure one panel (e.g., a respiratory PCR panel) and reuse it across multiple sample types.
At the moment, the configuration flow seems to force a panel to be tied to only one sample type at creation time.
Navigation Flow (Simple)
- Go to Admin
- Open Test Management Configuration
- Open Panel Management
- Click Create New Panel
- Fill panel name/details
- Select Sample Type (single selection)
- Save panel
Current Behavior
- During panel creation, only one sample type can be selected.
- The panel is then treated as belonging to that sample type in later assignment/order flows.
- Reusing the same panel across multiple sample types appears to require duplication or extra configuration work.
Expected Behavior (Question / Suggestion)
I want to confirm if the current behavior is intentional.
If not intentional, expected behavior would be:
- A panel can be associated with multiple sample types (one-to-many mapping from panel to sample-type associations).
- The same panel definition can be reused without duplicating panel setup.
- Test assignment and order entry should still filter correctly by sample type with panel mapping.
Why this matters
If a single panel cannot be reused across different sample types, this becomes a limitation:
- Duplicated panel definitions
- More maintenance overhead
- Higher risk of inconsistent panel/test configurations across sample types
Clarification Requested
Can you confirm whether:
- This is the intended design, or this should be considered a product limitation / enhancement request?