MIDOM in a web application whose primary purpose is to facilitate better communication within the medical community. It was realized using ASP .NET Core, using "WEB API "as backend, and "MVC "as frontend. One of the main challenges when developing MIDOM was a question of security, with the primary goal being uninterrupted user access. Keeping this in mind, OAuth 2.0 was chosen as the most appropriate security protocol, which focuses on separating client and authorization logic, and implementing this logic as a separate unit, realized using IdentityServer4. IdentityServer4 is available as a "nuget "package, and offers implementation of OpenID Connect, protocol build as an extension of OAuth 2.0, as well as the OAuth 2.0 itself. For IdentityServer4 to function correctly, "Config.cs "file needs to be set up first. Users can assume one of three roles: 1. Medical Specialist – Medical specialist whose primary use case consists of consulting on various study created by study providers 2. Study Provider – Person in need of a consultation, responsible for managing studies, and communication with the medical specialist 3. Admin – Person responsible for user management and various administrative tasks MIDOM also stores information about consultation requests and their status, as well as messages, logs, specializations, and studies. This is done using EF Core, an ORM, which translates C#s "LINQ quires "into SQL. In order to use WEB API, the user simply needs to call the right endpoint. For instance, sending a GET request to "ConsultationMessages/{id}. "Endpoint consists of a "controller "and an "action. " MIDOM consists of the following controllers: • "ConsultationMessagesController" • "ConsultationRequestsController", • "LogsController", • "MedicalSpecialistsController", • "SpecializationController", • "StudiesController", • "UserMangementController" All controllers have appropriate CRUD actions implemented, as well as specific actions to the controller. For testing "endpoints, "Swagger was used, which summarises all actions and allows trying said actions during development. In the future, MIDOM is expanding to mobile, which will use Xamarin.Forms to offer multiplatform "on the move "experience.