How yeury-dcm/medsync works
Project Type and Purpose
• This is a monolithic full‑stack ASP.NET Core MVC web application.
• It follows an Onion Architecture to manage patient data, appointments, doctors, lab tests/results, and user authentication/authorization in a medical center context.
File Structure
• Top‑level layers:
• MedSync.Core.Domain – pure business entities and enums.
• MedSync.Core.Application – use‑case services, interfaces (repositories, services), ViewModels, AutoMapper profiles.
• MedSync.Infrastructure.Persistence – EF Core DbContext, migrations, repository implementations.
• MedSync.Presentation.Web – MVC layer: Controllers, Razor Views, static assets, middleware, session management.
• Look for cross‑cutting concerns (e.g., password encryption helper, session helper, DI ServiceExtension classes).
• Configuration files: appsettings.json, launchSettings.json, .csproj files, migrations.
README for Additional Insights
• Confirms the four‑layer onion structure with responsibilities for each layer.
• Lists main features and user roles (Administrator, Assistant).
• Technologies: ASP.NET Core MVC, EF Core, SQL Server, Bootstrap/Razor UI.
Detail Without Overthinking
• 4 layers of the Onion Architecture explicitly.
• Core services (Account, Appointment, Patient, LabTest, LabResult).
• Session validation middleware and static file serving.
• Full request‑response cycle end to end.