The WiCis architecture has multiple ways of sharing the data it stores for analysis:
1. Reports: This is built into the system. A user can configure an unlimited number of reports (datasets) with fields from any custom CareFlow with a drag and drop interface.
As an example, one can create a simple dataset or report with pt. name, id, age, zip code, in whatever order the admin wants. No limit on columns.
A report or dataset, can also include ALL data from a given CareFlow. WiCis automatically sets up a Default report with ALL data, but it is not in a specific order.
This data can be 1) visualized on screen, 2) exported to a PDF file and 3) exported to a CSV file 4) Use intelligent searches to pick off certain criteria.
Caveats: Our software warns the administrator that any file (PDF, CSV that he/she creates must meet HIPAA requirements since they are so easily moved around the internet and a data breach is possible.
Level of Expertise: Beginner
2. CSV files. As noted above, these are very powerful when used inside Excel for instance, which can take up to 1M records. CSV files are exportable to many commercially available analytics tools. The admin MUST be careful to keep them HIPAA compliant by never creating one with a way to identify a patient.
Caveats: A CSV file is easily moved (email) and a rogue person within a company can steal and sell data easily. Only people who are trusted should be allowed to create these datasets or reports.
Level of Expertise: Beginner/Intermediate. A solid knowledge of Excel and pivot tables allows users to build a powerful reporting tool with up to 1 million records.
3. GeckoBoard: When one creates a report (step 1) which is in fact a dataset, the WiCis system allows you to check off fields that you wish to push to Geckoboard.
Geckoboard is a dataset visualization tool and the datasets have to be built with this in mind not to exceed their 5000 record limit.
As an example, imagine that you are the operations manager for United Airlines. You wish to follow certain metrics on a daily basis on a large screen for better management of your fleet. You would create widgets from your dataset for 1) how many planes are in the air now. 2) What was my fuel consumption yesterday vs hours flown. 3) What are my global fuel reserves? 4) How many pilots called in sick today, etc. All this can be seen on your screen in your office, your smartphone, and is updated live. In this screen you do not have access to ALL the data in the company, such as accounting, how many janitors I have in Milwaukee, etc. This is a data subset that is useful for making operations management decisions.
Think of Geckoboard as a way to have clever visualizations of datasets that are useful for specific needs. They are simple, easy to build, and allow for a growing healthcare company to make quick decisions.
Caveats: Since WiCis has a direct interface to Geckoboard, the data is less portable, but the admin can share dashboards with third parties. Again, admins must be trustworthy, and data passed through must NEVER include a way to identify the patient.
Level of Expertise: Intermediate. A solid understanding of datasets is needed so as to be able to extract the right data from our system. Knowledge of how to create widgets with Geckoboard.
4) Google Data Studio: If with Geckoboard or CSV files we were talking about limited size datasets, Google Data Studio, to which WiCis has a direct connection, can handle up to 2 billion records. Dashboards can also display data from multiple data sources. One could imagine a dashboard with results from a Google Ads campaign, juxtaposed with the number lab tests they done yesterday, with the cost associated with these.
Caveats: GDS has all the built-in securities that google has for its email. WiCis has a direct interface to GDS. Nevertheless, admins handling this data must be very trusted since in this case, ALL data can be moved to this platform.
Level of Expertise: Intermediate/Advanced. Again, solid knowledge of datasets is needed. If all data is moved from WiCis to Google Data Studio, datasets will need to be dealt with on the Google side.
5) WiCis API: One last way to extract data from our system is via the WiCis API and REST interface.
Level of Expertise: Advanced. A software engineer with knowledge of java, python, SQL, REST will be needed to create code that extracts this data from the WiCis system.
Caveats: The REST api has many authorizations and logins to keep data private. Nevertheless, a level of trust with the engineers is important to keep data safe.