The Request You've been tasked with building a custom dashboard for your pharmacists to help them access commonly used reports, monitor pharmacy dispenses and orders that need verification, and access...

I am working a Project based on Cogito fundamental to be done on a EPIC demo plat form . Need to know if you can support.Need to do this project on EPIC Demo platform .so it will need to be done when I am available with the tutor


The Request You've been tasked with building a custom dashboard for your pharmacists to help them access commonly used reports, monitor pharmacy dispenses and orders that need verification, and access other important resources. After doing some research in the Report Repository, you find a handful of reports and components that you can use out of the box. However, you will have to custom build a couple of the things the pharmacists are asking for and distribute those reports and components alongside the Epic-released ones in the new dashboard. Workbench Reports Your pharmacists have asked for a couple of real-time reports they will use on a day to day basis. You already found some Epic-released reports that meet their needs. In addition, you will need to build two custom Workbench reports that adhere to the following guidelines. Ordered Meds - Abuse Potential This report should be built from the Find Orders [440] template The report should be named Ordered Meds - Abuse Potential Users who have access to the Find Orders template should also have access to your report in their Analytics Catalog Your report should filter on the following conditions: Search base of Admitted Patients - All Orders and Medications with abuse potential Your pharmacists specify that the medications they classify as having abuse potential have a DEA code of C-II (High abuse potential) or C-III (Moderate dependence) To help improve the efficiency of your report, add an additional criteria. Your report should only include orders with a type of medication. The DEA code of each order should be visible in the results of your report (use a column that was already available on the template) Your pharmacists have some additional resources to share with patients taking medications with abuse potential. Patient's primary email address should by visible in the results of your report In order to find what item stores a patient's primary email address in Chronicles, use the following known test value: Patient Aubrey Shehulk has a primary email address of [email protected] Do not use a display column that retrieves data using an extension Orders for high abuse potential medications (DEA code = C-II) should show up as Important (Yellow) in the Results Viewer. Only the cell that displays the DEA code should turn yellow, not the entire row Your report should be tagged so it is easy to search for in the Analytics Catalog Users should be able to read a helpful description of your report in the Analytics Catalog Dispenses Last Week Report This report should be built from the Rx Dispenses [48008] template The report should be named Dispenses Last Week Users who have access to the Rx Dispenses template should also have access to your report in their Analytics Catalog Your report should filter on the following conditions: Don't include pending dispenses and Only include dispenses dispensed from the EMH Central Pharmacy[1] Your report should search over the last seven days through this morning at midnight. You will use this report to drive a bar graph visualization in a component you will add to the dashboard Do not change anything on the Display tab of your report before building this summary. Only use columns that were already listed as Available or Selected columns on the template Create a Workbench summary that displays a count of the different orders (order ID) that have been dispensed grouped first by Dispense Code and then by Dispense Type Since you are only using this summary to drive a component in Radar, this summary should not be available from the Results Viewer when a user runs this report Your report should be tagged so it is easy to search for in the Analytics Catalog Users should be able to read a helpful description of your report in the Analytics Catalog SlicerDicer Some of your pharmacists have hunches they'd like to investigate about which classifications of inpatient medications are most commonly ordered to be given as needed. You decide to build them a SlicerDicer session to help them get started with their investigation. Use the following specifications to build out a SlicerDicer session: Build your session while logged in as your Cogito Tools Administrator Your users would like to see a list of Inpatient Medication Orders Only show orders placed during Hospital Encounters (encounters with a type of 'Hospital Encounter') Break down your session into groups for the top ten component therapeutic classes Summarize the data as a percentage of the total population that were PRN Real Word Context PRN is an abbreviation for the Latin phrase "pro re nata", which translates to "when needed". PRN orders are given as needed. You data should be displayed as a vertical bar graph When you are complete, save your session as PRN Orders by Therapeutic Class. Save your session to My Sessions. Once you have saved your session, document the ID of your session. To find the ID of your Saved Session, click Load, hover over your session from My Sessions and note the ID. Finding your Session ID Radar Dashboard Build Create a new dashboard with the record name Pharmacist Dashboard Choose a suitable layout for your dashboard. Since your dashboard has the potential to grow as pharmacists start to use it, avoid any of the row layouts Your dashboard is designed for Inpatient Pharmacists. Select an appropriate Owning application and enter in a suitable display title and description Tag your dashboard with Pharmacy - Inpatient [139] so it is easy to find in the Analytics Catalog. Your dashboard should contain the following Epic-released components: RX VERIFY QUEUE [48100] Rx Drug Shortage Links [4080000071] Rx Pharmacy Message Board [4080000019] Rx PHARMACY STATUS [48101] Build the following custom components and add them to your Pharmacist Dashboard Access Critical You do not have the security to edit Humphrey Batwoman's User Security record - you only have the security to make changes to the dashboard, components, and reports you have created. Only modify records you have created. The sample pharmacist user Humphrey Batwoman (R EMP 600611) should have access to your dashboard Antimicrobial Reports Name this component Antimicrobial Reports Your component should be tagged so it is easy to search for in the Analytics Catalog Users should be able to read a description of your component in the Analytics Catalog This component should contain a list of all current and future Workbench and Epic-Crystal reports tagged with: Rx Antimicrobial Use and Resistance [1139] or Rx OPAT [1144] Separately group any Workbench reports together and any Epic-Crystal reports together The sample pharmacist user Humphrey Batwoman (R EMP 600611) should be able to find your component in the Analytics Catalog. Critical You do not have the security to edit Humphrey Batwoman's User Security record - you only have the security to make changes to the dashboard, components, and reports you have created. Only modify records you have created. Pharmacist Reports Name this component Pharmacist Reports Your component should be tagged so it is easy to search for in the Analytics Catalog Users should be able to read a description of your component in the Analytics Catalog This component should contain a list of the following specific Epic-released reports as well as the two custom reports you built in the Workbench Reports section of the project Rx Dispense Workload [7289] Rx Search Medication Orders [13710] Rx Verification Workload [7250] The three-Epic released reports should be listed first, followed by a single, visible line separator, followed by your two custom reports The sample pharmacist user Humphrey Batwoman (R EMP 600611) should be able to find your component in the Analytics Catalog. Dispenses by Code and Type Name this component Dispenses by Code and Type Your component should be tagged so it is easy to search for in the Analytics Catalog Users should be able to read a description of your component in the Analytics Catalog This component should be a graph component that uses the summary built in the Dispenses Last Week report The data should be presented as a stacked bar graph, where each bar represents a different dispense code. Each individual bar representing a dispense code should be broken up vertically by dispense type Users should not be able to show a table on this component The X-axis and Y-axis should both have appropriate labels The sample pharmacist user Humphrey Batwoman (R EMP 600611) should be able to find your component in the Analytics Catalog. Dispense Metrics Name this component Dispense Metrics Your component should be tagged so it is easy to search for in the Analytics Catalog Users should be able to read a description of your component right in the Analytics Catalog This component should be a table component displaying three common dispense metrics, per the specifications that follow Find the Right Metrics Your pharmacists would like to see the following metrics in a table component: Dispenses from Automatic Dispensing System The total number of dispenses that are coming from an automatic dispensing system Formulary Compliance The percentage of medication orders that were for medications on the formulary after verification Medication Turnaround Time The average time from when a medication order first entered the verification queue and when it was verified. Your pharmacists are interested in all medications, not just the high priority ones Luckily, you found a couple Epic-released metrics that seem like good candidates for this table component. Use the Metric Repository on the UserWeb to choose the correct metric from the list of possible IDN records in the table below using the descriptions for each metric above. If you don't have access to the Metric Repository on the Userweb, look up each metric in the Record Viewer and read the description. Metric Possible IDNs The Correct IDN Dispenses from Automatic Dispensing System R IDN 48052 R IDN 48163 R IDN 48420 Formulary Compliance R IDN 48051 R IDN 48054 R IDN 48059 Medication Turnaround Time R IDN 48050 R IDN 48053 R IDN 51010 Build the Component Your table component should show all three metrics, summarized by Service Area For this component only, specify a default service area of EHS Service Area[10] Your table component should display the metric data monthly Three months should be available You would like to tweak how some of the metrics are displayed in your component. Create a new Resource (IDK) record for the dispenses from automatic dispensing system metric and the formulary compliance metric according to the specifications listed below: Dispenses from ADS Show the total number of dispenses from the ADS as a whole number instead of a percentage of all dispenses Don't specify any thresholds; just the number is fine Formulary Compliance Show the data as a percentage of medication orders that were for medications on the formulary Your percentages should show up as whole numbers, always rounded down A percentage between 0 and 60 should turn red, above 60 and up to 90 should turn yellow, and above 90 and up to 100 should turn green For the medication turnaround time metric, find an Epic-released IDK record to use You are happy with the display as-is. Don't make any changes to the Epic-released IDK record The sample pharmacist user Humphrey Batwoman (R EMP 600611) should be able to find your component in the Analytics Catalog. Get the Component Reviewed Since your Dispense Metrics component includes so much valuable information, you decide to get it reviewed by your pharmacy subject matter experts. They get back