Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Iomed website screenshot

Iomed

IOMED is a Barcelona-based health-tech company operating a Data Space Platform that gives hospitals and life-science companies secure, GDPR-compliant access to real-world clinical data for secondary use and research. Using AI and natural language processing, IOMED transforms free-text electronic health records into structured, coded data standardized on the OMOP Common Data Model, then exposes it through a federated EU network of hospital partners. Platform capabilities include feasibility patient counts, aggregated patient characterization, patient-level data extraction, and a patient finder for clinical-trial recruitment. IOMED is ISO 27001:2022, ISO 27701:2019, and ISO 9001:2015 certified, and is backed by Speedinvest, Adara Ventures, XTX Markets, and Philips Ventures. This profile is maintained in the API Evangelist network; IOMED does not currently publish a public developer API.

human only

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles Iomed the way a machine reads it — 2 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Iomed scores 22.3/100 (emerging), with a separate agent-readiness read of 4/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 22.3/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 0.9 / 20
Commercial Clarity 7.4 / 20
Operational Transparency 2.1 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Regulatory · Health 7.8 / 15
Agent readiness — 4/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3

How we profile Iomed

Each block below is one kind of artifact we hold for Iomed. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Iomed Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Iomed Trust Center

ISO 27001:2022, ISO 27701:2019, ISO 9001:2015

SECURITY

Resources

Every other property we hold for Iomed — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/iomed · machine-readable index on apis.io