Phase 25 · Global Evidence Infrastructure

Build on inspectable health evidence

The developer kit exposes public, non-personal evidence reads. It does not certify integrations, grant clinical approval, or claim that any external organization has adopted these contracts.

Discover the contracts

Dependency-free TypeScript client

The repository client covers public evidence, safety, product, standards, globalization, and observational aggregate reads. It throws on HTTP and non-JSON failures rather than returning a plausible empty answer.

import { EvidenceBasedClient } from './src/developer-kit/client';

const evidence = new EvidenceBasedClient();
const { claims, dataSource } = await evidence.listClaims({ intervention: 'magnesium' });

// Keep the live/fallback label and evidence certainty visible.
console.log(dataSource, claims[0]?.certainty);

Distribution: repository-source. No npm publication or external adoption is claimed.

Validate locally

npm run standards:validate -- claim examples/developer-kit-claim.synthetic.json 1.0.0

Verify all public integration invariants with npm run developer-kit:verify -- https://evidencebased.info.

The validator runs on the integrator’s machine and transmits no record. Schema validity does not establish scientific truth, review, publication eligibility, safety, certification, regulatory approval, laboratory testing, external adoption, or reuse permission.

Integration invariants

  • Preserve dataSource, certainty, safety qualifiers, provenance, versions, and limitations.
  • Never convert fallback data, observational outcomes, or schema validity into clinical approval.
  • Never merge evidence certainty, interaction severity, product quality, value, or personal applicability into one score.
  • Do not send personal health information to public read endpoints or the offline validator.