Veratech for Health

VeraTech for Health S.L. is a Spanish semantic-interoperability consultancy and health-data tooling vendor, founded in 2010 in Valencia as a spin-off of the Biomedical Informatics group (IBIME) at the Universitat Politecnica de Valencia and based at BIOHUB VLC. It helps hospitals, regional health services and research networks make clinical data comprehensible and reusable, combining advisory work, an interoperability office model and applied innovation (NLP, knowledge graphs, machine learning) with its own LinkEHR Interoperability Platform. LinkEHR is a set of desktop and server tools for authoring clinical information models as archetypes and normalizing legacy clinical data into openEHR, ISO/EN 13606, HL7 CDA, HL7 FHIR, OMOP CDM and CDISC ODM. Veratech is an official openEHR training provider for CatSalut, is EHDEN-accredited for OMOP CDM mapping, and works on SNOMED CT adoption in the Spanish national health system. It publishes no public developer program, no API and no machine-readable contract; its software is distributed as downloadable builds and commercially licensed modules sold through direct contact.

Veratech for Health is profiled on the APIs.io network. Tagged areas include Company, Healthcare, Health Data, Semantic Interoperability, and openEHR.

Veratech for Health’s developer surface includes pricing, documentation, support, engineering blog, changelog, and 17 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

19.2/100 emerging ▬ flat Agent 3/100 human only Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemium

0 APIs

Company Healthcare Health DataSemantic InteroperabilityopenEHR FHIRISO 13606SNOMED CTOMOP CDMClinical Data Electronic Health Records Consulting Spain

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 19.2/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 1.8 / 17

Access Clarity 6.3 / 17

Operational Transparency 1.7 / 11

Contract Governance 1.9 / 10

Discoverability 4.7 / 9

Regulatory Posture 1.8 / 15

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

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 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/veratech/"><img src="https://apis.io/badge/veratech/card.svg" alt="Veratech for Health on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes

12 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 10.7 — up to +17.9 composite points
Access Clarity scores 36.8 — up to +12.6 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/veratech/apis.yml: open an issue on github.com/api-evangelist/veratech to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

HL7 FHIR

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

openEHR

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

Veratech for Health API pricing

Prices published by Veratech for Health. A free plan or tier is listed.

Plan	Price
LinkEHR Studio (free)	Free
LinkEHR Interoperability Platform (commercial modules)	—

Plan details, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

Veratech Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Veratech Rate Limits

0 limits

RATE LIMITS

Security Posture 1

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

Veratech Domain Security

DMARC

SECURITY

Resources

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

Manual

Manual

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Lifecycle

Lifecycle

Conformance

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

Packages

Packages

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 4

Status, limits, changes, and where to get help

RateLimits

Support

Contact

ChangeLog

Commercial 4

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

Plans

Company 5

The organization behind the API

Website

Website

Blog

Blog

Careers

Careers

LinkedIn

Twitter

Twitter

Other 2

Properties that don't map to a standard resource type

Download

Download

CookiePolicy

CookiePolicy

Source (apis.yml)

aid: veratech
name: Veratech for Health
description: VeraTech for Health S.L. is a Spanish semantic-interoperability consultancy and health-data tooling vendor, founded
  in 2010 in Valencia as a spin-off of the Biomedical Informatics group (IBIME) at the Universitat Politecnica de Valencia
  and based at BIOHUB VLC. It helps hospitals, regional health services and research networks make clinical data comprehensible
  and reusable, combining advisory work, an interoperability office model and applied innovation (NLP, knowledge graphs, machine
  learning) with its own LinkEHR Interoperability Platform. LinkEHR is a set of desktop and server tools for authoring clinical
  information models as archetypes and normalizing legacy clinical data into openEHR, ISO/EN 13606, HL7 CDA, HL7 FHIR, OMOP
  CDM and CDISC ODM. Veratech is an official openEHR training provider for CatSalut, is EHDEN-accredited for OMOP CDM mapping,
  and works on SNOMED CT adoption in the Spanish national health system. It publishes no public developer program, no API
  and no machine-readable contract; its software is distributed as downloadable builds and commercially licensed modules sold
  through direct contact.
url: https://raw.githubusercontent.com/api-evangelist/veratech/refs/heads/main/apis.yml
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: medium
  probe_state: none
  source:
  - plans
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
image: https://www.veratech.es/wp-content/uploads/2025/03/VT_15Aniversario-negativo.png
x-type: company
x-source: harvest:openehr-coalition
specificationVersion: '0.20'
created: '2026-09-02'
modified: '2026-09-02'
tags:
- Company
- Healthcare
- Health Data
- Semantic Interoperability
- openEHR
- FHIR
- ISO 13606
- SNOMED CT
- OMOP CDM
- Clinical Data
- Electronic Health Records
- Consulting
- Spain
tags_raw:
- Company
- Healthcare
- Health Data
- Semantic Interoperability
- openEHR
- HL7 FHIR
- ISO 13606
- SNOMED CT
- OMOP CDM
- Clinical Data
- Electronic Health Records
- Consulting
- Spain
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: RateLimits
  url: rate-limits/veratech-rate-limits.yml
- type: Pricing
  url: https://linkehr.veratech.es/getlinkehr.html
- type: Website
  url: https://veratech.es/
- type: Documentation
  url: https://linkehr.veratech.es/modules.html
- type: Manual
  url: https://linkehr.veratech.es/data/LinkEHRStudioManual.pdf
- type: Download
  url: https://linkehr.veratech.es/getlinkehr.html
- type: Support
  url: http://help.veratech.es
- type: Blog
  url: https://veratech.es/noticias/
- type: Contact
  url: https://veratech.es/hablemos/
- type: Careers
  url: https://veratech.es/trabaja-con-nosotros/
- type: TermsOfService
  url: https://veratech.es/aviso-legal/
- type: PrivacyPolicy
  url: https://veratech.es/politica-privacidad/
- type: CookiePolicy
  url: https://veratech.es/cookies/
- type: LinkedIn
  url: https://www.linkedin.com/company/veratech-for-health/
- type: Twitter
  url: https://twitter.com/veratech
- type: ChangeLog
  url: changelog/veratech-changelog.yml
- type: Lifecycle
  url: lifecycle/veratech-lifecycle.yml
- type: Packages
  url: packages/veratech-packages.yml
- type: Plans
  url: plans/veratech-plans-pricing.yml
- type: Conformance
  url: conformance/veratech-conformance.yml
- type: LLMsTxt
  url: llms/veratech-llms.txt
- type: DomainSecurity
  url: security/veratech-domain-security.yml
x-enrichment:
  date: '2026-09-02'
  status: minimal
  artifacts_added: 9
  pass: local-v1
x-coverage:
  state: none
  reason: no-developer-program
  detail: VeraTech for Health sells consulting plus the LinkEHR desktop/server tooling and has no developer program at all
    — full contract discovery across every company-controlled host found no OpenAPI, GraphQL, MCP, WSDL or AsyncAPI, no /.well-known/
    document, no SDK in any public registry and no GitHub organization; the only machine-readable file the company serves
    is a Yoast-generated /llms.txt, and its live openEHR-to-FHIR transformer at openehr2fhir.veratech.es is a browser-only
    app with no documented endpoint.
  evidence:
  - url: https://veratech.es/openapi.json
    status: 404
  - url: https://linkehr.veratech.es/openapi.json
    status: 404
  - url: https://openehr2fhir.veratech.es/openehr2fhir/v3/api-docs
    status: 404
  - url: https://veratech.es/.well-known/api-catalog
    status: 404
  - url: https://veratech.es/.well-known/agent-card.json
    status: 404
  - url: https://registry.npmjs.org/linkehr
    status: 404
  - url: https://veratech.es/llms.txt
    status: 200
  checked: '2026-09-02'

Veratech for Health API — frequently asked questions

How much does the Veratech for Health API cost?

APIs.io lists 2 pricing plans for Veratech for Health, with each plan's price, limits and inclusions under Pricing on this page.

Is the Veratech for Health API ready for AI agents?

Veratech for Health has a Kin Score of 19.2 out of 100 (emerging) and an Agent Readiness score of 2.5 (human-only), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/veratech"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/veratech/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/veratech/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.