Skip to content

Near real-time clinical database for research and innovation

Notifications You must be signed in to change notification settings

SAFEHR-data/emap

Folders and files

NameName
Last commit message
Last commit date

Latest commit

f2edcbc Β· Oct 23, 2024
Oct 7, 2024
Jun 6, 2024
Oct 7, 2024
Jun 6, 2024
Apr 12, 2024
Jun 6, 2024
Apr 12, 2024
Feb 27, 2023
Oct 23, 2024
Feb 27, 2023
Apr 12, 2024
Feb 23, 2023

Repository files navigation

Emap

Experimental Medicine Application Platform (EMAP) produces a near real-time database containing clinical data for research and dashboard development within UCLH.

This is a non-operational β€œmirror” of a subset of UCLH data (historical and live). The underpinning aim is to ensure that no clinical data are corrupted or destroyed during the interaction between the research process and the hospital’s systems and that the systems are not compromised (for instance, that they are not interrupted or slowed down by research enquiries).

For more information about EMAP, please see the docs

Developer onboarding

  • How to configure IntelliJ to build emap and run tests.
  • Onboarding gives details on how data items are processed and the test strategies used.

Setup

The EMAP project follows this structure, for deploying a live instance of EMAP follow the instructions in docs/core.md.

EMAP [your root emap directory]
β”œβ”€β”€ config [config files passed to docker containers, not in any repo]
β”œβ”€β”€ hoover [different repo]
β”œβ”€β”€ emap [this repo]
β”‚   β”œβ”€β”€ emap-star         [ formerly Inform-DB repo ]
β”‚   β”œβ”€β”€ emap-interchange  [ formerly Emap-Interchange repo ]
β”‚   β”œβ”€β”€ hl7-reader        [ formerly emap-hl7-processor repo ]
β”‚   β”œβ”€β”€ core              [ formerly Emap-Core repo ]
β”‚   β”œβ”€β”€ [etc.]

Monorepo migration

How were old repos migrated into this repo?

Branching strategy

main should always be usable in production, having gone through a validation run as well as the "standard" checks of code review and GHA tests using synthetic data.

The develop branch is a pre-release branch intended to bring together one or more PRs. The standard checks are performed when merging into here, but we can delay the full validation run until we're ready to merge to main.

About

Near real-time clinical database for research and innovation

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages