Wondering how to design an healthcare analytics portal? A portal (sometimes referred to as a dashboard) is a living thing that evolves with the needs of its users, as well as the availability and quality of the data used to create it. To ensure your healthcare analytics portal can provide actionable business intelligence and never becomes irrelevant, we have developed the Enterprise Dashboard Design Process.
On a high level, our process is a six-step exercise split into three phases. It involves careful research, thorough ideation, and deliberate design. The result is a custom-designed analytics portal tailored to your business, your data, and your goals. In this article, I’ll discuss go into detail on all the steps required to design an analytics portal, so feel free to navigate with the buttons here to jump to a certain part.
• Reduces risk. Our process increases awareness about your data and data literacy, user expectations, and potential roadblocks, allowing you to address issues early and avoid costly and time-consuming fixes farther down the line.
• Educates. Because our process emphasizes collaboration, important stakeholders from across your organization are actively involved everywhere that they need to be. This ensures your portal is aligned to business value and builds user trust, which is easy to lose and hard to regain.
• Provides clarity. As you evaluate data, create personas, and define goals, you’ll gain a clearer understanding of the state of your organization—and what to do with these insights.
• Spurs action. With a powerful healthcare analytics portal at your fingertips, taking action will be easier than ever. Simple visuals and digestible metrics will highlight where your team should focus its time and energy, ultimately resulting in behavioral change.
This design process is what we use to create portals for our clients. Want us to make yours? Learn more here.
Want to make your own healthcare portal? Let's get started!
For a dashboard to serve the needs of your business and your end users, you’ll need to talk to anyone that can or will be involved. Try to get a balanced representation from each of the following groups:
• Leadership and business owners
• End users (clinicians, HR executives, directors, and more)
• Custodians of your data
• Portal developers
Next, using the questions below as a guideline, interview your stakeholders. Their answers will help you clarify objectives, reduce risks, and gain valuable information about potential roadblocks:
• What is your role and what do you do day to day?
• What are your objectives and goals?
• How can this portal make your life easier?
• How do you currently access this data?
• What are your current challenges in accessing this data?
• What Key Performance Indicators (KPIs) do you currently use?
• What KPIs would you like to see?
Without a thorough understanding of your source material, you can’t get very far. In analytics, it’s important for you to understand your data, both at a high level and in detail. The more in-depth you get, the better, but even general information like what tables and columns are available is important. Understanding data quality is also recommended, but that can be tackled later if necessary. Regardless of what level you want to understand, you’ll need to speak with someone who works closely with the data and have them provide as much detail as possible. At the end of your conversation, you should:
• Understand what type(s) of data exist. Portals work with structured data—that is, data that is already organized into tables, columns, and rows—but it’s good to be aware of what else is out there that could inform decision-making.
• Collect the data. Get the database schema, as well as the schemas of any other data sources.
• Examine the data. Run through which columns have data of high enough quality for the first iteration of the portal. This is subjective, but the data should be robust enough to build confidence in anyone seeing it. A portal with incorrect or incomplete information isn’t very convincing and doesn't provide any value.
• Improve the data as needed. Come up with a plan to improve any lower-quality data so it can be added to later iterations of the portal.
The next step in our design process is to workshop your portal and begin the design process. To avoid having to redo any work or rehash any topics, it is critical to involve as many users and stakeholders as possible in this step. Gather users from across your organization. Together, you can agree on the overall purpose of the portal and brainstorm a comprehensive list of obstacles and risks.
The first phase of designing your portal is about personas, each of which represent a specific user group. You can leverage your work from Step 1 by merging some identities to create one to three primary personas. As you work, make note of what questions each persona might want answered, and note how thoroughly your current data is able to answer each question.
Next comes the tricky process of visualizing each persona’s questions in chart form. Each chart should meet several criteria:
• What question does this chart answer?
• What action needs to be taken as a result of what we see on the chart?
• Is the data behind the chart sufficiently reliable?
Complete this process for all the questions your personas might have. With completed visuals in hand, you are ready to mock-up your portal.
Before a developer can create a functional version of your portal, you’ll need to a provide a detailed mockup. Mocking up your portal is easiest using our kit. Whether you use that or choose to create by hand, you should focus on creating three types of panels: charts, filters, and KPIs. When put together, these become the content of your portal. Once your mockup is complete, you’re ready for the next step.
With your vision in hand, it’s time to work with a developer to create a live, functioning healthcare analytics portal. As you think about how to launch and share your portal, it may be helpful to look at the bullet points identified in Step 5. Choosing a platform that prioritizes usability and user requirements will save you time and money. Available options include Microsoft PowerBI, Tableau, Qlik, and more.
No matter which BI platform you use, modern business intelligence software is flexible enough to allow customization and accommodate best practices. Depending on how precisely you designed your wireframes in Step 3, some extra effort may be required to translate your vision into something your software can display. You and your portal developer should explore your design, customize it based on the tool’s capabilities, and establish best practices. Make sure to iron out any issues before moving on to Step 5.
An example of a finished healthcare analytics portal.
Now that you have a functioning portal based on a well-planned vision, someone needs to be responsible for making sure users know about the portal, how to use it, and how it can provide them value. Creating a plan for user adoption prepares you for deploying your portal and provides valuable user insights to improve future iterations.
What kind of knowledge management platform do people want to use? As it turns out, adoption is most successful for platforms that enable discovery, socialization, and gamification. People want easy access to a tool that is simple, useful, social, and fun. In practice, this equates to features like:
• Portal hosting
• Support for training materials
The platform you use is just one of the many decisions you will need to make as you deploy your portal. It’s important to integrate change management and training as a part of your adoption process. Pay close attention to your users and their experience; no matter how reliable your data or flashy your interface, if people struggle to use your dashboard in their daily work, adoption will not succeed.
Your portal is live and providing value for people across your organization. Congratulations!
As time goes on, requirements for your portal may change. For this reason, it’s a good practice to release a new version of your portal every three months for the first year of its life. We don’t mean data refresh velocity; the data powering your tool should always be up to date. The structure, however, can be revisited every three months and adjusted as needed. After the first year, you can revisit every six months. Our design process was created to work on both new and existing portals, so feel free to save this page as resource.