How axiss-groups/studentkare works
Studentkare is a student-owned health-records and campus-care platform with a React web/native client and a FastAPI service. The main user-to-result path is entering through a client route, using a care feature, and reaching backend APIs; the sampled code also shows API startup and clinical, billing, workflow, and telemetry subsystems. The README gives the product scope but few feature-flow details, and many listed modules were not sampled, so only documented or indexed relationships are drawn.
Main entry points: main.py API application · billing.py Billing service · clinical_api.py Clinical API · activity_telemetry.py Activity telemetry
Components 24
Client apps
- Web application
src/App.tsx - Native application
src/native/App.tsx - API client
src/data/api.ts - Knowledge manager
src/screens/workspace/KnowledgeManagerPanel.tsx
Care and AI
- Clinical API
backend/services/clinical_api.py - Preventive care
backend/services/preventive_care.py - Workflow models
backend/core/workflow_models.py - Agentic RAG
src/ai/engines/agenticRAGEngine.ts - AI constitution
src/ai/core/constitution.ts - Billing service
backend/services/billing.py - Billing models
backend/core/billing_models.py
Backend services
- API application
backend/app/main.py - Workflow API
backend/services/workflow_api.py - Workflow authorization
backend/services/workflow_auth.py - Activity telemetry
backend/services/activity_telemetry.py - Operations feed
backend/services/ops_feed.py - Integration config
backend/services/integration_config.py - Slack notifications
backend/services/slack_notifier.py
Platform foundations
- SQL database layer
backend/services/db_sql.py - Cross-platform storage
src/core/storage/CrossPlatformStorage.ts - Consent engine
backend/core/consent_engine.py - Backend telemetry
backend/core/telemetry.py - Demo data seeding
backend/services/demo_seed.py
Other components
- Student or staff
Connections 27
- Student or staff → Web application: uses
README.md - Student or staff → Native application: uses
README.md - Web application → API client: uses
src/App.tsx - Web application → API application: routes requests
- Native application → API client: uses
- Knowledge manager → API application: publishes source
- API application → Clinical API: mounts router
backend/app/main.py - API application → Workflow API: mounts router
backend/app/main.py - API application → Preventive care: imports service
backend/app/main.py - API application → Billing service: imports service
backend/app/main.py - API application → Activity telemetry: imports service
backend/app/main.py - API application → Backend telemetry: initializes
backend/app/main.py - API application → Demo data seeding: seeds data
backend/app/main.py - Clinical API → Activity telemetry: records activity
backend/services/clinical_api.py - Clinical API → Workflow models: uses models
backend/services/clinical_api.py - Clinical API → Workflow authorization: uses authorization
backend/services/clinical_api.py - Billing service → Billing models: uses models
backend/services/billing.py - Billing service → Operations feed: uses feed
backend/services/billing.py - Billing service → Workflow authorization: uses authorization
backend/services/billing.py - Activity telemetry → SQL database layer: persists via
backend/services/activity_telemetry.py - Activity telemetry → Workflow models: uses models
backend/services/activity_telemetry.py - Backend telemetry → SQL database layer: uses database
backend/core/telemetry.py - SQL database layer → Billing models: maps models
backend/services/db_sql.py - Agentic RAG → AI constitution: checks rules
src/ai/engines/agenticRAGEngine.ts - Knowledge manager → API client: loads resources
src/screens/workspace/KnowledgeManagerPanel.tsx - Integration config → Billing service: configures integrations
- Slack notifications → Backend telemetry: alerts on errors