Idea Transcript
On initial load of the Provider Dashboard, the user is presented with a sidebar menu along with a main content section. All of the CSS for this layout was custom developed and only makes use of JavaScript and JQuery/JQuery UI.
The sidebar menu offers navigation to all of the content areas in the dashboard.
Content areas that have items that need to be resolved are identified by the number of items that need resolution.
Security has been built in to allow managers to assume the identity of their staff. This does not allow a manager to sign or edit documents on behalf of their staff but rather allows a manager the ability to see what their staff has outstanding.
The Alerts and Messages tab has two sections of content. The first section identifies alerts that a Physician should address. These alerts are categorized by type and age. In the example above, the only alert is less than 36 hours old. If there were additional alerts greater than 36 hours, they would be categorized with yellow or red depending on whether they are greater than 72 hours or not.
The public messages section allows for posting of information that may be important to all users of the dashboard. Multiple messages can be created from within the dashboard and have expiry dates that self-remove the message when the date has passed.
Clicking on the alert will bring you to the detail screen for that alert.
In this example, a clinical note has been saved but not signed. You can see the status, patient name, MRN, FIN #, Document Type and Date the document was saved. Clicking anywhere on the line loads the clinical note where you can sign or modify the document.
The clinical note editing is now all handled by standard PowerChart functionality. After signing or editing the document you are returned to the dashboard. In this example, I am going to sign the document.
As you can see, the dashboard is updated and the signed document no longer shows up in my alerts.
The Schedule Tab allows you the ability to see a custom list of patients based on the Cerner Scheduling application. As a user, you can build a list of scheduling resources you are interested in and view a weekly schedule of patient appointments.
Clicking on a patient square will load that patient into PowerChart where you can perform any standard PowerChart task on the patient (e.g. Place Orders, Create Notes, etc.)
Each user can create their own personal list of resources which is saved on the back-end of Cerner for use next time in the Dashboard.
Adding or deleting from your personal list is a simple matter of clicking the Edit Resource List button and choosing the resources you wish to monitor.
To add a resource, click the name of a resource in the available resources list. It will be added to the Selected Resources panel. To remove or set as the default, click the name on the Selected Resources window and follow the instructions. When finish, click the Save or Cancel button.
The final tab in the Provider Dashboard is the Patient List tab. This tab lets you quickly view and open the patient chart of any patient is a patient list you have built in PowerChart.
First, click the name of the patient list you wish to view and the patients will appear on the window to the right.
In each patient window, you will see the name of the patient in the blue header, followed by the MRN, FIN, Location, Age, DOB, Gender, Patient Type, Medical Service and whether a Medication Reconciliation is required. Clicking on the box will launch PowerChart for the patient. If a Medication Reconciliation is required, clicking the red “Required” text will launch the Medications tab for the patient.
Summary In summary, this slide show demonstrates that mPages can easily be developed to both integrate with existing PowerChart functionality as well as any data located in the Cerner back-end through CCL scripts. In addition to retrieving data from Cerner through CCL, it is also useful and possible to store custom data in Cerner through an mPage and CCL. In this mPage example, not only were user preferences stored on the back-end, but also large content text messages. With my skill in CCL and web development technologies, the possibilities to what can be developed in an mPage are endless. Thank you. John Simpson