Alex Burns
Certified Salesforce Administrator
About Alex
Alexander Burns is a dynamic Salesforce Certified Administrator with a degree in criminal justice and computer forensics. His unique experience in the medical field has sharpened his problem-solving skills, making him adept at navigating the complexities of Salesforce. Passionate about the platform’s potential, Alexander tackles each challenge with enthusiasm and is actively advancing towards becoming a Salesforce Architect. His journey is a testament to his dedication and love for innovation in customer relationship management.
Purpose:
My demo org is a recreation of as much of the software I used to work with while I was a pharmacy tech as I could make in Salesforce. This includes a database of over 9,000 Drug NDCs, imported using Dataloader, a prescription fill path, a pharmacist approval process, patient person accounts, provider contacts, and provider office accounts. While some aspects of the previous software cannot be replicated such as insurance billing, I aimed to leverage chatter as one of the core problems of pharmacy work was communicating issues with prescriptions and ensuring they were followed up on additionally making tasks, activities, and cases invaluable CRM tools as these would at best be handled with a whiteboard in my experience. If I were to continue development of the demo org, many of the features I would like to add would likely need to be connected to external systems such as creating an inventory system off the back of an ERP/SAP server with POS connected. However, I am happy with it as this project brought me through flows, apex triggers, sales paths, global actions, validation rules, page layouts, search layouts, and just about everything else I could think of in Salesforce.
Use Case:
Briefly, a Prescription is created through global actions that have filtered look-ups for providers and patients based on their record type, as well as drugs filtered by active (theoretically active drugs would be based on inventory however, in this case, I have activated them manually). This creates the opportunity (while also auto-filling the close date and opportunity name). Once all the information is entered, the user must upload the scan of the prescription (in most cases this would be a scan of a physical script or fax) which activates an apex trigger to set a hidden value allowing them to submit it for approval from the pharmacist. The approval process updates the stage to be reviewed from data entry until the pharmacist approves or denies it based on the accuracy of the information. It is then sent to the fill stage. To simulate the filling process the pharmacy tech must complete a screen flow where they type in the RX number and NDC number on the bottle they will be using to fill the prescription (normally this would be done with a scanner and barcodes). If the entered information is correct the stage is updated to Final Review where the pharmacist checks the physical prescription against the data entered. If approved it goes to the Ready stage and waits for POS sale. If Denied it is set to return to stock and a Task is added to return that item to stock and fill it again.