> For the complete documentation index, see [llms.txt](https://au-dohp.gitbook.io/au-dohp-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://au-dohp.gitbook.io/au-dohp-docs/get-help/glossar.md).

# Glossar

C

**Chart** : Visual representation of data in the form of diagrams, maps or other formats. Charts can be customized according to user-defined dimensions and metrics.

**CSV (Comma-Separated Values)**: A file format used to store and exchange tabular data. Data is organized into rows, where each row represents a record, and columns, where each column represents a field. Fields are separated by a comma (or another separator, such as a semicolon, depending on regional settings).

### D <a href="#d" id="d"></a>

**DHIS2**: District Health Information Software : “an open source software platform for data reporting, analysis and dissemination for all health programs”

**Dimensions** : The data fields analyzed by a data product, such as countries, diseases, cases, deaths, etc.

**Dashboard**: A visual tool that brings together graphs, charts and data for fast, intuitive analysis.

**Data Integration**: The process of unifying data from multiple sources (e.g. CSV, Google Sheets, API, FHIR) into a consistent, usable format.

### E <a href="#e" id="e"></a>

**ETL (Extract, Transform, Load)** : A sequence of processes for extracting raw data, transforming it according to defined rules, then loading it into a destination for analysis or use.

**Execution interval**: The frequency with which a data product is refreshed. Example: every hour (@hourly) or every day (@daily).

### F <a href="#f" id="f"></a>

**FHIR (Fast Healthcare Interoperability Resources)**: A standard for data exchange in healthcare systems. It is designed to enable fast and efficient interoperability of medical information.

### I <a href="#i" id="i"></a>

**Integrated data** : Data combined and transformed from various sources to form a unified format, used for analysis and decision-making.

### O <a href="#o" id="o"></a>

**Orchestration** : an automated process for taking data from multiple sources, combining and transforming it, and making it available for analysis

### P <a href="#p" id="p"></a>

**Parquet file** : Parquet is an open source file format built to handle flat columnar storage data formats.

**Pipeline**: A process for preparing data from a source (Excel, CSV, DHIS2, etc.) for transformation within the platform. The pipeline is the starting point of any process chain.

**Pipeline template**: A predefined template used to create a data pipeline, including the processing steps applied to the data.

**Process Chain**: A series of automated steps that transform and process data in a defined sequence. It links a data source to programmed processing steps, enabling data to be refreshed in near-real time.

### S <a href="#s" id="s"></a>

**Superset :** A tool from the Apache suite integrated with RePAN for creating visualizations and graphs based on data sets processed by a process chain.

### U <a href="#u" id="u"></a>

**Unification (**&#x44;ata contex&#x74;**)**: Merge data from disparate sources into a coherent, accessible structure.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://au-dohp.gitbook.io/au-dohp-docs/get-help/glossar.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.