Topic: Supply Chain Dashboard. An example of using dashboards to assist with the complexities of a logistics system.
Hospitals, medical centers and other health systems are increasingly using digital dashboard technology to provide relevant, up-to-the-minute information to clinicians in a visually rich format to improve the quality of patient care.
Designing and using clinical dashboards requires substantial physician involvement and a well-defined process. The University of Pennsylvania Health System, a.k.a. Penn Medicine, is currently in the midst of developing the Penn Data Store, a data warehouse and series of individual dashboards, to serve our clinicians and researchers. The Penn story may be of use to you and your organization as you move forward in the world of dashboards.
So starts the article that details how an organization used Oracle’s Business Intelligence Suite to create a single data storehouse with all of their patient, admin, financial and supply chain data.
Here are the 8 steps:
- Meet with users to determine data needs
- Design the presentation layer
- Design the semantic layer
- Design the physical layer
- Develop and test all 3 layers
- Perform QA
- Conduct a Pilot
- Begin general rollout
Here are some particulars. See the article for the full story.
1. Meet with users to determine major data needs
Many users and potential users of dashboards aren’t familiar with the systems’ power and capabilities. They typically use noninteractive spreadsheets and graphs that present data in fixed rows and columns and lack the flexibility of Web-based tools.
The first step in this phase was to inform clinicians of the many additional possibilities that a more powerful tool offers. We did this by first building sample dashboards to demonstrate the tool’s capabilities. We then asked the clinicians to identify several key measures, dimensions and filtering criteria for the dashboards they were interested in.
2. Design the presentation layer
For dashboards to deliver the most benefit, users must agree on presentation standards before the design phase begins. It’s crucial to achieve agreement on items such as color schemes, graphical objects and navigation standards so future dashboards will look, feel and behave consistently. This will improve user satisfaction and reduce training demands for each new dashboard.
Designers must think carefully about the hierarchy of the data they want depicted in the dashboards and what levels of the hierarchy will be visible. In our example, the hierarchy is Practice Physician Patient. Depending on a user’s security status, he may or may not be able to see the patient data.
Once the hierarchy and associated measures such as year, month and practice name were grouped into a dashboard page, we selected the graphical elements. We chose histograms, line graphs, pie charts and simple tables to present the data in an intuitive fashion that met users’ needs and simplified navigation through the dashboard pages.
3. Design the semantic layer
The semantic layer maps the presentation layer to the physical layer. Developers prove their worth in the design of this layer. Defining patient populations by disease categories, grouping drugs hierarchically by therapeutic area and organizing physical locations are examples of the challenges that the semantic layer’s designer faces. Users play a key role in formulating those definitions. In-depth knowledge of both the presentation layer design and the physical data models is essential.
4. Design the physical layer
As mentioned, try not to change the design of the physical layer. Whenever possible, avoid creating an entire new physical data structure, because doing so generates the need for additional extract, transform and load (ETL) steps each time the clinical data warehouse is updated. Redundantly storing data produces additional storage, backup and maintenance costs and opens up the risk that duplicate copies of data won’t be updated with the same frequency as the original.
5. Develop and test all three layers
Users who are new to the dashboard development process will likely need to see how the systems operate with real data. We have found it useful to introduce clinicians to a working prototype to gain early feedback on the design. Regular weekly demo and review sessions then help developers refine and test the design. When you’re engaged in this phase of the project, take care to manage scope creep, since participants might be tempted to request new capabilities or data that weren’t in the original design. Put off responding to such requests until a subsequent release of the dashboard.
6. Perform quality assurance
Here are several quality-assurance requirements we developed at Penn Medicine:
- Use data from the actual data warehouse, rather than simulated or test data.
- Include monthly and quarterly data warehouse updates during the QA process, especially when the data being used in dashboards will cross calendar months, quarters and years. A year-end data update would be ideal, but most projects can’t wait that long.
- Compare dashboard data to the original source systems, to ensure that no translation or presentation errors were introduced during development.
- Test system performance and response times with large amounts of data to ensure that the dashboard responds effectively to users’ needs.
7. Conduct pilot tests
Before making a dashboard available, we ask a small group of users to pilot-test it for a few weeks, as a short extension of the QA phase. This provides additional information on usability, performance and quality. If the pilot group recommends moving forward, we proceed to the general rollout. If the pilot group identifies problems, the development team resolves them.
8. Begin general rollout
This phase involves these major components:
- User orientation: New users may need a brief training session. Those who have used dashboards in the past should be able to use the new dashboard with no assistance — if the presentation layer was designed well.
- Support documentation: Gather design and operational specifications and post them on support sites.
- Help-desk hand-off: Write scripts and give them to the help desk for guidance in responding to support calls.