Platform
How Clic Health works: from Tasy to dashboard
No long IT project and no changes to Tasy: four steps take the data to the board's screen, with patients by code and every step logged.
Understanding how it works helps IT and the executive board assess Clic Health safely. The principle is simple: Tasy remains the hospital's system of record. Clic Health only reads what the dashboards need, organizes that data by management rules and displays the result in the browser.
The four stages
1. DataClic: reading Tasy
DataClic is an agent that runs on a Windows server or virtual machine at the hospital. It connects to the Tasy database with a read-only user and runs the queries defined for each dashboard (the loads). On later updates it brings only what changed since the last read, so it does not burden the hospital database.
DataClic never writes to Tasy. Communication starts from DataClic and goes to the Connection Environment over HTTPS.
2. Data preparation
The data is organized according to the dashboard rules: accounting period, cost centers, income statement groups, payers, departments, specialties. This is where "revenue" is made to mean the same thing on every dashboard, and where the income statement number is reconciled with billing.
3. Connection Environment
The Connection Environment is Clic Health's data layer. It receives the loads, keeps the history, builds the final tables (the model) and publishes them to the Clic Health database. Patients arrive identified only by a code: names, national ID numbers and dates of birth stay at the hospital. Each hospital has its own access key to its data.
4. Clic Health
The board and managers sign in to Clic Health with a password and a personal code and open the dashboards in the browser. The data arrives already summarized for analysis, which keeps screens fast even at large hospitals.
When the data is refreshed
Updates follow a schedule agreed with each hospital, with set times throughout the day. Different loads can have different times: billing can be refreshed several times a day, accounting after month-end close. Each dashboard shows the date and time of the last update and the expected time of the next one.
If the board needs a number before a meeting, the Update now button places a request in DataClic's queue.
What the hospital needs
- Tasy in use, with read access to the database for DataClic (the hospital's IT team creates the user).
- A Windows server or virtual machine on the hospital network, running during scheduled times, with outbound HTTPS internet access.
- Someone from IT for the installation and someone from controllership or the board to validate the numbers with our team.
The full implementation plan and the most common questions are in the implementation and support FAQ. Integration details are in Tasy integration and data refresh.
How to know everything is working
The diagnostics screen shows, in plain language, whether DataClic is in contact, which version is installed, how the last load run went and when the model was published. When something stops, it points to the likely cause and what to do, for example "the DataClic server is turned off or offline".