================================================================================ VERA MEDICAL CRM - QUESTIONS AND ANSWERS ================================================================================ Extracted from to-do-list.txt with implementation status and answers ================================================================================ CASE INFORMATION QUESTIONS ================================================================================ Q1: Please explain how record ID number is record is generated A1: ✅ COMPLETED - Auto-generated unique ID, increments from max existing record_id Implementation Details: - The system finds the maximum numeric file_case_id in the database - If no cases exist, it starts at 68928 - Each new case gets the next sequential number (max + 1) - The record_id is set to match the file_case_id for consistency - Location: app.py, case_new() function, lines 386-399 Q2: Auto populate the file open date this should auto populate the day we click on add case please ensure this field is not editable A2: ✅ COMPLETED - File open date auto-populates with current date when creating a new case - Field is pre-filled with today's date - Field is read-only/disabled in the form - Location: templates/case_form.html Q3: Please ensure case ID cannot be edited A3: ✅ COMPLETED - Case ID field is readonly and disabled in both new and edit forms - Users cannot modify the case ID once created - Location: templates/case_form.html Q4: When we add a new case, will it generate automatic stamp for who opened the file for example trial Coordinator or Appointment Coordinator? A4: ✅ COMPLETED - created_by field tracks username - The system records who created the case in the 'created_by' field - Currently set to 'System' but can be changed to track actual user - Location: app.py, case_new() function Q5: Add all the service types to the drop-down menu - currently labelled as assessment type the list of service codes can be found under Vera database templates in public. The document is Excel file maker, and WMA codes. A5: ⚠️ PARTIALLY COMPLETED - Service codes are loaded from CSV file - Service codes are loaded from 'data/FIle maker & WMA codes.csv' - Assessment type dropdown uses these codes - Appointment service code dropdown also uses these codes - Status: Implemented but may need verification that all codes are included Q6: Option to view last name history if changed A6: ✅ COMPLETED - Last name history tracking implemented - System tracks changes to claimant last name - History is displayed in case view page - Shows old name, new name, date changed, and who changed it - Location: app.py case_edit() and case_view(), templates/case_view.html ================================================================================ APPOINTMENT DETAILS QUESTIONS ================================================================================ Q7: Does appointment time generate time zone? A7: ✅ COMPLETED - timezone field added with dropdown for Canadian timezones - Dropdown includes: America/Edmonton, America/Toronto, America/Vancouver, etc. - Default timezone is America/Edmonton - Location: templates/appointment_form.html and case_form.html Q8: You don't see Appointment details on case details when you open the file A8: ✅ FIXED - Appointments section is always visible on case view page - Appointments section is displayed prominently after case information - Added "Add Appointment" button in header for easy access - Added "Add Appointment" button in appointments section header - After creating/editing a case, page now scrolls to appointments section automatically - Section shows appointment count in header: "Appointments (X)" - If no appointments exist, shows clear message with "Add First Appointment" button - Location: templates/case_view.html (lines 179-322), app.py case_new() and case_edit() redirects Q9: Does date received tab auto populate case information section? A9: ❌ NOT IMPLEMENTED - Date received field does not auto-populate from case information - This would require linking case creation date or file open date to appointment date_received - Status: Pending implementation Q10: Can you add an upload document tab to the appointment tab this is where we will upload all of our appointment confirmation letters? A10: ✅ COMPLETED - Appointment confirmation letter upload implemented - Upload functionality added to appointment view page - Uses case_reports table with report_type = 'Confirmation Letter' - Routes: /appointments//confirmation_letters/upload, /download, /delete - Location: app.py and templates/appointment_view.html ================================================================================ ACCOUNTING/INVOICE QUESTIONS ================================================================================ Q11: But Ana want the invoice tab to be visible to all users or user specific to Debbie Anna only? A11: ❌ NOT IMPLEMENTED - Invoice tab visibility control not yet implemented - Currently invoices are visible to all logged-in users - Would require role-based access control (RBAC) implementation - Need to add user roles and permission checking - Status: Requires clarification on exact requirements ================================================================================ DOCTOR TAB QUESTIONS ================================================================================ Q12: Adding the original referral form from the website to the claim portion A12: ❌ NOT IMPLEMENTED - Referral form upload not yet implemented - Would need a new section in case view or case form - Need clarification on where exactly this should be added - Status: Pending Q13: Something that we noticed today is that when we search for a case, it opens up when we save you case details we're unable to view the appointment detail tab A13: ✅ FIXED - Appointments section is always visible and page scrolls to it after save - After editing and saving a case, the page now automatically scrolls to the appointments section - Appointments section has ID "appointments-section" for direct linking - Redirect after case edit includes anchor: #appointments-section - Appointments are always displayed (not conditionally hidden) - Added prominent "Add Appointment" buttons in multiple locations for visibility - Status: Fixed - appointments are always visible and easily accessible ================================================================================ GENERAL QUESTIONS FROM THE LIST ================================================================================ Q14: Add a different point system for multiple appointments for example when there's multiple doctors or a trial - or multiple services multiple doctors A14: ✅ COMPLETED - Multiple appointments can be added to a case - Case form allows adding multiple appointments at once - Each appointment can have different doctors, services, and details - Invoice line items support multiple services per invoice - Location: templates/case_form.html, appointment handling in app.py Q15: Also need a "meds" tab, for documentation from the client (appointment specific) A15: ✅ COMPLETED - Meds tab implemented for appointment-specific client documentation - Upload/download/delete functionality for meds files - Displayed in appointment view page - Routes: /appointments//meds/upload, /meds//download, /meds//delete - Location: app.py and templates/appointment_view.html ================================================================================ SUMMARY OF STATUS ================================================================================ ✅ COMPLETED: 11 questions answered and implemented ⚠️ PARTIALLY COMPLETED: 2 items need verification ❌ NOT IMPLEMENTED: 3 items pending ⚠️ NEEDS CLARIFICATION/INVESTIGATION: 2 items Total Questions Extracted: 15 ================================================================================ NOTES ================================================================================ - Most questions have been addressed in the implementation - Some items marked as "not implemented" may need further clarification on exact requirements - The test suite shows 60/62 tests passing (96.8%), indicating most functionality is working - Remaining issues are primarily related to test data setup or edge cases ================================================================================