ONE-OMICS, S.L. presents

Clinical truth, structured.

One-Me turns narrative clinical reports into IECC — Structured, Coded & Curated Reports: traceable, auditable and interoperable data, ready for care, management and research.

From chaos to data Scattered strokes and dots representing free text flow into an ordered grid of connected nodes, labelled with clinical ontology codes such as SNOMED CT, LOINC and FHIR. SNOMED CT LOINC RadLex ICD-10 HPO FHIR R4 ATC

The problem

Clinical data is trapped in free text.

Around 80 % of clinical information is generated as unstructured narrative. Readable for a clinician; invisible to a system.

No structure, no comparability

Two reports that say the same thing cannot be cross-referenced, aggregated or measured. Every document is an island.

No coding, no audit

What is not coded cannot be verified, traced or defended before an auditor or a regulator.

No curation, no science

Reproducible research demands data validated at source, not text interpreted after the fact.

The standard

IECC: a Structured, Coded & Curated Report.

Every clinical report becomes a structured data object, coded with official ontologies and curated by a physician. The result rests on five pillars.

Traceability

Full chain of custody with a hash seal: origin, transformations and the owner of every data point, end to end.

Auditability

An immutable record of every action: who did what, when and to which report. Ready for inspection.

Verifiability

SHA-256 hash and ontological completeness per report: any third party can check the integrity of the data.

Security

Encryption in transit and at rest, RBAC and per-user data confinement. Everyone sees only what they should.

Interoperability

FHIR R4, HL7 and OMOP out of the box. Data is born ready to flow into any system.

How it works

From narrative to verified data, in three steps.

  1. Structure

    Specialty-specific clinical templates turn the narrative into discrete fields: element, value, unit and context. Nothing stays buried in a paragraph.

  2. Code

    Each concept is linked to its official ontology. Seven standard vocabularies, one common language.

    • SNOMED CT
    • RadLex
    • LOINC
    • ICD-10
    • HPO
    • HGNC
    • ATC
  3. Curate

    AI proposes; the physician validates. No data is final without human validation. Clinical judgement always has the last word.

The platform, in numbers

100,000+ studies structured by radiologists
200,000+ patients managed
7 official ontologies
3 export standards

Figures from the platform in production.

Modules

Genuinely multi-specialty.

Every discipline, held to the same standard. No inherited hierarchies, no second-class modules.

Medical imaging

Radiology findings structured and coded, study by study, each with its specialty template.

Laboratory

Lab results normalised with LOINC, comparable across centres and over time.

Pathology

Biopsies, immunohistochemistry and molecular pathology with reference templates and sample traceability.

Diseases

Coded diagnostic history per patient and per cohort, aligned with ICD-10 and SNOMED CT.

Treatments

Therapy lines and drugs coded with ATC, with longitudinal analysis by active substance.

Biomarkers

Molecular and genetic markers (HGNC, HPO) integrated into the patient's history.

Advanced & semantic search

Cohorts by combined clinical criteria and similarity search across the whole corpus.

Research notebooks

DataBook · PaperBook · InsightBook: from curated data to publishable evidence, with verifiable citations.

Interoperability

Data is born ready to leave.

Open standards out of the box. No endless integration projects, no proprietary formats.

FHIR R4

DiagnosticReport, Patient and ImagingStudy ready to integrate with any modern hospital information system.

HL7 v2.x

Compatible with the hospital messaging deployed today in most centres.

OMOP CDM v5.4

The OHDSI community common model: multi-centre studies and Real-World Evidence without re-mapping.

REST API / OpenAPI

An open, documented specification to build on One-Me with guarantees and no surprises.

Security & compliance

Built to safeguard health data.

The special category of Article 9 GDPR demands more than good intentions. It demands architecture.

  • Infrastructure on Azure, Spain region Data residency on national territory (Spain Central).
  • TLS in transit and AES-256 at rest Cryptographic protection at every layer.
  • RBAC with per-user data confinement Each user accesses only their own perimeter.
  • Multi-factor authentication (MFA) Reinforced identity for every access.
  • Immutable audit trail with SHA-256 hash Tamper-evident activity log.
  • HMAC pseudonymisation of identifiers Two levels: reversible for care, irreversible for research.
  • GDPR, Article 9 Processing of special categories of data in line with European and Spanish law.

Who it's for

Where clinical data decides.

Health insurers

A population-level view of clinical activity with coded, comparable and auditable data across providers.

Hospital groups

A single data standard for every centre and every specialty in the group.

Public health services

Traceability, transparency and regulatory compliance out of the box, ready for inspection.

Teleradiology

Structured, coded reports inside the reading workflow itself, with no friction for the radiologist.

Clinical research (RWE)

Reproducible cohorts and OMOP export for real-world evidence with methodological guarantees.

Contact

Let's talk.

If your organisation manages clinical data, it is worth seeing it structured. One conversation is enough to scope it.

No forms. No cookies. We talk directly.