Case study · continuing medical education
MedUS: long-term development of a medical education platform
Development and long-term technical support for MedUS: product structure, frontend and backend work, integrations, controlled releases, and improvements after launch.
Case study by Bohdan Rykush, independent web developer and owner of Bohdan Rykush Softwareentwicklung in Germany.
Product and UX structure, frontend, backend, data flows, and integrations.
Planned releases with testing, deployment checks, and attention to regressions.
Long-term support after launch: maintenance, fixes, and new functionality.
MEDICAL UKRAINIAN SCHOOL («MedUS») operates the continuing medical education platform at med-us.com.ua.
What the MedUS engagement covers
- Product and UX structure, frontend, backend, data flows, and integrations.
- Planned releases with testing, deployment checks, and attention to regressions.
- Long-term support after launch: maintenance, fixes, and new functionality.
Public client reference: MedUS
MEDICAL UKRAINIAN SCHOOL («MedUS») operates the continuing medical education platform at med-us.com.ua.
I help develop and maintain the platform's core technical path, deliver changes through controlled releases, and provide long-term support so the MedUS team can focus on its education work.
- Public, working platform for continuing medical education.
- Multi-year technical support, maintenance, and iterative improvement.
What is public and what remains confidential
MedUS is a public client reference, while implementation details and other client projects may be protected by confidentiality agreements.
This page separates verifiable information from confidential work. You can open the live MedUS platform and verify the client entity; the technical plan below explains the type of work without exposing private systems, data, or contract details.
How a similar platform project can run
This public reference shows how I support a working web platform beyond its first launch.
- Product structure, frontend, backend, data, and integrations
- Testing, infrastructure, and controlled releases
- Maintenance and further development after launch
See a typical platform delivery plan
A similar platform engagement starts with business and user needs, then moves through architecture, implementation, launch, and support. The exact scope is agreed after a technical brief.
Typical starting points
A team may need to launch a new platform in stages, extend an existing system safely, or replace a fragile release process with a maintainable one.
Priorities for a maintainable platform
- Architecture that can accommodate new users, features, and integrations.
- Clear product layers for the interface, APIs, data, access rules, and background work.
- Planned releases with checks, monitoring, and a repeatable deployment path.
- Performance and technical SEO on public pages where discovery and sign-up matter.
A phased delivery plan
Work proceeds in phases. A typical plan includes:
- Discovery: users, business rules, existing constraints, scope, and milestones.
- Architecture: data, access boundaries, integrations, interface structure, and deployment approach.
- Implementation: product logic, database work, integrations, frontend, and backend.
- Launch: testing, cloud configuration, automated deployment, logging, and monitoring basics.
- Support: fixes, updates, and new features delivered without losing system clarity.
Technical capabilities
- Responsive public pages and an authenticated user account
- Server-side rules for access, purchases, tests, results, and certificates
- Data storage for users, learning content, questions, orders, and progress
- Payment and external-service integrations
- Deployment, logging, monitoring, and release support
Verified reference and delivery outcomes
- MedUS is available as a live public platform at med-us.com.ua.
- The client entity and contact details can be verified on this page.
- The engagement includes multi-year technical support and ongoing platform development.
- Changes follow a planned path from task and testing to release and follow-up.
Need a similar education or business platform?
Describe the users, core workflows, current system, and preferred timeline. I will respond with clarifying questions and a realistic next step.