In our examples today, we’ll be discussing our medical management program, specifically the Disease Mgmt portion. EHN will analyze several years worth of claims data to determine which employees we believe have or are at risk of contracting a chronic illness. We then help the member manage this disease. When we do this, we help to eliminate future medical expenses, and everyone wins.
Often, Collaboration is about people working together to further an Idea. “Let’s build a house together;” “Let’s work on this advertisement.” Each collaborator has a piece to add to the whole of the “Idea.” At EHN, each collaborator completes a piece of the process. For collaboration to be successful, all of the people involved must be able to work together in a way that doesn’t impede any of the other people involved.
It starts with a client. Each client will bring their own third party administrator. There are many different clients, and many TPAs, too. EHN Provides services for all clients and TPAs. Medical Management provides services for all Clients, and needs to work with all TPAs.
And there are rules, too. Clients cannot have access to Medical Management workspaces. They cannot see which employees have medical conditions. Clients and TPAs cannot see into other client or TPA workspaces
Because the Medical Management Company serves all of our clients, individual TPAs cannot have access to the Medical Management Workspace. Tasks for the TPA would have to be assigned first to EHN, then re-assigned to the appropriate TPA Files needed in the individual workspaces had to be copied, which led to multiple versions of each document. In this example, The TPA needs access to File A, But Cannot have access to File B or C. Medical Mgmt needs file C, But cannot have access to files A or B. Tasks have to be passed along like a game of telephone. This is not collaboration.
So we set out to fix the problem. Obviously, the privacy rules still apply. We wanted to make things easy for our company members by consolidating all of our files into one single repository. We also wanted to make sure that any tasks we have are not duplicated or passed along like a game of telephone.
Now, with the use of Shared Folders, we are able to meet our criteria. All three example workspaces remain, and a shared workspace is created. Members from each group are allowed access to the shared workspace. A single set of shared task lists exists. Each list has its own function. Shared folders allows EHN to house all files in the EHN Operations workspace, and share only the necessary files to the appropriate workspace.
We use templated workspaces When we add a new client/contractor, we can just clone a template and “connect” to the correct repository Central Desktop has some solid features, when viewed on their own. It is when you start to combine them, that you get the maximum benefit.
Contracts with thousands of providers and hospitals Need to give access to TPAs Not every TPA gets access to all contracts Need to easily point to the correct folder
Export the DB to excel, run a find and replace to change the workspace name Give the list of folders to the TPA, they can reference them at will. Scalability
Confidential, External Collaboration with 3rd Parties
Alan Bush Central Desktop Power User, and CentralDesktopHero.com Head Blogger email@example.com
<ul><li>About EHN: </li></ul><ul><li>PPO Network and Medical Management services company serving self-funded employer groups, health plans, TPAs, health systems, and providers. </li></ul><ul><li>Heavy emphasis on Data Analysis to control healthcare costs </li></ul><ul><li>Medical and Network Management Consultants </li></ul>
<ul><ul><li>EHN warehouses medical claims for data analysis and repricing (discounts) </li></ul></ul><ul><ul><li>The claims come from multiple inputs </li></ul></ul><ul><ul><li>Claims need to be assigned for entry in the most efficient manner possible </li></ul></ul><ul><ul><li>Originals need to be easily accessible, regardless of the client </li></ul></ul><ul><ul><li>Need to be able to easily add in a new client/contractor </li></ul></ul>
<ul><ul><li>Central Desktop Workspace Templates </li></ul></ul><ul><ul><li>Clone the new workspace </li></ul></ul><ul><ul><li>“ Connect” to the repository </li></ul></ul>
<ul><li>PROS: </li></ul><ul><li>Can interface directly with client’s system </li></ul><ul><li>No need for users to learn a new system </li></ul><ul><li>CONS: </li></ul><ul><li>Can be costly </li></ul><ul><li>Can be time consuming </li></ul><ul><li>ALTERNATIVES: </li></ul><ul><li>Search </li></ul><ul><li>Database </li></ul><ul><li>Links </li></ul>
<ul><li>For Example: </li></ul><ul><ul><li>File 123456 in the EHN Ops Workspace </li></ul></ul><ul><ul><li>File 123456 in the TPA 1 Workspace </li></ul></ul><ul><li>Workspace Name is the only part that changes </li></ul><ul><li>https://ehn.centraldesktop.com/cdwebinar ops /file/ 9336928 / </li></ul><ul><li>https://ehn.centraldesktop.com/cdwebinar tpa /file/ 9336928 / </li></ul>
<ul><li>What you should know about using Central Desktop for 3 rd party confidential collaboration: </li></ul><ul><li>Shared Folders are the key to consolidation </li></ul><ul><li>One central workspace for internal users, separate workspaces for collaborators </li></ul><ul><li>Central Desktop’s features are great individually, exceptional when combined </li></ul>