AI Full-Stack Dev for Blood & Emergency Platform

- How should the emergency blood request workflow operate from start to finish?

- What level of AI functionality are you expecting for donor matching and analytics? Should the AI donor matching be based solely on blood type, location, eligibility, and donation history, or do you envision more advanced predictive models?

Hi Karen, what would you like the first successful delivery to prove: a stable core web platform first, or the full emergency-response layer including geolocation, AI matching, alerts, gamification and mobile support?

Before moving forward, I have a few questions to better understand the project requirements and provide the most accurate implementation plan:

Do you already have an existing Blood Bank Management System/codebase that needs to be upgraded, or will this platform be developed from scratch?
Will there be any legacy data migration requirements from the current system? If yes, what technologies are currently being used?
Could you please clarify the user roles involved (e.g., donors, hospitals, blood bank staff, administrators, delivery personnel)?
Do you already have UI/UX designs and branding guidelines available, or would you like us to handle the complete design process?
For SMS, email, and push notifications, do you have preferred service providers in mind, or should we recommend the most suitable options?
Is the optional React Native application intended only for donors, or should it support all user roles?
For the AI-powered donor matching and analytics features, do you have specific requirements or existing models/services that you would like us to integrate?
What is your preferred deployment environment (AWS, Azure, DigitalOcean, Vercel, etc.)?

These details will help us define the architecture correctly and ensure a smooth delivery aligned with your expectations.

A few questions:
1. Is the current Blood Bank Management System already built, and which tech stack is it using?
2. Do you want the React Native mobile app included from the beginning or as a later phase?
3. Will SMS notifications be handled through Twilio or do you have another provider in mind?

Thanks for sharing the roadmap. A few questions that would help clarify scope and architecture:

• What technology stack is the existing Blood Bank Management System built on, and how much of the current codebase is expected to be reused versus rebuilt?

• Is there existing production data that must be migrated, including donor records, blood inventory, requests, and historical transactions?

• Which user roles will exist at launch (donors, hospitals, blood banks, administrators, logistics personnel, etc.)?

• For geolocation-based donor discovery, do you already have mapping/provider preferences (Google Maps, Mapbox, OpenStreetMap)?

• Which channels should be supported for notifications: email, SMS, push notifications, WhatsApp, or all of them?

• How should donor eligibility be determined for emergency matching (blood type, distance, donation history, health status, availability, etc.)?

• Will the AI donor matching logic be rule-based initially, or do you envision machine learning models from the start?

• Do hospitals and blood centers require separate dashboards and permissions?

• Are there any healthcare compliance, privacy, or regulatory requirements that must be considered for the regions where the platform will operate?

• Is the React Native mobile application part of the initial delivery scope or planned as a second phase after the web platform launch?

• Do you already have UI/UX designs available, or would the frontend design and user experience need to be created as part of the project?

• What is the expected number of users, donors, and blood centers during the first year so the infrastructure can be sized appropriately?