Participant and Staff Sections

In this week’s session we take a closer look at the Participant and Staff Sections in FlowLogic, giving you practical tips to better navigate, manage and utilise these core areas of the system.

• Participant Data
  • Basic Information
  • Goals
  • Funding
  • Service Agreements
  • Documentation
  • Communication
  • Health
  • Incidents

• Staff Data
  • Basic Information
  • Documentation
  • Communication

• User Management
  • Logon Details
  • Security
  • Pay Rate
  • Availability

• Flow Logic Overview: Daniel provided an overview of Flow Logic, focusing on how it stores data for staff and participants, and offering tips on using the system effectively.
  • Flow Logic Introduction: Daniel introduced Flow Logic, explaining its purpose in storing data for staff and participants. He emphasized the system’s flexibility and customization options to meet different organizational needs.
  • Data Storage: Daniel detailed how Flow Logic stores data for staff and participants, including basic details, goals, funding allocations, and service agreements. He highlighted the importance of accurate data entry for smooth operations.
  • User Management: Daniel briefly mentioned the importance of user management within Flow Logic, ensuring that user accounts are correctly linked to staff records for data security and accurate reporting.
    
    
• Participant Data: Daniel explained the importance of accurately entering participant data, including first name, last name, date of birth, and NDIS number, to ensure smooth operations and compliance.
  • Basic Information: Daniel emphasized the need to accurately enter participant data, such as first name, last name, date of birth, and NDIS number. He explained that this information is crucial for compliance and smooth operations within Flow Logic.
  • Data Accuracy: Daniel highlighted the importance of ensuring data accuracy, particularly the NDIS number, as it is essential for interactions with the NDIA and for tracking participant services and funding.
    
    
• Goals and Case Notes: Daniel emphasized the importance of recording participants’ goals and linking them to case notes to track progress and provide evidence for audits.
  • Recording Goals: Daniel discussed the importance of recording participants’ goals in Flow Logic. He explained that goals should be documented as they appear in the NDIS plan or as defined by the organization.
  • Linking to Case Notes: Daniel explained how linking goals to case notes helps track progress and provides evidence for audits. He suggested including a dropdown in shift notes to indicate if any goals were worked towards during a shift.
    
    
• Funding Allocations: Daniel discussed the significance of funding allocations in Flow Logic, explaining how they track spending and determine the source of funds for services provided.
  • Importance of Funding Allocations: Daniel explained that funding allocations are crucial for tracking participant spending and determining the source of funds for services provided. He emphasized the need to accurately enter this data to ensure proper financial management.
  • Tracking and Reporting: Daniel highlighted that funding allocations allow organizations to track spending against participants’ budgets and generate reports. He mentioned the use of graphs and history tracking within Flow Logic to monitor financial data.
    
    
• Service Agreements: Daniel highlighted the various ways to create and store service agreements in Flow Logic, including electronic signatures and document uploads.
  
  
• Document Storage: Daniel explained the importance of storing documents related to participants, such as service agreements, risk assessments, and care plans, in Flow Logic for easy access and compliance.
  
  
• Incident Reporting: Daniel discussed the process of recording incidents involving participants or staff members in Flow Logic, emphasizing the importance of documentation for legal and auditing purposes.
  
  
• Participant Needs: Daniel explained how to record participants’ specific needs, such as manual handling or peg feeding, in Flow Logic to ensure proper rostering and service provision.
  
  
• Staff Data: Daniel provided an overview of staff data in Flow Logic, including basic details, probity documents, and skills, to ensure compliance and efficient rostering.
  • Basic Staff Details: Daniel explained the importance of entering basic staff details, such as first name, last name, phone number, and email address, in Flow Logic. He mentioned that this information is essential for rostering and compliance.
  • Probity Documents: Daniel highlighted the need to store probity documents, such as first aid certificates and police checks, in Flow Logic. He explained that this ensures staff members are legally able to provide services and helps with auditing.
  • Staff Skills: Daniel discussed the importance of recording staff skills, such as manual handling or food handling, in Flow Logic. He explained that this information is used to match staff with participant needs during rostering.
    
    
• User Accounts: Daniel explained the difference between staff records and user accounts in Flow Logic, emphasizing the importance of linking user accounts to staff records for data security and accurate reporting.
  • Staff Records vs. User Accounts: Daniel explained that staff records and user accounts serve different purposes in Flow Logic. Staff records store all data related to staff members for legal and auditing purposes, while user accounts control access to the system.
  • Linking Accounts: Daniel emphasized the importance of linking user accounts to staff records to ensure data security and accurate reporting. He explained that this linkage allows for proper tracking of staff activities and compliance with legal requirements.
    
    
• Staff Availability: Daniel highlighted the importance of staff members setting their availability in Flow Logic to ensure accurate rostering and efficient operations.
  
  
• Payroll Categories: Daniel discussed the significance of selecting the correct payroll category for staff members in Flow Logic to ensure accurate timesheet exports and financial reporting.