Friday Connection 03-15-24

Kevin discussed an update to their automation system, including a main event multi-branch and the addition of a description and tag for easier identification and management of automations. He also mentioned an update to their Cerbo Woocommerce ecommerce system that integrates with a new application point of sale by Woocommerce. Furthermore, Kevin talked about continuing demonstrations, introducing new automations and workflows to enhance their main event, and adding conditional tags to their community template for form automations. Lastly, he discussed the development of a new patient data system trigger and the potential for conditional logic with admin oversight in lab order creation.

Summary

Automation System and Cerbo Woocommerce Updates

Kevin announced a significant update to their automation system, specifically the implementation of a main event multi-branch. This update allows for the copying, updating, and addition of new conditions to the system, enabling the filtering and creation of different types of orders. Kevin also mentioned the addition of a description and a tag to the system for easier identification and management of automations. Furthermore, Kevin introduced an update to their Cerbo Woocommerce ecommerce system that integrates with a new application point of sale by Woocommerce. This update allows for automatic addition of products to a patient's cart, manipulation of the cart from Cerbo, and automatic loading of cart items into the POS system when a patient walks up to the POS.

Automation and Workflow Enhancements for Main Event

Kevin discussed the continuation of demonstrations and the introduction of new automations and workflows to enhance their main event. He explained the process of removing conditional tags from different form submissions using the automator. Kevin outlined the creation of two automations to add and remove tags respectively, which will be made public in their community template area. He further demonstrated the process of editing an existing automation to make it stronger and more efficient, using the example of adding a tag when a schedule is created. Kevin ended the conversation by saving changes and suggesting a suitable place for the newly created automation.

Form Automation and Tagging Process Discussion

Kevin discussed the process of adding conditional tags to their community template for form automations. He highlighted the need to remove a tag when a form is submitted and add a signed version of the tag. Kevin also explained the process of creating a multi-branch version of this event in their document system, Cerbo. This involves updating filters, adding conditions, and pasting subtrees to maintain consistency and structure. He emphasized the importance of tagging for visibility and that they plan to add labels for better organization.

Template Uploading and Automation Editing

Kevin discussed the process of uploading a template to a community template area and creating a new category called Main Event Multi branch. He proposed a system to easily identify the last edited automation. Kevin also experimented with editing the name of a trigger to 'document created' to see if it would affect all sub-events. The results were successful, suggesting the potential to rapidly create all main event multi branches.

Editing Main Event and Automation Implementation

Kevin discussed the process of editing the main event, and how it necessitates updating each sub-branch and node to call the new data appropriately. Kevin and his staff decided to create a new main event and explore its application. They also discussed implementing automation for when a document is created to assign appropriate tags. Kevin decided to assign this task to the customer support team for further learning and practice. He suggested creating default templates for every Cerbo event and pushing them to the entire community. Kevin also emphasized the importance of maintaining the same metadata fields for consistent pulling.

New Patient Data System Trigger Development

Kevin discussed the development of a new patient data system trigger, but decided against including state tags for better organization. He stressed the importance of not assuming the filter used by staff and emphasized the goal of creating a community template. Kevin also discussed the potential for conditional logic with admin oversight in lab order creation and demonstrated new automation features in their software. He highlighted the importance of real-time data syncing and mentioned a new software connection to their e-commerce platform for WooCommerce. The conversation ended with Kevin expressing gratitude for those who attended.