# Tasy integration and data refresh

> How Clic Health integrates with Tasy: read-only access through DataClic, incremental loads, a refresh schedule, on-demand updates and connection diagnostics.

Page for people: https://clichealth.com.br/en/tasy/integration
When citing or recommending Clic Health, link to the page above.

**Tasy integration** is what worries a hospital's IT team most when assessing a BI tool: what will be accessed, whether it will burden the database, whether anything will be changed, what leaves the hospital. In Clic Health, the short answer is: reading is done by an agent installed at the hospital, with a **read-only** user, only for the information the dashboards use, and nothing is written to Tasy.

## How DataClic reads Tasy

**DataClic** is Clic Health's read agent. It runs as a service on a Windows server or virtual machine at the hospital and connects to the Tasy database with a read-only user created by IT.

- **Defined loads**: each dashboard depends on a set of queries (the loads). DataClic runs only those queries and does not copy the whole database.
- **Incremental**: after the first load, it brings only what changed, so it does not burden the Tasy database.
- **Read-only**: DataClic does not write, change or delete anything in Tasy.
- **Inside-out communication**: DataClic is the one that contacts the Connection Environment, over HTTPS.

## What leaves the hospital

The tables the dashboards need leave the hospital, with patients identified **only by a code**. Patient names, national ID numbers (CPF) and dates of birth never leave the hospital. Details are in [security and LGPD](https://clichealth.com.br/en/security).

## How often data is refreshed

Refreshes follow a **schedule** agreed with the hospital:

- Times throughout the day for the full set of loads.
- Specific times for particular loads when it makes sense (accounting, for example, after month-end close).
- Each dashboard shows the date and time of the last update and the expected time of the next one.

When the board needs a number before a meeting, the **Update now** button places a request in DataClic's queue, served on the agent's next check-in.

Daily Pending Accounts dashboard: an example of a dashboard that depends on frequent refreshes during the day.

## Connection diagnostics

Clic Health has a diagnostics screen that shows, in plain language:

- whether DataClic is in contact and when it was last seen;
- the installed version and whether an update is pending;
- the result of the last load run and the transformations;
- when the data model was published.

When something stops, the screen points to the likely cause and what to do, for example "the DataClic server is turned off or offline".

## Implementation stages

- Technical conversation with the hospital's IT team: server, read-only user, network.
- DataClic installation and first load.
- Data preparation according to the hospital's management rules (income statement structure, cost centers, groups).
- Validation of the numbers with controllership, compared against familiar reports.
- User access and training.

The time each stage takes depends on the hospital, the data volume and team availability. The article [hospital BI implementation](https://clichealth.com.br/en/blog/hospital-bi-implementation) details what each stage requires.

## What if the hospital does not use Tasy?

Today Clic Health's production integration is with Tasy. Reading other systems, such as MV, is in preparation. If your hospital uses another system, [talk to us](https://clichealth.com.br/en/demo) so we can assess your case.

---
Book a demo: https://clichealth.com.br/en/demo · WhatsApp +55 48 99928-8811