Validate
Verify any medical code in milliseconds.
SNOMED-first semantic API with ICD-10 mapping via /v1/translate. RxNorm, LOINC, FHIR, and HL7 integration guides are on the roadmap.
What you can do
Compose them like Lego to fix the interoperability layer of your product, all in pure HTTP.
Verify any medical code in milliseconds.
Turn raw clinical text into standard codes.
SNOMED ↔ ICD-10, ICD-O, and CTV3 via /v1/translate.
Navigate clinical hierarchies semantically.
Pick the right code with context.
The interop tax
Hospitals use SNOMED. Insurers use ICD-10. Labs use LOINC. Pharmacies use RxNorm. Every integration becomes a translation problem.
Hand-curated cross-walks burn six-figure budgets and months of clinical-informaticist time before a single record flows.
Yearly SNOMED, ICD-10, and FHIR releases ship breaking changes. Static mappings rot the moment you stop maintaining them.
Obscyro in one diagram
Architecture
Each request flows through the same four layers — from raw text to a fully coded, context-aware result you can trust.
Accept clinical text or structured payloads over REST and webhooks, then normalize encoding, language, and casing.
NER spans are embedded and matched against SNOMED with pgvector cosine + margin, then enriched with assertion, subject, and certainty.
Per-destination rules accept, flag, or escalate each concept using resolution status and context confidence.
Cross-map SNOMED to ICD-10, ICD-O, or CTV3 and emit an enriched, coded result ready for your system.
Pricing
No per-record fees. No hidden integration costs. Pay for the calls you make.
Build prototypes and explore the API surface.
During the public test phase, only the Free plan is available.
Need higher volume, dedicated tenancy, or BAA? Enterprise: custom pricing — contact us.
Mint your API key, copy a curl, ship coded data the same afternoon.