I need help
Describe a non-identifying need in ordinary language. The prototype surfaces relevant assistive-technology, navigation, research, and support pathways.
Unshaken Voice Productions · Public prototype
One doorway into Pittsburgh’s disability, health, research, and assistive-tech network.
Pittsburgh Health Connect is a PHI-free coordination prototype built around a simple premise: people should not have to understand a fragmented system before they can ask for help.
Prototype boundary: do not enter names, diagnoses, medical record numbers, insurance IDs, exact birth dates, or other protected health information. This version uses public-source organizations and client-side matching only. Inclusion does not imply partnership or endorsement.
PHI-freeNo account, patient chart, or clinical record required
Human-reviewedConsequential referrals remain subject to human confirmation
Source-linkedEvery seeded organization is tied to a public source
Pittsburgh-firstDesigned around the network described during Pittsburgh Tech Week
The system problem
Resources exist. The path between them is the missing product.
The prototype 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.
Need→Discovery→Evidence→Eligibility→Funding→Access→Follow-up
Three starting points
Start with what you need—not with the organization chart.
I need evidence or a partner
Explore public research, rehabilitation engineering, community co-design, demonstration, and statewide assistive-technology infrastructure.
I need a pathway to impact
Identify public navigation systems, disability-community connectors, and evidence partners that can help a pilot reach real people without bypassing human review.
Interactive matcher
Describe the need. The prototype finds plausible public pathways.
What are you trying to accomplish?
This browser-only demo does not submit the text to a server. Avoid PHI anyway.
Suggested pathways
Start with a plain-language need.The matcher will explain why each public resource may be relevant.
Live public data layer
Real regional signals, retrieved from public systems.
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.
Loading public sources…
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.
Medicare-registered Pittsburgh hospitals
Loading CMS Provider Data Catalog…
Pittsburgh-area clinical studies
Loading ClinicalTrials.gov…
Pittsburgh research & funding signals
Loading NIH RePORTER…
Current funding opportunities
Loading Grants.gov…
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.
Seeded Pittsburgh network
Real organizations, explicit source links, no implied partnership.
These nodes were selected because they represent distinct parts of the coordination chain: lived-experience and assistive-tech access, ecosystem connection, research, statewide device access, and public navigation.
Design review invitation
Built to be challenged by Leah, Inglis, and the disability community.
This prototype is intentionally not presented as a finished answer. The next design step is a structured review with people who already do this work: identify what is missing, where the workflow could create burden, what should remain human-led, what data should never be collected, and which closed-loop outcomes are worth tracking.