# hadeelalmajid779-sketch/lims architecture

> Architecture diagram of the GitHub repository hadeelalmajid779-sketch/lims, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-06-25). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/hadeelalmajid779-sketch/lims
- Repository: https://github.com/hadeelalmajid779-sketch/lims

## Overview

This repository is a single Django-based LIMS application: a server-rendered monolith for managing lab operations, patients, tests, and results. The README is minimal, but the project structure makes the intent clear.

1. **Top-level runtime and deployment shape**
   - `manage.py` is the Django entrypoint.
   - `backend/` is the Django project package with `settings.py`, `urls.py`, `asgi.py`, and `wsgi.py`.
   - `core/` is the main application where the business logic lives.
   - `db.sqlite3` shows the current persistence layer is SQLite, which suggests a simple deployment/local-first setup rather than a distributed backend.

2. **Main architectural boundary**
   - The codebase is split into a **project layer** (`backend`) and a **domain app layer** (`core`).
   - `backend` handles global configuration and URL aggregation.
   - `core` owns the LIMS domain: models, forms, views, templates, and app-specific URLs.

3. **Domain model focus**
   - The schema is centered on a few core clinical/lab entities:
     - **Patient**
     - **Test**
     - **PatientTest** or a similar join/assignment model
     - **TestResult**
   - The migrations include result fields like hematocrit and hemoglobin, indicating the system stores structured lab measurements rather than just free-text reports.

4. **Primary data flow**
   - Browser request enters Django through the project URL config.
   - `backend/urls.py` routes into `core/urls.py`.
   - `core/views.py` loads or mutates data through models in `core/models.py`.
   - Forms in `core/forms.py` validate user input.
   - Views render HTML templates under `core/templates/core/`.
   - Data persists to SQLite through Django ORM migrations and models.

5. **Server-rendered UI, not a separate frontend**
   - The UI is template-driven with no SPA framework present.
   - Shared layout comes from `templates/base.html`.
   - The app uses many role-specific and entity-specific templates, so the presentation layer is tightly coupled to Django views rather than a separate API/frontend split.

6. **Role-based operational screens**
   - There are dedicated dashboards for different operational roles:
     - `doctor_dashboard.html`
     - `lab_dashboard.html`
     - `reception_dashboard.html`
     - `accounting_dashboard.html`
     - `manager_dashboard.html`
   - `role_login.html` suggests role-aware entry or role selection.
   - This indicates the app is organized around staff workflows and permissions, not just generic CRUD.

7. **Workflow-oriented CRUD subsystem**
   - Each core entity has list/detail/form/delete templates, which suggests standard administrative workflows:
     - Patients: list, detail, form, confirm delete
     - Tests: list, detail, form, confirm delete
     - Patient tests: list, detail, form, confirm delete
     - Test results: list, detail, create, form, confirm delete, print
   - `testresult_print.html` shows the app supports printable lab outputs, which is a distinct operational path from normal browsing/editing.

8. **Shared context and request enrichment**
   - `core/context_processors.py` implies some UI state or role/session-derived data is injected globally into templates.
   - This typically supports dashboard navigation, role-aware menus, or session-based display logic across many pages.

9. **Administration and back-office access**
   - `core/admin.py` registers models with Django admin, meaning there is an alternate administrative boundary outside the custom dashboards.
   - The presence of `staticfiles/admin/` shows Django’s admin assets are included/collected, reinforcing that admin is part of the operational surface.

10. **Persistence and schema evolution**
   - `core/migrations/` contains the initial schema plus later result-field changes.
   - That indicates the data model evolved from a core patient/test structure into a richer result schema.
   - The database is currently a single local SQLite file, so the architecture is one shared datastore rather than per-service storage.

11. **Static asset boundary**
   - `staticfiles/` contains collected admin CSS/JS/images.
   - There is no obvious custom frontend build pipeline, bundler, or client-side app structure.
   - Static serving is therefore likely simple and Django-native.

12. **What is not present**
   - No evidence of microservices, message queues, background workers, REST API packages, or external integrations.
   - No separate frontend app or mobile client.
   - No third-party infrastructure components are visible beyond standard Django and SQLite.

13. **Best mental model for an architecture diagram**
   - Draw one Django web application boundary.
   - Inside it, show:
     - configuration/routing (`backend`)
     - domain logic (`core`)
     - server-rendered templates
     - Django admin
   - Outside it, show a single SQLite database as the persistence layer.
   - Use role-based user groups as the main interaction paths into shared patient/test/result data.

Main entry points: [`core/views.py`](https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/views.py) (Views), [`templates/base.html`](https://github.com/hadeelalmajid779-sketch/lims/blob/main/templates/base.html) (Base layout), [`core/models.py`](https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/models.py) (Models), [`backend/settings.py`](https://github.com/hadeelalmajid779-sketch/lims/blob/main/backend/settings.py) (Settings)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_group_runtime["Django runtime"]
  node_node_manage["manage.py<br/>entrypoint<br/>[manage.py]"]
  node_node_backend_settings["Settings<br/>config<br/>[settings.py]"]
  node_node_backend_urls["Project URLs<br/>router<br/>[urls.py]"]
  node_node_backend_asgi["ASGI<br/>server<br/>[asgi.py]"]
  node_node_backend_wsgi["WSGI<br/>server<br/>[wsgi.py]"]
end

subgraph group_group_domain["Core domain"]
  node_node_core_models[("Models<br/>domain model<br/>[models.py]")]
  node_node_core_forms["Forms<br/>validation<br/>[forms.py]"]
  node_node_core_views["Views<br/>request handlers<br/>[views.py]"]
  node_node_core_urls["App URLs<br/>router<br/>[urls.py]"]
  node_node_context["Context"]
  node_node_admin["Admin<br/>back-office<br/>[admin.py]"]
end

subgraph group_group_ui["Server UI"]
  node_node_templates_base["Base layout<br/>template layout<br/>[base.html]"]
  node_node_templates_dash["Role dashboards<br/>templates<br/>[dashboard.html]"]
  node_node_templates_crud["CRUD screens<br/>templates<br/>[patient_list.html]"]
  node_node_templates_print["Print view<br/>template"]
  node_node_static_admin["Admin assets<br/>static assets<br/>[base.css]"]
end

subgraph group_group_data["Data store"]
  node_node_db[("SQLite DB<br/>persistence<br/>[db.sqlite3]")]
  node_node_migrations["Migrations<br/>schema evolution<br/>[0001_initial.py]"]
end

node_node_manage -->|"loads"| node_node_backend_settings
node_node_manage -->|"runs"| node_node_backend_urls
node_node_backend_asgi -->|"configures"| node_node_backend_settings
node_node_backend_wsgi -->|"configures"| node_node_backend_settings
node_node_backend_urls -->|"routes to"| node_node_core_urls
node_node_core_urls -->|"dispatches"| node_node_core_views
node_node_core_views -->|"validates with"| node_node_core_forms
node_node_core_views -->|"reads/writes"| node_node_core_models
node_node_core_views -->|"renders"| node_node_templates_dash
node_node_core_views -->|"renders"| node_node_templates_crud
node_node_core_views -->|"renders"| node_node_templates_print
node_node_context -->|"injects into"| node_node_templates_base
node_node_core_views -->|"uses"| node_node_context
node_node_admin -->|"registers"| node_node_core_models
node_node_core_models -->|"evolves via"| node_node_migrations
node_node_migrations -->|"persists to"| node_node_db
node_node_core_models -->|"stores in"| node_node_db
node_node_templates_base -->|"shared by"| node_node_templates_dash
node_node_templates_base -->|"shared by"| node_node_templates_crud
node_node_templates_base -->|"shared by"| node_node_templates_print
node_node_static_admin -->|"supports"| node_node_admin

click node_node_manage "https://github.com/hadeelalmajid779-sketch/lims/blob/main/manage.py"
click node_node_backend_settings "https://github.com/hadeelalmajid779-sketch/lims/blob/main/backend/settings.py"
click node_node_backend_urls "https://github.com/hadeelalmajid779-sketch/lims/blob/main/backend/urls.py"
click node_node_backend_asgi "https://github.com/hadeelalmajid779-sketch/lims/blob/main/backend/asgi.py"
click node_node_backend_wsgi "https://github.com/hadeelalmajid779-sketch/lims/blob/main/backend/wsgi.py"
click node_node_core_models "https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/models.py"
click node_node_core_forms "https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/forms.py"
click node_node_core_views "https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/views.py"
click node_node_core_urls "https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/urls.py"
click node_node_context "https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/context_processors.py"
click node_node_admin "https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/admin.py"
click node_node_templates_base "https://github.com/hadeelalmajid779-sketch/lims/blob/main/templates/base.html"
click node_node_templates_dash "https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/templates/core/dashboard.html"
click node_node_templates_crud "https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/templates/core/patient_list.html"
click node_node_templates_print "https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/templates/core/testresult_print.html"
click node_node_db "https://github.com/hadeelalmajid779-sketch/lims/blob/main/db.sqlite3"
click node_node_migrations "https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/migrations/0001_initial.py"
click node_node_static_admin "https://github.com/hadeelalmajid779-sketch/lims/blob/main/staticfiles/admin/css/base.css"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_node_manage,node_node_backend_settings,node_node_backend_urls,node_node_backend_asgi,node_node_backend_wsgi toneBlue
class node_node_core_models,node_node_core_forms,node_node_core_views,node_node_core_urls,node_node_context,node_node_admin toneAmber
class node_node_templates_base,node_node_templates_dash,node_node_templates_crud,node_node_templates_print,node_node_static_admin toneMint
class node_node_db,node_node_migrations toneRose
```

## Components

### Django runtime

Project entrypoint, configuration, and request routing.

- [manage.py](https://github.com/hadeelalmajid779-sketch/lims/blob/main/manage.py): entrypoint · Django command entrypoint. · `manage.py`
- [Settings](https://github.com/hadeelalmajid779-sketch/lims/blob/main/backend/settings.py): config · Project-wide Django settings. · `backend/settings.py`
- [Project URLs](https://github.com/hadeelalmajid779-sketch/lims/blob/main/backend/urls.py): router · Top-level URL configuration for the project. · `backend/urls.py`
- [ASGI](https://github.com/hadeelalmajid779-sketch/lims/blob/main/backend/asgi.py): server · ASGI application bootstrap. · `backend/asgi.py`
- [WSGI](https://github.com/hadeelalmajid779-sketch/lims/blob/main/backend/wsgi.py): server · WSGI application bootstrap. · `backend/wsgi.py`

### Core domain

LIMS business logic, forms, views, and data model.

- [Models](https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/models.py): domain model · Patient, test, assignment, and result entities. · `core/models.py`
- [Forms](https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/forms.py): validation · Input validation and form handling. · `core/forms.py`
- [Views](https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/views.py): request handlers · Workflow and CRUD handlers for LIMS operations. · `core/views.py`
- [App URLs](https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/urls.py): router · Core app route definitions. · `core/urls.py`
- [Context](https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/context_processors.py): template context · Global template context enrichment. · `core/context_processors.py`
- [Admin](https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/admin.py): back-office · Django admin registrations for models. · `core/admin.py`

### Server UI

Template-driven screens and dashboards rendered by Django.

- [Base layout](https://github.com/hadeelalmajid779-sketch/lims/blob/main/templates/base.html): template layout · Shared HTML shell for server-rendered pages. · `templates/base.html`
- [Role dashboards](https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/templates/core/dashboard.html): templates · Doctor, lab, reception, accounting, and manager screens. · `core/templates/core/dashboard.html`
- [CRUD screens](https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/templates/core/patient_list.html): templates · Patient, test, assignment, and result list/detail/form pages. · `core/templates/core/patient_list.html`
- [Print view](https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/templates/core/testresult_print.html): template · Printable test result output. · `core/templates/core/testresult_print.html`
- [Admin assets](https://github.com/hadeelalmajid779-sketch/lims/blob/main/staticfiles/admin/css/base.css): static assets · Collected Django admin CSS, JS, and images. · `staticfiles/admin/css/base.css`

### Data store

Persistent database and schema evolution.

- [SQLite DB](https://github.com/hadeelalmajid779-sketch/lims/blob/main/db.sqlite3): persistence · Single-file application database. · `db.sqlite3`
- [Migrations](https://github.com/hadeelalmajid779-sketch/lims/blob/main/core/migrations/0001_initial.py): schema evolution · Initial schema and later test result field changes. · `core/migrations/0001_initial.py`

## Connections

- manage.py → Settings: loads · Django management uses project settings.
- manage.py → Project URLs: runs · Management commands operate within the configured project.
- ASGI → Settings: configures · ASGI bootstrap uses project settings.
- WSGI → Settings: configures · WSGI bootstrap uses project settings.
- Project URLs → App URLs: routes to · Project URL config delegates into the core app routes.
- App URLs → Views: dispatches · App routes map to view handlers.
- Views → Forms: validates with · Views use forms for user input validation.
- Views → Models: reads/writes · Views coordinate domain data through models.
- Views → Role dashboards: renders · Role-specific workflows render dashboard templates.
- Views → CRUD screens: renders · CRUD workflows render entity templates.
- Views → Print view: renders · Result printing uses a dedicated template.
- Context → Base layout: injects into · Global context supports shared layout and navigation.
- Views → Context: uses · Views rely on shared context data for template rendering.
- Admin → Models: registers · Models are exposed through Django admin.
- Models → Migrations: evolves via · Schema changes are captured in migrations.
- Migrations → SQLite DB: persists to · Migrations materialize the SQLite schema.
- Models → SQLite DB: stores in · ORM-managed data is persisted in SQLite.
- Base layout → Role dashboards: shared by · Dashboards extend the shared base layout.
- Base layout → CRUD screens: shared by · CRUD pages extend the shared base layout.
- Base layout → Print view: shared by · Printable output uses the common layout shell.
- Admin assets → Admin: supports · Collected assets back the Django admin surface.