Software & Backend
Healthcare Portal UI Prototype
An MVC and Razor interface prototype showing healthcare landing pages, doctor-dashboard navigation and registration/login layouts, with incomplete server-side functionality.
Original code-generated category illustration; not a product screenshot.
Overview
This ASP.NET Core MVC project preserves healthcare-themed page layouts and doctor-dashboard navigation. Controllers, models, Razor views and static assets are present in the source. It targets net6.0; data/business layers and production authentication are not implemented. It is evaluated as a presentation prototype rather than a patient-management system.
My role: MVC interface-prototype work preserved in the repository. A healthcare organization, real-user deployment or team role is not verified by the sources.
Core components
- Healthcare landing-page layout.
- Doctor-dashboard page and separate dashboard layout.
- Registration/login interface layouts.
- MVC separation of controllers and views.
Validation and current status
- Source and project structure were reviewed; dotnet restore/build/run were not run in the audit environment.
- There is no shared automated test suite.
- The open PR contains documentation changes only.
- Registration does not create secure accounts; verified identity and persistence are absent.
- .NET 6 is unsupported; deployment requires a separate migration and tests.
- Use with real patient records or hospital services has not been verified.
Show additional technical details
Problem and objectives
A healthcare portal needs exploration of landing-page, registration and doctor-workspace layouts. This interface study must remain distinct from server responsibilities such as secure account creation, authorization and patient-record processing, none of which follows merely from displaying the relevant pages.
Solution approach
Controller actions serve Razor pages, while shared layouts and static resources provide consistent presentation. The landing page’s doctor-panel action is prototype navigation. The open documentation PR explains the backend boundary and historical runtime without presenting missing authentication or persistence behavior as implemented.
Architecture flow
- Program.cs configures MVC and static-file serving.
- Controller actions for landing pages, doctor dashboard and registration.
- Razor views and shared layouts.
- Local model placeholders and wwwroot static assets.
Technical challenges
- Moving from the unsupported net6.0 target to a verified runtime.
- The gap between authentication middleware and missing service configuration.
- Clearly separating interface navigation from real authorization.
Engineering decisions
- The project is labeled as an interface prototype.
- Framework migration and a real backend are separate changes requiring tests.
- The portfolio uses only synthetic interface content.
Outcomes
- A preserved presentation prototype demonstrating MVC page layouts.
- No working healthcare backend or successful current build is claimed.
The technical account also draws on documentation in the open improvement PR. This does not imply that the PR has been merged or the product released.