Hospital System

A 2024 academic Windows Forms project exploring patient, doctor and secretary workflows with C#, .NET Framework, ADO.NET and SQL Server.

Archive Notice

Repository status: Source archive. This repository preserves code excerpts, a SQL Server schema and privacy-safe interface evidence from the original 2024 academic build. The original Visual Studio solution, project, Designer and resource files are not currently included, so the application cannot be built directly from this repository.

Public code excerpts and visual evidence in the current tree have been sanitized to remove personal identifiers, local machine names and example personal data. Placeholder values are used where the original archive contained environment-specific information.

View the complete portfolio case study · Visit the portfolio

Project Overview

Hospital System is an individual academic desktop-software project developed in 2024 for a Visual Programming course. It demonstrates multi-form navigation, database-backed credential checks, appointment-slot workflows and CRUD operations across patient, doctor and secretary interfaces.

The project is preserved as technical evidence of the original implementation rather than as a currently runnable software release.

Portfolio Case Study

The complete Hospital System portfolio case study presents the project context, verified workflow, interface evidence and technical reflection in a dedicated format.

The broader portfolio is available at kaanbalci.com.

Verified Scope

The archive provides evidence for:

• 15 Windows Forms covering patient, doctor and secretary interfaces
• Multi-form navigation between role-specific workflows
• Database-backed registration and credential checks
• Appointment-slot creation, filtering and assignment
• Doctor, branch and announcement management
• SQL-backed create, read, update and delete operations
• Direct ADO.NET access from form event handlers

User Roles

Patient

• Registration
• Database credential check
• Profile editing
• Branch and doctor selection
• Available appointment filtering
• Appointment booking
• Appointment-list viewing

Doctor

• Database credential check
• Profile information
• Assigned appointment listing
• Complaint-detail viewing
• Announcement access
• Profile editing

Secretary

• Database credential check
• Appointment-slot creation
• Doctor management
• Branch management
• Announcement creation
• Full appointment-list viewing

Role separation is implemented through dedicated forms and database credential checks, not through a centralized authorization framework.

Appointment Workflow

Secretary
→ selects date, time, branch and doctor
→ creates an available appointment row

Patient
→ filters available appointments by branch and doctor
→ selects a row with RandevuDurum = 0
→ associates the appointment with patient and complaint information

Doctor
→ views appointment rows associated with the doctor
→ inspects the selected appointment detail

Technology Stack

• C#
• .NET Framework
• Windows Forms
• SQL Server
• ADO.NET
• System.Data.SqlClient
• DataGridView
• SQL CRUD operations

Repository Contents

• 17 archived C# code excerpts stored as .txt, including 15 form implementations
• SQL Server schema-only export
• Five privacy-safe interface and database evidence images
• README documentation

Legacy screenshots and PDFs containing personal identifiers, example records or local environment details are intentionally excluded from the current tree.

The original solution, project, source, Designer, resource, application-configuration and build-output files are not currently part of this archive.

Database Model

The archived SQL Server schema includes:

• Tbl_Hastalar
• Tbl_Doktorlar
• Tbl_Sekreter
• Tbl_Branslar
• Tbl_Randevular
• Tbl_Duyurular

The archived schema stores patients, doctors, secretaries, branches, appointment slots and announcements. Forms access the database directly through ADO.NET commands and adapters.

Documented schema boundaries:

• Date and time values are stored as strings.
• Doctor and branch relationships are represented mainly through text values.
• Patient association uses a TC-style identifier string.
• The archived schema does not include a complete PK/FK/unique/check constraint structure.
• RandevuDurum uses a default value of 0.

Interface Evidence

The following privacy-safe derivatives preserve interface evidence without exposing the identifiers, names, complaint text, passwords or local server name visible in removed legacy screenshots.

Patient appointment workflow

Patient interface for filtering available slots and associating an appointment with patient and complaint information.

Secretary operations panel

Secretary interface for creating appointment slots and opening doctor, branch, appointment and announcement tools.

Doctor appointment view

Doctor interface for reviewing assigned appointment rows and opening appointment details.

SQL Server appointment schema

Archived Tbl_Randevular column structure with the local server identifier removed.

Patient registration form

Patient registration interface with empty input fields.

Known Technical Limitations

This project reflects my development level and learning goals in 2024. The following limitations are documented to keep the archive technically accurate and to identify clear areas for a future rebuild.

• The original Visual Studio solution and project files are not currently included.
• Runtime behavior cannot be reverified from the archived repository alone.
• UI, business and database logic are primarily combined inside form event handlers.
• Passwords are stored and compared as plain text in the archived implementation.
• A centralized authorization layer is not implemented.
• Some SQL filters use string concatenation.
• Connection lifecycle management is incomplete.
• Exception handling and transactions are not implemented.
• Appointment cancellation and rescheduling are not included.
• Database constraints and relationships are limited.

Security & Privacy Notice

This repository is an academic archive and must not be used for real patient or healthcare data.

• Do not use real personal information.
• Do not use the archived password model in production.
• Do not treat the screenshots as production healthcare records.
• Environment-specific connection information uses the YOUR_SQL_SERVER placeholder.
• No healthcare compliance or security certification is claimed.
• The project is not affiliated with or deployed by a hospital.

Original Project Context

• Year: 2024
• Format: Individual academic project
• Course context: Visual Programming
• Main learning areas:
  • Event-driven C#
  • Multi-form navigation
  • Windows Forms UI
  • ADO.NET
  • SQL Server
  • CRUD operations
  • Role-specific workflows

The project was created as coursework and does not claim an official relationship with a hospital or university.

Future Restoration Path

A future restoration would require:

1. Recovering the original .sln and .csproj
2. Restoring .cs, Designer and .resx files
3. Confirming the target .NET Framework version
4. Moving the connection string into local configuration
5. Rebuilding the SQL setup process
6. Replacing plain-text password handling
7. Adding PK/FK and data-integrity constraints
8. Introducing exception and transaction handling
9. Separating UI and data-access responsibilities
10. Adding tests and a reproducible setup

Contact

• Portfolio: https://kaanbalci.com/
• Case study: https://kaanbalci.com/hospital-system-case-study.html
• LinkedIn: https://www.linkedin.com/in/balcikaan/
• GitHub: https://github.com/UAJOP
• Email: kaanb8776@gmail.com