https://github.com/vemarahub/gerimedica_appointments
Backend Service for Gerimedica appointment app
https://github.com/vemarahub/gerimedica_appointments
Last synced: 8 months ago
JSON representation
Backend Service for Gerimedica appointment app
- Host: GitHub
- URL: https://github.com/vemarahub/gerimedica_appointments
- Owner: vemarahub
- Created: 2025-02-08T22:05:10.000Z (8 months ago)
- Default Branch: main
- Last Pushed: 2025-02-08T23:02:47.000Z (8 months ago)
- Last Synced: 2025-02-08T23:25:13.470Z (8 months ago)
- Language: Java
- Size: 16.6 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Gerimedica Assignment
Welcome to this **Gerimedica** repository. This is a **Spring Boot** project built for an **assignment**. The code, while functional, **is not production-ready** and **may contain questionable or non-ideal implementations**. Part of the challenge is to **discover**, **review**, and **improve** these elements.
---
## What to Expect
- A **simple** REST API for managing `Patients` and their `Appointments`.
- Multiple classes (controllers, services, entities, and repositories).
- **Incomplete** or **inefficient** approaches to certain tasks.
---
## Glossary
Below are the primary entities you’ll find in this codebase:
1. **Patient**
- Represents an individual in the hospital system.
- Fields may include:
- `id`: auto-generated primary key
- `name`: name of the patient
- `ssn`: Social Security Number (used here as a unique identifier)
- `appointments`: a list of `Appointment` objects linked to this patient
2. **Appointment**
- Represents a scheduled appointment or event for a patient.
- Fields may include:
- `id`: auto-generated primary key
- `reason`: a textual reason for the appointment (e.g., “Checkup”)
- `date`: the date of the appointment
- `patient`: a reference to the `Patient` who owns this appointment
---
## Goals
1. **Explore the codebase**: Familiarize yourself with the structure and logic.
2. **Identify potential issues**: Think about security, performance, maintainability, design patterns, etc.
3. **Propose and/or implement improvements**: Refactor, rewrite, or reorganize parts of the code to showcase your approach.
---