Responsibility & architecture
Technical Lead across professional education and the platform modules for medical representatives and directors.
Constraints
Educational content, professional interactions and team workflows have different release stages and should not be presented as equally available.
Separate client and server data concerns
React, TypeScript and TanStack Query organize client-side data access; Express modules handle backend operations.
Engineering tradeoff: A client cache improves data coordination in the interface, but server authorization remains authoritative.
Modular document-oriented backend
MongoDB and Mongoose underpin modules for content, interactions, representatives and directors.
Engineering tradeoff: Document flexibility still requires clear validation and lifecycle rules, especially as related modules evolve.
Architecture overview based on implementation scope. The tradeoffs describe engineering considerations, not measured outcomes.
Delivery context
Professional education is presented publicly as a pilot. Medical-representative preparation and director dashboards are described as in development. Repository modules do not establish a public release.
The challenge
Scientific content, professional education and field visits often sit in separate workflows. MedGalaxis connects these experiences so healthcare professionals, medical representatives and marketing teams can work from a shared context.
Technical scope
I lead the technical work on MedGalaxis. The React and TypeScript frontend uses Vite and TanStack Query; a Node.js/Express API uses MongoDB through Mongoose. Backend modules separate educational content, professional interactions, medical-representative tools and director dashboards.
Platform scope
Healthcare-professional education is available in pilot. Visit-preparation assistance for medical representatives and management dashboards are in development.