Beta· Test phase — feedback welcome at obscyro-team@obscyro.com

Health data, finally fluent.

SNOMED-first semantic API with ICD-10 mapping via /v1/translate. RxNorm, LOINC, FHIR, and HL7 integration guides are on the roadmap.

Get API key Read the docs

Edition: SNOMED IE Feb 2026
Translate: ICD-10 · ICD-O · CTV3
Phase: Public beta

POST /v1/normalizebash

curl -X POST https://api.obscyro.com/v1/normalize \
  -H "Authorization: Bearer obs_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "text": "patient presented with acute MI",
    "limit": 3
  }'

↓ response

200 OKjson

{
  "matches": [
    {
      "code": "22298006",
      "term": "Myocardial infarction",
      "conceptName": "Myocardial infarction",
      "confidence": 0.94,
      "matchType": "fts"
    }
  ]
}

POST /v1/normalizebash

curl -X POST https://api.obscyro.com/v1/normalize \
  -H "Authorization: Bearer obs_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "text": "patient presented with acute MI",
    "limit": 3
  }'

POST /v1/normalizeAuthorization: Bearer obs_live_…

What you can do

Five primitives. Endless integrations.

Compose them like Lego to fix the interoperability layer of your product, all in pure HTTP.

Validate

Verify any medical code in milliseconds.

{
  "code": "22298006",
  "active": true,
  "preferredTerm": "Myocardial infarction"
}

Normalize

Turn raw clinical text into standard codes.

{
  "text": "patient with acute MI",
  "matches": [{"code":"22298006","confidence":0.94}]
}

Translate

SNOMED ↔ ICD-10, ICD-O, and CTV3 via /v1/translate.

{
  "from": "snomed", "to": "icd10",
  "translations": [{"source":"22298006","target":"I21.9"}]
}

Expand

Navigate clinical hierarchies semantically.

GET /v1/concepts/22298006/descendants
=> 247 SNOMED codes

Disambiguate

Pick the right code with context.

{
  "winner":{"code":"22298006","preferredTerm":"Myocardial infarction"},
  "contextSimilarity": 0.81
}

The interop tax

Healthcare data doesn't speak one language.

Different systems, same data, different codes

Hospitals use SNOMED. Insurers use ICD-10. Labs use LOINC. Pharmacies use RxNorm. Every integration becomes a translation problem.

Manual mapping costs $300K+ per integration

Hand-curated cross-walks burn six-figure budgets and months of clinical-informaticist time before a single record flows.

Built once, breaks at every standards update

Yearly SNOMED, ICD-10, and FHIR releases ship breaking changes. Static mappings rot the moment you stop maintaining them.

Obscyro in one diagram

Raw clinical input

"pt with acute MI"SNOMED 22298006ICD-10: I21.9

"pt with acute MI"
SNOMED 22298006
ICD-10: I21.9

Obscyro API

normalize · translate · expandvalidate · disambiguate

normalize · translate · expand
validate · disambiguate

Normalized output

SNOMED 22298006ICD-10 I21.9preferredTerm + hierarchy

SNOMED 22298006
ICD-10 I21.9
preferredTerm + hierarchy

Pricing

Simple, predictable, healthcare-friendly.

No per-record fees. No hidden integration costs. Pay for the calls you make.

Free

$0forever

Build prototypes and explore the API surface.

1,000 calls / month
100 req/min rate limit
All endpoints unlocked
Community support

Start free

Starter

Pro

Free

$0forever

Build prototypes and explore the API surface.

1,000 calls / month
100 req/min rate limit
All endpoints unlocked
Community support

Start free

Starter

Pro

Free

$0forever

Build prototypes and explore the API surface.

1,000 calls / month
100 req/min rate limit
All endpoints unlocked
Community support

Start free

Starter

Pro

During the public test phase, only the Free plan is available.

Need higher volume, dedicated tenancy, or BAA? Enterprise: custom pricing — contact us.

Start building in minutes.

Mint your API key, copy a curl, ship coded data the same afternoon.

Get your API key