Medical

In app/Services/PlanfactService.php at lines 3991–3999, inside parseQuoteMedical(), the Plan Type switch is case-sensitive. Other enum mappings in the same method use strtolower() to normalize before matching.

Please:
1. Show me the Plan Type switch.
2. Add strtolower() to the input value before the switch (matching the pattern used elsewhere in this parser).
3. Make sure the case statements use lowercase.
4. Show me the proposed change.

In app/Services/PlanfactService.php at lines 4026–4067, inside parseQuoteMedical(), the multi-network handling uses a deductible-based sort heuristic when there are more than 2 networks.

The current logic:
- Builds an associative array from networks[0], networks[1], and networks[count-1] only.
- Sorts by deductible.

Issues:
- 4+ networks: middle networks are silently ignored.
- Networks with equal deductibles: ordering is undefined.

Please:
1. Show me the current logic.
2. Recommend an improvement: either explicitly limit to 3 networks at parse time with a log warning when more are encountered, OR find a more reliable signal than deductible (e.g., network name pattern matching).
3. Don't change anything yet — show the proposed approach.

In app/Services/PlanfactService.php at lines 4313–4348, inside parseQuoteMedical(), there's a non-obvious contract for multi-network copay combining:
- When type is "Other", the actual value is in [service]Other (not [service]).
- Form / display code must check Type first to know which field to read.

Please:
1. Show me the current logic.
2. Add an inline comment block (4–6 lines) explaining the contract and pointing at the frontend file that consumes it.
3. Don't change behavior — just document.

In app/Services/PlanfactService.php at line 4484, inside parseQuoteMedical(), drug tier parsing hard-stops at 6 tiers. Tiers beyond the 6th are silently dropped.

Please:
1. Show me the line.
2. Check the Quote model and form template — is RxTier defined for tiers 1–6 only, or higher?
3. If the limit is real (form only supports 6), add a log warning when more tiers are encountered, so we know if this becomes an issue.
4. If higher tiers are supported on the form but not in the parser, raise the parser's limit.

In app/Services/PlanfactService.php inside parseQuoteMedical(), several deductible extractions use truthy checks like:
if ($ded) { ... }

PHP treats "0" as falsy, so a $0 deductible value would be skipped. $0 deductibles are valid (e.g., HSA-paired or first-dollar plans).

Please:
1. Find every instance of this pattern in parseQuoteMedical() and the helper functions it calls (parseMoney, parseCopay).
2. Replace truthy checks with explicit "is not null and is not empty string" checks where the field semantically allows "0" as a valid value.
3. Show me the affected lines and the proposed change.

In app/Services/PlanfactService.php inside parseQuoteMedical() (lines 4072 onward), many lookups concatenate the network name into a Plan Facts path key:
$value = $data['Overall Deductible'][$networkName]['Overall Individual Deductible'] ?? null;

If a carrier's network name contains unusual whitespace or characters that don't match what's in the response, the lookup silently fails.

Please:
1. Find all such concatenations in this parser.
2. Wrap them in a helper that, on lookup failure, logs the network name being searched and the available keys at that level. This makes future failures debuggable instead of silent.
3. Show me the proposed helper and an example of how to apply it.