Postpartum navigation as a family-support benefit.
A UI-only preview of how employers could eventually support postpartum care navigation across doulas, lactation, mental health, pelvic floor PT, newborn care, meal support, home support, and classes while preserving privacy boundaries.
Cognito-protected route boundary
Cognito/Auth.js authentication and coarse role routing are active here. The page still uses sample data only; real PHI or operational records require app-owned RBAC, MFA where appropriate, audit logging, secure storage, and review.
For employers
UI-only partner preview.
This employer page uses simulated metrics only. No individual employee PHI, patient record, case file, claim, or identifiable outcome is displayed. Production reporting requires HIPAA-aware security, RBAC, audit logs, consent/privacy review, BAAs/vendor review, de-identification and aggregation rules, and legal/compliance review.
Employer reporting should be aggregate and de-identified unless a specific legal basis and consent or authorization permits otherwise.
Benefit use cases
Employee experience preview
Step 1
Public discovery
Families can browse services, resources, classes, and provider profiles without creating an account today.
Step 2
Future matching concept
Future support matching may recommend service categories and reviewed providers after the platform is approved for that workflow.
Step 3
Navigator follow-up later
Future account-gated workflows can support saved providers, class registration, navigator outreach, and care case access.
Step 4
Aggregate reporting concept
Employer reporting should be aggregate and de-identified unless a specific legal basis and authorization permits otherwise.
Employer value
Postpartum access navigation
Help families find appropriate local support across recovery, feeding, mental health, newborn care, classes, meals, and home support.
High-touch support layer
Position future care navigation as an employee benefit without implying active provider matching today.
Privacy-aware reporting
Future employer reporting should stay aggregate and de-identified, with no individual employee PHI sharing without proper basis.
Employee support framing
Focus on access, navigation, and family support without overclaiming medical, productivity, or return-to-work outcomes.
Aggregate outcomes preview
Sample reporting can show future time-to-support, first-visit completion, satisfaction preview, and care gaps closed preview.
Future employer dashboard
A later dashboard can summarize benefit utilization only after security, consent, and reporting governance are mature.
Sample aggregate employer metrics
Metrics shown here are simulated and sample-only. They demonstrate future reporting patterns, not real partner analytics, claims analytics, or production outcomes.
Average time to match
1.4 business days
First visit completion preview
2 of 3
Satisfaction preview
4.7 / 5 sample average
Care gaps closed preview
3 sample gaps closed
Reporting boundary
No real PHI is displayed. No partner reporting export, real aggregate analytics pipeline, claims analytics, payer report, employer report, or contracting workflow is active.
Future benefit journey
01
Discover
Employee finds public services, resources, classes, and providers.
02
Plan
Future matching may recommend relevant support categories after approval.
03
Navigate
Navigator follow-up becomes available after secure account workflows.
04
Connect
Family connects with future reviewed providers through gated actions after the platform is approved for that workflow.
05
Support
Care completion and follow-up signals can be measured later.
06
Report
Employer receives aggregate, de-identified program insights only.