Repository of Intervertebral Disc Patient-Specific Finite Element Models

Open data API in a single place

Provided by Zenodo

Get early access to Repository of Intervertebral Disc Patient-Specific Finite Element Models API!

Let us know and we will figure it out for you.

Dataset information

Catalog

Zenodo catalog

Country of origin

EU institutions

Updated

2026.01.08 00:00

Created

2026.01.01

Available languages

English

Keywords

finite element method, intervertebral disc, patient-specific, machine learning, morphing algorithm, patient-personalized

Datasource

Official portal for European data link

Quality scoring

Dataset description

Free-access repository of 169 patient-personalized (PP) finite element (FE) intervertebral disc (IVD) models. This cohort was generated through a morphing pipeline and released to empower the scientific community. The initiative reflects our commitment to standardization and supports a more comprehensive understanding of the mechanisms underpinning IVD degeneration. All input files are fully compatible with our coupled mechano-transport simulation subroutines, available on GitHub: https://github.com/bmmbUPF/abaqusIVD Input-file convention: .inp files with the _tr suffix correspond to the transport model; all other .inp files correspond to the mechanical simulations. Author web: https://estefano23.github.io/

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

countries and EU institutions

2019

API-first since

Free API quota

for evaluation and prototypes

SLA

history and push on production APIs

FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.

Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.

Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.

Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.

Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service