Project : DocuCare, trademark pending, is a Doctor Platform that transforms recorded medical information into concise summaries and actionable insights for both doctors and patients. The doctor is provided with immediate patient information, a summary of their past visits, real time analysis, and potential diagnosis. DocuCare aims to enhance the doctor-patient relationship through intelligent data utilization./
Team Number : 9
Team Name : NA ACQ SA
Demonstration Video : demon video Passcode: .V!r84+C)
DocuCare, trademark pending, is a Doctor-Patient Platform that transforms recorded medical information into concise summaries and actionable insights for both doctors and patients. Doctors can analyze similar symptoms across patients, while patients can ask follow-up questions based on their history, fostering efficient and informed healthcare communication. DocuCare aims to enhance the doctor-patient relationship through intelligent data utilization.
Please explain why you decided to build the application/demonstration for this project. What inspired you? What problems does it solve or how will it make Presales activities easier?
Just like Docucare shows, MongoDB’s developer data platform allows organizations to integrates all of the data services you need to build modern applications in a unified developer experience. It handles transactional workloads, full-text search, AI-enhanced experiences, stream data processing, and more, all while reducing data infrastructure sprawl and complexity!
Describe the architecture of your application and include a diagram.
Our application uses the following components:
- Atlas Database
- Atlas Full Text Search
- Atlas Vector Search
- Atlas App Services (functions, HTTP Endpoints)
- Azure OpenAI
- Kafka, Atlas Stream Processing and Time Series
Describe what you application does and how it works
- Aashish Regmi
- Role: Backend Developer
- Responsibility: write backend API endpoints, Atlas functions and HTTPS endpoints, search queries, prompt engineering with RAG
- Adlai Gordon
- Role: Front Developer
- Responsibility: react frontend development, graphic design
- Allan Schiebold
- Role: Data Engineer
- Responsibility: generate sample Data, write aggregation queries, architecture diagram, documentation, presentation slides, Charts design
- Brent Dorenkamp
- Role: Data Engineer
- Responsibility: generate sample data, video recording, documentation, presentation slides
- Clarence Ondieki
- Role: Backend Tech Lead
- Responsibility: led backend tasks planning/assignment, tech support to the team, backend API endpoints development, Atlas HTTPS endpoints, Atlas functions, full text and vector search queries, contribute to README.md
- Michael Pepe
- Role: Domain Expert, Tech Consultant
- Responsibility: architecture diagram, script generation, healthcare consulting, use case development
- Travis Williams
- Role: Frontend Tech Lead, General Coach
- Responsibility: led hackathon planning, tech support to the team, Azure openAI lead, application architecture design, react frontend development
- Yang Li
- Role: Backend Developer
- Responsibility: load data, generate embeddings, search queries, Atlas functions, contribute to README.md and architecture diagram
- Younes Berrada
- Role: Frontend and Backend Developer
- Responsibility: IoT gateway, time series, Atlas Charts, Kafka connector, Atlas Stream Processing
Demonstration script (or link to script) goes here
The demonstration script should provide all the information required for another MongoDB SA to deliver your demonstration to a prospect. This should include:
- setup/installation steps
- step by step instructions on how to give the demonstration
- key points to emphasize at each point in the demonstration
- any tear down steps required to reset the demonstration so it is ready for the next time