SOURCE-AWARE COMPARISON
From a functional website to a connected digital front door.
The left side describes observable public NVHC website capabilities. The right side shows the CareOS design concepts; this is not an evaluation of the institution’s private clinical systems.

| Area | Observable public-site experience | KINGAI CareOS proposed expansion |
|---|---|---|
| Public services | Service listings and patient resource pages | Structured services with location/provider relationships and clearer pathways |
| Providers | Searchable public provider directory | Shared structured data, records history, multilingual views and automated publishing review |
| Locations | Region and WIC location resources | ZIP search, service combinations, verified hours, field-program status and maps roadmap |
| Appointments | Existing patient portal and scheduling paths | Facility-specific portal handoffs and step-by-step navigation for each care type |
| Mobile programs | Mammovan, mobile dentistry and other programs | Single outreach hub, calendar publishing and field coordination planning |
| Accessibility | Public site can be tested against accessibility standards | Documented WCAG test plan, accessible components and issue-remediation workflow |
| Content workflows | Internal editing capabilities not publicly visible | Proposed editorial roles, review gates, bulk migration and release controls |
| Operations | Private staff systems not observable from public pages | Illustrative role workspaces, governance and workflow interoperability roadmap |
| AI services | No verified connection inferred from public site | Optional public-knowledge assistant with approved sources and human escalation |
Implementation note: The previously submitted Nevada Health Centers WordPress proposal and contract scope remain distinct from this long-term platform vision. A public demo does not prove actual clinical integrations, HIPAA compliance or production readiness.