I need help
Describe a non-identifying need in ordinary language. The demonstration surfaces relevant assistive-technology, navigation, research, and support pathways.
Pittsburgh Health Connect is a data-minimized coordination demonstration built around a simple premise: people should not have to understand a fragmented system before they can ask for help. The public experience is designed not to request protected health information.
The system treats the problem as a broken chain rather than a shortage of isolated programs. A need can require service discovery, evidence, eligibility, funding, acquisition, implementation, and follow-up across multiple institutions.
Across Pittsburgh conversations about health, disability, accessibility, research, technology, and community support, the same structural problem keeps surfacing: the region has strong people, institutions, research, technology, and public resources, but the path between them is often fragmented. Pittsburgh Health Connect is a working response to that coordination gap.
The first goal is not to export a generic platform into Pittsburgh. It is to let Pittsburgh's disability community, assistive-technology professionals, researchers, health organizations, public-resource navigators, founders, and funders shape the first working network. If the model later travels, Pittsburgh remains the place where the connective architecture was first assembled and tested.
Describe a non-identifying need in ordinary language. The demonstration surfaces relevant assistive-technology, navigation, research, and support pathways.
Explore public research, rehabilitation engineering, community co-design, demonstration, and statewide assistive-technology infrastructure.
Identify public navigation systems, disability-community connectors, and evidence partners that can help a pilot reach real people through verified consent, transparent matching, and human review where required.
This browser-only demo does not submit the text to a server. Avoid PHI anyway.
This next layer turns the demonstration into a two-sided Pittsburgh network. People and families can request nonclinical resources or connections. Researchers, providers, builders, funders, navigators, community organizations, and ecosystem connectors can describe what they can offer. Matching is explainable, consent-gated, and designed to preserve human authority.
This layer is read-only and PHI-free. It brings public demographic context, Medicare-registered Pittsburgh hospitals, Pittsburgh-area clinical studies, federally funded Pittsburgh research, and current federal funding opportunities into the same coordination view. Each record keeps a direct source path.
2024 ACS disability characteristics.
Medicare-registered hospitals returned for Pittsburgh, Pennsylvania.
Pittsburgh-location study records surfaced by the live API.
Pittsburgh active research matched to disability, rehabilitation, mobility, assistive technology, or accessibility.
Posted or forecasted federal opportunities matched to assistive technology, disability, or rehabilitation.
Public data can be incomplete, delayed, or administrative rather than service-availability data. CMS hospital registration does not establish current capacity, accessibility, payer acceptance, or suitability. ClinicalTrials.gov entries do not establish eligibility. NIH awards do not imply partnership. Grants.gov opportunities require independent eligibility review. Census figures are aggregate statistics and are never used to infer disability status about an individual.
Explore the network · PHI-free public data
After the public data layer above, this interactive graph provides a spatial view of the same source-backed information: resource categories, CMS hospital records, ClinicalTrials.gov studies, NIH RePORTER projects, Grants.gov opportunities, and aggregate Census context. It visualizes structure and source coverage without creating a hospital ranking, clinical recommendation, or partnership claim.
Drag to rotate the public-data field in three dimensions, drag vertically to change the viewing angle, scroll to zoom, isolate data layers, or explode the field to separate dense clusters. Hover or select towers to inspect their public source.
Curated resource entries use neutral public labels while preserving direct source links. Some live government, hospital, study, or research records may identify institutions because that identity is part of the official source record. In every case, inclusion is data provenance only and does not mean client status, partnership, endorsement, co-design participation, or any other formal relationship with UVP.
Health Connect is being built as part of the same Pittsburgh-first connective model already explored across economic development, community-resource navigation, and human-directed problem solving. Each surface keeps its own scope and governance instead of collapsing every use case into one database or one score.
This demonstration is not presented as a finished answer. UVP welcomes structured review from disability-community members, healthcare and assistive-technology professionals, researchers, service navigators, funders, and other practitioners who can identify missing pathways, unnecessary burden, accessibility concerns, data that should never be collected, and outcomes worth tracking.