Public healthcare intelligence should be usable by default.

Healthcare has public data, but not public intelligence. Open-Informatics turns scattered records into tools, profiles, and publishing infrastructure that agents and people can actually use.

Explore the portfolioView GitHub
Built for trust and use

The intelligence stack.

Four reinforcing surfaces turn public records into judgment, evidence, reference work, and distribution.

Featured project

Healthcare Agents routes operating questions to specialist workups.

A Codex-oriented bench of healthcare administration specialists with active GitHub development, reviewed releases, and open contribution paths for healthcare operators and builders.

  1. RouteSelect the right administration specialist.
  2. Work upFrame context, evidence needs, constraints, and risks.
  3. Hand offReturn a structured workup for human review.

Administrative operating questions

  • Capacity
  • Revenue cycle
  • Compliance
  • Quality and safety
  • Health IT
  • Strategy
41GitHub stars
8forks
v1.5.0latest release
1k+total downloads
Contribute on GitHub
BetaHealthcare Data MCP

The connector layer for the scattered public healthcare record.

Public healthcare data is everywhere and nowhere: CMS files, price transparency disclosures, research registries, sanctions lists, provider identifiers, grant databases, contract records, quality programs, demographic context, and market geography.

Healthcare Data MCP is a FastMCP toolkit that turns those sources into callable tools with structured responses, source metadata, bounded caches, and deployment modes for local agents or shared local processes.

PythonFastMCPLocal agentsShared processStructured responsesSource metadataBounded cache
  • Current beta release: 18 MCP servers and 100+ callable tools.
  • Designed for agent workflows that need sourced retrieval instead of hand-waved healthcare claims.
  • Provenance stays visible because public healthcare data is incomplete, messy, and frequently delayed.
18MCP servers
100+callable tools
v0.4.0latest release
sourcemetadata carried
cachebounded behavior
traceevidence first
Contribute on GitHub
DATA CONNECTOR COVERAGEPublic sources normalized for agent calls.

Tool responses carry source metadata, bounded cache behavior, and structured outputs instead of unsupported healthcare claims.

CMS and facility dataNPPES, quality, safety, star ratings.
Price and claims contextRates, volumes, service lines, case mix.
Public recordsSAM.gov, CHPL, 340B, breaches, exclusions.
Research and trialsNIH RePORTER, ClinicalTrials.gov profiles.
Market geographyDrive times, service areas, Census context.
Referral networksPhysician flows, leakage, network mapping.
REPOSITORY SIGNALBeta codebase, regularly updated and seeking contributors.
  • 6stars
  • 2forks
  • 0open issues
BuildingUnited States Health Systems Observatory

The largest encyclopedia of comparative U.S. health system data.

USHSO is the synthesis layer: a living reference library that compares health systems as organizations, competitors, employers, capital allocators, care delivery networks, and public institutions.

Each report is designed to combine audited filings, CMS quality data, price transparency signals, service-line volumes, market geography, referral behavior, leadership changes, M&A activity, strategy, and public commitments into a single defensible profile.

System profilesAudited filingsCMS qualityMarket geographyReferral behaviorLeadership changesStudent access
  • The goal is breadth and depth: system-by-system intelligence that students, operators, researchers, founders, journalists, and communities can actually use.
  • Early coverage is intentionally narrow while the report format and data pipeline harden; Jefferson Health and Temple Health are the first visible examples.
  • Student access is free. The commercial model exists to fund maintenance without hiding the methodology.
2visible examples
HBSFoundry accepted
Freestudent access
Sourcemethodology-first
Paidsupport model
Review evidence posture
PROFILE DOSSIERComparative system intelligence with visible methodology.

Reports are meant to read like living dossiers: financial evidence, care quality, market position, and strategic movement in one place.

Financial performanceMargins, cash, debt, payer mix, capital allocation.
Quality and outcomesHCAHPS, readmissions, safety, star ratings.
Market positionShare, service areas, volumes, competitors.
Strategic directionLeadership, M&A, partnerships, expansion.
EARLY COVERAGE
Jefferson HealthTemple HealthReport format hardeningData pipeline hardening
LiveAmerican Journal of Healthcare Strategy

Open-access healthcare strategy needs serious publishing operations.

AJHCS is the public distribution partner in the portfolio: a journal, media platform, and knowledge institution built around open access to healthcare strategy, leadership, and management thought.

Open-Informatics supports organizations like AJHCS with website publishing, ranking, bookstore infrastructure, discoverability, and digital operations. That matters because open knowledge fails when the publishing layer looks amateur, fragile, or invisible.

Open accessPodcastingBookstoreReportsSearchNewsletterInstitutional reach
  • AJHCS gives the portfolio a public venue for evidence-based essays, interviews, reports, podcasts, and practical healthcare strategy writing.
  • The operating model keeps credible healthcare knowledge easier to publish and easier to find while sponsored infrastructure funds hardening.
  • Publishing reach compounds over time; the site is treated as infrastructure, not a campaign.
13K+subscribers
1M+monthly web views
200+podcast episodes
Visit AJHCS
PUBLISHING OPERATIONSOpen healthcare strategy moves through a durable distribution stack.

AJHCS is treated as live infrastructure: publishing, packaging, and audience channels are supported as one operating surface.

AJHCS.org homepage preview
Live AJHCS.org publishing surface: editorial homepage, bookstore, podcast library, search, newsletter, and institutional distribution paths.
PublishEssays, interviews, reports, podcasts.
PackageBookstore, reports, feeds, archives.
DistributeSearch, social, newsletter, institutions.
MeasureAudience reach, library depth, discovery.

Impressive is not the same thing as inflated.

The portfolio is ambitious because the problem is large. The claims stay concrete: working repositories, visible publishing infrastructure, specific data sources, defined agent domains, and an explicit admission that public healthcare data is imperfect.

Source-first.

Agents should be pushed toward public evidence, citations, and data retrieval instead of confident unsupported summaries.

Open where possible.

The tools and publishing infrastructure are designed to expand access, not create another closed advisory moat.

Competitive by design.

The end state is a market where more people can compare health systems, challenge assumptions, and build better healthcare organizations.

Token unlock

Give us tokens, and we turn them into public infrastructure.

Compute is the bottleneck, not imagination. The portfolio already has agents, public-data tooling, system profiles, and distribution; token support lets that surface area compound faster without closing it off.

CoverageWith token support, public-data connectors and health-system profiles can expand from narrow early coverage into a repeatable national map.
AgentsWith token support, specialist workups can run more evidence retrieval, comparisons, and quality checks before human review.
DistributionWith token support, publishing, search, and contributor review can move faster while the core infrastructure stays open.