Dev preview · simulated
Walk the geospatial care operating window.
Each role opens a simulated portal anchored on a 130-patient synthetic panel across Queens Village, Jamaica, Cambria Heights, St. Albans, Laurelton, Springfield Gardens, Elmont, and Valley Stream. No real authentication, no live GPS, no PHI.
Provider Command Center
Patient panel map · live CHW field view · review queue · care gaps · referral closure · telehealth join · provider-reviewed sign-off.
portal-provider
geospatial · simulated
CHW Field Navigation
Today's route map · simulated GPS · turn-by-turn next stop · home-visit checklist · SDOH assessment · barrier documentation · provider escalation · time log.
portal-chw
simulated GPS
no real geolocation
Documentation Readiness
Patient panel map filtered for documentation and billing readiness · claims-readiness queue · missing documentation · provider review status · time-log summary · denial-risk flags · export synthetic billing packet.
portal-biller
commercial ledger only
no clinical decisioning
Super Admin Dev Console
Tenant overview · 130-patient map · CHW team field visibility · role / permission map · ledger separation board · PromptOps trail · dev-only audited impersonation (never a production auth bypass).
portal-admin
dev-only · audited
not production auth
Every action inside these portals is a static walk-through. No data is written, no API is called, no credential is exchanged. Patient names, addresses, lat/lng, conditions, and SDOH flags are synthetic.
Future geospatial integration
When this becomes a real product surface.
Future production versions may integrate Google Maps Platform capabilities — map rendering, geocoding, route optimization, travel-time estimates, Street View-style context, and aerial / 3D geospatial views. Any production integration would require patient consent, role-based access, audit trails, HIPAA-aligned vendor review, data minimization, and operator-governed configuration. This dev preview uses local synthetic data only and does not call Google APIs.
- Roles: super_dev_admin · super_admin · provider_user · chw_user · biller_user · beta_applicant.
- Registration lifecycle: requested → email_verified → pending_admin_review → approved | rejected | needs_changes → active | suspended | deleted.
- Super admin bypass: explicitly prohibited. The safe pattern is super_dev_admin authenticates normally then uses a dev-only audited impersonation control under a separately authorized non-production gate.
- Audit: every state transition emits a ledger-tagged audit record. PHI stays under custody; downstream metadata is minimized.
- Geospatial governance: patient location, CHW location, and route data are PHI-adjacent. Production integration requires consent, audit, and minimization policy authored under a separately authorized future gate.
Compliance-safe disclaimer
Sign-in shown here is a non-functional UI prototype. No HIPAA, FDA, SOC2, HITRUST, or reimbursement certification claim. No autonomous clinical, billing, payroll, or legal decisioning. Synthetic identifiers only on every portal page.