Follow-up Required Flag

[Daniel-Warner-X]

As a veterinarian, I want to mark a pet’s visit with a ‘follow-up required’ flag and add a short note, so I can track which pets need further attention after a visit.

Requirements:

• A checkbox or toggle for Follow-Up Required on the visit form.
• The default behavior of the checkbox should be unchecked.
• If the checkbox is unchecked, the follow-up notes should not persist.
• A text area for Follow-Up Notes (optional unless the flag is checked).
• The character limit for the follow-up notes should be 500 characters.
• The follow-up notes should not support any special formatting.
• If 'Follow-Up Required' is checked but there are no notes, the user should get an alert asking them to add a note describing why the follow-up is needed.
• The follow-up required flag should have a visual indication on the visit record.
• The follow-up notes should be displayed in full on the visit record.
• There should not be any notifications or alerts related to the follow-up visits.
• Any logged-in user can mark a visit with 'Follow-Up Required'.
• This flag will only apply to new visits going forward.
• UAT testing is not required.
• There is no special documentation required; training will be conducted offline.
• The implementation will require a database schema change.
• The change should be completed with no perceptible impact on performance.

---

[kgilpin]

These can also be broken down into sub issues if that makes it easier to handle.

[Daniel-Warner-X]

As a veterinarian, I want to mark a pet’s visit with a ‘follow-up required’ flag and add a short note, so I can track which pets need further attention after a visit.

Requirements:

A checkbox or toggle for Follow-Up Required on the visit form.
The default behavior of the checkbox should be unchecked.
If the checkbox is unchecked, the follow-up notes should not persist.
A text area for Follow-Up Notes (optional unless the flag is checked).
The character limit for the follow-up notes should be 500 characters.
The follow-up notes should not support any special formatting.
If 'Follow-Up Required' is checked but there are no notes, the user should get an alert asking them to add a note describing why the follow-up is needed.
The follow-up required flag should have a visual indication on the visit record.
The follow-up notes should be displayed in full on the visit record.
There should not be any notifications or alerts related to the follow-up visits.
Any logged-in user can mark a visit with 'Follow-Up Required'.
This flag will only apply to new visits going forward.
UAT testing is not required.
There is no special documentation required; training will be conducted offline.
The implementation will require a database schema change.
The change should be completed with no perceptible impact on performance.

---

To efficiently break down the issue into sub-issues for three developers, we can categorize the tasks into three main areas: Frontend, Backend, and Database. Here's a suggested breakdown:

Frontend Tasks

1. Add Follow-Up Required Checkbox

   • Implement a checkbox or toggle for "Follow-Up Required" on the visit form.
   • Ensure the default behavior of the checkbox is unchecked.

2. Add Follow-Up Notes Text Area

   • Implement a text area for "Follow-Up Notes" (optional unless the flag is checked).
   • Enforce a character limit of 500 characters for the follow-up notes.
   • Ensure the follow-up notes do not support any special formatting.

3. Validation and Alerts

   • Implement validation to ensure that if "Follow-Up Required" is checked but there are no notes, the user gets an alert asking them to add a note describing why the follow-up is needed.

4. Visual Indication

   • Ensure the follow-up required flag has a visual indication on the visit record.
   • Ensure the follow-up notes are displayed in full on the visit record.

Backend Tasks

1. Update Visit Model

   • Add a boolean field for "Follow-Up Required" to the Visit model.
   • Add a text field for "Follow-Up Notes" to the Visit model.

2. Business Logic

   • Implement logic to ensure that if the checkbox is unchecked, the follow-up notes do not persist.
   • Ensure that any logged-in user can mark a visit with "Follow-Up Required".

3. API Endpoints

   • Update or create API endpoints to handle the new fields in the Visit model.
   • Ensure the follow-up required flag and notes are correctly handled in the API responses.

Database Tasks

1. Schema Changes

   • Implement the required database schema changes to add the new fields to the Visit table.
   • Ensure the changes are completed with no perceptible impact on performance.

2. Data Persistence

   • Ensure that the follow-up required flag and notes are correctly persisted in the database.
   • Implement any necessary migrations to handle existing data.

Summary

• Frontend Developer: Focus on the UI elements and validation.
• Backend Developer: Focus on the model updates, business logic, and API endpoints.
• Database Developer: Focus on the schema changes, data persistence, and visual indication on the visit record.

This breakdown ensures that each developer has a clear set of tasks that align with their expertise, and it allows for parallel development to efficiently complete the issue.