HHE Component Migration

Migration Priority

Tier 1 has 4 components (1-2 days). Tier 2 has 3 components (3-5 days). Should they be batched or phased?

A) Tier 1 now, Tier 2 next sprint

Ship quick wins immediately. Schedule Tier 2 separately.

B) Batch Tier 1 + Tier 2 in one sprint

Single focused migration sprint (5-7 days total). Avoids context-switching.

C) Tier 1 only, reassess Tier 2

Conservative. Ship Tier 1, evaluate impact before committing to Tier 2.

Typesense vs Algolia

PD has Typesense client ready. HHM roadmap mentions Algolia. Both solve the same problem (full-text search for 60k+ practitioners).

A) Typesense

PD config ready. Self-hosted option. Open-source. Geo-search native. Lower cost at scale.

B) Algolia

Managed SaaS. Mature ecosystem. More expensive. No self-hosted option.

C) Evaluate both

Run a comparison before committing. Delays implementation by 1-2 weeks.

Trust Badge Field Management

Migration adds 3 boolean fields to HHM Practitioner: malpracticeInsured, backgroundCheckComplete, acceptsHsaFsa. Who manages these?

A) Admin-managed initially

Admin sets badge values. Add to practitioner onboarding flow later.

B) Onboarding from day one

Practitioners self-report during onboarding. Requires verification workflow.

C) Automated third-party verification

Integrate with verification services. Most trustworthy but highest complexity.

SMS Schema Alignment

PD sms_logs has: twilio_message_id (unique), message_type enum, opt-out fields. HHM SmsLog has: status tracking, credit integration. Different but overlapping.

A) Extend HHM's SmsLog

Add PD's unique fields (twilio_message_id UK, opt-out tracking) to existing HHM model. Preserves HHM's credit system.

B) Replace with PD's schema

Use PD's sms_logs as the new model. Simpler but loses HHM's credit integration.

C) Keep both with adapter

Maintain compatibility. Highest complexity, but zero disruption to existing HHM SMS features.

Next.js 16 Upgrade Timeline

HHM is on Next.js 14. PD is on Next.js 16 + React 19. Upgrading 70+ pages is a dedicated effort.

A) Q2 2026, after migration stable

Ship component migrations first. Upgrade framework when features are proven.

B) Q3 2026, align with major release

Bundle with a major release. More time to prepare, but delays React 19 benefits.

C) Not on roadmap

Next.js 14 is stable and supported. Upgrade only when forced by dependency requirements.

Geolocation Method

PD uses browser navigator.geolocation (precise, requires user permission). HHM has IP-based geo.ts for EU cookie consent detection (approximate, no permission needed).

A) Browser geolocation (precise)

GPS-level accuracy. Requires user permission prompt. Best for "Near Me" feature.

B) IP-based geolocation (approximate)

No permission needed. City-level accuracy only. May not satisfy "Near Me" expectations.

C) Hybrid: IP default + browser opt-in

Show approximate results immediately. Upgrade to precise when user clicks "Near Me."

Component Migration Decisions