#carerequest
LightNews LightNews
donnell.bsky.social
Up this morning adding what I thought was going to be a simple expansion: letting care providers assign care requests to groups. I even created this diagram to visualize it, only to quickly realize… nothing simple about this. Yay! Looks like I’ve got my work cut out for me. 🤷🏾‍♂️🤦🏾‍♂️ #buildinpublic
UML class diagram showing relationships between key components of a care group assignment system. Includes Team, TeamGroupSettings, CareRequest, Group, CareRequestGroup, GroupAssignmentRule, GroupAssignmentValidationService, and ActivityLog classes. Lines show relationships between classes including one-to-many and many-to-many connections. Notes indicate key functionalities like historical tracking and validation rules.
November 22, 2024 at 1:56 PM
homecompanion.bsky.social
Head to our website to fill out a care request form today!

#homecompanionsolutions #home #care #companion #homeservices #homecare #chicago #illinois #inhomecare #companionship #care #aginginplace #familycare #compassionatecare #dailycare #qualitycare #seniorservices #caregiversupport #carerequest
August 14, 2026 at 4:05 PM
donnell.bsky.social
Hey 🏗️, I’m up trying to fix a bug in my ActionTokenService class. I need to invalidate and delete tokens for a previous CareRequest when it has been reassigned, but it’s not deleting or invalidating the token correctly. The reassignment itself is working fine.

#buildinpublic
This image contains a PHP function named invalidateAllUserTokens, designed to invalidate and delete user tokens associated with a specific model ($tokenable) in a Laravel application. Key elements of the code include: 1. Logging Query Parameters: The function logs user ID, tokenable type, and tokenable ID for debugging purposes. 2. Query Preparation and Logging: It builds a query to select tokens associated with the given user and model, then logs the raw SQL query and bindings. 3. Retrieving Tokens: The function retrieves all tokens that need to be invalidated and logs the token count for further debugging. 4. Clearing Cache: For each retrieved token, it clears cached values related to predefined actions such as ACTION_ACCEPT, ACTION_REJECT, ACTION_COMPLETE, etc., using cache()->forget(). 5. Deleting Tokens: Finally, it deletes the tokens from the database using a query with where conditions for tokenable_type, tokenable_id, and user_id. The function uses Laravel’s query builder, logging, and caching utilities to handle the tokens efficiently while ensuring comprehensive debugging and traceability.
December 9, 2024 at 1:37 PM
donnell.bsky.social
Coding at Costco while waiting for a tire repair. Trying to finish up this automation:

CareRequest Creation -> Automation -> CategoryGroup Action -> CareRequestCategory Condition

It seems simple, but the complexity lies in the Automation Service.

#buildinpublic
The workflow represents the process of handling a Care Request in a Care Management System: 1. Intake Phase: • The process starts with “Intake,” where a front desk enters basic information. This is shown by a dashed line leading to this step. • From “Intake,” the data is submitted to the “Router.” 2. Routing and Rules Checking: • The “Router” submits the care request and checks the “RoutingRules” table for applicable rules. 3. Assignment Actions: • A block labeled “Assignment Actions” includes: • CareRequestAssignment, which branches into several actions: • “Accept” leads to “Accepted.” • “Reject” leads to “Rejected.” • “Request Reassignment” leads to “Reassignment.” • “New” also leads to “Reassignment.” 4. Care Delivery: • After assignment is accepted, the “CareDelivery” step begins. • A dashed line indicates that “Care is provided” during this phase. 5. Care Report: • Upon completion of care delivery, the process moves to “CareReport,” which branches into: • “No Follow-up” (ends the process). • “Follow-up Requested” (leads to a “FollowUp” process). This diagram outlines a structured flow for managing care requests, from intake to routing, assignment, delivery, reporting, and potential follow-up actions.
January 13, 2025 at 4:07 PM
donnell.bsky.social
Thanks @jaredbybike.bsky.social ! I’ve spent the last two hours writing tests and checks to ensure my solution is error-free and secure. It’s been a valuable learning experience. I also added a boot function to ensure assignments are handled correctly.
This screenshot shows a CareRequest model’s boot method, which overrides the parent boot method to add custom logic for the saving lifecycle event. The key logic in the code performs validation when the user_id field changes (isDirty('user_id')) and ensures that the assigned user belongs to the same team as the care request. Detailed Description: 1. Parent Boot Call: The parent::boot() method is invoked to ensure base model behaviors are not overridden. 2. Saving Event: • A static saving event is registered to validate the user_id field when it changes. • The condition checks if user_id has been modified (isDirty) and is not null. 3. Validation Logic: • The new assignee’s record is retrieved using User::with('team')->findOrFail($careRequest->user_id). • If the new user’s team_id does not match the team_id of the CareRequest, a ValidationException is thrown with a message: “Cannot assign to user from different team.” 4. Error Handling: • If the User model for the new user_id is not found, a ModelNotFoundException is caught. • A ValidationException is then thrown with a message: “Selected user does not exist.” 5. Validation Exceptions: • The ValidationException::withMessages() method is used to provide user-friendly error messages under the user_id key. This method enforces strict validation rules for team assignments and provides detailed error messages for assignment issues or invalid user references.
December 9, 2024 at 6:43 PM
homecompanion.bsky.social
Please use the form to contact us regarding the care you are needing for yourself or a loved one. Click the link in our bio to fill it out!

#homecompanionsolutions #home #care #companion #homeservices #homecare #chicago #illinois #carerequest
June 25, 2025 at 10:02 PM