←Insights

CAMS Requests: Our New Secure, In-Application Messaging Workflow

January 19, 2022

Dealing with difficult posting and balancing problems can be a slow and disorganized process, especially at big institutions with multiple facilities and a large cash posting and accounting staff.

To make problem solving fast, easy, and organized, Fawkes Health has just created a new collaborative in-application messaging workflow within CAMS to assist staff in communicating issues and ultimately seeking issue resolution across business units called our “Requests” feature.

 
 

Using Requests, any CAMS user can raise a hand to ask for help with reconciling posted cash to a Ticket, or with fixing a problem on a Remittance Edit, or even to get a second pair of eyes on a Manually Created Remittance before it goes out the door to post. All housed within our SaaS application CAMS to maintain a streamlined process and a high level of HIPAA compliant data security.

Requests are assigned back and forth between people and groups as they collaborate. Ever lost track of a problem your co-worker asked you to look into? Don’t worry, when a Request is assigned to you, a simple notification appears on your individual CAMS landing page so you can maintain a work queue of open items and resolve them accordingly.

 
 

Leveraging our Requests feature within the CAMS application not only has benefits of streamlining communication between various business units - especially within large multi-hospital organizations. Furthermore, in today’s world where many are now working at home, simply assigning a Request within CAMS leverages our interconnected data model to effectively triage a request to the right person or team. And lastly, keeping communications within our HIPAA compliant application promotes users to communicate in a secure way, therefore reducing the risk of protected health information (PHI) being exposed in other methods of communication.  

 
 

Once a Request is created, it stays tagged to the item in question (the Ticket, Remittance Edit, etc.) until the problem is solved. Within that single Request, read a concise history of all comments made, all users and groups assigned, and even add and view attachments, so that a full audit trail exists as items get resolved.