Clinical study data and analytics

Your whole study, in one workspace.

Limora brings a study's CRFs, SDTM and ADaM datasets, documents and outputs together, so your team can browse them, discuss them and ask an AI assistant that shows its work.

Illustration of the Chat tab, using synthetic data.

Built for the files a study already has

  • CRF data
  • SDTM
  • ADaM
  • define.xml
  • Lab data
  • Protocols and SAPs
  • TFL outputs

How it works

From a folder of files to answers your team can check

Each study gets its own workspace. Four steps take it from raw files to shared understanding.

  1. Organize

    Group files by source, such as EDC, SDTM, ADaM, lab and documents. Each data cut is kept as its own version.

  2. Explore

    Browse forms, the visit schedule, datasets and documents in tabs made for clinical data, with subject filters throughout.

  3. Collaborate

    Attach notes and issues to the exact form, field, row or document page they are about.

  4. Ask

    Put a question to the assistant in plain language. It writes Python, runs it on the study's data and shows you both.

Features

Everything a study team needs to review data together

An assistant that shows its work

Ask about enrolment, adverse events or anything else in the data. The assistant runs real code against your study and returns the tables and charts along with the code that made them, so a statistician can check every step.

  • Code shown with every answer
  • Runs in an isolated sandbox
  • Every conversation kept

Data cuts, kept in order

Every upload is a new revision with its own checksum. Nothing is overwritten, and each person chooses which cut they are looking at.

Compare versions side by side

Open any dataset, filter to the subjects you care about and switch on compare mode to see what changed between cuts.

Search inside documents

Protocols, SAPs and annotated CRFs are searchable page by page, next to the data they describe.

Notes and issues in context

Raise a question on a single record or page. Everyone sees it right where the data is, not in a separate spreadsheet.

Blinding respected

Unblinded content needs its own grant. Without it, those files, records and search results stay hidden, whatever a person's role.

Security and control

Built for regulated work

Limora was designed for clinical study data from the first line of code.

  • Your own AWS account

    Each customer runs in a separate AWS account, with its own database and storage.

  • Nothing is deleted

    Records are retired or superseded, never removed, and every file revision is kept.

  • A complete audit trail

    Changes to membership, roles, unblinding and records are written to an append-only log.

  • Access by study

    People see only the studies they belong to, as a viewer, collaborator or owner.

  • A contained assistant

    Assistant code runs in a sandbox with read-only, short-lived access to one study.

  • Strong sign-in

    Every sign-in needs an emailed code, and sessions end after 30 minutes of inactivity.

Limora is a workspace for exploratory review. It holds a convenience copy of your study data, never the authoritative record, and results should be validated in your own systems.

See Limora with your own study

We'll walk you through the workspace and answer your team's questions.

Request a demo