OHDSI / OHDSI/Data2Evidence

Documentation and technical improvements

Open
#369 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
43
Forks
12
Avg merge
4d 10h
Merged PRs (30d)
92

Description

This issue tracks ongoing technical improvements to the Data2Evidence (D2E) platform to ensure it remains robust, maintainable, and adaptable to evolving needs. The planned work focuses on general modernization of the technology stack, deployment and infrastructure enhancements, expanded database support, backend optimization, and comprehensive documentation updates. By addressing these areas, D2E will provide a more secure, performant, and user-friendly experience for both end users and contributors.

Key focus areas include:

  • Modernizing the technology stack through regular upgrades of libraries, frameworks, and core components across the frontend and backend, ensuring improved security, performance, and long-term maintainability.

  • Enhancing deployment and infrastructure options (e.g., Kubernetes support via Helm charts) for more scalable and reproducible platform operation.

  • Expanding multi-database support—including BigQuery integration, flexible execution strategies, and the ability to add proprietary database drivers—to accommodate a wider range of research and enterprise requirements.

  • Unifying and optimizing backend service APIs and workflows for greater efficiency and consistency (e.g., aligning concept search clients and evaluating Trex SQL for Hades execution).

  • Improving and expanding user, developer, API, and administrative documentation to streamline onboarding, system administration, and integration efforts.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by inventorying the existing deployment, database, backend API, frontend, and documentation areas against the listed focus areas, then split the work into scoped changes. Done requires separately verifiable modernization, infrastructure, database, API, and documentation improvements.

Written by the indexing model from the issue text.

Assessment

Tech stack
google-cloud, helm, kubernetes, typescript
Domain
api, backend, databases, devops, documentation, frontend, infrastructure
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.