Home

HOLON Client

@ontomorph/holon-client is the official TypeScript client for the HOLON clinical-knowledge API. It gives you one typed client over a normalized layer that spans SNOMED CT, RxNorm, LOINC, ICD, and more.

The problem it solves

The same clinical idea (a drug, a lab test, a diagnosis) has a different code in every vocabulary. A RxNorm code for a medication does not match its SNOMED code, and neither matches the LOINC code for a related lab test. Moving a patient's data between systems means reconciling all of those codes by hand.

HOLON normalizes across vocabularies. Each idea gets a stable numeric conceptId that stays the same no matter which coding system named it first. You work with one concept instead of many codes, and the client hides the HTTP, auth, and error plumbing behind typed methods.

Why you would want it

You are building on top of clinical data and you need answers, not a coding-system reconciliation project. This client answers the recurring questions (what is this code, what does it map to, is this drug pair safe, is this lab value normal for this patient) through five typed namespaces.

What you can do

• Search concepts, resolve a vocabulary code to a concept, and walk the hierarchy up (ancestors) or down (descendants).
• Screen a drug pair or a whole medication list for known interactions.
• Translate a code from one vocabulary into another.
• Read age and sex adjusted reference ranges for lab tests, and score similarity between two sets of phenotype terms.

Quickstart

// quickstart.ts
import { createHolonClient } from "@ontomorph/holon-client";

const holon = createHolonClient({
  apiUrl: "https://holon-api.ontomorph.com",
  apiKey: process.env.HOLON_API_KEY, // holon_…
});

// Search for a drug concept.
const results = await holon.concepts.search("atorvastatin");
const atorvastatin = results.hits[0];
console.log(atorvastatin.conceptId, atorvastatin.conceptName);

Runs on Node.js 18+, Bun, Deno, and any runtime with a global fetch. See Getting-Started for install and auth.

Pages

• Getting-Started: install, authentication, and your first call.
• Concepts: the vocabulary this client speaks, and why each idea matters.
• Guides: one section per namespace, with a code example and when to use it.
• Use-Cases: four end-to-end scenarios you can copy from.
• API-Reference: every method, option, return field, and error code.
• FAQ: short answers to the common questions.