obscyro
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.

Edition
SNOMED IE Feb 2026
Translate
ICD-10 · ICD-O · CTV3
Phase
Public beta
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.

Normalize

Turn raw clinical text into standard codes.

Translate

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

Expand

Navigate clinical hierarchies semantically.

Disambiguate

Pick the right code with context.

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
Obscyro API
normalize · translate · expandvalidate · disambiguate
Normalized output
SNOMED 22298006ICD-10 I21.9preferredTerm + hierarchy

Architecture

One layered pipeline, every record.

Each request flows through the same four layers — from raw text to a fully coded, context-aware result you can trust.

01
Intake

Ingest & normalize

Accept clinical text or structured payloads over REST and webhooks, then normalize encoding, language, and casing.

02
Semantics

Concept & context extraction

NER spans are embedded and matched against SNOMED with pgvector cosine + margin, then enriched with assertion, subject, and certainty.

03
Decision

Route by confidence

Per-destination rules accept, flag, or escalate each concept using resolution status and context confidence.

04
Output

Translate & emit

Cross-map SNOMED to ICD-10, ICD-O, or CTV3 and emit an enriched, coded result ready for your system.

Pricing

Simple, predictable, healthcare-friendly.

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

Most popular

Free

$0forever

Build prototypes and explore the API surface.

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

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.