Patient IO
Patient IO (legal entity Filament Labs, Inc.) was an Austin, Texas care coordination and patient engagement platform founded in 2013 by Jason Bornhorst, Colin Anawaty, and Brian Gambs out of the Techstars Austin accelerator. Its API-first mobile platform connected health systems with patients between visits to support the transition to value-based care. athenahealth acquired Patient IO in August 2016 and its architecture became the foundation of athenahealth's patient-facing athenawell application. The standalone product, developer program, and public API surface have since been retired; patientio.com now serves only a placeholder page and its mail is handled by athenahealth.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
Patient IO is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Patient IO scores 5.7/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
Resources
Every other property we hold for Patient IO — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Company 1
The organization behind the API
Patient IO is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/patient-io · machine-readable index on apis.io