QlikView Hospital Activity - Report Example

Introduction

According to the QlikView dashboard, the number of specialties, which had the least wait time were: rheumatology, pediatrics, medical oncology, diabetic medicine, intermediate care, geriatric medicine, adult mental illness, and clinical hematology. On average pain management, patients' wait time in December of 2008 to 2009 was 82.20 days. According to Connelly (2020) in Great Britain, the average wait time for patients with chronic pain is 14 weeks and varies hugely. Thus, in comparison average wait time of 82.20 days is much significant improvement which can booster the patients' confidence with the hospital.

Is your time best spent reading someone else’s essay? Get a 100% original essay FROM A CERTIFIED WRITER!

Save 25%

The QlikView dashboard also revealed that, on average, the day-case admission wait time length in October of 2009 to 2010 was 38.51 days. Also, there was a total of 1576 oral surgery patients who were white during September 200-2010. On the average patient in neurology, both elective and non-elective in August 2009 to 2010 stayed for 24 days. Further, the QlikView dashboard reveals that the average length of stay for patients in the 81 to 95 age group in August 2008 to 2009 was 7.39 days.

Basing on the QlikView dashboard, on average, neonatology patient's length of stay is 10.22 days. For the age group of 0-12, the average length of stay was 1.52 days. Also, the dashboard reveals that between 2007 and 2010, emergency pediatrics had 4907 spells. This high number of spells could be attributed to the high frequency to which patients visit the pediatrics emergency department even though they are judged as inappropriate and non-urgent (Wong et al., 2015).

Visuals and Data Points

The dashboard presents various visuals and data points, communicating relevant hospital information. The QlikView dashboard can be used as a reliable and useful health information system to be accessed by final users such as health practitioners, patients, policymakers, and researchers (Lohr, 2015). For instance, policymakers may utilize the dashboard when making decisions on unmet health needs. From the dashboard, the average wait time of pain management patients in December of 2008 to December of 2009 was 82.2 days. The lengthy wait time may imply a lack of adequate resources, either facilities or human resources. It may necessitate the introduction and implementation of policies and strategies to solve the lack of resources. Also, from the dashboard, the number of emergency pediatrics between 2007 and 2010 was 4907. This number is high and may be a cause of interest among the researchers who would like to examine the antecedent factors leading to many patients in emergency pediatrics.

Additionally, when presented with QlikView dashboard information, they may be able to adjust their expectations and plan their health requirements. Interested patients may use the information to inform their hospital visits and stay decisions. Most importantly, QlikView dashboard visuals and data may be handy to different health practitioners such as hospital managers, doctors, and nurses. They can use various information such as the number of oral surgery patients, average wait time for plastic surgery patients, among other details to inform hospital-related decisions.

QlikView Verdict

QlikView dashboard is a robust and easily manipulates huge data. The ability to handle enormous data easily and quickly is impressive. When I was building the dashboard, I found it fairly easy to create connections to other databases and sources of data and generate various visuals, which made the process appealing and enjoyable. Its simplicity in creating, deploying, and using is great compared to other applications such as Microsoft Power BI or Google Public Data (Qlik, 2020).

In terms of intuition, the QlikView dashboard allows the cleaning and data customization with ease. I enjoyed the power and capability to clean the data and deploy it to work according to my need. Also, the ability to bring data together from various sources and servers ensures that its intuition is highly optimized. Further, the powerful script editor with multiple functions and the speediest memory tool that can build custom objects helps with the dashboard's intuition capability.

Generally, I found that once the reports are set, there is a tiny chance of getting things wrong. The ultimate user can access the reports and interact with them without the worries of changing anything in the report's set because the admin makes any changes. It gives the final user flexibility and confidence to apply and play with as many filters.

On the negative side, there are too many configurations and properties available, which, although they give flexibility, can be easily clubbed together systematically and waste the user's time in finding the appropriate configuration properties. Additionally, although QlikView is easy to handle, a person without programmer knowledge or relational database may find it difficult to operate. Also, the user interface does not look pretty; there are fewer charts than other applications such as Microsoft Power BI.

However, in my opinion, the benefits are more than the disadvantages; hence it can be a useful application in the hospital organization. Since QlikView handles enormous data, it is very useful in organizations that generate, store, and use huge data to make decisions such as hospitals. The QlikView dashboard can be used to generate a report for every department in a hospital. The reports can be curated and used as productive resources for the final users. Also, the QlikView dashboard can be very used to solve hospital problems and inform different decisions. The application can be used in a hospital setting as a tool for modeling and data transformation. It can also be utilized to store data and reports in various formats such as CSV, qvds, among others.

Conclusion

In comparison, my overall experience working on QlikView was great; however, working on Google Public Data was also excellent. The main difference is that in Google public data, I found that the visualizations were already generated. There are multiple chart types that I was presented to choose from and check the results. Although Google public data was excellent at visualizations, it was limited because I did not have the flexibility to create visualizations into my liking. In contrast, QlikView did not have ready-made visualizations, but the process of dashboard creation was great and gave you a sense of credibility and ownership of the visuals. QlikView dashboard creation was a hands-on skill and experience which I found easy to navigate and build. Also, data gathering and presentation in QlikView was flexible.

Additionally, it is hard to get ideas on data what data preparation or what performance metrics can be used with Google public data and in which order. In contrast, QlikView allows flexibility, and as a user, I was able to visualize my data in different graphs and the exact numbers related to graphs.

On the similarity side, both Google public data and QlikView allows easiness of use, and the data visuals are good. Both systems need little training to get the final user operating. In QlikView, it just takes a few minutes to build a basic dashboard and start operating and a few hours to create a much more sophisticated dashboard. In comparison, Google public data does not require training since the user is presented with the visuals required.

References

Connelly, D. (2020, February 6). Some patients with chronic pain face waiting years to see a specialist. Pharmaceutical Journal.
https://www.pharmaceutical-journal.com/news-and-analysis/news/opioid-prescribing-in-wales-increases-by-30-in-a-decade/news-and-analysis/news/some-patients-with-chronic-pain-face-waiting-years-to-see-a-specialist/20207637.fullarticle

Lohr, K. (2015). Reviews and Notes: Health Data in the Information Age: Use, Disclosure, and Privacy. Annals of Internal Medicine, 122(10), 805–813.
https://doi.org/10.7326/0003-4819-122-10-199505150-00027

Qlik. (2020). QlikView – Powerful Interactive Analytics & Dashboards. Qlik.
https://www.qlik.com/us/products/qlikview.

Wong, A. C., Claudet, I., Sorum, P., & Mullet, E. (2015). Why Do Parents Bring Their Children to the Emergency Department? A Systematic Inventory of Motives. International Journal of Family Medicine, 20(15), 1–10. https://doi.org/10.1155/2015/978412.