ARIS - User contributions [en]

Data analysis/pt

2026-02-27T10:43:56Z

Alberto: Created page with "===Testes por resultado=== Esta aba agrupa todos os resultados iguais para cada tipo de teste e mostra ao supervisor do laboratório o quantidade de cada um. Também informa a qual área do laboratório cada tipo de teste pertence.</br> No canto inferior esquerdo desta aba, há um botão de download (ou transferência). Ao clicar nele, todas as informações encontradas na tela serão baixadas para o computador do supervisor do laboratório."

[[Category:Data analysis]]
<languages/>
Fornece uma funcionalidade analítica muito básica baseada em contadores.
Ele basicamente permite que o supervisor do laboratório acompanhe o número de testes realizados (potencialmente agrupados) e alguns elementos básicos relacionados às solicitações.

<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph FunctionalitiesDiagram {
node [shape="oval" style=filled fillcolor="orange" fontsize="9pt"];
//----- Data Analysis graph
// Nodes
DataAnalysis [label="Análise de Dados"];
GlobalIndicators [label="Indicadores Globais" shape=tab URL="#Indicadores_globais" ];
TestsPerLaboratoryArea [label="Testes por área de laboratório" shape=tab URL="#Testes_por_área_laboratorial"];
TestsPerKind [label="Testes por tipo" shape=tab URL="#Testes_por_tipo"];
TestsPerResult [label="Testes por resultado" shape=tab URL="#Testes_por_resultado"];
TestsPerGender [label="Testes por gênero" shape=tab URL="#Testes_por_gênero"];
// Edges
DataAnalysis -> GlobalIndicators;
DataAnalysis -> TestsPerLaboratoryArea;
DataAnalysis -> TestsPerKind;
DataAnalysis -> TestsPerResult;
DataAnalysis -> TestsPerGender;
}
</graphviz>
</div>

__TOC__

==Consultas de banco de dados==
[[File:DataAnalysis.PNG|350px|right|thumb|Formulário de análise de dados]]
Este formulário contém um filtro na parte superior da mesma vista, que permite ao supervisor do laboratório escolher o parâmetro para a busca no banco de dados.
Há nove campos de filtro disponíveis, no máximo (somente aqueles que estão sendo usados nas solicitações existentes são exibidos).
#De (data de criação da solicitação): os dados coletados conterão apenas solicitações criadas após essa data.
#Até (data de criação da solicitação): os dados coletados conterão apenas solicitações criadas antes dessa data.
#Estado da solicitação de teste
#Área de laboratório
#Centro de solicitação
#Unidade solicitante
#Sexo do paciente
#Região de procedência do paciente
#Local de procedência do paciente

Nem todos os filtros estão sempre visíveis. Se o banco de dados ARIS não contiver valores para um elemento específico, o filtro para esse elemento não será exibido ao supervisor do laboratório.

===Indicadores globais===
Esta aba contém uma tabela com contadores, que mostra ao supervisor do laboratório o número de determinados elementos que estão no banco de dados ARIS.

===Testes por área laboratorial===
Esta aba agrupa todos os testes que pertencem a cada área do laboratório e mostra ao supervisor do laboratório o número de cada um.</br>
No canto inferior esquerdo desta aba, há um botão de download. Ao clicar nele, todas as informações encontradas na tela serão baixadas para o computador do supervisor do laboratório.

===Testes por tipo===
Esta aba agrupa todos os tipos de testes e mostra ao supervisor do laboratório o número de cada um. Também informa a qual área do laboratório cada tipo de teste pertence.</br>
No canto inferior esquerdo desta aba, há um botão de download. Ao clicar nele, todas as informações encontradas na tela serão baixadas para o computador do supervisor do laboratório.

===Testes por resultado===
Esta aba agrupa todos os resultados iguais para cada tipo de teste e mostra ao supervisor do laboratório o quantidade de cada um. Também informa a qual área do laboratório cada tipo de teste pertence.</br>
No canto inferior esquerdo desta aba, há um botão de download (ou transferência). Ao clicar nele, todas as informações encontradas na tela serão baixadas para o computador do supervisor do laboratório.

===Testes por gênero===
Esta aba agrupa todos os testes que pertencem a cada gênero e mostra ao supervisor do laboratório o número de cada um.</br>
No canto inferior esquerdo desta aba, há um botão de download. Ao clicar nele, todas as informações encontradas na tela serão baixadas para o computador do supervisor do laboratório.

Data analysis/es

2026-02-27T10:43:33Z

Alberto:

[[Category:Data analysis]]
<languages/>
Este análisis proporciona una capacidad muy básica basada en contadores.
Básicamente permite al supervisor del laboratorio realizar un seguimiento del número de pruebas realizadas (potencialmente agrupadas) y de algunos elementos básicos relacionados con las solicitudes.

<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph FunctionalitiesDiagram {
node [shape="oval" style=filled fillcolor="orange" fontsize="9pt"];
//----- Data Analysis graph
// Nodes
DataAnalysis [label="Análisis de Datos"];
GlobalIndicators [label="Indicadores Globales" shape=tab URL="#Indicadores_globales" ];
TestsPerLaboratoryArea [label="Tests por Área de Laboratorio" shape=tab URL="#Tests_por_área_de_laboratorio"];
TestsPerKind [label="Tests por Tipo" shape=tab URL="#Tests_por_tipo"];
TestsPerResult [label="Tests por resultado" shape=tab URL="#Tests_por_resultado"];
TestsPerGender [label="Tests por Género" shape=tab URL="#Tests_por_género"];
// Edges
DataAnalysis -> GlobalIndicators;
DataAnalysis -> TestsPerLaboratoryArea;
DataAnalysis -> TestsPerKind;
DataAnalysis -> TestsPerResult;
DataAnalysis -> TestsPerGender;
}
</graphviz>
</div>

__TOC__

==Consultas de base de datos==
[[File:DataAnalysis.PNG|350px|right|thumb|Formulario de análisis de datos]]
Este formulario contiene un filtro en la parte superior de la pantalla, que permite al supervisor del laboratorio elegir el parámetro para la búsqueda en la base de datos.
Hay nueve campos de filtro disponibles como máximo (solo se muestran aquellos que se utilizan en las solicitudes existentes).
#Desde (fecha de creación de la solicitud): los datos tomados sólo contendrán las solicitudes creadas después de esta fecha.
#Hasta (fecha de creación de la solicitud): los datos tomados sólo contendrán las solicitudes creadas antes de esta fecha.
#Estado de solicitud de prueba
#Área de laboratorio
#Centro que realiza la solicitud
#Unidad solicitante
#Sexo del paciente
#Región de procedencia del paciente
#Lugar de residencia del paciente

No todos los filtros son siempre visibles. Si la base de datos de ARIS no contiene valores para un elemento específico, el filtro para este elemento no se mostrará al supervisor del laboratorio.

===Indicadores globales===
Esta pestaña contiene una tabla con contadores, que muestra al supervisor del laboratorio la cantidad de ciertos elementos que se encuentran en la base de datos de ARIS.

===Tests por área de laboratorio===
Esta pestaña agrupa todos los tests que pertenecen a cada área del laboratorio y muestra al supervisor del laboratorio el número de cada uno.</br>
En la parte inferior izquierda de esta pestaña, hay un botón de descarga. Al hacer clic en este botón, se descargará toda la información que se encuentre en la pantalla en la computadora del supervisor del laboratorio.

===Tests por tipo===
Esta pestaña agrupa todos los tipos de tests y muestra al supervisor del laboratorio el número de cada una. También informa al supervisor del laboratorio a qué área del laboratorio pertenece cada tipo de prueba.</br>
En la parte inferior izquierda de esta pestaña, hay un botón de descarga. Al hacer clic en este botón, se descargará toda la información que se encuentre en la pantalla en la computadora del supervisor del laboratorio.

===Tests por resultado===
Esta pestaña agrupa todos los resultados iguales para cada tipo de test y muestra al supervisor del laboratorio el número de cada uno. También informa al supervisor del laboratorio de a qué área del laboratorio pertenece cada tipo de prueba.</br>
En la parte inferior izquierda de esta pestaña, hay un botón de descarga. Al hacer clic en este botón, se descargará toda la información que se encuentre en la pantalla en el ordenador del supervisor del laboratorio.

===Tests por género===
Esta pestaña agrupa todos los tests realizados para cada género y muestra al supervisor del laboratorio el número de cada uno de ellos.</br>
En la parte inferior izquierda de esta pestaña, hay un botón de descarga. Al hacer clic en este botón, se descargará toda la información que se encuentre en la pantalla en la computadora del supervisor del laboratorio.

Translations:Data analysis/10/es

2026-02-27T10:43:21Z

Alberto:

===Tests por resultado===
Esta pestaña agrupa todos los resultados iguales para cada tipo de test y muestra al supervisor del laboratorio el número de cada uno. También informa al supervisor del laboratorio de a qué área del laboratorio pertenece cada tipo de prueba.</br>
En la parte inferior izquierda de esta pestaña, hay un botón de descarga. Al hacer clic en este botón, se descargará toda la información que se encuentre en la pantalla en el ordenador del supervisor del laboratorio.

Translations:Data analysis/10/pt

2026-02-27T10:43:00Z

===Testes por resultado===
Esta aba agrupa todos os resultados iguais para cada tipo de teste e mostra ao supervisor do laboratório o quantidade de cada um. Também informa a qual área do laboratório cada tipo de teste pertence.</br>
No canto inferior esquerdo desta aba, há um botão de download (ou transferência). Ao clicar nele, todas as informações encontradas na tela serão baixadas para o computador do supervisor do laboratório.

Data analysis/es

2026-02-27T10:40:04Z

Alberto: Created page with "===Tests por tipo=== Esta pestaña agrupa todos los resultados iguales para cada tipo de test y muestra al supervisor del laboratorio el número de cada uno. También informa al supervisor del laboratorio de a qué área del laboratorio pertenece cada tipo de prueba.</br> En la parte inferior izquierda de esta pestaña, hay un botón de descarga. Al hacer clic en este botón, se descargará toda la información que se encuentre en la pantalla en el ordenador del supervis..."

[[Category:Data analysis]]
<languages/>
Este análisis proporciona una capacidad muy básica basada en contadores.
Básicamente permite al supervisor del laboratorio realizar un seguimiento del número de pruebas realizadas (potencialmente agrupadas) y de algunos elementos básicos relacionados con las solicitudes.

<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph FunctionalitiesDiagram {
node [shape="oval" style=filled fillcolor="orange" fontsize="9pt"];
//----- Data Analysis graph
// Nodes
DataAnalysis [label="Análisis de Datos"];
GlobalIndicators [label="Indicadores Globales" shape=tab URL="#Indicadores_globales" ];
TestsPerLaboratoryArea [label="Tests por Área de Laboratorio" shape=tab URL="#Tests_por_área_de_laboratorio"];
TestsPerKind [label="Tests por Tipo" shape=tab URL="#Tests_por_tipo"];
TestsPerResult [label="Tests por resultado" shape=tab URL="#Tests_por_resultado"];
TestsPerGender [label="Tests por Género" shape=tab URL="#Tests_por_género"];
// Edges
DataAnalysis -> GlobalIndicators;
DataAnalysis -> TestsPerLaboratoryArea;
DataAnalysis -> TestsPerKind;
DataAnalysis -> TestsPerResult;
DataAnalysis -> TestsPerGender;
}
</graphviz>
</div>

__TOC__

==Consultas de base de datos==
[[File:DataAnalysis.PNG|350px|right|thumb|Formulario de análisis de datos]]
Este formulario contiene un filtro en la parte superior de la pantalla, que permite al supervisor del laboratorio elegir el parámetro para la búsqueda en la base de datos.
Hay nueve campos de filtro disponibles como máximo (solo se muestran aquellos que se utilizan en las solicitudes existentes).
#Desde (fecha de creación de la solicitud): los datos tomados sólo contendrán las solicitudes creadas después de esta fecha.
#Hasta (fecha de creación de la solicitud): los datos tomados sólo contendrán las solicitudes creadas antes de esta fecha.
#Estado de solicitud de prueba
#Área de laboratorio
#Centro que realiza la solicitud
#Unidad solicitante
#Sexo del paciente
#Región de procedencia del paciente
#Lugar de residencia del paciente

No todos los filtros son siempre visibles. Si la base de datos de ARIS no contiene valores para un elemento específico, el filtro para este elemento no se mostrará al supervisor del laboratorio.

===Indicadores globales===
Esta pestaña contiene una tabla con contadores, que muestra al supervisor del laboratorio la cantidad de ciertos elementos que se encuentran en la base de datos de ARIS.

===Tests por área de laboratorio===
Esta pestaña agrupa todos los tests que pertenecen a cada área del laboratorio y muestra al supervisor del laboratorio el número de cada uno.</br>
En la parte inferior izquierda de esta pestaña, hay un botón de descarga. Al hacer clic en este botón, se descargará toda la información que se encuentre en la pantalla en la computadora del supervisor del laboratorio.

===Tests por tipo===
Esta pestaña agrupa todos los tipos de tests y muestra al supervisor del laboratorio el número de cada una. También informa al supervisor del laboratorio a qué área del laboratorio pertenece cada tipo de prueba.</br>
En la parte inferior izquierda de esta pestaña, hay un botón de descarga. Al hacer clic en este botón, se descargará toda la información que se encuentre en la pantalla en la computadora del supervisor del laboratorio.

===Tests por tipo===
Esta pestaña agrupa todos los resultados iguales para cada tipo de test y muestra al supervisor del laboratorio el número de cada uno. También informa al supervisor del laboratorio de a qué área del laboratorio pertenece cada tipo de prueba.</br>
En la parte inferior izquierda de esta pestaña, hay un botón de descarga. Al hacer clic en este botón, se descargará toda la información que se encuentre en la pantalla en el ordenador del supervisor del laboratorio.

===Tests por género===
Esta pestaña agrupa todos los tests realizados para cada género y muestra al supervisor del laboratorio el número de cada uno de ellos.</br>
En la parte inferior izquierda de esta pestaña, hay un botón de descarga. Al hacer clic en este botón, se descargará toda la información que se encuentre en la pantalla en la computadora del supervisor del laboratorio.

Data analysis/pt

2026-02-27T10:40:04Z

Alberto:

[[Category:Data analysis]]
<languages/>
Fornece uma funcionalidade analítica muito básica baseada em contadores.
Ele basicamente permite que o supervisor do laboratório acompanhe o número de testes realizados (potencialmente agrupados) e alguns elementos básicos relacionados às solicitações.

<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph FunctionalitiesDiagram {
node [shape="oval" style=filled fillcolor="orange" fontsize="9pt"];
//----- Data Analysis graph
// Nodes
DataAnalysis [label="Análise de Dados"];
GlobalIndicators [label="Indicadores Globais" shape=tab URL="#Indicadores_globais" ];
TestsPerLaboratoryArea [label="Testes por área de laboratório" shape=tab URL="#Testes_por_área_laboratorial"];
TestsPerKind [label="Testes por tipo" shape=tab URL="#Testes_por_tipo"];
TestsPerResult [label="Testes por resultado" shape=tab URL="#Testes_por_resultado"];
TestsPerGender [label="Testes por gênero" shape=tab URL="#Testes_por_gênero"];
// Edges
DataAnalysis -> GlobalIndicators;
DataAnalysis -> TestsPerLaboratoryArea;
DataAnalysis -> TestsPerKind;
DataAnalysis -> TestsPerResult;
DataAnalysis -> TestsPerGender;
}
</graphviz>
</div>

__TOC__

==Consultas de banco de dados==
[[File:DataAnalysis.PNG|350px|right|thumb|Formulário de análise de dados]]
Este formulário contém um filtro na parte superior da mesma vista, que permite ao supervisor do laboratório escolher o parâmetro para a busca no banco de dados.
Há nove campos de filtro disponíveis, no máximo (somente aqueles que estão sendo usados nas solicitações existentes são exibidos).
#De (data de criação da solicitação): os dados coletados conterão apenas solicitações criadas após essa data.
#Até (data de criação da solicitação): os dados coletados conterão apenas solicitações criadas antes dessa data.
#Estado da solicitação de teste
#Área de laboratório
#Centro de solicitação
#Unidade solicitante
#Sexo do paciente
#Região de procedência do paciente
#Local de procedência do paciente

Nem todos os filtros estão sempre visíveis. Se o banco de dados ARIS não contiver valores para um elemento específico, o filtro para esse elemento não será exibido ao supervisor do laboratório.

===Indicadores globais===
Esta aba contém uma tabela com contadores, que mostra ao supervisor do laboratório o número de determinados elementos que estão no banco de dados ARIS.

===Testes por área laboratorial===
Esta aba agrupa todos os testes que pertencem a cada área do laboratório e mostra ao supervisor do laboratório o número de cada um.</br>
No canto inferior esquerdo desta aba, há um botão de download. Ao clicar nele, todas as informações encontradas na tela serão baixadas para o computador do supervisor do laboratório.

===Testes por tipo===
Esta aba agrupa todos os tipos de testes e mostra ao supervisor do laboratório o número de cada um. Também informa a qual área do laboratório cada tipo de teste pertence.</br>
No canto inferior esquerdo desta aba, há um botão de download. Ao clicar nele, todas as informações encontradas na tela serão baixadas para o computador do supervisor do laboratório.

<div lang="en" dir="ltr" class="mw-content-ltr">
===Tests per result===
This tab groups together all the same results for every kind of test and shows the laboratory supervisor the number of each one. It also informs the laboratory supervisor as to which laboratory area each kind of test belongs to.</br>
At the bottom left of this tab, there is a download button. When clicked, this button will download every piece of information found in the screen into the laboratory supervisor's computer.
</div>

===Testes por gênero===
Esta aba agrupa todos os testes que pertencem a cada gênero e mostra ao supervisor do laboratório o número de cada um.</br>
No canto inferior esquerdo desta aba, há um botão de download. Ao clicar nele, todas as informações encontradas na tela serão baixadas para o computador do supervisor do laboratório.

Translations:Data analysis/2/pt

2026-02-27T10:39:24Z

Alberto:

<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph FunctionalitiesDiagram {
node [shape="oval" style=filled fillcolor="orange" fontsize="9pt"];
//----- Data Analysis graph
// Nodes
DataAnalysis [label="Análise de Dados"];
GlobalIndicators [label="Indicadores Globais" shape=tab URL="#Indicadores_globais" ];
TestsPerLaboratoryArea [label="Testes por área de laboratório" shape=tab URL="#Testes_por_área_laboratorial"];
TestsPerKind [label="Testes por tipo" shape=tab URL="#Testes_por_tipo"];
TestsPerResult [label="Testes por resultado" shape=tab URL="#Testes_por_resultado"];
TestsPerGender [label="Testes por gênero" shape=tab URL="#Testes_por_gênero"];
// Edges
DataAnalysis -> GlobalIndicators;
DataAnalysis -> TestsPerLaboratoryArea;
DataAnalysis -> TestsPerKind;
DataAnalysis -> TestsPerResult;
DataAnalysis -> TestsPerGender;
}
</graphviz>
</div>

Translations:Data analysis/10/es

2026-02-27T10:35:57Z

===Tests por tipo===
Esta pestaña agrupa todos los resultados iguales para cada tipo de test y muestra al supervisor del laboratorio el número de cada uno. También informa al supervisor del laboratorio de a qué área del laboratorio pertenece cada tipo de prueba.</br>
En la parte inferior izquierda de esta pestaña, hay un botón de descarga. Al hacer clic en este botón, se descargará toda la información que se encuentre en la pantalla en el ordenador del supervisor del laboratorio.

Translations:Data analysis/2/es

2026-02-27T10:34:17Z

Alberto:

<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph FunctionalitiesDiagram {
node [shape="oval" style=filled fillcolor="orange" fontsize="9pt"];
//----- Data Analysis graph
// Nodes
DataAnalysis [label="Análisis de Datos"];
GlobalIndicators [label="Indicadores Globales" shape=tab URL="#Indicadores_globales" ];
TestsPerLaboratoryArea [label="Tests por Área de Laboratorio" shape=tab URL="#Tests_por_área_de_laboratorio"];
TestsPerKind [label="Tests por Tipo" shape=tab URL="#Tests_por_tipo"];
TestsPerResult [label="Tests por resultado" shape=tab URL="#Tests_por_resultado"];
TestsPerGender [label="Tests por Género" shape=tab URL="#Tests_por_género"];
// Edges
DataAnalysis -> GlobalIndicators;
DataAnalysis -> TestsPerLaboratoryArea;
DataAnalysis -> TestsPerKind;
DataAnalysis -> TestsPerResult;
DataAnalysis -> TestsPerGender;
}
</graphviz>
</div>

Data analysis

2026-02-27T10:32:40Z

Alberto: Marked this version for translation

[[Category:Data analysis]]
<languages/>
<translate>

This provides a very basic analytical functionality based on counters.
It basically allows the laboratory supervisor to keep track of the number of tests performed (potentially grouped) and some basic elements related to the requests.


<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph FunctionalitiesDiagram {
node [shape="oval" style=filled fillcolor="orange" fontsize="9pt"];
//----- Data Analysis graph
// Nodes
DataAnalysis [label="Data Analysis"];
GlobalIndicators [label="Global Indicators" shape=tab URL="#Global_indicators" ];
TestsPerLaboratoryArea [label="Tests Per Laboratory Area" shape=tab URL="#Tests_per_laboratory_area"];
TestsPerKind [label="Tests Per Kind" shape=tab URL="#Tests_per_kind"];
TestsPerResult [label="Tests Per Result" shape=tab URL="#Tests_per_result"];
TestsPerGender [label="Tests Per Gender" shape=tab URL="#Tests_per_gender"];
// Edges
DataAnalysis -> GlobalIndicators;
DataAnalysis -> TestsPerLaboratoryArea;
DataAnalysis -> TestsPerKind;
DataAnalysis -> TestsPerResult;
DataAnalysis -> TestsPerGender;
}
</graphviz>
</div>


__TOC__


==Database queries==
[[File:DataAnalysis.PNG|350px|right|thumb|Data analysis form]]
This form contains a filter at the top of the screen, which allows the laboratory supervisor to choose the parameter for the database search.
There are nine filter fields available, at most (only those being used in the existing requests are shown).
#From (request's creation date): the data taken will only contain requests created after this date.
#Until (request's creation date): the data taken will only contain requests created before this date.
#Test request state
#Laboratory area
#Requesting centre
#Requesting unit
#Patient's gender
#Patient's provenance region
#Patient's provenance location


Not all filters are always visible. If the ARIS database does not contain values for a specific element, the filter for this element will not be shown to the laboratory supervisor.


===Global indicators===
This tab contains a table with counters, which shows the laboratory supervisor the number of certain elements that are in the ARIS database.


===Tests per laboratory area===
This tab groups together all the tests that belong to each laboratory area and shows the laboratory supervisor the number of each one.</br>
At the bottom left of this tab, there is a download button. When clicked, this button will download every piece of information found in the screen into the laboratory supervisor's computer.


===Tests per kind===
This tab groups together all the kinds of tests and shows the laboratory supervisor the number of each one. It also informs the laboratory supervisor as to which laboratory area each kind of test belongs to.</br>
At the bottom left of this tab, there is a download button. When clicked, this button will download every piece of information found in the screen into the laboratory supervisor's computer.


===Tests per result===
This tab groups together all the same results for every kind of test and shows the laboratory supervisor the number of each one. It also informs the laboratory supervisor as to which laboratory area each kind of test belongs to.</br>
At the bottom left of this tab, there is a download button. When clicked, this button will download every piece of information found in the screen into the laboratory supervisor's computer.


===Tests per gender===
This tab groups together all the tests that belong to each gender and shows the laboratory supervisor the number of each one.</br>
At the bottom left of this tab, there is a download button. When clicked, this button will download every piece of information found in the screen into the laboratory supervisor's computer.
</translate>

File:DataAnalysis.PNG

2026-02-27T10:29:49Z

Alberto: Alberto uploaded a new version of File:DataAnalysis.PNG

Data analysis

2026-02-27T10:27:42Z

Alberto:

[[Category:Data analysis]]
<languages/>
<translate>

This provides a very basic analytical functionality based on counters.
It basically allows the laboratory supervisor to keep track of the number of tests performed (potentially grouped) and some basic elements related to the requests.


<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph FunctionalitiesDiagram {
node [shape="oval" style=filled fillcolor="orange" fontsize="9pt"];
//----- Data Analysis graph
// Nodes
DataAnalysis [label="Data Analysis"];
GlobalIndicators [label="Global Indicators" shape=tab URL="#Global_indicators" ];
TestsPerLaboratoryArea [label="Tests Per Laboratory Area" shape=tab URL="#Tests_per_laboratory_area"];
TestsPerKind [label="Tests Per Kind" shape=tab URL="#Tests_per_kind"];
TestsPerResult [label="Tests Per Result" shape=tab URL="#Tests_per_result"];
TestsPerGender [label="Tests Per Gender" shape=tab URL="#Tests_per_gender"];
// Edges
DataAnalysis -> GlobalIndicators;
DataAnalysis -> TestsPerLaboratoryArea;
DataAnalysis -> TestsPerKind;
DataAnalysis -> TestsPerResult;
DataAnalysis -> TestsPerGender;
}
</graphviz>
</div>


__TOC__

==Database queries== 
[[File:DataAnalysis.PNG|350px|right|thumb|Data analysis form]]
This form contains a filter at the top of the screen, which allows the laboratory supervisor to choose the parameter for the database search.
There are nine filter fields available, at most (only those being used in the existing requests are shown).
#From (request's creation date): the data taken will only contain requests created after this date.
#Until (request's creation date): the data taken will only contain requests created before this date.
#Test request state
#Laboratory area
#Requesting centre
#Requesting unit
#Patient's gender
#Patient's provenance region
#Patient's provenance location


Not all filters are always visible. If the ARIS database does not contain values for a specific element, the filter for this element will not be shown to the laboratory supervisor.

===Global indicators=== 
This tab contains a table with counters, which shows the laboratory supervisor the number of certain elements that are in the ARIS database.

===Tests per laboratory area=== 
This tab groups together all the tests that belong to each laboratory area and shows the laboratory supervisor the number of each one.</br>
At the bottom left of this tab, there is a download button. When clicked, this button will download every piece of information found in the screen into the laboratory supervisor's computer.

===Tests per kind=== 
This tab groups together all the kinds of tests and shows the laboratory supervisor the number of each one. It also informs the laboratory supervisor as to which laboratory area each kind of test belongs to.</br>
At the bottom left of this tab, there is a download button. When clicked, this button will download every piece of information found in the screen into the laboratory supervisor's computer.

===Tests per result===
This tab groups together all the same results for every kind of test and shows the laboratory supervisor the number of each one. It also informs the laboratory supervisor as to which laboratory area each kind of test belongs to.</br>
At the bottom left of this tab, there is a download button. When clicked, this button will download every piece of information found in the screen into the laboratory supervisor's computer.

===Tests per gender=== 
This tab groups together all the tests that belong to each gender and shows the laboratory supervisor the number of each one.</br>
At the bottom left of this tab, there is a download button. When clicked, this button will download every piece of information found in the screen into the laboratory supervisor's computer.
</translate>

Data analysis

2026-02-27T10:26:33Z

Alberto:

[[Category:Data analysis]]
<languages/>
<translate>

This provides a very basic analytical functionality based on counters.
It basically allows the laboratory supervisor to keep track of the number of tests performed (potentially grouped) and some basic elements related to the requests.


<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph FunctionalitiesDiagram {
node [shape="oval" style=filled fillcolor="orange" fontsize="9pt"];
//----- Data Analysis graph
// Nodes
DataAnalysis [label="Data Analysis"];
GlobalIndicators [label="Global Indicators" shape=tab URL="#Global_indicators" ];
TestsPerLaboratoryArea [label="Tests Per Laboratory Area" shape=tab URL="#Tests_per_laboratory_area"];
TestsPerKind [label="Tests Per Kind" shape=tab URL="#Tests_per_kind"];
TestsPerGender [label="Tests Per Gender" shape=tab URL="#Tests_per_gender"];
// Edges
DataAnalysis -> GlobalIndicators;
DataAnalysis -> TestsPerLaboratoryArea;
DataAnalysis -> TestsPerKind;
DataAnalysis -> TestsPerGender;
}
</graphviz>
</div>


__TOC__

==Database queries== 
[[File:DataAnalysis.PNG|350px|right|thumb|Data analysis form]]
This form contains a filter at the top of the screen, which allows the laboratory supervisor to choose the parameter for the database search.
There are nine filter fields available, at most (only those being used in the existing requests are shown).
#From (request's creation date): the data taken will only contain requests created after this date.
#Until (request's creation date): the data taken will only contain requests created before this date.
#Test request state
#Laboratory area
#Requesting centre
#Requesting unit
#Patient's gender
#Patient's provenance region
#Patient's provenance location


Not all filters are always visible. If the ARIS database does not contain values for a specific element, the filter for this element will not be shown to the laboratory supervisor.

===Global indicators=== 
This tab contains a table with counters, which shows the laboratory supervisor the number of certain elements that are in the ARIS database.

===Tests per laboratory area=== 
This tab groups together all the tests that belong to each laboratory area and shows the laboratory supervisor the number of each one.</br>
At the bottom left of this tab, there is a download button. When clicked, this button will download every piece of information found in the screen into the laboratory supervisor's computer.

===Tests per kind=== 
This tab groups together all the kinds of tests and shows the laboratory supervisor the number of each one. It also informs the laboratory supervisor as to which laboratory area each kind of test belongs to.</br>
At the bottom left of this tab, there is a download button. When clicked, this button will download every piece of information found in the screen into the laboratory supervisor's computer.

===Tests per result===
This tab groups together all the same results for every kind of test and shows the laboratory supervisor the number of each one. It also informs the laboratory supervisor as to which laboratory area each kind of test belongs to.</br>
At the bottom left of this tab, there is a download button. When clicked, this button will download every piece of information found in the screen into the laboratory supervisor's computer.

===Tests per gender=== 
This tab groups together all the tests that belong to each gender and shows the laboratory supervisor the number of each one.</br>
At the bottom left of this tab, there is a download button. When clicked, this button will download every piece of information found in the screen into the laboratory supervisor's computer.
</translate>

System administration/pt

2026-02-26T15:43:17Z

Alberto:

[[Category:System administration]]
<languages/>
Isso agrupa todos os botões que permitem gerenciar e adaptar o comportamento do ARIS às necessidades do laboratório e às preferências do usuário.
Eles são agrupados em dois para facilitar seu acesso.
O primeiro é mais genérico e permite que tanto o supervisor do laboratório quanto a administração do sistema acessem algumas informações básicas.
O segundo está disponível apenas para o administrador do sistema, pois é considerado como exigindo habilidades tecnológicas mais avançadas.

<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border="frame" format="svg">
digraph AdministrationDiagram {
node [shape=oval style=filled fillcolor=orange fontsize="9pt"];
//----- System Administration graph
// Nodes
SystemAdministration [label="Administração do Sistema"];
Generic [label="Genérico" URL="#Genérico"];
Technical [label="Técnico" URL="#Técnico"];
Users [label="Usuários" shape=tab URL="#Usuários"];
AccessLog [label="Registro de acesso" shape=tab URL="#Access_log"];
DownloadedFields [label="CamposBaixados" shape=tab URL="#Campos_baixados"];
SummaryOfInstances [label="Resumo de Instâncias" shape=tab URL="#Resumo_de_instâncias"];
Roles [label="Roles" shape=tab URL="#Roles"];
Parameters [label="Parâmetros" shape=tab URL="#Parâmetros"];
// Edges
SystemAdministration -> Generic;
SystemAdministration -> Technical;
// Edges
Generic -> Users;
Generic -> AccessLog;
Generic -> DownloadedFields;
// Edges
Technical -> SummaryOfInstances;
Technical -> Roles;
Technical -> Parameters;
}
</graphviz>
</div>

__TOC__

==Genérico==
Isso agrupa todas as funcionalidades básicas de administração.
Eles estão disponíveis tanto para a administração do sistema quanto para o supervisor do laboratório.

===Usuários===
[[File:Newuser.PNG|right|thumb|750px|Formulário de criação de usuário]]
Ao clicar nos botões "Editar" ou "Novo usuário", um formulário é exibido na tela. As informações necessárias para criar um usuário consistem em "Nome de usuário", "Nome", "Nome do meio", "Senha" e a [[#Funções|Função]] da pessoa no sistema.
Esta função determinará as funcionalidades disponíveis para o usuário.
Uma nota, sem qualquer efeito no comportamento do aplicativo, pode ser adicionada para indicar qualquer informação relevante ao administrador do sistema.

Este mesmo formulário permite que o administrador do sistema modifique a senha de qualquer outro usuário.
Por razões de segurança, esta senha deve conter algum número, alguma letra maiúscula, alguma letra minúscula e pelo menos oito caracteres.

Como eles são usados para auditar alterações em pacientes e solicitações, os usuários não podem ser excluídos do sistema.
No entanto, eles podem ser declarados como inativos, o que os impediria de efetuar login, mas ainda assim manteriam um registro no banco de dados de todas as suas ações passadas.

===Registro de acesso===
O "registro de acesso" mostra ao usuário qual usuário realizou uma ação no sistema e exatamente quando. O registro de data e hora está no formato '''Ano-Mês-Dia Hora:Minuto:Segundo'''
[[File:Accesslog.PNG|right|thumb|600px|Exemplo de registro de acesso]]</br>
Há três ações registradas no log de acesso: "login bem-sucedido", "usuário incorreto" e "login com falha". Esta última ação se refere ao uso de uma senha incorreta.

===Campos baixados===
O ARIS permite que o supervisor do laboratório baixe todas as informações do banco de dados em um único arquivo em seu computador.
Há duas opções possíveis de download, dependendo do formato do arquivo gerado: CSV simples ou ZIP compactado e protegido por senha.
Esses documentos conterão informações sobre as solicitações e, por extensão, sobre os pacientes correspondentes.
Portanto, devido à confidencialidade do paciente, nem todos os dados pessoais devem estar no arquivo baixado.
As caixas de seleção neste formulário permitem que o supervisor do laboratório, bem como o administrador do sistema, decidam quais campos serão baixados em cada um dos formatos.

Além disso, o sistema fornece dois parâmetros de configuração para personalizar a estrutura do arquivo CSV: "csv_delimiter", que define o caractere usado para separar os campos de dados no arquivo CSV, e "csv_decimal", que especifica o caractere usado para representar valores decimais em campos numéricos. É essencial configurar esses parâmetros de acordo com as configurações usadas pelo sistema e pelo software de planilha (por exemplo, Excel) para garantir a interpretação correta dos dados. O uso de um delimitador ou separador decimal incorreto pode resultar em problemas de formatação ao abrir o arquivo.

==Técnico==
Isso agrupa todas as funcionalidades de administração mais avançadas.
Eles estão disponíveis apenas para a administração do sistema.

===Resumo de instâncias===
[[File:Summaryofinstancessmol.PNG|right|250px|thumb|Resumo das instâncias]]
Esta aba exibe informações sobre as diferentes instâncias existentes no aplicativo.
Alguns exemplos são: número de pacientes, usuários, solicitações ou gêneros.
Essas informações vêm diretamente do banco de dados e são atualizadas automaticamente após cada modificação no sistema.
Pode ser útil investigar potenciais problemas de desempenho em caso de números extremamente grandes.
Para facilitar a leitura e identificação dos diferentes tipos de instâncias, as informações estão divididas em três seções: ''Dados'', ''Administração'' e ''Configuração''.

===Roles===
Esta aba é exibida e funciona da mesma forma que a aba [[Configuration/pt#Estado_da_solicitação|Estado da solicitação]] na funcionalidade [[Configuration/pt|Configuração]].
As funções são imutáveis, mas seus rótulos (não a funcionalidade correspondente) podem ser personalizados.

Cada função tem diferentes ações permitidas dentro do aplicativo, escolhidas devido às tarefas que as pessoas devem realizar.
Assim, existem cinco papéis dentro do sistema, que indicam as funcionalidades que um usuário pode desempenhar, como pode ser visto na tabela a seguir.

{| class="wikitable" style="margin:auto; text-align: center;"
|+ Funcionalidades permitidas por roles
|-
!colspan="2"| Funcionalidades !! Gerente de Pacientes !! Técnico de Laboratório !! Técnico de Laboratório com Validação !! Supervisor de Laboratório !! Administrador de Sistemas
|-
| style="text-align:left;" rowspan="2" | Paciente || style="text-align:left;" | Criar ||[[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Pesquisar || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="6" | Solicitar || style="text-align:left;" | Criar ||[[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Alterar informações || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Entregar amostras || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Apresentar resultados || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Validar resultados || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Histórico de pesquisa || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" colspan="2" | Análise de dados || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="2" | Configuração || style="text-align:left;" | Genérico || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|-
| style="text-align:left;" | Técnico || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="2" | Administração || style="text-align:left;"| Genérico || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|-
| style="text-align:left;" | Técnico || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|}

===Parâmetros===
Os parâmetros determinam o comportamento de algumas funcionalidades.
Portanto, eles não podem ser criados ou excluídos.
No entanto, seus valores podem ser atualizados para personalizar o sistema.
Neste ponto é importante destacar que ao atualizá-los, o tipo de dado deve ser respeitado.
Fornecer um valor do tipo de dado errado (por exemplo, uma string em vez de um inteiro) pode provocar o mau funcionamento de todo o aplicativo.

A tabela a seguir contém a lista de parâmetros existentes, juntamente com o tipo de dados correspondente e uma breve descrição.

{| class="wikitable" style="margin:auto; text-align: left;"
|+ Parâmetros do sistema
|-
! Nome !! Tipo de dados !! Descrição
|-
| ''attribute_reserved1'' || String || Rótulo do primeiro campo de uso livre nas requisições (escreva 'DoNotShow' para ocultá-lo)
|-
| ''attribute_reserved2'' || String || Rótulo do segundo campo de uso livre nas requisições (escreva 'DoNotShow' para ocultá-lo)
|-
| ''attribute_reserved3'' || String || Rótulo do terceiro campo de uso livre nas requisições (escreva 'DoNotShow' para ocultá-lo)
|-
| ''frequência_de_backup'' || Número inteiro || Quantidade mínima de horas necessárias para que o sistema gere uma nova cópia do banco de dados
|-
| ''backup_history'' || Número inteiro || Número máximo de cópias do banco de dados mantidas (quando atingido, a cópia mais antiga na pasta é excluída)
|-
| ''bluetooth_enabler'' || String || Indica a disponibilidade de testes automáticos por meio de conexão Bluetooth (os valores aceitos são 'Enabled' e 'Disabled'), que é usada apenas no projeto [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page IMAGING]
|-
| ''csv_decimal'' || String || Especifica o caractere usado para representar o ponto decimal em valores numéricos no arquivo CSV gerado (os valores aceitos são ''.'' e '','')
|-
| ''csv_delimiter'' || String || Especifica o caractere usado para separar os campos no arquivo CSV gerado (os valores aceitos são '';'' e '','')
|-
| ''idioma_padrão'' || String || Idioma definido por padrão ao fazer login (o mesmo para todos os usuários)
|-
| ''filename_background'' || String || Arquivo contendo a imagem exibida no fundo
|-
| ''filename_favicon'' || String || Ícone do sistema usado na aba do navegador
|-
| ''filename_sidebarlogo'' || String || Arquivo contendo o logotipo exibido na parte inferior da barra lateral
|-
| ''filename_worklistlogo'' || String || Logotipo usado nos relatórios da lista de trabalho
|-
| ''groups_profiles'' || String || Mostra grupos e perfis para testes analíticos (os valores aceitos são 'Ativado' e 'Desativado')
|-
| ''log_history'' || Número inteiro || Número máximo de dias para manter os registros no log de acesso (os registros mais antigos que este serão excluídos automaticamente)
|-
| ''max_image_volume'' || Número inteiro || Número máximo de megabytes usados para armazenar imagens (quando atingido, as imagens mais antigas da pasta são excluídas)
|-
| ''nome'' || Texto || Legenda a ser exibida na parte superior da tela (na barra de navegação), bem como na lista de tarefas e nos relatórios
|-
| ''report_subtitle'' || String || Subtítulo a ser usado na lista de tarefas e nos relatórios
|-
| ''set_sample_delivery_default'' || String || Indica se as amostras devem ser entregues por defeito ou não (os valores aceites são 'True' e 'False'); definir como 'True' oculta os itens 'Alterar informações' e 'Entregar amostras' na barra lateral
|-
| ''show_validate_all_button'' || String || Indica se o botão para validar todos os testes de uma vez está visível ou não (os valores aceites são 'True' e 'False').
|-
| ''table_default_paging'' || Número inteiro || Indica a paginação inicial de todas as tabelas (os valores aceitos são 5, 10 ou 25)
|-
| ''table_min_rows_for_search'' || Número inteiro || Este é o número mínimo de linhas que uma tabela deve ter para exibir o campo de pesquisa correspondente.
|-
| ''timeout'' || Número inteiro || Tempo (em minutos) após o qual a conexão com o servidor requer um novo login
|-
| ''versão'' || String || Versão do sistema
|-
| ''zip_password'' || String || Esta é a senha que será usada para gerar o arquivo zip baixado
|}

Translations:System administration/15/pt

2026-02-26T15:42:12Z

Alberto:

{| class="wikitable" style="margin:auto; text-align: left;"
|+ Parâmetros do sistema
|-
! Nome !! Tipo de dados !! Descrição
|-
| ''attribute_reserved1'' || String || Rótulo do primeiro campo de uso livre nas requisições (escreva 'DoNotShow' para ocultá-lo)
|-
| ''attribute_reserved2'' || String || Rótulo do segundo campo de uso livre nas requisições (escreva 'DoNotShow' para ocultá-lo)
|-
| ''attribute_reserved3'' || String || Rótulo do terceiro campo de uso livre nas requisições (escreva 'DoNotShow' para ocultá-lo)
|-
| ''frequência_de_backup'' || Número inteiro || Quantidade mínima de horas necessárias para que o sistema gere uma nova cópia do banco de dados
|-
| ''backup_history'' || Número inteiro || Número máximo de cópias do banco de dados mantidas (quando atingido, a cópia mais antiga na pasta é excluída)
|-
| ''bluetooth_enabler'' || String || Indica a disponibilidade de testes automáticos por meio de conexão Bluetooth (os valores aceitos são 'Enabled' e 'Disabled'), que é usada apenas no projeto [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page IMAGING]
|-
| ''csv_decimal'' || String || Especifica o caractere usado para representar o ponto decimal em valores numéricos no arquivo CSV gerado (os valores aceitos são ''.'' e '','')
|-
| ''csv_delimiter'' || String || Especifica o caractere usado para separar os campos no arquivo CSV gerado (os valores aceitos são '';'' e '','')
|-
| ''idioma_padrão'' || String || Idioma definido por padrão ao fazer login (o mesmo para todos os usuários)
|-
| ''filename_background'' || String || Arquivo contendo a imagem exibida no fundo
|-
| ''filename_favicon'' || String || Ícone do sistema usado na aba do navegador
|-
| ''filename_sidebarlogo'' || String || Arquivo contendo o logotipo exibido na parte inferior da barra lateral
|-
| ''filename_worklistlogo'' || String || Logotipo usado nos relatórios da lista de trabalho
|-
| ''groups_profiles'' || String || Mostra grupos e perfis para testes analíticos (os valores aceitos são 'Ativado' e 'Desativado')
|-
| ''log_history'' || Número inteiro || Número máximo de dias para manter os registros no log de acesso (os registros mais antigos que este serão excluídos automaticamente)
|-
| ''max_image_volume'' || Número inteiro || Número máximo de megabytes usados para armazenar imagens (quando atingido, as imagens mais antigas da pasta são excluídas)
|-
| ''nome'' || Texto || Legenda a ser exibida na parte superior da tela (na barra de navegação), bem como na lista de tarefas e nos relatórios
|-
| ''report_subtitle'' || String || Subtítulo a ser usado na lista de tarefas e nos relatórios
|-
| ''set_sample_delivery_default'' || String || Indica se as amostras devem ser entregues por defeito ou não (os valores aceites são 'True' e 'False'); definir como 'True' oculta os itens 'Alterar informações' e 'Entregar amostras' na barra lateral
|-
| ''show_validate_all_button'' || String || Indica se o botão para validar todos os testes de uma vez está visível ou não (os valores aceites são 'True' e 'False').
|-
| ''table_default_paging'' || Número inteiro || Indica a paginação inicial de todas as tabelas (os valores aceitos são 5, 10 ou 25)
|-
| ''table_min_rows_for_search'' || Número inteiro || Este é o número mínimo de linhas que uma tabela deve ter para exibir o campo de pesquisa correspondente.
|-
| ''timeout'' || Número inteiro || Tempo (em minutos) após o qual a conexão com o servidor requer um novo login
|-
| ''versão'' || String || Versão do sistema
|-
| ''zip_password'' || String || Esta é a senha que será usada para gerar o arquivo zip baixado
|}

Translations:System administration/15/es

2026-02-26T14:52:45Z

Alberto:

{| class="wikitable" style="margin:auto; text-align: left;"
|+ Parámetros del Sistema
|-
! Nombre !! Tipo de Datos !! Descripción
|-
| ''attribute_reserved1'' || String || Etiqueta del primer campo de uso discrecional en las solicitudes (escribe 'DoNotShow' para ocultarlo)
|-
| ''attribute_reserved2'' || String || Etiqueta del segundo campo de uso discrecional en las solicitudes (escribe 'DoNotShow' para ocultarlo)
|-
| ''attribute_reserved3'' || String || Etiqueta del tercer campo de uso discrecional en las solicitudes (escribe 'DoNotShow' para ocultarlo)
|-
| ''backup_frequency'' || Integer || Mínimo número de horas que deben pasar para que el sistema vuelva a generar una copia de seguridad
|-
| ''backup_history'' || Integer || Máximo número de copias de seguridad de la base de datos que se guardan (una vez alcanzado este número, la copia más antigua se borrará)
|-
| ''bluetooth_enabler'' || String || Indica la disponibilidad de test automáticos a través de conexión Bluetooth (los valores aceptados son 'Enabled' y 'Disabled'), lo cual se utiliza únicamente en el contexto del [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page Proyecto IMAGING]
|-
| ''csv_decimal'' || String || Especifica el carácter utilizado para representar el punto decimal en valores numéricos en el archivo CSV generado (valores aceptados: '.' y ',').
|-
| ''csv_delimiter'' || String || Especifica el carácter utilizado para separar los campos en el archivo CSV generado (valores aceptados: ';' y ',').
|-
| ''default_language'' || String || Idioma establecido por defecto al iniciar la sesión (será el mismo para todos los usuarios)
|-
| ''filename_background'' || String || Fichero que contiene la imagen de fondo
|-
| ''filename_favicon'' || String || Icono del sistema usado en la correspondiente pestaña del navegador
|-
| ''filename_sidebarlogo'' || String || Fichero que contiene el logo mostrado en la parte superior de la barra lateral
|-
| ''filename_worklistlogo'' || String || Logo utilizado en la lista de trabajo y reportes
|-
| ''group_profiles'' || String || Muestra los grupos y perfiles de tests analíticos (los valores aceptados son 'Enabled' y 'Disabled')
|-
| ''log_history'' || Integer || Número máximo de días que se guardarán las entradas en el registro de acceso (las que sean más antiguas que este límite se borraran automáticamente)
|-
| ''max_image_volume'' || Integer || Máximo número de megabytes utilizados para el almacenamiento de imagenes used to store images en el contexto del [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page Proyecto IMAGING] (una vez alcanzado este límite, las más antiguas se borrarán)
|-
| ''name'' || String || Título que aparece en la parte superior de la pantalla (en la barra de navegación), así como en la lista de trabajo y en los reportes
|-
| ''report_subtitle'' || String || Subtítulo que se utilizará en la lista de trabajo y los reportes
|-
| ''set_sample_delivery_default'' || String || Indica si se asume por defecto que las muestras han sido siempre entregadas o no (los valores aceptados son 'True' y 'False'); poniendolo a 'True' hace que 'Cambiar información' y 'Entrega de muestras' desaparezcan de la barra lateral
|-
| ''show_validate_all_button'' || String || Indica si se mostrará el botón para validar todos los tests de golpe o no (los valores aceptados son 'True' y 'False').
|-

| ''table_default_paging'' || Integer || Indica la paginación inicial de todas las tablas (los valores aceptados son 5, 10 y 25)
|-
| ''table_min_rows_for_search'' || Integer || Mínimo número de filas que una tabla debe tener para mostrar el correspondiente campo de búsqueda
|-
| ''timeout'' || Integer || Tiempo (en minutos) después del cual la conexión con el backend requiere un nuevo inicio de sesión
|-
| ''version'' || String || Versión del Sistema
|-
| ''zip_password'' || String || Palabra clave que será utilizada para generar el fichero zip descargable
|}

System administration

2026-02-26T14:49:26Z

Alberto: /* Parameters */

[[Category:System administration]]
<languages/>
<translate>

This groups all knobs that allow to manage and adapt the behavior of ARIS to the needs of the laboratory and user preferences.
They are grouped in two to facilitate their access.
The first one is more generic and allows both laboratory supervisor and system administration to access some basic stuff.
The second one is only available to the system administrator, since it is considered to require more advance technological skills.


<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border="frame" format="svg">
digraph AdministrationDiagram {
node [shape=oval style=filled fillcolor=orange fontsize="9pt"];
//----- System Administration graph
// Nodes
SystemAdministration [label="System Administration"];
Generic [label="Generic" URL="#Generic"];
Technical [label="Technical" URL="#Technical"];
Users [label="Users" shape=tab URL="#Users"];
AccessLog [label="Access Log" shape=tab URL="#Access_log"];
DownloadedFields [label="Downloaded Fields" shape=tab URL="#Downloaded_fields"];
SummaryOfInstances [label="Summary of Instances" shape=tab URL="#Summary_of_instances"];
Roles [label="Roles" shape=tab URL="#Roles"];
Parameters [label="Parameters" shape=tab URL="#Parameters"];
// Edges
SystemAdministration -> Generic;
SystemAdministration -> Technical;
// Edges
Generic -> Users;
Generic -> AccessLog;
Generic -> DownloadedFields;
// Edges
Technical -> SummaryOfInstances;
Technical -> Roles;
Technical -> Parameters;
}
</graphviz>
</div>


__TOC__


==Generic==
This groups all the basic administration functionalities.
They are available for both the system administration and the laboratory supervisor.


===Users===
[[File:Newuser.PNG|right|thumb|750px|User creation form]]
When clicking on the edit or ''New user'' buttons, a form pops up on the screen. The information necessary to create a user consists of a ''Username'', ''Name'', ''Middle name'', ''password'' and the person's [[#Roles|Role]] within the system.
This Role will determine the functionalities available to the user.
A note, without any effect in the behaviour of the application, can be added to indicate any relevant information to the system administrator.


This same form allows the system administrator to modify the password of any other user.
For security reasons, this password must contain some number, some capital letter, some small letter, and at least eight characters.


Since they are used for auditing changes in patients and requests, the users cannot be deleted from the system.
However, they can be declared not to be active, which would prevent them from logging in, but still keep track in the database of all their past actions.


===Access log===
The ''access log'' shows the user which user has done an action within the system and exactly when. The timestamp is in the format '''Year-Month-Day Hour:Minute:Second'''
[[File:Accesslog.PNG|right|thumb|600px|Example of access log]]</br>
There are three actions recorded by the access log, ''successful log in'', ''wrong user'' and ''failed log in''. This last action refers to the wrong password being used.


===Downloaded fields===
ARIS allows the laboratory supervisor to download all the information in the database into a single file in their computer.
There are two possible download options, depending on the format of the generated file being plain CSV or compressed and password-protected ZIP.
These documents will contain information on the requests, and by extension, on the corresponding patients.
Thus, due to patient confidentiality, not all the personal data should be in the downloaded file.
The checkboxes in this form allow the laboratory supervisor as well as the system administrator to decide which fields will be downloaded in each one of the formats.


Additionally, the system provides two configuration parameters to customize the structure of the CSV file: ''csv_delimiter'', which defines the character used to separate data fields in the CSV file, and ''csv_decimal'', which specifies the character used to represent decimal values in numerical fields. It is essential to configure these parameters according to the settings used by the system and the spreadsheet software (e.g Excel) to ensure proper data interpretation. Using an incorrect delimiter or decimal separator may result in formatting issues when opening the file.


==Technical==
This groups all the more advanced administration functionalities.
They are available only for the system administration.


===Summary of instances===
[[File:Summaryofinstancessmol.PNG|right|250px|thumb|Summary of instances]]
This tab displays information about the different existing instances in the application.
Some examples are: the number of patients, users, requests or genders.
This information comes directly from the database and is automatically updated after every modification in the system.
It can be useful to investigate potential performance problems in case of extremely large numbers.
To facilitate the reading and identification of the different kinds of instances, the information is divided into three sections: ''Data'', ''Administration'' and ''Configuration''.


===Roles===
This tab is displayed and works, in the same way as the [[Configuration#State of the request|State of the request]] tab in the [[Configuration|Configuration]] functionality.
The roles are unchangeable, but their labels (not the corresponding functionality) can be customized.


Each role has different actions allowed within the application, chosen due to the tasks the people are expected to carry out.
Thus, there are five roles within the system, which indicate the functionalities that a user can perform, as can be seen in the following table.


{| class="wikitable" style="margin:auto; text-align: center;"
|+ Allowed functionalities per role
|-
!colspan="2"| Functionalities !! Patient Manager !! Laboratory Technician !! Laboratory Technician with Validation !! Laboratory Supervisor !! System administrator
|-
| style="text-align:left;" rowspan="2" | Patient || style="text-align:left;" | Create || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Search || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="6" | Request || style="text-align:left;" | Create || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Change information || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Deliver samples || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Introduce results || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Validate results || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Search historic || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" colspan="2" | Data analysis || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="2" | Configuration || style="text-align:left;" | Generic || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|-
| style="text-align:left;" | Technical || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="2" | Administration || style="text-align:left;"| Generic || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|-
| style="text-align:left;" | Technical || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|}


===Parameters===
Parameters determine the behaviour of some functionalities.
Thus, they cannot be created or deleted.
However, their values can be updated to customize the system.
At this point it is important to highlight the on updating them, the data type must be respected.
Providing a value of the wrong data type (e.g., a string instead of an integer) can provoke the malfunction of the whole application.


The following table contains the list of existing parameters together with the corresponding data type and a brief description.


{| class="wikitable" style="margin:auto; text-align: left;"
|+ System parameters
|-
! Name !! Data type !! Description
|-
| ''attribute_reserved1'' || String || Label of the first field of free use in the requests (write 'DoNotShow' to hide it)
|-
| ''attribute_reserved2'' || String || Label of the second field of free use in the requests (write 'DoNotShow' to hide it)
|-
| ''attribute_reserved3'' || String || Label of the third field of free use in the requests (write 'DoNotShow' to hide it)
|-
| ''backup_frequency'' || Integer || Minimum amount of hours that need to pass for the system to generate a new copy of the database
|-
| ''backup_history'' || Integer || Maximum number of copies of the database kept (once reached, the oldest copy in the folder is deleted)
|-
| ''bluetooth_enabler'' || String || Indicates the availability of automatic tests through Bluetooth connection (accepted values are 'Enabled' and 'Disabled'), which is only used in the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page IMAGING project]
|-
| ''csv_decimal'' || String || Specifies the character used to represent the decimal point in numerical values in the generated csv file (accepted values are ''.'' and '','')
|-
| ''csv_delimiter'' || String || Specifies the character used to separate fields in the generated csv file (accepted values are '';'' and '','')
|-
| ''default_language'' || String || Language set by default on logging in (the same for all users)
|-
| ''filename_background'' || String || File containing the image displayed in the background
|-
| ''filename_favicon'' || String || Icon of the system used in the browser tab
|-
| ''filename_sidebarlogo'' || String || File containing the logo displayed at the bottom of the sidebar
|-
| ''filename_worklistlogo'' || String || Logo used in the worklist reports
|-
| ''groups_profiles'' || String || Shows groups and profiles for analytical tests (accepted values are 'Enabled' and 'Disabled')
|-
| ''log_history'' || Integer || Maximum number of days to keep registries in the access log (those older than this will be automatically deleted)
|-
| ''max_image_volume'' || Integer || Maximum number of megabytes used to store images (once reached, the oldest ones in the folder are deleted)
|-
| ''name'' || String || Caption to appear at the top of the screen (in the navigation bar), as well as in the worklist and reports
|-
| ''report_subtitle'' || String || Subtitle to be used in the worklist and reports
|-
| ''set_sample_delivery_default'' || String || Indicates whether samples are assumed to be delivered or not by default (accepted values are 'True' and 'False'); setting it to 'True' makes 'Change information' and 'Samples' items in the sidebar be hidden.
|-
| ''show_validate_all_button'' || String || Specifies whether the button to validate all tests at once is visible or not (accepted values are 'True' and 'False').
|-
| ''table_default_paging'' || Integer || Indicates the initial paging of all the tables (accepted values are 5, 10 or 25)
|-
| ''table_min_rows_for_search'' || Integer || Minimum number of rows a table must have to show the corresponding search field
|-
| ''timeout'' || Integer || Time (in minutes) after which the connection to the backend requires a new log in
|-
| ''version'' || String || Version of the system
|-
| ''zip_password'' || String || Password that will be used to generate the downloaded zip file
|}
</translate>

System administration/pt

2026-01-09T11:52:57Z

Alberto:

[[Category:System administration]]
<languages/>
Isso agrupa todos os botões que permitem gerenciar e adaptar o comportamento do ARIS às necessidades do laboratório e às preferências do usuário.
Eles são agrupados em dois para facilitar seu acesso.
O primeiro é mais genérico e permite que tanto o supervisor do laboratório quanto a administração do sistema acessem algumas informações básicas.
O segundo está disponível apenas para o administrador do sistema, pois é considerado como exigindo habilidades tecnológicas mais avançadas.

<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border="frame" format="svg">
digraph AdministrationDiagram {
node [shape=oval style=filled fillcolor=orange fontsize="9pt"];
//----- System Administration graph
// Nodes
SystemAdministration [label="Administração do Sistema"];
Generic [label="Genérico" URL="#Genérico"];
Technical [label="Técnico" URL="#Técnico"];
Users [label="Usuários" shape=tab URL="#Usuários"];
AccessLog [label="Registro de acesso" shape=tab URL="#Access_log"];
DownloadedFields [label="CamposBaixados" shape=tab URL="#Campos_baixados"];
SummaryOfInstances [label="Resumo de Instâncias" shape=tab URL="#Resumo_de_instâncias"];
Roles [label="Roles" shape=tab URL="#Roles"];
Parameters [label="Parâmetros" shape=tab URL="#Parâmetros"];
// Edges
SystemAdministration -> Generic;
SystemAdministration -> Technical;
// Edges
Generic -> Users;
Generic -> AccessLog;
Generic -> DownloadedFields;
// Edges
Technical -> SummaryOfInstances;
Technical -> Roles;
Technical -> Parameters;
}
</graphviz>
</div>

__TOC__

==Genérico==
Isso agrupa todas as funcionalidades básicas de administração.
Eles estão disponíveis tanto para a administração do sistema quanto para o supervisor do laboratório.

===Usuários===
[[File:Newuser.PNG|right|thumb|750px|Formulário de criação de usuário]]
Ao clicar nos botões "Editar" ou "Novo usuário", um formulário é exibido na tela. As informações necessárias para criar um usuário consistem em "Nome de usuário", "Nome", "Nome do meio", "Senha" e a [[#Funções|Função]] da pessoa no sistema.
Esta função determinará as funcionalidades disponíveis para o usuário.
Uma nota, sem qualquer efeito no comportamento do aplicativo, pode ser adicionada para indicar qualquer informação relevante ao administrador do sistema.

Este mesmo formulário permite que o administrador do sistema modifique a senha de qualquer outro usuário.
Por razões de segurança, esta senha deve conter algum número, alguma letra maiúscula, alguma letra minúscula e pelo menos oito caracteres.

Como eles são usados para auditar alterações em pacientes e solicitações, os usuários não podem ser excluídos do sistema.
No entanto, eles podem ser declarados como inativos, o que os impediria de efetuar login, mas ainda assim manteriam um registro no banco de dados de todas as suas ações passadas.

===Registro de acesso===
O "registro de acesso" mostra ao usuário qual usuário realizou uma ação no sistema e exatamente quando. O registro de data e hora está no formato '''Ano-Mês-Dia Hora:Minuto:Segundo'''
[[File:Accesslog.PNG|right|thumb|600px|Exemplo de registro de acesso]]</br>
Há três ações registradas no log de acesso: "login bem-sucedido", "usuário incorreto" e "login com falha". Esta última ação se refere ao uso de uma senha incorreta.

===Campos baixados===
O ARIS permite que o supervisor do laboratório baixe todas as informações do banco de dados em um único arquivo em seu computador.
Há duas opções possíveis de download, dependendo do formato do arquivo gerado: CSV simples ou ZIP compactado e protegido por senha.
Esses documentos conterão informações sobre as solicitações e, por extensão, sobre os pacientes correspondentes.
Portanto, devido à confidencialidade do paciente, nem todos os dados pessoais devem estar no arquivo baixado.
As caixas de seleção neste formulário permitem que o supervisor do laboratório, bem como o administrador do sistema, decidam quais campos serão baixados em cada um dos formatos.

Além disso, o sistema fornece dois parâmetros de configuração para personalizar a estrutura do arquivo CSV: "csv_delimiter", que define o caractere usado para separar os campos de dados no arquivo CSV, e "csv_decimal", que especifica o caractere usado para representar valores decimais em campos numéricos. É essencial configurar esses parâmetros de acordo com as configurações usadas pelo sistema e pelo software de planilha (por exemplo, Excel) para garantir a interpretação correta dos dados. O uso de um delimitador ou separador decimal incorreto pode resultar em problemas de formatação ao abrir o arquivo.

==Técnico==
Isso agrupa todas as funcionalidades de administração mais avançadas.
Eles estão disponíveis apenas para a administração do sistema.

===Resumo de instâncias===
[[File:Summaryofinstancessmol.PNG|right|250px|thumb|Resumo das instâncias]]
Esta aba exibe informações sobre as diferentes instâncias existentes no aplicativo.
Alguns exemplos são: número de pacientes, usuários, solicitações ou gêneros.
Essas informações vêm diretamente do banco de dados e são atualizadas automaticamente após cada modificação no sistema.
Pode ser útil investigar potenciais problemas de desempenho em caso de números extremamente grandes.
Para facilitar a leitura e identificação dos diferentes tipos de instâncias, as informações estão divididas em três seções: ''Dados'', ''Administração'' e ''Configuração''.

===Roles===
Esta aba é exibida e funciona da mesma forma que a aba [[Configuration/pt#Estado_da_solicitação|Estado da solicitação]] na funcionalidade [[Configuration/pt|Configuração]].
As funções são imutáveis, mas seus rótulos (não a funcionalidade correspondente) podem ser personalizados.

Cada função tem diferentes ações permitidas dentro do aplicativo, escolhidas devido às tarefas que as pessoas devem realizar.
Assim, existem cinco papéis dentro do sistema, que indicam as funcionalidades que um usuário pode desempenhar, como pode ser visto na tabela a seguir.

{| class="wikitable" style="margin:auto; text-align: center;"
|+ Funcionalidades permitidas por roles
|-
!colspan="2"| Funcionalidades !! Gerente de Pacientes !! Técnico de Laboratório !! Técnico de Laboratório com Validação !! Supervisor de Laboratório !! Administrador de Sistemas
|-
| style="text-align:left;" rowspan="2" | Paciente || style="text-align:left;" | Criar ||[[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Pesquisar || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="6" | Solicitar || style="text-align:left;" | Criar ||[[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Alterar informações || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Entregar amostras || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Apresentar resultados || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Validar resultados || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Histórico de pesquisa || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" colspan="2" | Análise de dados || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="2" | Configuração || style="text-align:left;" | Genérico || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|-
| style="text-align:left;" | Técnico || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="2" | Administração || style="text-align:left;"| Genérico || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|-
| style="text-align:left;" | Técnico || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|}

===Parâmetros===
Os parâmetros determinam o comportamento de algumas funcionalidades.
Portanto, eles não podem ser criados ou excluídos.
No entanto, seus valores podem ser atualizados para personalizar o sistema.
Neste ponto é importante destacar que ao atualizá-los, o tipo de dado deve ser respeitado.
Fornecer um valor do tipo de dado errado (por exemplo, uma string em vez de um inteiro) pode provocar o mau funcionamento de todo o aplicativo.

A tabela a seguir contém a lista de parâmetros existentes, juntamente com o tipo de dados correspondente e uma breve descrição.

{| class="wikitable" style="margin:auto; text-align: left;"
|+ Parâmetros do sistema
|-
! Nome !! Tipo de dados !! Descrição
|-
| ''attribute_reserved1'' || String || Rótulo do primeiro campo de uso livre nas requisições (escreva 'DoNotShow' para ocultá-lo)
|-
| ''attribute_reserved2'' || String || Rótulo do segundo campo de uso livre nas requisições (escreva 'DoNotShow' para ocultá-lo)
|-
| ''attribute_reserved3'' || String || Rótulo do terceiro campo de uso livre nas requisições (escreva 'DoNotShow' para ocultá-lo)
|-
| ''frequência_de_backup'' || Número inteiro || Quantidade mínima de horas necessárias para que o sistema gere uma nova cópia do banco de dados
|-
| ''backup_history'' || Número inteiro || Número máximo de cópias do banco de dados mantidas (quando atingido, a cópia mais antiga na pasta é excluída)
|-
| ''bluetooth_enabler'' || String || Indica a disponibilidade de testes automáticos por meio de conexão Bluetooth (os valores aceitos são 'Enabled' e 'Disabled'), que é usada apenas no projeto [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page IMAGING]
|-
| ''csv_decimal'' || String || Especifica o caractere usado para representar o ponto decimal em valores numéricos no arquivo CSV gerado (os valores aceitos são ''.'' e '','')
|-
| ''csv_delimiter'' || String || Especifica o caractere usado para separar os campos no arquivo CSV gerado (os valores aceitos são '';'' e '','')
|-
| ''idioma_padrão'' || String || Idioma definido por padrão ao fazer login (o mesmo para todos os usuários)
|-
| ''filename_background'' || String || Arquivo contendo a imagem exibida no fundo
|-
| ''filename_favicon'' || String || Ícone do sistema usado na aba do navegador
|-
| ''filename_sidebarlogo'' || String || Arquivo contendo o logotipo exibido na parte inferior da barra lateral
|-
| ''filename_worklistlogo'' || String || Logotipo usado nos relatórios da lista de trabalho
|-
| ''groups_profiles'' || String || Mostra grupos e perfis para testes analíticos (os valores aceitos são 'Ativado' e 'Desativado')
|-
| ''log_history'' || Número inteiro || Número máximo de dias para manter os registros no log de acesso (os registros mais antigos que este serão excluídos automaticamente)
|-
| ''max_image_volume'' || Número inteiro || Número máximo de megabytes usados para armazenar imagens (quando atingido, as imagens mais antigas da pasta são excluídas)
|-
| ''nome'' || Texto || Legenda a ser exibida na parte superior da tela (na barra de navegação), bem como na lista de tarefas e nos relatórios
|-
| ''report_subtitle'' || String || Subtítulo a ser usado na lista de tarefas e nos relatórios
|-
| ''set_sample_delivery_default'' || String || Indica se as amostras devem ser entregues por defeito ou não (os valores aceites são 'True' e 'False'); definir como 'True' oculta os itens 'Alterar informações' e 'Entregar amostras' na barra lateral
|-
| ''table_default_paging'' || Número inteiro || Indica a paginação inicial de todas as tabelas (os valores aceitos são 5, 10 ou 25)
|-
| ''table_min_rows_for_search'' || Número inteiro || Este é o número mínimo de linhas que uma tabela deve ter para exibir o campo de pesquisa correspondente.
|-
| ''timeout'' || Número inteiro || Tempo (em minutos) após o qual a conexão com o servidor requer um novo login
|-
| ''versão'' || String || Versão do sistema
|-
| ''zip_password'' || String || Esta é a senha que será usada para gerar o arquivo zip baixado
|}

Translations:System administration/15/pt

2026-01-09T11:52:07Z

Alberto:

{| class="wikitable" style="margin:auto; text-align: left;"
|+ Parâmetros do sistema
|-
! Nome !! Tipo de dados !! Descrição
|-
| ''attribute_reserved1'' || String || Rótulo do primeiro campo de uso livre nas requisições (escreva 'DoNotShow' para ocultá-lo)
|-
| ''attribute_reserved2'' || String || Rótulo do segundo campo de uso livre nas requisições (escreva 'DoNotShow' para ocultá-lo)
|-
| ''attribute_reserved3'' || String || Rótulo do terceiro campo de uso livre nas requisições (escreva 'DoNotShow' para ocultá-lo)
|-
| ''frequência_de_backup'' || Número inteiro || Quantidade mínima de horas necessárias para que o sistema gere uma nova cópia do banco de dados
|-
| ''backup_history'' || Número inteiro || Número máximo de cópias do banco de dados mantidas (quando atingido, a cópia mais antiga na pasta é excluída)
|-
| ''bluetooth_enabler'' || String || Indica a disponibilidade de testes automáticos por meio de conexão Bluetooth (os valores aceitos são 'Enabled' e 'Disabled'), que é usada apenas no projeto [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page IMAGING]
|-
| ''csv_decimal'' || String || Especifica o caractere usado para representar o ponto decimal em valores numéricos no arquivo CSV gerado (os valores aceitos são ''.'' e '','')
|-
| ''csv_delimiter'' || String || Especifica o caractere usado para separar os campos no arquivo CSV gerado (os valores aceitos são '';'' e '','')
|-
| ''idioma_padrão'' || String || Idioma definido por padrão ao fazer login (o mesmo para todos os usuários)
|-
| ''filename_background'' || String || Arquivo contendo a imagem exibida no fundo
|-
| ''filename_favicon'' || String || Ícone do sistema usado na aba do navegador
|-
| ''filename_sidebarlogo'' || String || Arquivo contendo o logotipo exibido na parte inferior da barra lateral
|-
| ''filename_worklistlogo'' || String || Logotipo usado nos relatórios da lista de trabalho
|-
| ''groups_profiles'' || String || Mostra grupos e perfis para testes analíticos (os valores aceitos são 'Ativado' e 'Desativado')
|-
| ''log_history'' || Número inteiro || Número máximo de dias para manter os registros no log de acesso (os registros mais antigos que este serão excluídos automaticamente)
|-
| ''max_image_volume'' || Número inteiro || Número máximo de megabytes usados para armazenar imagens (quando atingido, as imagens mais antigas da pasta são excluídas)
|-
| ''nome'' || Texto || Legenda a ser exibida na parte superior da tela (na barra de navegação), bem como na lista de tarefas e nos relatórios
|-
| ''report_subtitle'' || String || Subtítulo a ser usado na lista de tarefas e nos relatórios
|-
| ''set_sample_delivery_default'' || String || Indica se as amostras devem ser entregues por defeito ou não (os valores aceites são 'True' e 'False'); definir como 'True' oculta os itens 'Alterar informações' e 'Entregar amostras' na barra lateral
|-
| ''table_default_paging'' || Número inteiro || Indica a paginação inicial de todas as tabelas (os valores aceitos são 5, 10 ou 25)
|-
| ''table_min_rows_for_search'' || Número inteiro || Este é o número mínimo de linhas que uma tabela deve ter para exibir o campo de pesquisa correspondente.
|-
| ''timeout'' || Número inteiro || Tempo (em minutos) após o qual a conexão com o servidor requer um novo login
|-
| ''versão'' || String || Versão do sistema
|-
| ''zip_password'' || String || Esta é a senha que será usada para gerar o arquivo zip baixado
|}

Requests/pt

2026-01-09T11:35:03Z

Alberto: Created page with "Ao definir o parâmetro ''set_sample_delivery_default'' para ''True'', este formulário desaparece do menu."

[[Category:Requests]]
<languages/>
As solicitações são as entidades mais importantes no ARIS, cujo objetivo principal é gerenciá-las.
Estão sempre associados a um determinado paciente, que deve ter sido criado previamente.

<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph RequestsDiagram {
node [shape="oval" style=filled fillcolor="orange" fontsize="9pt"];
//edge [minlen=2];
//----- Requests graph
// Nodes
Requests [label="Solicitações" ];
Create [label="Criar", URL="#Criar" ];
ChangeInformation [label="Alterar informações", URL="#Alterar_informações"];
PatientsData [label="Dados do Paciente", shape="tab", URL="#Criar"];
AdditionalInformation [label="Informações adicionais", shape="tab", URL="#Criar"];
BiologicalSamples [label="Amostras Biológicas", shape="tab", URL="#Criar" ];
AnalyticalTests [label="Testes Analíticos", shape="tab", URL="#Criar" ];
DeliverSamples [label="Entregar Amostras", URL="#Entregar_amostras" ];
IntroduceResults [label="Apresentar Resultados", URL="#Introduzir_resultados" ];
ValidateResults [label="Validar Resultados", URL="#Validar_resultados"];
SearchHistoric [label="Pesquisar Histórico", URL="#Pesquisar_histórico"];
// Edges
Requests -> Create;
Requests -> ChangeInformation;
Create -> PatientsData;
ChangeInformation -> PatientsData;
PatientsData -> BiologicalSamples [dir=both minlen=2];
BiologicalSamples -> AnalyticalTests [dir=both minlen=2];
AnalyticalTests -> AdditionalInformation [dir=both minlen=2];
Requests -> DeliverSamples
DeliverSamples -> BiologicalSamples;
Requests -> IntroduceResults;
IntroduceResults -> AnalyticalTests;
Requests -> ValidateResults;
ValidateResults -> AnalyticalTests;
Requests -> SearchHistoric;
{ rank=same; Create ChangeInformation DeliverSamples ValidateResults IntroduceResults SearchHistoric}
{ rank=same; PatientsData AnalyticalTests AdditionalInformation BiologicalSamples}
}
</graphviz>
</div>

__TOC__

==Vida útil da solicitação==
<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph StatesDiagram {
node [shape=rectangle style=rounded fontsize="9pt"];
edge [fontsize="7pt"];
//----- Main graph
// Nodes
Begin [label="" shape="circle" style=filled fillcolor=black fixedsize=true width=0.2 height=0.2];
Registered [label="Registrado"];
Processing [label="Processando"];
WithResults [label="Com Resultados"];
Validated [label="Validado"];
Cancelled [label="Cancelado"];
End [label="" shape="doublecircle" style=filled fillcolor="black" fixedsize=true width=0.2 height=0.2];
// Edges
Begin -> Registered [constraint=false];
Registered -> Processing [label="Algumas amostras entregues" constraint=false];
Processing -> WithResults [label="Todos os resultados fornecidos" constraint=false];
WithResults -> Validated [label="Todos os testes validados" constraint=false];
Validated -> End [constraint=false];
Registered -> Cancelled [label="Cancelar"];
Processing -> Cancelled [label="Cancelar"];
WithResults -> Cancelled [label="Cancelar"];
Cancelled -> End [constraint=falso];
{ rank=same; Begin Registered Processing WithResults Validated}
{ rank=same; Cancelled End}
}
</graphviz>
</div>

Durante sua vida útil, as solicitações passam por diferentes estados que determinam as funcionalidades oferecidas a elas no sistema.
Esses estados são representados no diagrama, e seus rótulos são modificáveis e configuráveis em [[Configuration/pt#Estado_da_solicitação|Estado da solicitação]].

Na criação, o estado da solicitação é ''Registrado'', e permite fornecer as informações básicas, bem como associar diferentes testes a ela.
Após indicar que algumas amostras foram entregues, o estado muda para ''Processando'' e os dados da solicitação não podem mais ser modificados.
Outras amostras podem ser entregues posteriormente, mas neste momento, os resultados podem ser fornecidos para os testes cuja amostra já foi entregue.
Quando todos os testes não cancelados tiverem um resultado, o estado da solicitação muda para ''WithResults''.
Nesse estado, os resultados ainda podem ser modificados, mas espera-se que sejam eventualmente validados.
Uma solicitação com todos os seus testes não cancelados sendo validados é considerada ''Validada''.

A qualquer momento, uma solicitação, suas amostras ou seus testes podem ser cancelados.
Uma amostra com todos os seus testes cancelados é considerada cancelada, e uma solicitação com todas as amostras canceladas também é considerada cancelada.

Durante o período de vigência de uma solicitação, ela estará disponível para todos os técnicos de laboratório, exceto a validação, que só poderá ser feita por um supervisor de laboratório ou um técnico de laboratório especialmente autorizado.

==Criar==
[[File:Selectpatient1.PNG|350px|right|thumb|Criar formulário de solicitação]]

Este formulário é dividido em abas. A aba em que o técnico de laboratório está é indicada pela marcação laranja da aba. Acima, encontra-se o campo obrigatório "Centro solicitante", juntamente com o campo adicional "Unidade solicitante" e a caixa de seleção "Urgente". Para criar uma solicitação, siga os seguintes passos:

#Selecionar um paciente → A primeira aba envolve a busca e seleção de um paciente. A grade de busca pode ser refinada com o campo de busca. Após a seleção de um paciente, as informações principais e importantes sobre ele serão exibidas na parte inferior do formulário, em uma tabela. Até que o paciente seja selecionado, o técnico de laboratório não poderá salvar a nova solicitação.
#Testes analíticos | Nesta aba, o técnico de laboratório deve escolher quais testes são solicitados e necessários para o paciente. Grupos e perfis serão exibidos caso o parâmetro [[System administration#Parameters|parameter]] apropriado esteja habilitado. Mais de um elemento de cada lista pode ser selecionado, mas pelo menos um teste deve ser solicitado de uma forma ou de outra. Os testes selecionados como parte de um grupo ou perfil (destacados em roxo) não podem ser desmarcados individualmente.
#Amostras biológicas → Esta aba informa ao técnico de laboratório o tipo de amostra que deve ser coletada, dependendo dos testes selecionados na aba anterior. Não há campos obrigatórios nesta aba, mas se o técnico de laboratório quiser adicionar um comentário, há uma caixa de comentários para cada amostra. [[File:Comments.PNG|1000px]]
#Informações básicas → Nesta aba, outros campos opcionais são fornecidos, como médico, quarto ou leito do paciente. Informações adicionais, como orientação diagnóstica ou estado gestacional, também podem ser indicadas.

Em nenhum momento o botão ''Salvar valores'' poderá ser utilizado caso algum dos campos obrigatórios não esteja preenchido.

==Alterar informações==
[[File:SearchRequest.PNG|350px|right|thumb|Formulário de alteração de informações]]

Este formulário é para edição de solicitações cujas amostras ainda não foram entregues.
Clicar em qualquer parte da linha levará o técnico de laboratório a um formulário semelhante ao [[#Criar|criar]], com todas as suas guias e formato e comportamento semelhantes.

Ao definir o [[System_administration/pt#Parâmetros|parâmetro]] ''set_sample_delivery_default'' para ''True'', este formulário desaparece do menu.

==Entregar amostras==
Semelhante ao formulário anterior, este também exibe uma lista de solicitações ''Registradas'' ou ''Em processamento'', para que o técnico de laboratório escolha uma delas.
[[File:DeliverSamples1.PNG|350px|right|thumb|Formulário de entrega de amostras]]
Após selecionar uma solicitação, cinco abas são exibidas: os dados do paciente, os exames analíticos possivelmente já realizados nesta solicitação, a lista de amostras biológicas, os dados da solicitação e os exames de solicitações anteriores.
Apenas as amostras biológicas permitem alguma interação. As demais são somente leitura (se habilitadas).

Cada uma das amostras mostradas contém um campo para fornecer comentários, e pode ser marcada como entregue ou cancelada clicando no botão vermelho correspondente.
Na entrega de uma amostra, sua origem ou incidência pode ser opcionalmente fornecida.
Ao cancelar, uma caixa de diálogo pop-up é exibida, fornecendo alguma justificativa para isso.

É importante ressaltar que os exames associados à solicitação não poderão ser alterados após a entrega da primeira amostra.

Ao definir o [[System_administration/pt#Parâmetros|parâmetro]] ''set_sample_delivery_default'' para ''True'', este formulário desaparece do menu.

==Apresentar resultados==
Como nos casos anteriores, uma lista de solicitações é exibida.
Neste caso, esta lista contém todas as solicitações no estado ''Processando''.
Clicando no botão correspondente na parte inferior, é possível baixar uma lista de trabalho com todos os exames pendentes nessas solicitações, para trabalhar neles off-line.

[[File:IntroduceResults1.PNG|350px|right|thumb|Formulário para apresentar resultados]]

Após o técnico de laboratório escolher uma solicitação, cinco abas são exibidas com os dados do paciente, sua lista de testes analíticos, sua lista de amostras biológicas, outros dados da solicitação e, potencialmente, testes anteriores do mesmo paciente.
Apenas os testes analíticos permitem alguma interação. Os demais são somente leitura.
Além da mesma caixa de busca presente em todas as tabelas do sistema, há também a possibilidade de filtrar os exames por grupo de exames (caso algum tenha sido escolhido para esta requisição).
Um botão vermelho no canto superior direito permite cancelar a solicitação.

A tabela de testes contém as seguintes colunas:
#Nome → Mostra o nome e o código do tipo de teste. Fica vermelho se o teste ou sua amostra foram cancelados.
#Resultado → Permite introduzir o resultado do teste.
#Nota de teste genérica → Mostra a nota informativa associada ao tipo de teste, se houver.
#Resultado dentro do intervalo → Indica se o resultado do teste está no intervalo esperado de valores para o tipo de teste (marca de verificação verde) ou não (cruz vermelha).
#Referido → Indica se o teste foi feito ou se espera que seja feito em outro laboratório (marca verde) ou não (cruz vermelha).
#Automático (não visível por padrão) → Indica se o teste é realizado ou se espera que seja realizado automaticamente (marca de seleção verde) ou não (cruz vermelha). Os testes automáticos são realizados por meio do [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Microscope:Main Microscópio robótico] e do [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/MobileApp:Main Aplicativo Móvel]. Seus resultados não devem ser digitados manualmente, mas enviados via Bluetooth. Este recurso é habilitado por meio do [[System_administration#Parameters|parâmetro do sistema]] correspondente. Se habilitado, o campo é editável aqui para permitir a substituição dos resultados automáticos.
#O teste tem alguma nota → Indica se o teste tem alguma nota associada (marca verde) ou não (cruz vermelha).
#Detalhes do teste → Este ícone deve permitir a navegação para mais detalhes do teste. No entanto, se o teste ou a amostra correspondente for cancelado, a mensagem correspondente em vermelho será exibida.
#Cancelar teste → Ícone para cancelar o teste. Se o teste for cancelado, um rótulo vermelho "cancelado" aparecerá.

[[File:TestDetails1.PNG|350px|right|thumb|Detalhes do teste]]

Ao o técnico de laboratório acessar os detalhes do teste, temos acesso à visualização de muitas outras coisas (por exemplo, unidades do resultado, medida de referência inferior, medida de referência superior, o usuário que introduziu os resultados, bem como detalhes fornecidos para a amostra correspondente na entrega).
Além disso, isso também permite alterar se o teste é automático ou diferido, indicar alguma incidência na amostra ou fornecer alguma observação (observe que o conteúdo desta observação ficará visível ao paciente no relatório da solicitação).
É importante observar que nenhuma informação fornecida neste formulário será mantida no disco até que seja inserida novamente na lista e salva a partir daí.

Se o resultado do teste foi fornecido automaticamente (o que não é habilitado por padrão e está disponível apenas no contexto do [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page IMAGING project]), a imagem correspondente e sua nota associada serão mostradas na parte inferior dos detalhes do teste.

==Validar resultados==
[[File:Validateresults.mp4|left]]
Esta funcionalidade, disponível apenas para o supervisor do laboratório ou um técnico de laboratório autorizado a validar, utiliza exatamente a mesma interface de introdução de resultados, mas a tabela mostra mais uma coluna, ''Validado'', com uma caixa de seleção para cada teste.
Eles podem ser verificados um por um, ou todos de uma vez, escolhendo um grupo concreto de testes na caixa suspensa na parte superior.
Ao fazer isso, aparecerá um botão para verificar todos os testes do grupo.

Além de fazer isso na lista, os resultados podem ser substituídos e o teste validado a partir dos detalhes do teste.
Além de exibir todas as informações relacionadas ao teste em modo somente leitura, o formulário correspondente também oferece a possibilidade de adicionar uma nota ao teste, bem como alterar se o teste é automático/referenciado ou não, cancelar o teste ou toda a solicitação.

É importante notar que os testes não serão realmente validados até que o botão inferior direito seja pressionado para salvar as alterações.

==Pesquisa histórica==
[[File:Download.mp4|left]]
Esta funcionalidade, disponível tanto para o técnico de laboratório quanto para o supervisor, permite visualizar qualquer solicitação no histórico do laboratório.
Eles podem ser filtrados por estado e data da solicitação.
Ao clicar na linha correspondente, todos os detalhes da solicitação podem ser visualizados.

No canto inferior esquerdo deste formulário, há dois botões de download.
Clicar em qualquer um deles gerará e baixará o arquivo correspondente (por exemplo, CSV ou ZIP).
As caixas de seleção na aba [[System_administration/pt#Campos_baixados|Campos baixados]] indicam quais campos serão incluídos em cada um desses arquivos.
Além disso, o arquivo ZIP é protegido por senha.
A senha utilizada é indicada pelo parâmetro do sistema ''zip_password'', cujo valor pode ser visto e modificado na aba [[System_administration/pt#Parâmetros|Parâmetros]].

Configuration/pt

2026-01-09T11:34:59Z

Alberto: Created page with "A ordem dos valores nas listas suspensas posteriores não será alfabética, mas sim a ordem pela qual foram introduzidos na lista de valores (isto pode ser útil para definir uma ordem, caso existam muitos valores)."

[[Category:Configuration]]
<languages/>
A funcionalidade de configuração permite ao usuário manipular o ARIS, adicionando ou alterando alguns de seus aspectos para uma melhor personalização.
Elas foram divididas em dois grupos, dependendo do conhecimento necessário para utilizá-las.
O primeiro grupo é absolutamente genérico e tanto o supervisor do laboratório quanto o administrador do sistema devem ser capazes de fornecer as informações necessárias.
Entretanto, para o segundo grupo, serão necessários conhecimentos biomédicos mais específicos e, consequentemente, somente o supervisor do laboratório poderá fazê-lo.

<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph ConfigurationDiagram {
nodesep=0.05;
node [shape=oval style=filled fillcolor=orange fontsize="9pt" margin="0.01, 0.01"];
Configuration [label="Configuração"];
ConfGeneric [label="Genérico", URL="#Configuração_genérica"];
ConfTechnical [label="Técnico", URL="#Configuração_técnica"];
Configuration -> ConfGeneric;
Configuration -> ConfTechnical;
Regions [label="Regiões", shape=tab, URL="#Configuração_genérica"];
Locations [label="Locais", shape=tab, URL="#Generic_configuration"];
Units [label="Unidades", shape=tab, URL="#Configuração_genérica"];
HealthFacilities [label="Saúde, Instalações" shape=tab, URL="#Generic_configuration"];
Physicians [label="Médicos", shape=tab, URL="#Configuração_genérica"];
Gender [label="Gênero", shape=tab, URL="#Configuração_genérica"];
IdentificationCards [label="Cartões de Identificação", shape=tab, URL="#Configuração_genérica"];
StateOfTheRequest [label="Estado da solicitação", shape=tab URL="#Estado_da_solicitação"];
ConfGeneric -> Regions;
ConfGeneric -> Locations;
ConfGeneric -> Units;
ConfGeneric -> HealthFacilities;
ConfGeneric -> Physicians;
ConfGeneric -> Gender;
ConfGeneric -> IdentificationCards;
ConfGeneric -> StateOfTheRequest;
LaboratoryAreas [label="Áreas de Laboratório", shape=tab, URL="#Configuração_técnica"];
AnalyticalTests [label="Testes Analíticos", forma=tab URL="#Testes_analíticos"];
AnalyticalTestsGroups [label="Grupos de testes analíticos", shape=tab URL="#Grupos_de_testes analíticos"];
AnalyticalProfiles [label="Perfis Analíticos", shape=tab URL="#Perfis_Analíticos"];
KindsOfSamples [label="Tipos de amostras", shape=tab, URL="#Configuração_técnica"];
SampleIncidents [label="Exemplos de incidentes", shape=tab, URL="#Configuração_técnica"];
SampleOrigins [label="Origens de amostra", shape=tab, URL="#Configuração_técnica"];
PregnancyPhases [label="Fases da Gravidez", shape=tab, URL="#Configuração_técnica"];
DataTypes [label="Tipos de dados", shape=tab, URL="#Tipos_de_dados"];
ReportingOrder [label="Ordem de Relatórios", shape=tab, URL="#Ordem_de_relatório"];
ConfTechnical -> LaboratoryAreas;
ConfTechnical -> AnalyticalTests;
ConfTechnical -> AnalyticalTestsGroups;
ConfTechnical -> AnalyticalProfiles;
ConfTechnical -> KindsOfSamples;
ConfTechnical -> SampleIncidents;
ConfTechnical -> SampleOrigins;
ConfTechnical -> PregnancyPhases;
ConfTechnical -> DataTypes;
ConfTechnical -> ReportingOrder;
{ rank=same; Regions Units Physicians IdentificationCards LaboratoryAreas AnalyticalTestsGroups KindsOfSamples SampleOrigins DataTypes}
{ rank=same; ConfGeneric ConfTechnical}
{ rank=sink; Locations HealthFacilities Gender StateOfTheRequest AnalyticalTests AnalyticalProfiles SampleIncidents PregnancyPhases ReportingOrder}}
</graphviz>
</div>

__TOC__

==Configuração genérica==
[[File:Genericconfiguration.PNG|right|600px|thumb|Editando os rótulos usados para os estados]]
Este formulário controla os valores de todos os campos de texto não livre (ou seja, aqueles que aparecem ao clicar em uma [[User_Guide/pt#Características_gerais|seta]]) no sistema. Em cada aba, o usuário pode criar, editar e excluir os valores de um desses campos.
Caso o laboratório não esteja interessado em um dos valores, mas o usuário não queira excluir as informações do sistema, ele pode ser simplesmente desativado, para que não seja exibido no menu suspenso correspondente. Isso é feito desmarcando a caixa de seleção "Ativo".
Este é um recurso muito importante, pois a exclusão de algum valor de configuração produzirá um efeito sequencial que excluirá todos os outros registros de configuração que apontam para aquele excluído (por exemplo, excluir uma região excluirá todos os seus locais).
Pacientes ou solicitações não serão excluídos, mas as informações correspondentes não serão mais exibidas (por exemplo, após excluir uma região, essas informações no paciente ficarão vazias).</br>
[[File:Activecheckbox.PNG|75px|Caixa de seleção ativada]] ⇔ [[File:Deactivatedcheckbox.PNG|75px|Caixa de seleção desativada]] </br>
Lista de abas:
*Regiões (inicialmente vazias)
*Locais (inicialmente vazios)
*Unidades
*Unidades de Saúde (inicialmente vazias)
*Médicos (inicialmente vazios)
*Gênero
*Cartões de identificação
*Estado da solicitação

Alguns deles também incluem informações hierárquicas. Assim, os médicos apontam para os Centros de saúde, os Centros de saúde apontam para os locais e estes para as regiões. Essas informações são usadas nos formulários para mostrar os valores corretos disponíveis, dependendo da escolha do pai na hierarquia.

===Estado da solicitação===
Na aba "estado da solicitação", apenas o campo "label" pode ser editado. Observe que ele indica as diferentes fases pelas quais uma solicitação passa na aplicação durante seu ciclo de vida, e não apenas um valor passivo a ser armazenado.

==Configuração técnica==
As abas ''Áreas de laboratório'', ''Tipos de amostra'', ''Incidentes de amostra'', ''Origens da amostra'' e ''Fases da gravidez'' têm exatamente o mesmo efeito que as abas da [[#Configuração genérica|configuração genérica]] (ou seja, elas simplesmente fornecem os valores disponíveis em caixas suspensas).
Entretanto, as guias a seguir têm outros efeitos no comportamento dos formulários.

===Testes analíticos===
[[File:Analyticalprofile.PNG|right|thumb|700px| Editando perfis analíticos]]
Este é sem dúvida o conceito mais crucial na configuração, pois define os tipos de testes disponíveis no laboratório.
Eles são identificados por um nome, mas também contêm um código que sempre será exibido ao lado do nome.
Para facilitar a gestão do laboratório, são atribuídos a uma área laboratorial tipos de exames que serão utilizados tanto na geração de relatórios para os pacientes, quanto na análise de dados referentes ao desempenho do próprio laboratório.

Cada tipo de teste está relacionado a um tipo de amostra.
Somente quando o paciente forneça a amostra, é quando o teste relacionado poderá ter resultado associado.

Cada teste deve ter um [[Configuration/pt#Tipos_de_dados|tipo de dado]], que indica o tipo de resultado que ele aceitará, podendo ser numérico (inteiro ou real) ou enumerado.
Para resultados de testes numéricos, as unidades do teste podem ser indicadas para fins informativos, juntamente com limites superiores e inferiores do resultado que podem ser definidos.
Elas serão verificadas automaticamente.
Somente os resultados dentro dos limites declarados receberão uma marca de verificação verde ao lado.
Aqueles fora dos limites serão detectados e automaticamente marcados com uma cruz vermelha.
A validação do valor dependerá de qualquer forma do supervisor do laboratório.
No entanto, uma nota pode ser fornecida aqui para indicar exceções aos limites ou qualquer informação que seja considerada relevante para o técnico ou o supervisor.

Por fim, existem dois campos booleanos específicos:
* Encaminhado → Indica que uma ação ou exame é realizado em outro hospital. A opção marcada na configuração apenas determina o padrão deste campo para cada exame. Não impede que o supervisor do laboratório escolha de forma diferente nos formulários [[Requests/pt|Solicitações]].
* Automático → Permite que o tipo de teste seja parcialmente automatizado. O resultado do teste não é obtido manualmente por uma pessoa, mas por uma IA. Se esta opção estiver desabilitada na configuração, o supervisor do laboratório não poderá marcá-la de outra forma nos formulários [[Requests/pt|Solicitações]]. No entanto, se estiver habilitada, o supervisor do laboratório poderá escolher se deseja que o teste seja feito automaticamente ou não nos formulários [[Requests/pt|Solicitações]].

===Grupos de testes analíticos===
Nesta aba, grupos de exames podem ser formados para uma seleção mais rápida na hora de escolher quais exames realizar em um paciente. Ao criar ou editar um novo grupo, o formulário "Informações do Grupo de Exames" deve ser preenchido ou modificado. Neste formulário, o grupo deve receber um nome e o supervisor do laboratório deve escolher os exames incluídos no grupo na caixa fornecida. Na lista à esquerda, os grupos estão em ordem alfabética e, se o supervisor do laboratório desejar uma opção mais rápida, há uma barra de pesquisa na parte superior da caixa para anotar e filtrar os exames.
Basta clicar no nome de um teste para adicioná-lo ao grupo, aparecendo assim na lista do lado direito.

Os grupos de testes analíticos também são usados para classificar os testes no relatório gerado de uma solicitação.

===Perfis analíticos===
Nesta aba, perfis de testes podem ser formados para uma seleção mais rápida ao escolher quais grupos de testes ou testes individuais realizar em um paciente.
Ao criar ou editar um novo perfil, um formulário ''Informações de Perfil Analítico'' deve ser preenchido ou modificado.
Neste formulário, o perfil deve receber um nome e o supervisor do laboratório deve escolher os testes e os grupos incluídos no perfil nas listas fornecidas.
Os grupos e testes estão em ordem alfabética e, se o supervisor do laboratório desejar uma opção mais rápida, há uma barra de pesquisa na parte superior da caixa para anotar e filtrar os testes e grupos.

A escolha de um grupo seleciona na lista correspondente todos os testes pertencentes a ele.
Então, eles não podem ser removidos individualmente do perfil, mas apenas removendo o grupo.
Além disso, um teste adicionado posteriormente ao grupo aparecerá automaticamente como parte de qualquer perfil que contenha esse grupo, o que é indicado por um ícone de cadeado ao lado do nome do teste.

Perfis analíticos não têm nenhum efeito no relatório gerado para uma solicitação.

<span id="Datatypes"></span>
===Tipos de dados===

Os tipos de dados enumerados podem ser definidos aqui (números inteiros e reais estão sempre disponíveis).
Estas são simplesmente listas de resultados potenciais que podem ser usados em qualquer tipo de teste.

A ordem dos valores nas listas suspensas posteriores não será alfabética, mas sim a ordem pela qual foram introduzidos na lista de valores (isto pode ser útil para definir uma ordem, caso existam muitos valores).

===Ordem de relatório===
[[File:Reportingorder.PNG|Centro|500px|thumb|Editando a ordem das áreas do laboratório na aba de áreas de relatórios]]
Esta aba permite ordenar os elementos na lista de trabalho em PDF e no relatório de uma solicitação.
Os testes que aparecem neles serão primeiramente classificados por área de laboratório, depois por grupos de testes e, por fim, por testes individuais.
É feito escolhendo um dos três elementos, o que levará a outro formulário com uma lista e duas setas verticais no lado esquerdo da imagem.
Qualquer número de elementos pode ser selecionado simultaneamente simplesmente clicando neles.
Então, as setas permitirão movê-los para cima ou para baixo na lista e, consequentemente, nos documentos PDF gerados.

Translations:Configuration/27/pt

2026-01-09T11:34:38Z

A ordem dos valores nas listas suspensas posteriores não será alfabética, mas sim a ordem pela qual foram introduzidos na lista de valores (isto pode ser útil para definir uma ordem, caso existam muitos valores).

Translations:Requests/34/pt

2026-01-09T11:33:38Z

Alberto: Created page with "Ao definir o parâmetro ''set_sample_delivery_default'' para ''True'', este formulário desaparece do menu."

Ao definir o [[System_administration/pt#Parâmetros|parâmetro]] ''set_sample_delivery_default'' para ''True'', este formulário desaparece do menu.

Translations:Requests/33/pt

2026-01-09T11:33:32Z

Alberto: Created page with "Ao definir o parâmetro ''set_sample_delivery_default'' para ''True'', este formulário desaparece do menu."

Ao definir o [[System_administration/pt#Parâmetros|parâmetro]] ''set_sample_delivery_default'' para ''True'', este formulário desaparece do menu.

Translations:System administration/15/pt

2026-01-09T11:30:37Z

Alberto:

{| class="wikitable" style="margin:auto; text-align: left;" |+ Parâmetros do sistema |- ! Nome !! Tipo de dado !! Descrição |- | ''attribute_reserved1'' || String || Rótulo do primeiro campo de uso livre nas requisições (escreva 'DoNotShow' para ocultá-lo) |- | ''attribute_reserved2'' || String || Rótulo do segundo campo de uso livre nas requisições (escreva 'DoNotShow' para ocultá-lo) |- | ''attribute_reserved3'' || String || Rótulo do terceiro campo de uso livre nas requisições (escreva 'DoNotShow' para ocultá-lo) |- | ''backup_frequency'' || Inteiro || Quantidade mínima de horas que precisam passar para o sistema gerar uma nova cópia do banco de dados |- | ''backup_history'' || Inteiro || Número máximo de cópias do banco de dados mantidas (uma vez atingido, a cópia mais antiga na pasta é excluída) |- | ''bluetooth_enabler'' || String || Indica a disponibilidade de testes automáticos por meio da conexão Bluetooth (os valores aceitos são 'Habilitado' e 'Desabilitado'), que é usada somente no [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page projeto IMAGING] |- | ''csv_decimal'' || String || Especifica o caractere usado para representar o ponto decimal em valores numéricos no arquivo csv gerado (os valores aceitos são ''.'' e '','') |- | ''csv_delimiter'' || String || Especifica o caractere usado para separar campos no arquivo csv gerado (os valores aceitos são '';'' e '','') |- | ''default_language'' || String || Idioma definido por padrão no login (o mesmo para todos os usuários) |- | ''filename_background'' || String || Arquivo contendo a imagem exibida em segundo plano |- | ''filename_favicon'' || String || Ícone do sistema usado na aba do navegador |- | ''filename_sidebarlogo'' || String || Arquivo contendo o logotipo exibido na parte inferior da barra lateral |- | ''filename_worklistlogo'' || String || Logotipo usado nos relatórios da lista de trabalho |- | ''groups_profiles'' || String || Mostra grupos e perfis para testes analíticos (os valores aceitos são 'Habilitado' e 'Desabilitado') |- | ''log_history'' || Inteiro || Número máximo de dias para manter registros no log de acesso (aqueles mais antigos que isso serão excluídos automaticamente) |- | ''max_image_volume'' || Inteiro || Número máximo de megabytes usados para armazenar imagens (uma vez atingido, os mais antigos na pasta são excluídos) |- | ''name'' || String || Legenda a ser exibida na parte superior da tela (na barra de navegação), bem como na lista de trabalho e nos relatórios |- | ''report_subtitle'' || String || Subtítulo a ser usado na lista de trabalho e nos relatórios
|-
| ''set_sample_delivery_default'' || String || Indica se as amostras devem ser entregues por defeito ou não (os valores aceites são 'True' e 'False'); definir como 'True' oculta os itens 'Alterar informações' e 'Entregar amostras' na barra lateral
|- | ''table_default_paging'' || Inteiro || Indica a paginação inicial de todas as tabelas (os valores aceitos são 5, 10 ou 25) |- | ''table_min_rows_for_search'' || Inteiro || Este é o número mínimo de linhas que uma tabela deve ter para mostrar o campo de pesquisa correspondente |- | ''timeout'' || Inteiro || Tempo (em minutos) após o qual a conexão com o backend requer um novo login |- | ''version'' || String || Versão do sistema |- | ''zip_password'' || String || Esta é a senha que será usada para gerar o arquivo zip baixado |}

Requests/es

2026-01-08T17:50:38Z

Alberto: Created page with "Poniendo el parámetro ''set_sample_delivery_default'' a ''True'', este formulario desaparece del menú lateral."

[[Category:Requests]]
<languages/>
La gestión de las solicitudes es el proceso más importante que realiza ARIS, siendo éste el objetivo principal de la aplicación.
Las solicitudes siempre están asociadas a un paciente determinado, que debe haber sido creado previamente.

<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph RequestsDiagram {
node [shape="oval" style=filled fillcolor="orange" fontsize="9pt"];
//edge [minlen=2];
//----- Requests graph
// Nodes
Requests [label="Solicitudes" ];
Create [label="Creación de Solicitud", URL="#Creación_de_Solicitud"];
ChangeInformation [label="Cambiar Información", URL="#Cambiar_información"];
PatientsData [label="Datos del Paciente", shape="tab", URL="#Creación_de_Solicitud"];
AdditionalInformation [label="Información Adicional", shape="tab", URL="#Creación_de_Solicitud"];
BiologicalSamples [label="Muestras Biológicas", shape="tab", URL="#Creación_de_Solicitud"];
AnalyticalTests [label="Tests Analíticos", shape="tab", URL="#Creación_de_Solicitud"];
DeliverSamples [label="Entrega de Muestras", URL="#Entrega_de_muestras" ];
IntroduceResults [label="Introducción de los Resultados", URL="#Introducción_de_los_resultados" ];
ValidateResults [label="Validar Resultados", URL="#Validar_resultados"];
SearchHistoric [label="Buscar en el Histórico", URL="#Buscar_en_el_histórico"];
// Edges
Requests -> Create;
Requests -> ChangeInformation;
Create -> PatientsData;
ChangeInformation -> PatientsData;
PatientsData -> BiologicalSamples [dir=both minlen=2];
BiologicalSamples -> AnalyticalTests [dir=both minlen=2];
AnalyticalTests -> AdditionalInformation [dir=both minlen=2];
Requests -> DeliverSamples
DeliverSamples -> BiologicalSamples;
Requests -> IntroduceResults;
IntroduceResults -> AnalyticalTests;
Requests -> ValidateResults;
ValidateResults -> AnalyticalTests;
Requests -> SearchHistoric;
{ rank=same; Create ChangeInformation DeliverSamples ValidateResults IntroduceResults SearchHistoric}
{ rank=same; PatientsData AnalyticalTests AdditionalInformation BiologicalSamples}
}
</graphviz>
</div>

__TOC__

==Ciclo de vida de la Solicitud ==
<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph StatesDiagram {
node [shape=rectangle style=rounded fontsize="9pt"];
edge [fontsize="7pt"];
//----- Main graph
// Nodes
Begin [label="" shape="circle" style=filled fillcolor=black fixedsize=true width=0.2 height=0.2];
Registered [label="Registrada"];
Processing [label="Procesando"];
WithResults [label="Con Resultados"];
Validated [label="Validada"];
Cancelled [label="Cancelada"];
End [label="" shape="doublecircle" style=filled fillcolor="black" fixedsize=true width=0.2 height=0.2];
// Edges
Begin -> Registered [constraint=false];
Registered -> Processing [label="Alguna muestra entregada" constraint=false];
Processing -> WithResults [label="Todos los resultados disponibles" constraint=false];
WithResults -> Validated [label="Todos los tests validados" constraint=false];
Validated -> End [constraint=false];
Registered -> Cancelled [label="Cancelar"];
Processing -> Cancelled [label="Cancelar"];
WithResults -> Cancelled [label="Cancelar"];
Cancelled -> End [constraint=false];
{ rank=same; Begin Registered Processing WithResults Validated}
{ rank=same; Cancelled End}
}
</graphviz>
</div>

Durante su vida útil, las solicitudes pasan por diferentes estados que determinan las funcionalidades que se les ofrecen en el sistema.
Estos estados se muestran en el diagrama y sus etiquetas se pueden modificar y configurar en [[Configuration/es#Estado_de_la_solicitud|Estado de la Solicitud]].

Al crear una nueva solicitud, el estado en el que aparece es ''Registrada'', y permite proporcionar la información básica, así como asociarle diferentes test.
Después de marcar que algunas de las muestras han sido entregadas, el estado cambia a ''Procesando'' y los datos de la solicitud ya no se pueden modificar.
Se pueden entregar otras muestras más adelante, pero en este punto ya se pueden proporcionar los resultados de los test cuya muestra ya se entregó.
Una vez que todos los test no cancelados tengan un resultado, el estado de la solicitud cambia a ''Con Resultados''.
En este estado, los resultados aún se pueden modificar, mientras se espera que eventualmente se validen.
Una solicitud con todos sus test no cancelados y validados se considera ''Validada''.

En cualquier momento se podrá cancelar una solicitud, sus muestras o sus test.
Una muestra con todas sus pruebas canceladas se considera cancelada y una solicitud con todas sus muestras canceladas también se considera cancelada.

Durante la vida útil de una solicitud, ésta está a disposición de los técnicos de laboratorio, excepto para realizar la validación, que sólo puede ser realizada por un supervisor de laboratorio o un técnico de laboratorio especialmente autorizado para ello.

==Creación de Solicitud==
[[File:Selectpatient1.PNG|350px|right|thumb|Formulario de creación de solicitud]]

Este formulario se divide en pestañas. La pestaña en la que se encuentra el técnico de laboratorio se indica mediante la etiqueta de la pestaña que se pone en color naranja. Encima se encuentra el campo obligatorio “Centro solicitante”, junto con el campo adicional “Unidad solicitante” y la casilla de verificación “Urgente”. Para crear una solicitud se deben realizar los siguientes pasos:

#Seleccionar un paciente → La primera pestaña permite buscar y seleccionar un paciente. La tabla de búsqueda se puede acotar con el campo de búsqueda. Una vez seleccionado un paciente, la información principal más importante sobre este paciente se mostrará en la parte inferior del formulario en una tabla estática. Hasta que no se haya seleccionado el paciente, el técnico de laboratorio no puede guardar la nueva solicitud.
#Pruebas analíticas → En esta pestaña, el técnico de laboratorio debe elegir qué pruebas se solicitan y requieren para el paciente. Los grupos y perfiles aparecerán en caso de que se habilite el [[System administration/es#Parameters#Parámetros|parámetro]] adecuado. Se puede elegir más de un elemento de cada lista, pero al menos un test debe solicitarse de una forma u otra. Los tests seleccionados como parte de un grupo o perfil (resaltados en violeta) no se pueden deseleccionar individualmente.
#Muestras biológicas → Esta pestaña informa al técnico de laboratorio del tipo de muestra que debe tomar, dependiendo de las pruebas elegidas en la pestaña anterior. No hay campos obligatorios en esta pestaña, pero si el técnico de laboratorio desea agregar un comentario, hay un cuadro de comentarios para cada muestra. [[File:Comments.PNG|1000px]]
#Información básica → En esta pestaña, se proporcionan otros campos opcionales como el médico, la habitación o la cama del paciente. También se puede indicar información adicional como una orientación diagnóstica o el estado de embarazo.

En todo momento, no se podrá utilizar el botón “Guardar valores” si alguno de los campos obligatorios no está rellenado.

==Cambiar información==
[[File:SearchRequest.PNG|350px|right|thumb|Formulario de cambio de información]]

Este formulario es para editar solicitudes cuyas muestras aún no se han entregado.
Al hacer clic en cualquier parte de la fila, el técnico de laboratorio accederá a un formulario similar al de [[#Creación_de_Solicitud|Creación de Solicitud]], con todas sus pestañas y formato y comportamiento similar.

Poniendo el [[System_administration/es#Parámetros|parámetro]] ''set_sample_delivery_default'' a ''True'', este formulario desaparece del menú lateral.

==Entrega de muestras==
Al igual que el formulario anterior, este también muestra una lista de solicitudes ''Registradas'' o ''Procesando'', para que el técnico de laboratorio elija una de ellas.
[[File:DeliverSamples1.PNG|350px|right|thumb|Formulario de entrega de muestras]]
Una vez elegida una solicitud, se muestran cinco pestañas: Los datos del paciente, las posibles pruebas analíticas ya realizadas en esta solicitud, su lista de muestras biológicas, los datos de la solicitud y las pruebas de solicitudes anteriores.
Solo las muestras biológicas permiten cierta interacción. Las demás son de solo lectura (si están habilitadas).

Cada una de las muestras mostradas contiene un campo para proporcionar comentarios, y se puede marcar como entregada o cancelar haciendo clic en el botón rojo correspondiente.
A la entrega de una muestra se podrá indicar opcionalmente su origen o alguna incidencia detectada en la misma.
Al cancelar, un cuadro de diálogo emergente permite proporcionar alguna justificación para hacerlo.

Es importante tener en cuenta que los test asociados a la solicitud no se pueden cambiar una vez entregada la primera muestra.

Poniendo el [[System_administration/es#Parámetros|parámetro]] ''set_sample_delivery_default'' a ''True'', este formulario desaparece del menú lateral.

==Introducción de los resultados==
Como en los casos anteriores, se muestra una lista de solicitudes.
En esta lista todas las solicitudes se encuentran en estado ''Procesando''.
Al hacer clic en el botón correspondiente en la parte inferior, es posible descargar una lista de trabajo con todas las pruebas pendientes en estas solicitudes, para trabajar en ellas fuera de línea.

[[File:IntroduceResults1.PNG|350px|right|thumb|Formulario de introducción de resultados]]

Una vez que el técnico de laboratorio elige una solicitud, se muestran cinco pestañas con los datos del paciente, su lista de tests analíticos, su listado de muestras biológicas, y potencialmente los test previos del mismo paciente.
Las primeras tres pestañas y la última son sólo de lectura.
Sólo las pruebas analíticas permiten cierta interacción. El resto de pestañas son de solo lectura.
Además de la misma casilla de búsqueda presente en todas las tablas del sistema, también existe la posibilidad de filtrar los test por grupo de test (si se eligió algún grupo para esta solicitud).
Un botón rojo en la esquina superior derecha permite cancelar la solicitud.

La tabla de test contiene las siguientes columnas.
#Nombre → Muestra el nombre y el código del tipo de test. Se colorea de rojo si se canceló el test o su muestra.
#Resultado → Permite introducir el resultado del test.
#Generic test note → Muestra la nota informativa asociada al tipo de test, si la hubiera.
#Resultado dentro de rango → Indica si el resultado de la prueba está en el rango de valores esperado para el tipo de prueba (check verde) o no (cruz roja).
#Referido → Indica si la prueba se realiza o se espera que se realice en otro laboratorio (check verde) o no (cruz roja).
#Automático (no visible por defecto) → Indica si la prueba se realiza o se espera que se realice automáticamente (check verde) o no (cruz roja). Las pruebas automáticas se realizan mediante el [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Microscope:Main Microscopio robotizado] y el [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/MobileApp:Main Aplicación móbil]. Sus resultados no deben escribirse manualmente, sino cargarse a través de Bluetooth. Esta característica se habilita a través del correspondiente [[System_administration/es#Parámetros|parámetro del sistema]]. Si está habilitado, el campo se puede editar aquí para permitir sobrescribir los resultados automáticos.
#La prueba tiene alguna nota→ Indica si la prueba tiene alguna nota asociada (check verde) o no (cruz roja). Las pruebas cuyos resultados se generaron automáticamente siempre tendrán una nota asociada.
#Detalles del test → Esto debería mostrar un icono para navegar a más detalles del test. Sin embargo, si el test o su correspondiente muestra fue cancelada, se mostrará el mensaje correspondiente en rojo.
#Cancelar prueba→ Icono para cancelar la prueba. Si se cancela la prueba, aparece una etiqueta roja que dice "Cancelado".

[[File:TestDetails1.PNG|350px|right|thumb|Detalles del test]]

Al acceder el técnico de laboratorio a los detalles del test, se pueden visualizar muchas otras cosas (como unidades del resultado, medida de referencia inferior, medida de referencia superior, el usuario que introdujo los resultados, así como los detalles proporcionados para la correspondiente muestra al entregarla).
Además, esto también permite cambiar si el test es automático o diferido, indicar alguna incidencia en la muestra, o añadir alguna nota (nótese que el contenido de esta nota será visible para el paciente en el reporte de la petición).
Es importante tener en cuenta que la información proporcionada en este formulario no se conservará en el disco hasta que vuelva a la lista y se guarde desde allí.

Si el resultado del test se proporcionó automáticamente (no está habilitado de forma predeterminada y solo está disponible en el contexto del [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page Proyecto IMAGING]), la imagen correspondiente y su nota asociada se mostrarán en la parte inferior del detalle del test.

==Validar resultados==
[[File:Validateresults.mp4|left]]
Esta funcionalidad, disponible sólo para el supervisor del laboratorio o un tècnico especialmente autorizado para ello, utiliza exactamente la misma interfaz que la introducción de resultados, pero la tabla muestra una columna más, ''Validado'', con una casilla de verificación para cada test.
Estos se pueden verificar uno por uno o todos a la vez eligiendo un grupo concreto de test en el cuadro desplegable en la parte superior.
Al hacer esto último aparecerá un botón para consultar todos los test del grupo.

Además de poder sobrescribir y validar los resultados en la lista, también se puede hacer desde los detalles del test.
Junto a mostrar toda la información relacionada con el test en modo de solo lectura, el formulario correspondiente también ofrece la posibilidad de añadir una nota al test, así como cambiar si el test es automático o referido, cancelar el test o la solicitud completa.

Es importante tener en cuenta que los test no quedarán realmente validados hasta que se presione el botón inferior derecho para guardar los cambios.

==Buscar en el histórico==
[[File:Download.mp4|left]]
Esta funcionalidad, disponible tanto para el técnico de laboratorio como para el supervisor, permite ver cualquier solicitud en el historial del laboratorio.
Se pueden filtrar por estado y por fecha de la solicitud.
Al hacer clic en la fila correspondiente se podrán visualizar todos los detalles de la solicitud.

En la parte inferior izquierda de este formulario, hay dos botones de descarga.
Al hacer clic en cualquiera de ellos, se generará y descargará el archivo correspondiente (es decir, CSV o ZIP).
Las casillas de verificación en la pestaña [[System_administration/es#Campos_descargados|Campos Descargados]] indican qué campos se incluirán en cada uno de estos archivos.
Además, el archivo ZIP está protegido con contraseña.
La contraseña utilizada viene indicada por el parámetro del sistema ''zip_password'', cuyo valor se puede ver y modificar desde la pestaña [[System_administration/es#Parámetros|Parámetros]].
Adicionalmente, el separador de campos y el punto decimal utilizado en el fichero CSV también se pueden configurar en la misma pestaña.

Translations:Requests/33/es

2026-01-08T17:48:12Z

Alberto:

Poniendo el [[System_administration/es#Parámetros|parámetro]] ''set_sample_delivery_default'' a ''True'', este formulario desaparece del menú lateral.

Translations:Requests/34/es

2026-01-08T17:48:07Z

Alberto: Created page with "Poniendo el parámetro ''set_sample_delivery_default'' a ''True'', este formulario desaparece del menú lateral."

Poniendo el [[System_administration/es#Parámetros|parámetro]] ''set_sample_delivery_default'' a ''True'', este formulario desaparece del menú lateral.

Translations:Requests/33/es

2026-01-08T17:47:46Z

Alberto: Created page with "Poniendo el parámetro ''set_sample_delivery_default'' a ''True'' este formulario desaparece del menú lateral."

Poniendo el [[System_administration/es#Parámetros|parámetro]] ''set_sample_delivery_default'' a ''True'' este formulario desaparece del menú lateral.

Translations:System administration/15/es

2026-01-08T17:46:03Z

Alberto:

{| class="wikitable" style="margin:auto; text-align: left;"
|+ Parámetros del Sistema
|-
! Nombre !! Tipo de Datos !! Descripción
|-
| ''attribute_reserved1'' || String || Etiqueta del primer campo de uso discrecional en las solicitudes (escribe 'DoNotShow' para ocultarlo)
|-
| ''attribute_reserved2'' || String || Etiqueta del segundo campo de uso discrecional en las solicitudes (escribe 'DoNotShow' para ocultarlo)
|-
| ''attribute_reserved3'' || String || Etiqueta del tercer campo de uso discrecional en las solicitudes (escribe 'DoNotShow' para ocultarlo)
|-
| ''backup_frequency'' || Integer || Mínimo número de horas que deben pasar para que el sistema vuelva a generar una copia de seguridad
|-
| ''backup_history'' || Integer || Máximo número de copias de seguridad de la base de datos que se guardan (una vez alcanzado este número, la copia más antigua se borrará)
|-
| ''bluetooth_enabler'' || String || Indica la disponibilidad de test automáticos a través de conexión Bluetooth (los valores aceptados son 'Enabled' y 'Disabled'), lo cual se utiliza únicamente en el contexto del [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page Proyecto IMAGING]
|-
| ''csv_decimal'' || String || Especifica el carácter utilizado para representar el punto decimal en valores numéricos en el archivo CSV generado (valores aceptados: '.' y ',').
|-
| ''csv_delimiter'' || String || Especifica el carácter utilizado para separar los campos en el archivo CSV generado (valores aceptados: ';' y ',').
|-
| ''default_language'' || String || Idioma establecido por defecto al iniciar la sesión (será el mismo para todos los usuarios)
|-
| ''filename_background'' || String || Fichero que contiene la imagen de fondo
|-
| ''filename_favicon'' || String || Icono del sistema usado en la correspondiente pestaña del navegador
|-
| ''filename_sidebarlogo'' || String || Fichero que contiene el logo mostrado en la parte superior de la barra lateral
|-
| ''filename_worklistlogo'' || String || Logo utilizado en la lista de trabajo y reportes
|-
| ''group_profiles'' || String || Muestra los grupos y perfiles de tests analíticos (los valores aceptados son 'Enabled' y 'Disabled')
|-
| ''log_history'' || Integer || Número máximo de días que se guardarán las entradas en el registro de acceso (las que sean más antiguas que este límite se borraran automáticamente)
|-
| ''max_image_volume'' || Integer || Máximo número de megabytes utilizados para el almacenamiento de imagenes used to store images en el contexto del [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page Proyecto IMAGING] (una vez alcanzado este límite, las más antiguas se borrarán)
|-
| ''name'' || String || Título que aparece en la parte superior de la pantalla (en la barra de navegación), así como en la lista de trabajo y en los reportes
|-
| ''report_subtitle'' || String || Subtítulo que se utilizará en la lista de trabajo y los reportes
|-
| ''set_sample_delivery_default'' || String || Indica si se asume por defecto que las muestras han sido siempre entregadas o no (los valores aceptados son 'True' y 'False'); poniendolo a 'True' hace que 'Cambiar información' y 'Entrega de muestras' desaparezcan de la barra lateral
|-
| ''table_default_paging'' || Integer || Indica la paginación inicial de todas las tablas (los valores aceptados son 5, 10 y 25)
|-
| ''table_min_rows_for_search'' || Integer || Mínimo número de filas que una tabla debe tener para mostrar el correspondiente campo de búsqueda
|-
| ''timeout'' || Integer || Tiempo (en minutos) después del cual la conexión con el backend requiere un nuevo inicio de sesión
|-
| ''version'' || String || Versión del Sistema
|-
| ''zip_password'' || String || Palabra clave que será utilizada para generar el fichero zip descargable
|}

Requests

2026-01-08T17:40:56Z

Alberto: Marked this version for translation

[[Category:Requests]]
<languages/>
<translate>

Requests are the most important entities in ARIS, whose main purpose is to manage them.
They are always associated to a given patient, who must have been created before hand.


<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph RequestsDiagram {
node [shape="oval" style=filled fillcolor="orange" fontsize="9pt"];
//edge [minlen=2];
//----- Requests graph
// Nodes
Requests [label="Requests" ];
Create [label="Create", URL="#Create" ];
ChangeInformation [label="Change Information", URL="#Change_information"];
PatientsData [label="Patients' Data", shape="tab", URL="#Create"];
AdditionalInformation [label="Additional Information", shape="tab", URL="#Create"];
BiologicalSamples [label="Biological Samples", shape="tab", URL="#Create" ];
AnalyticalTests [label="Analytical Tests", shape="tab", URL="#Create" ];
DeliverSamples [label="Deliver Samples", URL="#Deliver_samples" ];
IntroduceResults [label="Introduce Results", URL="#Introduce_results" ];
ValidateResults [label="Validate Results", URL="#Validate_results"];
SearchHistoric [label="Search Historic", URL="#Search_historic"];
// Edges
Requests -> Create;
Requests -> ChangeInformation;
Create -> PatientsData;
ChangeInformation -> PatientsData;
PatientsData -> BiologicalSamples [dir=both minlen=2];
BiologicalSamples -> AnalyticalTests [dir=both minlen=2];
AnalyticalTests -> AdditionalInformation [dir=both minlen=2];
Requests -> DeliverSamples;
DeliverSamples -> BiologicalSamples;
Requests -> IntroduceResults;
IntroduceResults -> AnalyticalTests;
Requests -> ValidateResults;
ValidateResults -> AnalyticalTests;
Requests -> SearchHistoric;
{ rank=same; Create ChangeInformation DeliverSamples ValidateResults IntroduceResults SearchHistoric}
{ rank=same; PatientsData AnalyticalTests AdditionalInformation BiologicalSamples }
}
</graphviz>
</div>


__TOC__


==Request Lifespan==
<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph StatesDiagram {
node [shape=rectangle style=rounded fontsize="9pt"];
edge [fontsize="7pt"];
//----- Main graph
// Nodes
Begin [label="" shape="circle" style=filled fillcolor=black fixedsize=true width=0.2 height=0.2];
Registered [label="Registered"];
Processing [label="Processing"];
WithResults [label="WithResults"];
Validated [label="Validated"];
Cancelled [label="Cancelled"];
End [label="" shape="doublecircle" style=filled fillcolor="black" fixedsize=true width=0.2 height=0.2];
// Edges
Begin -> Registered [constraint=false];
Registered -> Processing [label="Some sample delivered" constraint=false];
Processing -> WithResults [label="All results provided" constraint=false];
WithResults -> Validated [label="All tests validated" constraint=false];
Validated -> End [constraint=false];
Registered -> Cancelled [label="Cancel"];
Processing -> Cancelled [label="Cancel"];
WithResults -> Cancelled [label="Cancel"];
Cancelled -> End [constraint=false];
{ rank=same; Begin Registered Processing WithResults Validated}
{ rank=same; Cancelled End}
}
</graphviz>
</div>


During their lifespan, requests go through some different states that determine the functionalities offered for them in the system.
These states are depicted in the diagram, and their labels are modifaiable and configurable at [[Configuration#State_of_the_request|State of the request]].


On creation, the state of the request is ''Registered'', and allows to provide the basic information, as well as associate different tests to it.
After indicating that some of the samples have been delivered, the state changes to ''Processing'' and the data of the request cannot be modified anymore.
Other samples can be delivered later, but at this point, results can be provided for the tests whose sample was already delivered.
Once all non-cancelled tests have a result, the state of the request changes to ''WithResults''.
At this state, results can still be modified, but they are expected to be eventually validated.
A request with all its non-cancelled tests being validated is considered ''Validated''.


At any time, a request, its samples or its tests can be cancelled.
A sample with all its tests cancelled is considered cancelled, and a request with all samples cancelled is considered cancelled, too.


During the lifespan of a request, it is available to all the laboratory technicians, except for the validation, which can only be done by a laboratory supervisor or a specially authorized laboratory technician.


==Create==
[[File:Selectpatient1.PNG|350px|right|thumb|Create request form]]


This form is divided into tabs. The tab the laboratory technician is on is indicated by the label of the tab turning orange. Above, it can be found the ''Requesting centre'' mandatory field, alongside with the additional ''Requesting unit'' field and the ''Urgent'' checkbox. To create a request, the following steps must be executed:


#Select a patient → The first tab involves searching and selecting a patient. The search grid can be narrowed down with the search field. Once a patient is selected, the main and important information about this patient will be displayed at the bottom of the form in a table. Until the patient has been selected, the laboratory technician cannot save the new request.
#Analytical tests → In this tab, the laboratory technician must choose which tests are requested and required for the patient. Groups and profiles will appear in case the proper [[System administration#Parameters|parameter]] is enabled. More than one element from each list may be chosen, but at least one test must be requested one way or another. Tests selected as part of a group or profile (highlighted in purple) cannot be deselected individually.
#Biological samples → This tab informs the laboratory technician of the type of sample that must be taken, depending on the tests chosen in the previous tab. There are no required fields in this tab, but if the laboratory technician wants to add a comment, there is a comment box for each sample. [[File:Comments.PNG|1000px]]
#Basic information → In this tab, other optional fields are provided like physician, the room or bed of the patient. Additional information like a diagnostic orientation or the pregnancy status can also be indicated.


At any moment, the ''Save values'' button cannot be used if any of the required fields is not filled in.


==Change information==
[[File:SearchRequest.PNG|350px|right|thumb|Change information form]]


This form is for editing requests whose samples were not yet delivered.
Clicking on any part of the row will bring the laboratory technician to a form similar to the [[#Create|create]] one, with all of its tabs and similar format and behavior.


By setting the [[System administration#Parameters|parameter]] ''set_sample_delivery_default'' to ''True'' this form disappears from the menu.


==Deliver samples==
Similarly to the previous form, this also displays a list of either ''Registered'' or ''Processing'' requests, for the laboratory technician to choose one of them.
[[File:DeliverSamples1.PNG|350px|right|thumb|Deliver samples form]]
Once a request is chosen, five tabs are shown. The patient's data, potentially analytical tests already done in this request, its list of biological samples, the request data, and tests in previous requests.
Just the biological samples allows some interaction. The other ones are read-only (if enabled at all).


Each of the samples shown contains a field to provide comments, and it can be either checked as delivered or cancelled by click the corresponding red button.
On the delivering of a sample, its origin or incident can be optionally provided.
On cancelling, a pop-up dialogue allows, providing some justification for this.


It is important to notice that the tests associated to the request cannot be changed once the first sample as been delivered.


By setting the [[System administration#Parameters|parameter]] ''set_sample_delivery_default'' to ''True'' this form disappears from the menu.


==Introduce results==
As in the previous cases, a list of requests is shown.
In this case, this list contains all requests in ''Processing'' state.
Clicking the corresponding button at the bottom, it is possible to download a worklist with all pending tests in these requests, to work on them off-line.


[[File:IntroduceResults1.PNG|350px|right|thumb|Form to Introduce Results]]


Once the laboratory technician has chosen a request, five tabs are shown with the patient's data, its list of analytical tests, its list of biological samples, other request data, and potentially previous tests of the same patient.
Just the analytical tests allows some interaction. The other ones are read-only.
Besides the same search box present in all the tables in the system, there is also the possibility of filtering the tests by group of tests (if any was chosen for this request).
A red button in the top right corner allows cancelling the request.


The table of tests contains the following columns:
#Name → Shows the name and the code of the kind of test. It is coloured red if either the test or its sample was cancelled.
#Result → Allows to introduce the result of the test.
#Generic test note → Shows the informative note associated to the kind of test, if any.
#Result within range → Indicates whether the result of the test is in the expected range of values for the kind of test (green check) or not (red cross).
#Referred → Indicates whether the test is done or expected to be done in another laboratory (green check) or not (red cross).
#Automatic (not visible by default) → Indicates whether the test is done or expected to be done automatically (green check) or not (red cross). Automatic tests are done by means of the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Microscope:Main Robotized microscope] and the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/MobileApp:Main Mobile App]. Their results should not be typed manually, but uploaded through Bluetooth. This feature is enabled through the corresponding [[System_administration#Parameters|system parameter]]. If enabled, the field is editable here to allow overwriting the automatic results.
#The test has some note → Indicates whether the test has some associated note (green check) or not (red cross).
#Test details → This should show an icon to navigate to further details of the test. However, if the test or its corresponding sample was cancelled, the corresponding message in red will be shown.
#Cancel test → Icon to cancel the test. If the test is cancelled. A red ''cancelled'' label appears.


[[File:TestDetails1.PNG|350px|right|thumb|Test details]]


On the laboratory technician accessing the details of the test, we gain access to visualize many other things (i.e., units of the result, inferior reference measure, superior reference measure, the user who introduced the results, as well as details provided for the corresponding sample on delivering it).
Moreover, this also allows changing if the test is automatic or deferred, indicate some incidence on the sample, or provide some note (notice that the content of this note will be visible to the patient in the report of the request).
It is important to notice that any of the information provided in this form will not be persisted in the disk until back in the list and saved from there.


If the result of the test was provided automatically (which is not enabled by default and only available in the context of the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page IMAGING project]), the corresponding image and its associated note will be shown at the bottom of the details of the test.


==Validate results==
[[File:Validateresults.mp4|left]]
This functionality, available only to the laboratory supervisor or a laboratory technician authorized to validate, uses exactly the same interface as introducing results, but the table shows one more column, ''Validated'', with a checkbox for each test.
These can be checked one by one, or all at once, by choosing a concrete group of tests in the dropbox at the top.
On doing the latter, a button to check all the tests of the group will appear.


Besides doing it in the list, the results can be overwritten and the test validated from the details of the test.
Together with displaying all the information related to the test in read-only mode, the corresponding form also offers the possibility of adding a note to the test, as well as changing whether the test is automatic/referred or not, cancelling the test or the whole request.


It is important to notice that the tests will not be really validated until the bottom right button is pressed to save the changes.


==Search historic==
[[File:Download.mp4|left]]
This functionality, available to both laboratory technician and supervisor allows to see any request in the history of the laboratory.
They can be filtered out by the state and the date of the request.
By clicking on the corresponding row, all the details of the request can be visualized.


At the bottom left of this form, there are two download buttons.
Clicking any of them will generate and download the corresponding file (i.e., CSV or ZIP).
The checkboxes in the [[System administration#Downloaded fields|Downloaded fields]] tab indicate which fields will be included in each of these files.
Moreover, the ZIP file is password protected.
The password used is indicated by the system parameter ''zip_password'', whose value can be seen and modified from [[System administration#Parameters|Parameters]] tab.
Additionally, the field separator and decimal characters used in the CSV file can also be configured in the same tab.
</translate>

System administration

2026-01-08T17:39:45Z

Alberto: Marked this version for translation

[[Category:System administration]]
<languages/>
<translate>

This groups all knobs that allow to manage and adapt the behavior of ARIS to the needs of the laboratory and user preferences.
They are grouped in two to facilitate their access.
The first one is more generic and allows both laboratory supervisor and system administration to access some basic stuff.
The second one is only available to the system administrator, since it is considered to require more advance technological skills.


<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border="frame" format="svg">
digraph AdministrationDiagram {
node [shape=oval style=filled fillcolor=orange fontsize="9pt"];
//----- System Administration graph
// Nodes
SystemAdministration [label="System Administration"];
Generic [label="Generic" URL="#Generic"];
Technical [label="Technical" URL="#Technical"];
Users [label="Users" shape=tab URL="#Users"];
AccessLog [label="Access Log" shape=tab URL="#Access_log"];
DownloadedFields [label="Downloaded Fields" shape=tab URL="#Downloaded_fields"];
SummaryOfInstances [label="Summary of Instances" shape=tab URL="#Summary_of_instances"];
Roles [label="Roles" shape=tab URL="#Roles"];
Parameters [label="Parameters" shape=tab URL="#Parameters"];
// Edges
SystemAdministration -> Generic;
SystemAdministration -> Technical;
// Edges
Generic -> Users;
Generic -> AccessLog;
Generic -> DownloadedFields;
// Edges
Technical -> SummaryOfInstances;
Technical -> Roles;
Technical -> Parameters;
}
</graphviz>
</div>


__TOC__


==Generic==
This groups all the basic administration functionalities.
They are available for both the system administration and the laboratory supervisor.


===Users===
[[File:Newuser.PNG|right|thumb|750px|User creation form]]
When clicking on the edit or ''New user'' buttons, a form pops up on the screen. The information necessary to create a user consists of a ''Username'', ''Name'', ''Middle name'', ''password'' and the person's [[#Roles|Role]] within the system.
This Role will determine the functionalities available to the user.
A note, without any effect in the behaviour of the application, can be added to indicate any relevant information to the system administrator.


This same form allows the system administrator to modify the password of any other user.
For security reasons, this password must contain some number, some capital letter, some small letter, and at least eight characters.


Since they are used for auditing changes in patients and requests, the users cannot be deleted from the system.
However, they can be declared not to be active, which would prevent them from logging in, but still keep track in the database of all their past actions.


===Access log===
The ''access log'' shows the user which user has done an action within the system and exactly when. The timestamp is in the format '''Year-Month-Day Hour:Minute:Second'''
[[File:Accesslog.PNG|right|thumb|600px|Example of access log]]</br>
There are three actions recorded by the access log, ''successful log in'', ''wrong user'' and ''failed log in''. This last action refers to the wrong password being used.


===Downloaded fields===
ARIS allows the laboratory supervisor to download all the information in the database into a single file in their computer.
There are two possible download options, depending on the format of the generated file being plain CSV or compressed and password-protected ZIP.
These documents will contain information on the requests, and by extension, on the corresponding patients.
Thus, due to patient confidentiality, not all the personal data should be in the downloaded file.
The checkboxes in this form allow the laboratory supervisor as well as the system administrator to decide which fields will be downloaded in each one of the formats.


Additionally, the system provides two configuration parameters to customize the structure of the CSV file: ''csv_delimiter'', which defines the character used to separate data fields in the CSV file, and ''csv_decimal'', which specifies the character used to represent decimal values in numerical fields. It is essential to configure these parameters according to the settings used by the system and the spreadsheet software (e.g Excel) to ensure proper data interpretation. Using an incorrect delimiter or decimal separator may result in formatting issues when opening the file.


==Technical==
This groups all the more advanced administration functionalities.
They are available only for the system administration.


===Summary of instances===
[[File:Summaryofinstancessmol.PNG|right|250px|thumb|Summary of instances]]
This tab displays information about the different existing instances in the application.
Some examples are: the number of patients, users, requests or genders.
This information comes directly from the database and is automatically updated after every modification in the system.
It can be useful to investigate potential performance problems in case of extremely large numbers.
To facilitate the reading and identification of the different kinds of instances, the information is divided into three sections: ''Data'', ''Administration'' and ''Configuration''.


===Roles===
This tab is displayed and works, in the same way as the [[Configuration#State of the request|State of the request]] tab in the [[Configuration|Configuration]] functionality.
The roles are unchangeable, but their labels (not the corresponding functionality) can be customized.


Each role has different actions allowed within the application, chosen due to the tasks the people are expected to carry out.
Thus, there are five roles within the system, which indicate the functionalities that a user can perform, as can be seen in the following table.


{| class="wikitable" style="margin:auto; text-align: center;"
|+ Allowed functionalities per role
|-
!colspan="2"| Functionalities !! Patient Manager !! Laboratory Technician !! Laboratory Technician with Validation !! Laboratory Supervisor !! System administrator
|-
| style="text-align:left;" rowspan="2" | Patient || style="text-align:left;" | Create || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Search || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="6" | Request || style="text-align:left;" | Create || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Change information || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Deliver samples || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Introduce results || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Validate results || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Search historic || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" colspan="2" | Data analysis || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="2" | Configuration || style="text-align:left;" | Generic || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|-
| style="text-align:left;" | Technical || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="2" | Administration || style="text-align:left;"| Generic || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|-
| style="text-align:left;" | Technical || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|}


===Parameters===
Parameters determine the behaviour of some functionalities.
Thus, they cannot be created or deleted.
However, their values can be updated to customize the system.
At this point it is important to highlight the on updating them, the data type must be respected.
Providing a value of the wrong data type (e.g., a string instead of an integer) can provoke the malfunction of the whole application.


The following table contains the list of existing parameters together with the corresponding data type and a brief description.


{| class="wikitable" style="margin:auto; text-align: left;"
|+ System parameters
|-
! Name !! Data type !! Description
|-
| ''attribute_reserved1'' || String || Label of the first field of free use in the requests (write 'DoNotShow' to hide it)
|-
| ''attribute_reserved2'' || String || Label of the second field of free use in the requests (write 'DoNotShow' to hide it)
|-
| ''attribute_reserved3'' || String || Label of the third field of free use in the requests (write 'DoNotShow' to hide it)
|-
| ''backup_frequency'' || Integer || Minimum amount of hours that need to pass for the system to generate a new copy of the database
|-
| ''backup_history'' || Integer || Maximum number of copies of the database kept (once reached, the oldest copy in the folder is deleted)
|-
| ''bluetooth_enabler'' || String || Indicates the availability of automatic tests through Bluetooth connection (accepted values are 'Enabled' and 'Disabled'), which is only used in the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page IMAGING project]
|-
| ''csv_decimal'' || String || Specifies the character used to represent the decimal point in numerical values in the generated csv file (accepted values are ''.'' and '','')
|-
| ''csv_delimiter'' || String || Specifies the character used to separate fields in the generated csv file (accepted values are '';'' and '','')
|-
| ''default_language'' || String || Language set by default on logging in (the same for all users)
|-
| ''filename_background'' || String || File containing the image displayed in the background
|-
| ''filename_favicon'' || String || Icon of the system used in the browser tab
|-
| ''filename_sidebarlogo'' || String || File containing the logo displayed at the bottom of the sidebar
|-
| ''filename_worklistlogo'' || String || Logo used in the worklist reports
|-
| ''groups_profiles'' || String || Shows groups and profiles for analytical tests (accepted values are 'Enabled' and 'Disabled')
|-
| ''log_history'' || Integer || Maximum number of days to keep registries in the access log (those older than this will be automatically deleted)
|-
| ''max_image_volume'' || Integer || Maximum number of megabytes used to store images (once reached, the oldest ones in the folder are deleted)
|-
| ''name'' || String || Caption to appear at the top of the screen (in the navigation bar), as well as in the worklist and reports
|-
| ''report_subtitle'' || String || Subtitle to be used in the worklist and reports
|-
| ''set_sample_delivery_default'' || String || Indicates whether samples are assumed to be delivered or not by default (accepted values are 'True' and 'False'). Setting it to 'True' makes 'Change information' and 'Samples' items in the sidebar be hidden.
|-
| ''table_default_paging'' || Integer || Indicates the initial paging of all the tables (accepted values are 5, 10 or 25)
|-
| ''table_min_rows_for_search'' || Integer || Minimum number of rows a table must have to show the corresponding search field
|-
| ''timeout'' || Integer || Time (in minutes) after which the connection to the backend requires a new log in
|-
| ''version'' || String || Version of the system
|-
| ''zip_password'' || String || Password that will be used to generate the downloaded zip file
|}
</translate>

System administration

2026-01-08T17:36:39Z

Alberto:

[[Category:System administration]]
<languages/>
<translate>

This groups all knobs that allow to manage and adapt the behavior of ARIS to the needs of the laboratory and user preferences.
They are grouped in two to facilitate their access.
The first one is more generic and allows both laboratory supervisor and system administration to access some basic stuff.
The second one is only available to the system administrator, since it is considered to require more advance technological skills.


<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border="frame" format="svg">
digraph AdministrationDiagram {
node [shape=oval style=filled fillcolor=orange fontsize="9pt"];
//----- System Administration graph
// Nodes
SystemAdministration [label="System Administration"];
Generic [label="Generic" URL="#Generic"];
Technical [label="Technical" URL="#Technical"];
Users [label="Users" shape=tab URL="#Users"];
AccessLog [label="Access Log" shape=tab URL="#Access_log"];
DownloadedFields [label="Downloaded Fields" shape=tab URL="#Downloaded_fields"];
SummaryOfInstances [label="Summary of Instances" shape=tab URL="#Summary_of_instances"];
Roles [label="Roles" shape=tab URL="#Roles"];
Parameters [label="Parameters" shape=tab URL="#Parameters"];
// Edges
SystemAdministration -> Generic;
SystemAdministration -> Technical;
// Edges
Generic -> Users;
Generic -> AccessLog;
Generic -> DownloadedFields;
// Edges
Technical -> SummaryOfInstances;
Technical -> Roles;
Technical -> Parameters;
}
</graphviz>
</div>


__TOC__

==Generic== 
This groups all the basic administration functionalities.
They are available for both the system administration and the laboratory supervisor.

===Users=== 
[[File:Newuser.PNG|right|thumb|750px|User creation form]]
When clicking on the edit or ''New user'' buttons, a form pops up on the screen. The information necessary to create a user consists of a ''Username'', ''Name'', ''Middle name'', ''password'' and the person's [[#Roles|Role]] within the system.
This Role will determine the functionalities available to the user.
A note, without any effect in the behaviour of the application, can be added to indicate any relevant information to the system administrator.


This same form allows the system administrator to modify the password of any other user.
For security reasons, this password must contain some number, some capital letter, some small letter, and at least eight characters.


Since they are used for auditing changes in patients and requests, the users cannot be deleted from the system.
However, they can be declared not to be active, which would prevent them from logging in, but still keep track in the database of all their past actions.

===Access log=== 
The ''access log'' shows the user which user has done an action within the system and exactly when. The timestamp is in the format '''Year-Month-Day Hour:Minute:Second'''
[[File:Accesslog.PNG|right|thumb|600px|Example of access log]]</br>
There are three actions recorded by the access log, ''successful log in'', ''wrong user'' and ''failed log in''. This last action refers to the wrong password being used.

===Downloaded fields=== 
ARIS allows the laboratory supervisor to download all the information in the database into a single file in their computer.
There are two possible download options, depending on the format of the generated file being plain CSV or compressed and password-protected ZIP.
These documents will contain information on the requests, and by extension, on the corresponding patients.
Thus, due to patient confidentiality, not all the personal data should be in the downloaded file.
The checkboxes in this form allow the laboratory supervisor as well as the system administrator to decide which fields will be downloaded in each one of the formats.


Additionally, the system provides two configuration parameters to customize the structure of the CSV file: ''csv_delimiter'', which defines the character used to separate data fields in the CSV file, and ''csv_decimal'', which specifies the character used to represent decimal values in numerical fields. It is essential to configure these parameters according to the settings used by the system and the spreadsheet software (e.g Excel) to ensure proper data interpretation. Using an incorrect delimiter or decimal separator may result in formatting issues when opening the file.

==Technical== 
This groups all the more advanced administration functionalities.
They are available only for the system administration.

===Summary of instances=== 
[[File:Summaryofinstancessmol.PNG|right|250px|thumb|Summary of instances]]
This tab displays information about the different existing instances in the application.
Some examples are: the number of patients, users, requests or genders.
This information comes directly from the database and is automatically updated after every modification in the system.
It can be useful to investigate potential performance problems in case of extremely large numbers.
To facilitate the reading and identification of the different kinds of instances, the information is divided into three sections: ''Data'', ''Administration'' and ''Configuration''.

===Roles=== 
This tab is displayed and works, in the same way as the [[Configuration#State of the request|State of the request]] tab in the [[Configuration|Configuration]] functionality.
The roles are unchangeable, but their labels (not the corresponding functionality) can be customized.


Each role has different actions allowed within the application, chosen due to the tasks the people are expected to carry out.
Thus, there are five roles within the system, which indicate the functionalities that a user can perform, as can be seen in the following table.


{| class="wikitable" style="margin:auto; text-align: center;"
|+ Allowed functionalities per role
|-
!colspan="2"| Functionalities !! Patient Manager !! Laboratory Technician !! Laboratory Technician with Validation !! Laboratory Supervisor !! System administrator
|-
| style="text-align:left;" rowspan="2" | Patient || style="text-align:left;" | Create || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Search || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="6" | Request || style="text-align:left;" | Create || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Change information || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Deliver samples || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Introduce results || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Validate results || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Search historic || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" colspan="2" | Data analysis || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="2" | Configuration || style="text-align:left;" | Generic || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|-
| style="text-align:left;" | Technical || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="2" | Administration || style="text-align:left;"| Generic || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|-
| style="text-align:left;" | Technical || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|}

===Parameters=== 
Parameters determine the behaviour of some functionalities.
Thus, they cannot be created or deleted.
However, their values can be updated to customize the system.
At this point it is important to highlight the on updating them, the data type must be respected.
Providing a value of the wrong data type (e.g., a string instead of an integer) can provoke the malfunction of the whole application.


The following table contains the list of existing parameters together with the corresponding data type and a brief description.


{| class="wikitable" style="margin:auto; text-align: left;"
|+ System parameters
|-
! Name !! Data type !! Description
|-
| ''attribute_reserved1'' || String || Label of the first field of free use in the requests (write 'DoNotShow' to hide it)
|-
| ''attribute_reserved2'' || String || Label of the second field of free use in the requests (write 'DoNotShow' to hide it)
|-
| ''attribute_reserved3'' || String || Label of the third field of free use in the requests (write 'DoNotShow' to hide it)
|-
| ''backup_frequency'' || Integer || Minimum amount of hours that need to pass for the system to generate a new copy of the database
|-
| ''backup_history'' || Integer || Maximum number of copies of the database kept (once reached, the oldest copy in the folder is deleted)
|-
| ''bluetooth_enabler'' || String || Indicates the availability of automatic tests through Bluetooth connection (accepted values are 'Enabled' and 'Disabled'), which is only used in the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page IMAGING project]
|-
| ''csv_decimal'' || String || Specifies the character used to represent the decimal point in numerical values in the generated csv file (accepted values are ''.'' and '','')
|-
| ''csv_delimiter'' || String || Specifies the character used to separate fields in the generated csv file (accepted values are '';'' and '','')
|-
| ''default_language'' || String || Language set by default on logging in (the same for all users)
|-
| ''filename_background'' || String || File containing the image displayed in the background
|-
| ''filename_favicon'' || String || Icon of the system used in the browser tab
|-
| ''filename_sidebarlogo'' || String || File containing the logo displayed at the bottom of the sidebar
|-
| ''filename_worklistlogo'' || String || Logo used in the worklist reports
|-
| ''groups_profiles'' || String || Shows groups and profiles for analytical tests (accepted values are 'Enabled' and 'Disabled')
|-
| ''log_history'' || Integer || Maximum number of days to keep registries in the access log (those older than this will be automatically deleted)
|-
| ''max_image_volume'' || Integer || Maximum number of megabytes used to store images (once reached, the oldest ones in the folder are deleted)
|-
| ''name'' || String || Caption to appear at the top of the screen (in the navigation bar), as well as in the worklist and reports
|-
| ''report_subtitle'' || String || Subtitle to be used in the worklist and reports
|-
| ''set_sample_delivery_default'' || String || Indicates whether samples are assumed to be delivered or not by default (accepted values are 'True' and 'False'). Setting it to 'True' makes 'Change information' and 'Samples' items in the sidebar be hidden.
|-
| ''table_default_paging'' || Integer || Indicates the initial paging of all the tables (accepted values are 5, 10 or 25)
|-
| ''table_min_rows_for_search'' || Integer || Minimum number of rows a table must have to show the corresponding search field
|-
| ''timeout'' || Integer || Time (in minutes) after which the connection to the backend requires a new log in
|-
| ''version'' || String || Version of the system
|-
| ''zip_password'' || String || Password that will be used to generate the downloaded zip file
|}
</translate>

Requests

2026-01-08T17:34:47Z

Alberto:

[[Category:Requests]]
<languages/>
<translate>

Requests are the most important entities in ARIS, whose main purpose is to manage them.
They are always associated to a given patient, who must have been created before hand.


<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph RequestsDiagram {
node [shape="oval" style=filled fillcolor="orange" fontsize="9pt"];
//edge [minlen=2];
//----- Requests graph
// Nodes
Requests [label="Requests" ];
Create [label="Create", URL="#Create" ];
ChangeInformation [label="Change Information", URL="#Change_information"];
PatientsData [label="Patients' Data", shape="tab", URL="#Create"];
AdditionalInformation [label="Additional Information", shape="tab", URL="#Create"];
BiologicalSamples [label="Biological Samples", shape="tab", URL="#Create" ];
AnalyticalTests [label="Analytical Tests", shape="tab", URL="#Create" ];
DeliverSamples [label="Deliver Samples", URL="#Deliver_samples" ];
IntroduceResults [label="Introduce Results", URL="#Introduce_results" ];
ValidateResults [label="Validate Results", URL="#Validate_results"];
SearchHistoric [label="Search Historic", URL="#Search_historic"];
// Edges
Requests -> Create;
Requests -> ChangeInformation;
Create -> PatientsData;
ChangeInformation -> PatientsData;
PatientsData -> BiologicalSamples [dir=both minlen=2];
BiologicalSamples -> AnalyticalTests [dir=both minlen=2];
AnalyticalTests -> AdditionalInformation [dir=both minlen=2];
Requests -> DeliverSamples;
DeliverSamples -> BiologicalSamples;
Requests -> IntroduceResults;
IntroduceResults -> AnalyticalTests;
Requests -> ValidateResults;
ValidateResults -> AnalyticalTests;
Requests -> SearchHistoric;
{ rank=same; Create ChangeInformation DeliverSamples ValidateResults IntroduceResults SearchHistoric}
{ rank=same; PatientsData AnalyticalTests AdditionalInformation BiologicalSamples }
}
</graphviz>
</div>


__TOC__


==Request Lifespan==
<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph StatesDiagram {
node [shape=rectangle style=rounded fontsize="9pt"];
edge [fontsize="7pt"];
//----- Main graph
// Nodes
Begin [label="" shape="circle" style=filled fillcolor=black fixedsize=true width=0.2 height=0.2];
Registered [label="Registered"];
Processing [label="Processing"];
WithResults [label="WithResults"];
Validated [label="Validated"];
Cancelled [label="Cancelled"];
End [label="" shape="doublecircle" style=filled fillcolor="black" fixedsize=true width=0.2 height=0.2];
// Edges
Begin -> Registered [constraint=false];
Registered -> Processing [label="Some sample delivered" constraint=false];
Processing -> WithResults [label="All results provided" constraint=false];
WithResults -> Validated [label="All tests validated" constraint=false];
Validated -> End [constraint=false];
Registered -> Cancelled [label="Cancel"];
Processing -> Cancelled [label="Cancel"];
WithResults -> Cancelled [label="Cancel"];
Cancelled -> End [constraint=false];
{ rank=same; Begin Registered Processing WithResults Validated}
{ rank=same; Cancelled End}
}
</graphviz>
</div>


During their lifespan, requests go through some different states that determine the functionalities offered for them in the system.
These states are depicted in the diagram, and their labels are modifaiable and configurable at [[Configuration#State_of_the_request|State of the request]].


On creation, the state of the request is ''Registered'', and allows to provide the basic information, as well as associate different tests to it.
After indicating that some of the samples have been delivered, the state changes to ''Processing'' and the data of the request cannot be modified anymore.
Other samples can be delivered later, but at this point, results can be provided for the tests whose sample was already delivered.
Once all non-cancelled tests have a result, the state of the request changes to ''WithResults''.
At this state, results can still be modified, but they are expected to be eventually validated.
A request with all its non-cancelled tests being validated is considered ''Validated''.


At any time, a request, its samples or its tests can be cancelled.
A sample with all its tests cancelled is considered cancelled, and a request with all samples cancelled is considered cancelled, too.


During the lifespan of a request, it is available to all the laboratory technicians, except for the validation, which can only be done by a laboratory supervisor or a specially authorized laboratory technician.


==Create==
[[File:Selectpatient1.PNG|350px|right|thumb|Create request form]]


This form is divided into tabs. The tab the laboratory technician is on is indicated by the label of the tab turning orange. Above, it can be found the ''Requesting centre'' mandatory field, alongside with the additional ''Requesting unit'' field and the ''Urgent'' checkbox. To create a request, the following steps must be executed:


#Select a patient → The first tab involves searching and selecting a patient. The search grid can be narrowed down with the search field. Once a patient is selected, the main and important information about this patient will be displayed at the bottom of the form in a table. Until the patient has been selected, the laboratory technician cannot save the new request.
#Analytical tests → In this tab, the laboratory technician must choose which tests are requested and required for the patient. Groups and profiles will appear in case the proper [[System administration#Parameters|parameter]] is enabled. More than one element from each list may be chosen, but at least one test must be requested one way or another. Tests selected as part of a group or profile (highlighted in purple) cannot be deselected individually.
#Biological samples → This tab informs the laboratory technician of the type of sample that must be taken, depending on the tests chosen in the previous tab. There are no required fields in this tab, but if the laboratory technician wants to add a comment, there is a comment box for each sample. [[File:Comments.PNG|1000px]]
#Basic information → In this tab, other optional fields are provided like physician, the room or bed of the patient. Additional information like a diagnostic orientation or the pregnancy status can also be indicated.


At any moment, the ''Save values'' button cannot be used if any of the required fields is not filled in.


==Change information==
[[File:SearchRequest.PNG|350px|right|thumb|Change information form]]


This form is for editing requests whose samples were not yet delivered.
Clicking on any part of the row will bring the laboratory technician to a form similar to the [[#Create|create]] one, with all of its tabs and similar format and behavior.

By setting the [[System administration#Parameters|parameter]] ''set_sample_delivery_default'' to ''True'' this form disappears from the menu.


==Deliver samples==
Similarly to the previous form, this also displays a list of either ''Registered'' or ''Processing'' requests, for the laboratory technician to choose one of them.
[[File:DeliverSamples1.PNG|350px|right|thumb|Deliver samples form]]
Once a request is chosen, five tabs are shown. The patient's data, potentially analytical tests already done in this request, its list of biological samples, the request data, and tests in previous requests.
Just the biological samples allows some interaction. The other ones are read-only (if enabled at all).


Each of the samples shown contains a field to provide comments, and it can be either checked as delivered or cancelled by click the corresponding red button.
On the delivering of a sample, its origin or incident can be optionally provided.
On cancelling, a pop-up dialogue allows, providing some justification for this.


It is important to notice that the tests associated to the request cannot be changed once the first sample as been delivered.

By setting the [[System administration#Parameters|parameter]] ''set_sample_delivery_default'' to ''True'' this form disappears from the menu.


==Introduce results==
As in the previous cases, a list of requests is shown.
In this case, this list contains all requests in ''Processing'' state.
Clicking the corresponding button at the bottom, it is possible to download a worklist with all pending tests in these requests, to work on them off-line.


[[File:IntroduceResults1.PNG|350px|right|thumb|Form to Introduce Results]]


Once the laboratory technician has chosen a request, five tabs are shown with the patient's data, its list of analytical tests, its list of biological samples, other request data, and potentially previous tests of the same patient.
Just the analytical tests allows some interaction. The other ones are read-only.
Besides the same search box present in all the tables in the system, there is also the possibility of filtering the tests by group of tests (if any was chosen for this request).
A red button in the top right corner allows cancelling the request.


The table of tests contains the following columns:
#Name → Shows the name and the code of the kind of test. It is coloured red if either the test or its sample was cancelled.
#Result → Allows to introduce the result of the test.
#Generic test note → Shows the informative note associated to the kind of test, if any.
#Result within range → Indicates whether the result of the test is in the expected range of values for the kind of test (green check) or not (red cross).
#Referred → Indicates whether the test is done or expected to be done in another laboratory (green check) or not (red cross).
#Automatic (not visible by default) → Indicates whether the test is done or expected to be done automatically (green check) or not (red cross). Automatic tests are done by means of the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Microscope:Main Robotized microscope] and the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/MobileApp:Main Mobile App]. Their results should not be typed manually, but uploaded through Bluetooth. This feature is enabled through the corresponding [[System_administration#Parameters|system parameter]]. If enabled, the field is editable here to allow overwriting the automatic results.
#The test has some note → Indicates whether the test has some associated note (green check) or not (red cross).
#Test details → This should show an icon to navigate to further details of the test. However, if the test or its corresponding sample was cancelled, the corresponding message in red will be shown.
#Cancel test → Icon to cancel the test. If the test is cancelled. A red ''cancelled'' label appears.


[[File:TestDetails1.PNG|350px|right|thumb|Test details]]


On the laboratory technician accessing the details of the test, we gain access to visualize many other things (i.e., units of the result, inferior reference measure, superior reference measure, the user who introduced the results, as well as details provided for the corresponding sample on delivering it).
Moreover, this also allows changing if the test is automatic or deferred, indicate some incidence on the sample, or provide some note (notice that the content of this note will be visible to the patient in the report of the request).
It is important to notice that any of the information provided in this form will not be persisted in the disk until back in the list and saved from there.


If the result of the test was provided automatically (which is not enabled by default and only available in the context of the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page IMAGING project]), the corresponding image and its associated note will be shown at the bottom of the details of the test.


==Validate results==
[[File:Validateresults.mp4|left]]
This functionality, available only to the laboratory supervisor or a laboratory technician authorized to validate, uses exactly the same interface as introducing results, but the table shows one more column, ''Validated'', with a checkbox for each test.
These can be checked one by one, or all at once, by choosing a concrete group of tests in the dropbox at the top.
On doing the latter, a button to check all the tests of the group will appear.


Besides doing it in the list, the results can be overwritten and the test validated from the details of the test.
Together with displaying all the information related to the test in read-only mode, the corresponding form also offers the possibility of adding a note to the test, as well as changing whether the test is automatic/referred or not, cancelling the test or the whole request.


It is important to notice that the tests will not be really validated until the bottom right button is pressed to save the changes.


==Search historic==
[[File:Download.mp4|left]]
This functionality, available to both laboratory technician and supervisor allows to see any request in the history of the laboratory.
They can be filtered out by the state and the date of the request.
By clicking on the corresponding row, all the details of the request can be visualized.


At the bottom left of this form, there are two download buttons.
Clicking any of them will generate and download the corresponding file (i.e., CSV or ZIP).
The checkboxes in the [[System administration#Downloaded fields|Downloaded fields]] tab indicate which fields will be included in each of these files.
Moreover, the ZIP file is password protected.
The password used is indicated by the system parameter ''zip_password'', whose value can be seen and modified from [[System administration#Parameters|Parameters]] tab.
Additionally, the field separator and decimal characters used in the CSV file can also be configured in the same tab.
</translate>

Requests

2026-01-08T17:31:48Z

Alberto: /* Deliver samples */

[[Category:Requests]]
<languages/>
<translate>

Requests are the most important entities in ARIS, whose main purpose is to manage them.
They are always associated to a given patient, who must have been created before hand.


<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph RequestsDiagram {
node [shape="oval" style=filled fillcolor="orange" fontsize="9pt"];
//edge [minlen=2];
//----- Requests graph
// Nodes
Requests [label="Requests" ];
Create [label="Create", URL="#Create" ];
ChangeInformation [label="Change Information", URL="#Change_information"];
PatientsData [label="Patients' Data", shape="tab", URL="#Create"];
AdditionalInformation [label="Additional Information", shape="tab", URL="#Create"];
BiologicalSamples [label="Biological Samples", shape="tab", URL="#Create" ];
AnalyticalTests [label="Analytical Tests", shape="tab", URL="#Create" ];
DeliverSamples [label="Deliver Samples", URL="#Deliver_samples" ];
IntroduceResults [label="Introduce Results", URL="#Introduce_results" ];
ValidateResults [label="Validate Results", URL="#Validate_results"];
SearchHistoric [label="Search Historic", URL="#Search_historic"];
// Edges
Requests -> Create;
Requests -> ChangeInformation;
Create -> PatientsData;
ChangeInformation -> PatientsData;
PatientsData -> BiologicalSamples [dir=both minlen=2];
BiologicalSamples -> AnalyticalTests [dir=both minlen=2];
AnalyticalTests -> AdditionalInformation [dir=both minlen=2];
Requests -> DeliverSamples;
DeliverSamples -> BiologicalSamples;
Requests -> IntroduceResults;
IntroduceResults -> AnalyticalTests;
Requests -> ValidateResults;
ValidateResults -> AnalyticalTests;
Requests -> SearchHistoric;
{ rank=same; Create ChangeInformation DeliverSamples ValidateResults IntroduceResults SearchHistoric}
{ rank=same; PatientsData AnalyticalTests AdditionalInformation BiologicalSamples }
}
</graphviz>
</div>


__TOC__


==Request Lifespan==
<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph StatesDiagram {
node [shape=rectangle style=rounded fontsize="9pt"];
edge [fontsize="7pt"];
//----- Main graph
// Nodes
Begin [label="" shape="circle" style=filled fillcolor=black fixedsize=true width=0.2 height=0.2];
Registered [label="Registered"];
Processing [label="Processing"];
WithResults [label="WithResults"];
Validated [label="Validated"];
Cancelled [label="Cancelled"];
End [label="" shape="doublecircle" style=filled fillcolor="black" fixedsize=true width=0.2 height=0.2];
// Edges
Begin -> Registered [constraint=false];
Registered -> Processing [label="Some sample delivered" constraint=false];
Processing -> WithResults [label="All results provided" constraint=false];
WithResults -> Validated [label="All tests validated" constraint=false];
Validated -> End [constraint=false];
Registered -> Cancelled [label="Cancel"];
Processing -> Cancelled [label="Cancel"];
WithResults -> Cancelled [label="Cancel"];
Cancelled -> End [constraint=false];
{ rank=same; Begin Registered Processing WithResults Validated}
{ rank=same; Cancelled End}
}
</graphviz>
</div>


During their lifespan, requests go through some different states that determine the functionalities offered for them in the system.
These states are depicted in the diagram, and their labels are modifaiable and configurable at [[Configuration#State_of_the_request|State of the request]].


On creation, the state of the request is ''Registered'', and allows to provide the basic information, as well as associate different tests to it.
After indicating that some of the samples have been delivered, the state changes to ''Processing'' and the data of the request cannot be modified anymore.
Other samples can be delivered later, but at this point, results can be provided for the tests whose sample was already delivered.
Once all non-cancelled tests have a result, the state of the request changes to ''WithResults''.
At this state, results can still be modified, but they are expected to be eventually validated.
A request with all its non-cancelled tests being validated is considered ''Validated''.


At any time, a request, its samples or its tests can be cancelled.
A sample with all its tests cancelled is considered cancelled, and a request with all samples cancelled is considered cancelled, too.


During the lifespan of a request, it is available to all the laboratory technicians, except for the validation, which can only be done by a laboratory supervisor or a specially authorized laboratory technician.


==Create==
[[File:Selectpatient1.PNG|350px|right|thumb|Create request form]]


This form is divided into tabs. The tab the laboratory technician is on is indicated by the label of the tab turning orange. Above, it can be found the ''Requesting centre'' mandatory field, alongside with the additional ''Requesting unit'' field and the ''Urgent'' checkbox. To create a request, the following steps must be executed:


#Select a patient → The first tab involves searching and selecting a patient. The search grid can be narrowed down with the search field. Once a patient is selected, the main and important information about this patient will be displayed at the bottom of the form in a table. Until the patient has been selected, the laboratory technician cannot save the new request.
#Analytical tests → In this tab, the laboratory technician must choose which tests are requested and required for the patient. Groups and profiles will appear in case the proper [[System administration#Parameters|parameter]] is enabled. More than one element from each list may be chosen, but at least one test must be requested one way or another. Tests selected as part of a group or profile (highlighted in purple) cannot be deselected individually.
#Biological samples → This tab informs the laboratory technician of the type of sample that must be taken, depending on the tests chosen in the previous tab. There are no required fields in this tab, but if the laboratory technician wants to add a comment, there is a comment box for each sample. [[File:Comments.PNG|1000px]]
#Basic information → In this tab, other optional fields are provided like physician, the room or bed of the patient. Additional information like a diagnostic orientation or the pregnancy status can also be indicated.


At any moment, the ''Save values'' button cannot be used if any of the required fields is not filled in.


==Change information==
[[File:SearchRequest.PNG|350px|right|thumb|Change information form]]


This form is for editing requests whose samples were not yet delivered.
Clicking on any part of the row will bring the laboratory technician to a form similar to the [[#Create|create]] one, with all of its tabs and similar format and behavior.


By setting the parameter ''set_sample_delivery_default'' to ''True'' this form disappears from the menu.

==Deliver samples==
Similarly to the previous form, this also displays a list of either ''Registered'' or ''Processing'' requests, for the laboratory technician to choose one of them.
[[File:DeliverSamples1.PNG|350px|right|thumb|Deliver samples form]]
Once a request is chosen, five tabs are shown. The patient's data, potentially analytical tests already done in this request, its list of biological samples, the request data, and tests in previous requests.
Just the biological samples allows some interaction. The other ones are read-only (if enabled at all).


Each of the samples shown contains a field to provide comments, and it can be either checked as delivered or cancelled by click the corresponding red button.
On the delivering of a sample, its origin or incident can be optionally provided.
On cancelling, a pop-up dialogue allows, providing some justification for this.


It is important to notice that the tests associated to the request cannot be changed once the first sample as been delivered.


By setting the parameter ''set_sample_delivery_default'' to ''True'' this form disappears from the menu.

==Introduce results==
As in the previous cases, a list of requests is shown.
In this case, this list contains all requests in ''Processing'' state.
Clicking the corresponding button at the bottom, it is possible to download a worklist with all pending tests in these requests, to work on them off-line.


[[File:IntroduceResults1.PNG|350px|right|thumb|Form to Introduce Results]]


Once the laboratory technician has chosen a request, five tabs are shown with the patient's data, its list of analytical tests, its list of biological samples, other request data, and potentially previous tests of the same patient.
Just the analytical tests allows some interaction. The other ones are read-only.
Besides the same search box present in all the tables in the system, there is also the possibility of filtering the tests by group of tests (if any was chosen for this request).
A red button in the top right corner allows cancelling the request.


The table of tests contains the following columns:
#Name → Shows the name and the code of the kind of test. It is coloured red if either the test or its sample was cancelled.
#Result → Allows to introduce the result of the test.
#Generic test note → Shows the informative note associated to the kind of test, if any.
#Result within range → Indicates whether the result of the test is in the expected range of values for the kind of test (green check) or not (red cross).
#Referred → Indicates whether the test is done or expected to be done in another laboratory (green check) or not (red cross).
#Automatic (not visible by default) → Indicates whether the test is done or expected to be done automatically (green check) or not (red cross). Automatic tests are done by means of the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Microscope:Main Robotized microscope] and the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/MobileApp:Main Mobile App]. Their results should not be typed manually, but uploaded through Bluetooth. This feature is enabled through the corresponding [[System_administration#Parameters|system parameter]]. If enabled, the field is editable here to allow overwriting the automatic results.
#The test has some note → Indicates whether the test has some associated note (green check) or not (red cross).
#Test details → This should show an icon to navigate to further details of the test. However, if the test or its corresponding sample was cancelled, the corresponding message in red will be shown.
#Cancel test → Icon to cancel the test. If the test is cancelled. A red ''cancelled'' label appears.


[[File:TestDetails1.PNG|350px|right|thumb|Test details]]


On the laboratory technician accessing the details of the test, we gain access to visualize many other things (i.e., units of the result, inferior reference measure, superior reference measure, the user who introduced the results, as well as details provided for the corresponding sample on delivering it).
Moreover, this also allows changing if the test is automatic or deferred, indicate some incidence on the sample, or provide some note (notice that the content of this note will be visible to the patient in the report of the request).
It is important to notice that any of the information provided in this form will not be persisted in the disk until back in the list and saved from there.


If the result of the test was provided automatically (which is not enabled by default and only available in the context of the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page IMAGING project]), the corresponding image and its associated note will be shown at the bottom of the details of the test.


==Validate results==
[[File:Validateresults.mp4|left]]
This functionality, available only to the laboratory supervisor or a laboratory technician authorized to validate, uses exactly the same interface as introducing results, but the table shows one more column, ''Validated'', with a checkbox for each test.
These can be checked one by one, or all at once, by choosing a concrete group of tests in the dropbox at the top.
On doing the latter, a button to check all the tests of the group will appear.


Besides doing it in the list, the results can be overwritten and the test validated from the details of the test.
Together with displaying all the information related to the test in read-only mode, the corresponding form also offers the possibility of adding a note to the test, as well as changing whether the test is automatic/referred or not, cancelling the test or the whole request.


It is important to notice that the tests will not be really validated until the bottom right button is pressed to save the changes.


==Search historic==
[[File:Download.mp4|left]]
This functionality, available to both laboratory technician and supervisor allows to see any request in the history of the laboratory.
They can be filtered out by the state and the date of the request.
By clicking on the corresponding row, all the details of the request can be visualized.


At the bottom left of this form, there are two download buttons.
Clicking any of them will generate and download the corresponding file (i.e., CSV or ZIP).
The checkboxes in the [[System administration#Downloaded fields|Downloaded fields]] tab indicate which fields will be included in each of these files.
Moreover, the ZIP file is password protected.
The password used is indicated by the system parameter ''zip_password'', whose value can be seen and modified from [[System administration#Parameters|Parameters]] tab.
Additionally, the field separator and decimal characters used in the CSV file can also be configured in the same tab.
</translate>

Requests

2026-01-08T17:30:55Z

Alberto: /* Change information */

[[Category:Requests]]
<languages/>
<translate>

Requests are the most important entities in ARIS, whose main purpose is to manage them.
They are always associated to a given patient, who must have been created before hand.


<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph RequestsDiagram {
node [shape="oval" style=filled fillcolor="orange" fontsize="9pt"];
//edge [minlen=2];
//----- Requests graph
// Nodes
Requests [label="Requests" ];
Create [label="Create", URL="#Create" ];
ChangeInformation [label="Change Information", URL="#Change_information"];
PatientsData [label="Patients' Data", shape="tab", URL="#Create"];
AdditionalInformation [label="Additional Information", shape="tab", URL="#Create"];
BiologicalSamples [label="Biological Samples", shape="tab", URL="#Create" ];
AnalyticalTests [label="Analytical Tests", shape="tab", URL="#Create" ];
DeliverSamples [label="Deliver Samples", URL="#Deliver_samples" ];
IntroduceResults [label="Introduce Results", URL="#Introduce_results" ];
ValidateResults [label="Validate Results", URL="#Validate_results"];
SearchHistoric [label="Search Historic", URL="#Search_historic"];
// Edges
Requests -> Create;
Requests -> ChangeInformation;
Create -> PatientsData;
ChangeInformation -> PatientsData;
PatientsData -> BiologicalSamples [dir=both minlen=2];
BiologicalSamples -> AnalyticalTests [dir=both minlen=2];
AnalyticalTests -> AdditionalInformation [dir=both minlen=2];
Requests -> DeliverSamples;
DeliverSamples -> BiologicalSamples;
Requests -> IntroduceResults;
IntroduceResults -> AnalyticalTests;
Requests -> ValidateResults;
ValidateResults -> AnalyticalTests;
Requests -> SearchHistoric;
{ rank=same; Create ChangeInformation DeliverSamples ValidateResults IntroduceResults SearchHistoric}
{ rank=same; PatientsData AnalyticalTests AdditionalInformation BiologicalSamples }
}
</graphviz>
</div>


__TOC__


==Request Lifespan==
<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph StatesDiagram {
node [shape=rectangle style=rounded fontsize="9pt"];
edge [fontsize="7pt"];
//----- Main graph
// Nodes
Begin [label="" shape="circle" style=filled fillcolor=black fixedsize=true width=0.2 height=0.2];
Registered [label="Registered"];
Processing [label="Processing"];
WithResults [label="WithResults"];
Validated [label="Validated"];
Cancelled [label="Cancelled"];
End [label="" shape="doublecircle" style=filled fillcolor="black" fixedsize=true width=0.2 height=0.2];
// Edges
Begin -> Registered [constraint=false];
Registered -> Processing [label="Some sample delivered" constraint=false];
Processing -> WithResults [label="All results provided" constraint=false];
WithResults -> Validated [label="All tests validated" constraint=false];
Validated -> End [constraint=false];
Registered -> Cancelled [label="Cancel"];
Processing -> Cancelled [label="Cancel"];
WithResults -> Cancelled [label="Cancel"];
Cancelled -> End [constraint=false];
{ rank=same; Begin Registered Processing WithResults Validated}
{ rank=same; Cancelled End}
}
</graphviz>
</div>


During their lifespan, requests go through some different states that determine the functionalities offered for them in the system.
These states are depicted in the diagram, and their labels are modifaiable and configurable at [[Configuration#State_of_the_request|State of the request]].


On creation, the state of the request is ''Registered'', and allows to provide the basic information, as well as associate different tests to it.
After indicating that some of the samples have been delivered, the state changes to ''Processing'' and the data of the request cannot be modified anymore.
Other samples can be delivered later, but at this point, results can be provided for the tests whose sample was already delivered.
Once all non-cancelled tests have a result, the state of the request changes to ''WithResults''.
At this state, results can still be modified, but they are expected to be eventually validated.
A request with all its non-cancelled tests being validated is considered ''Validated''.


At any time, a request, its samples or its tests can be cancelled.
A sample with all its tests cancelled is considered cancelled, and a request with all samples cancelled is considered cancelled, too.


During the lifespan of a request, it is available to all the laboratory technicians, except for the validation, which can only be done by a laboratory supervisor or a specially authorized laboratory technician.


==Create==
[[File:Selectpatient1.PNG|350px|right|thumb|Create request form]]


This form is divided into tabs. The tab the laboratory technician is on is indicated by the label of the tab turning orange. Above, it can be found the ''Requesting centre'' mandatory field, alongside with the additional ''Requesting unit'' field and the ''Urgent'' checkbox. To create a request, the following steps must be executed:


#Select a patient → The first tab involves searching and selecting a patient. The search grid can be narrowed down with the search field. Once a patient is selected, the main and important information about this patient will be displayed at the bottom of the form in a table. Until the patient has been selected, the laboratory technician cannot save the new request.
#Analytical tests → In this tab, the laboratory technician must choose which tests are requested and required for the patient. Groups and profiles will appear in case the proper [[System administration#Parameters|parameter]] is enabled. More than one element from each list may be chosen, but at least one test must be requested one way or another. Tests selected as part of a group or profile (highlighted in purple) cannot be deselected individually.
#Biological samples → This tab informs the laboratory technician of the type of sample that must be taken, depending on the tests chosen in the previous tab. There are no required fields in this tab, but if the laboratory technician wants to add a comment, there is a comment box for each sample. [[File:Comments.PNG|1000px]]
#Basic information → In this tab, other optional fields are provided like physician, the room or bed of the patient. Additional information like a diagnostic orientation or the pregnancy status can also be indicated.


At any moment, the ''Save values'' button cannot be used if any of the required fields is not filled in.


==Change information==
[[File:SearchRequest.PNG|350px|right|thumb|Change information form]]


This form is for editing requests whose samples were not yet delivered.
Clicking on any part of the row will bring the laboratory technician to a form similar to the [[#Create|create]] one, with all of its tabs and similar format and behavior.


By setting the parameter ''set_sample_delivery_default'' to ''True'' this form disappears from the menu.

==Deliver samples==
Similarly to the previous form, this also displays a list of either ''Registered'' or ''Processing'' requests, for the laboratory technician to choose one of them.
[[File:DeliverSamples1.PNG|350px|right|thumb|Deliver samples form]]
Once a request is chosen, five tabs are shown. The patient's data, potentially analytical tests already done in this request, its list of biological samples, the request data, and tests in previous requests.
Just the biological samples allows some interaction. The other ones are read-only (if enabled at all).


Each of the samples shown contains a field to provide comments, and it can be either checked as delivered or cancelled by click the corresponding red button.
On the delivering of a sample, its origin or incident can be optionally provided.
On cancelling, a pop-up dialogue allows, providing some justification for this.


It is important to notice that the tests associated to the request cannot be changed once the first sample as been delivered.


==Introduce results==
As in the previous cases, a list of requests is shown.
In this case, this list contains all requests in ''Processing'' state.
Clicking the corresponding button at the bottom, it is possible to download a worklist with all pending tests in these requests, to work on them off-line.


[[File:IntroduceResults1.PNG|350px|right|thumb|Form to Introduce Results]]


Once the laboratory technician has chosen a request, five tabs are shown with the patient's data, its list of analytical tests, its list of biological samples, other request data, and potentially previous tests of the same patient.
Just the analytical tests allows some interaction. The other ones are read-only.
Besides the same search box present in all the tables in the system, there is also the possibility of filtering the tests by group of tests (if any was chosen for this request).
A red button in the top right corner allows cancelling the request.


The table of tests contains the following columns:
#Name → Shows the name and the code of the kind of test. It is coloured red if either the test or its sample was cancelled.
#Result → Allows to introduce the result of the test.
#Generic test note → Shows the informative note associated to the kind of test, if any.
#Result within range → Indicates whether the result of the test is in the expected range of values for the kind of test (green check) or not (red cross).
#Referred → Indicates whether the test is done or expected to be done in another laboratory (green check) or not (red cross).
#Automatic (not visible by default) → Indicates whether the test is done or expected to be done automatically (green check) or not (red cross). Automatic tests are done by means of the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Microscope:Main Robotized microscope] and the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/MobileApp:Main Mobile App]. Their results should not be typed manually, but uploaded through Bluetooth. This feature is enabled through the corresponding [[System_administration#Parameters|system parameter]]. If enabled, the field is editable here to allow overwriting the automatic results.
#The test has some note → Indicates whether the test has some associated note (green check) or not (red cross).
#Test details → This should show an icon to navigate to further details of the test. However, if the test or its corresponding sample was cancelled, the corresponding message in red will be shown.
#Cancel test → Icon to cancel the test. If the test is cancelled. A red ''cancelled'' label appears.


[[File:TestDetails1.PNG|350px|right|thumb|Test details]]


On the laboratory technician accessing the details of the test, we gain access to visualize many other things (i.e., units of the result, inferior reference measure, superior reference measure, the user who introduced the results, as well as details provided for the corresponding sample on delivering it).
Moreover, this also allows changing if the test is automatic or deferred, indicate some incidence on the sample, or provide some note (notice that the content of this note will be visible to the patient in the report of the request).
It is important to notice that any of the information provided in this form will not be persisted in the disk until back in the list and saved from there.


If the result of the test was provided automatically (which is not enabled by default and only available in the context of the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page IMAGING project]), the corresponding image and its associated note will be shown at the bottom of the details of the test.


==Validate results==
[[File:Validateresults.mp4|left]]
This functionality, available only to the laboratory supervisor or a laboratory technician authorized to validate, uses exactly the same interface as introducing results, but the table shows one more column, ''Validated'', with a checkbox for each test.
These can be checked one by one, or all at once, by choosing a concrete group of tests in the dropbox at the top.
On doing the latter, a button to check all the tests of the group will appear.


Besides doing it in the list, the results can be overwritten and the test validated from the details of the test.
Together with displaying all the information related to the test in read-only mode, the corresponding form also offers the possibility of adding a note to the test, as well as changing whether the test is automatic/referred or not, cancelling the test or the whole request.


It is important to notice that the tests will not be really validated until the bottom right button is pressed to save the changes.


==Search historic==
[[File:Download.mp4|left]]
This functionality, available to both laboratory technician and supervisor allows to see any request in the history of the laboratory.
They can be filtered out by the state and the date of the request.
By clicking on the corresponding row, all the details of the request can be visualized.


At the bottom left of this form, there are two download buttons.
Clicking any of them will generate and download the corresponding file (i.e., CSV or ZIP).
The checkboxes in the [[System administration#Downloaded fields|Downloaded fields]] tab indicate which fields will be included in each of these files.
Moreover, the ZIP file is password protected.
The password used is indicated by the system parameter ''zip_password'', whose value can be seen and modified from [[System administration#Parameters|Parameters]] tab.
Additionally, the field separator and decimal characters used in the CSV file can also be configured in the same tab.
</translate>

System administration

2026-01-08T16:49:47Z

Alberto:

[[Category:System administration]]
<languages/>
<translate>

This groups all knobs that allow to manage and adapt the behavior of ARIS to the needs of the laboratory and user preferences.
They are grouped in two to facilitate their access.
The first one is more generic and allows both laboratory supervisor and system administration to access some basic stuff.
The second one is only available to the system administrator, since it is considered to require more advance technological skills.


<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border="frame" format="svg">
digraph AdministrationDiagram {
node [shape=oval style=filled fillcolor=orange fontsize="9pt"];
//----- System Administration graph
// Nodes
SystemAdministration [label="System Administration"];
Generic [label="Generic" URL="#Generic"];
Technical [label="Technical" URL="#Technical"];
Users [label="Users" shape=tab URL="#Users"];
AccessLog [label="Access Log" shape=tab URL="#Access_log"];
DownloadedFields [label="Downloaded Fields" shape=tab URL="#Downloaded_fields"];
SummaryOfInstances [label="Summary of Instances" shape=tab URL="#Summary_of_instances"];
Roles [label="Roles" shape=tab URL="#Roles"];
Parameters [label="Parameters" shape=tab URL="#Parameters"];
// Edges
SystemAdministration -> Generic;
SystemAdministration -> Technical;
// Edges
Generic -> Users;
Generic -> AccessLog;
Generic -> DownloadedFields;
// Edges
Technical -> SummaryOfInstances;
Technical -> Roles;
Technical -> Parameters;
}
</graphviz>
</div>


__TOC__

==Generic== 
This groups all the basic administration functionalities.
They are available for both the system administration and the laboratory supervisor.

===Users=== 
[[File:Newuser.PNG|right|thumb|750px|User creation form]]
When clicking on the edit or ''New user'' buttons, a form pops up on the screen. The information necessary to create a user consists of a ''Username'', ''Name'', ''Middle name'', ''password'' and the person's [[#Roles|Role]] within the system.
This Role will determine the functionalities available to the user.
A note, without any effect in the behaviour of the application, can be added to indicate any relevant information to the system administrator.


This same form allows the system administrator to modify the password of any other user.
For security reasons, this password must contain some number, some capital letter, some small letter, and at least eight characters.


Since they are used for auditing changes in patients and requests, the users cannot be deleted from the system.
However, they can be declared not to be active, which would prevent them from logging in, but still keep track in the database of all their past actions.

===Access log=== 
The ''access log'' shows the user which user has done an action within the system and exactly when. The timestamp is in the format '''Year-Month-Day Hour:Minute:Second'''
[[File:Accesslog.PNG|right|thumb|600px|Example of access log]]</br>
There are three actions recorded by the access log, ''successful log in'', ''wrong user'' and ''failed log in''. This last action refers to the wrong password being used.

===Downloaded fields=== 
ARIS allows the laboratory supervisor to download all the information in the database into a single file in their computer.
There are two possible download options, depending on the format of the generated file being plain CSV or compressed and password-protected ZIP.
These documents will contain information on the requests, and by extension, on the corresponding patients.
Thus, due to patient confidentiality, not all the personal data should be in the downloaded file.
The checkboxes in this form allow the laboratory supervisor as well as the system administrator to decide which fields will be downloaded in each one of the formats.


Additionally, the system provides two configuration parameters to customize the structure of the CSV file: ''csv_delimiter'', which defines the character used to separate data fields in the CSV file, and ''csv_decimal'', which specifies the character used to represent decimal values in numerical fields. It is essential to configure these parameters according to the settings used by the system and the spreadsheet software (e.g Excel) to ensure proper data interpretation. Using an incorrect delimiter or decimal separator may result in formatting issues when opening the file.

==Technical== 
This groups all the more advanced administration functionalities.
They are available only for the system administration.

===Summary of instances=== 
[[File:Summaryofinstancessmol.PNG|right|250px|thumb|Summary of instances]]
This tab displays information about the different existing instances in the application.
Some examples are: the number of patients, users, requests or genders.
This information comes directly from the database and is automatically updated after every modification in the system.
It can be useful to investigate potential performance problems in case of extremely large numbers.
To facilitate the reading and identification of the different kinds of instances, the information is divided into three sections: ''Data'', ''Administration'' and ''Configuration''.

===Roles=== 
This tab is displayed and works, in the same way as the [[Configuration#State of the request|State of the request]] tab in the [[Configuration|Configuration]] functionality.
The roles are unchangeable, but their labels (not the corresponding functionality) can be customized.


Each role has different actions allowed within the application, chosen due to the tasks the people are expected to carry out.
Thus, there are five roles within the system, which indicate the functionalities that a user can perform, as can be seen in the following table.


{| class="wikitable" style="margin:auto; text-align: center;"
|+ Allowed functionalities per role
|-
!colspan="2"| Functionalities !! Patient Manager !! Laboratory Technician !! Laboratory Technician with Validation !! Laboratory Supervisor !! System administrator
|-
| style="text-align:left;" rowspan="2" | Patient || style="text-align:left;" | Create || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Search || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="6" | Request || style="text-align:left;" | Create || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Change information || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Deliver samples || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Introduce results || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Validate results || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Search historic || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" colspan="2" | Data analysis || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="2" | Configuration || style="text-align:left;" | Generic || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|-
| style="text-align:left;" | Technical || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="2" | Administration || style="text-align:left;"| Generic || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|-
| style="text-align:left;" | Technical || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|}

===Parameters=== 
Parameters determine the behaviour of some functionalities.
Thus, they cannot be created or deleted.
However, their values can be updated to customize the system.
At this point it is important to highlight the on updating them, the data type must be respected.
Providing a value of the wrong data type (e.g., a string instead of an integer) can provoke the malfunction of the whole application.


The following table contains the list of existing parameters together with the corresponding data type and a brief description.


{| class="wikitable" style="margin:auto; text-align: left;"
|+ System parameters
|-
! Name !! Data type !! Description
|-
| ''attribute_reserved1'' || String || Label of the first field of free use in the requests (write 'DoNotShow' to hide it)
|-
| ''attribute_reserved2'' || String || Label of the second field of free use in the requests (write 'DoNotShow' to hide it)
|-
| ''attribute_reserved3'' || String || Label of the third field of free use in the requests (write 'DoNotShow' to hide it)
|-
| ''backup_frequency'' || Integer || Minimum amount of hours that need to pass for the system to generate a new copy of the database
|-
| ''backup_history'' || Integer || Maximum number of copies of the database kept (once reached, the oldest copy in the folder is deleted)
|-
| ''bluetooth_enabler'' || String || Indicates the availability of automatic tests through Bluetooth connection (accepted values are 'Enabled' and 'Disabled'), which is only used in the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page IMAGING project]
|-
| ''csv_decimal'' || String || Specifies the character used to represent the decimal point in numerical values in the generated csv file (accepted values are ''.'' and '','')
|-
| ''csv_delimiter'' || String || Specifies the character used to separate fields in the generated csv file (accepted values are '';'' and '','')
|-
| ''default_language'' || String || Language set by default on logging in (the same for all users)
|-
| ''filename_background'' || String || File containing the image displayed in the background
|-
| ''filename_favicon'' || String || Icon of the system used in the browser tab
|-
| ''filename_sidebarlogo'' || String || File containing the logo displayed at the bottom of the sidebar
|-
| ''filename_worklistlogo'' || String || Logo used in the worklist reports
|-
| ''groups_profiles'' || String || Shows groups and profiles for analytical tests (accepted values are 'Enabled' and 'Disabled')
|-
| ''log_history'' || Integer || Maximum number of days to keep registries in the access log (those older than this will be automatically deleted)
|-
| ''max_image_volume'' || Integer || Maximum number of megabytes used to store images (once reached, the oldest ones in the folder are deleted)
|-
| ''name'' || String || Caption to appear at the top of the screen (in the navigation bar), as well as in the worklist and reports
|-
| ''report_subtitle'' || String || Subtitle to be used in the worklist and reports
|-
| ''set_sample_delivery_default'' || String || Indicates whether samples are assumed to be delivered or not by default (accepted values are 'True' and 'False'.
|-
| ''table_default_paging'' || Integer || Indicates the initial paging of all the tables (accepted values are 5, 10 or 25)
|-
| ''table_min_rows_for_search'' || Integer || Minimum number of rows a table must have to show the corresponding search field
|-
| ''timeout'' || Integer || Time (in minutes) after which the connection to the backend requires a new log in
|-
| ''version'' || String || Version of the system
|-
| ''zip_password'' || String || Password that will be used to generate the downloaded zip file
|}
</translate>

System administration

2026-01-08T16:48:53Z

Alberto:

[[Category:System administration]]
<languages/>
<translate>

This groups all knobs that allow to manage and adapt the behavior of ARIS to the needs of the laboratory and user preferences.
They are grouped in two to facilitate their access.
The first one is more generic and allows both laboratory supervisor and system administration to access some basic stuff.
The second one is only available to the system administrator, since it is considered to require more advance technological skills.


<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border="frame" format="svg">
digraph AdministrationDiagram {
node [shape=oval style=filled fillcolor=orange fontsize="9pt"];
//----- System Administration graph
// Nodes
SystemAdministration [label="System Administration"];
Generic [label="Generic" URL="#Generic"];
Technical [label="Technical" URL="#Technical"];
Users [label="Users" shape=tab URL="#Users"];
AccessLog [label="Access Log" shape=tab URL="#Access_log"];
DownloadedFields [label="Downloaded Fields" shape=tab URL="#Downloaded_fields"];
SummaryOfInstances [label="Summary of Instances" shape=tab URL="#Summary_of_instances"];
Roles [label="Roles" shape=tab URL="#Roles"];
Parameters [label="Parameters" shape=tab URL="#Parameters"];
// Edges
SystemAdministration -> Generic;
SystemAdministration -> Technical;
// Edges
Generic -> Users;
Generic -> AccessLog;
Generic -> DownloadedFields;
// Edges
Technical -> SummaryOfInstances;
Technical -> Roles;
Technical -> Parameters;
}
</graphviz>
</div>


__TOC__

==Generic== 
This groups all the basic administration functionalities.
They are available for both the system administration and the laboratory supervisor.

===Users=== 
[[File:Newuser.PNG|right|thumb|750px|User creation form]]
When clicking on the edit or ''New user'' buttons, a form pops up on the screen. The information necessary to create a user consists of a ''Username'', ''Name'', ''Middle name'', ''password'' and the person's [[#Roles|Role]] within the system.
This Role will determine the functionalities available to the user.
A note, without any effect in the behaviour of the application, can be added to indicate any relevant information to the system administrator.


This same form allows the system administrator to modify the password of any other user.
For security reasons, this password must contain some number, some capital letter, some small letter, and at least eight characters.


Since they are used for auditing changes in patients and requests, the users cannot be deleted from the system.
However, they can be declared not to be active, which would prevent them from logging in, but still keep track in the database of all their past actions.

===Access log=== 
The ''access log'' shows the user which user has done an action within the system and exactly when. The timestamp is in the format '''Year-Month-Day Hour:Minute:Second'''
[[File:Accesslog.PNG|right|thumb|600px|Example of access log]]</br>
There are three actions recorded by the access log, ''successful log in'', ''wrong user'' and ''failed log in''. This last action refers to the wrong password being used.

===Downloaded fields=== 
ARIS allows the laboratory supervisor to download all the information in the database into a single file in their computer.
There are two possible download options, depending on the format of the generated file being plain CSV or compressed and password-protected ZIP.
These documents will contain information on the requests, and by extension, on the corresponding patients.
Thus, due to patient confidentiality, not all the personal data should be in the downloaded file.
The checkboxes in this form allow the laboratory supervisor as well as the system administrator to decide which fields will be downloaded in each one of the formats.


Additionally, the system provides two configuration parameters to customize the structure of the CSV file: ''csv_delimiter'', which defines the character used to separate data fields in the CSV file, and ''csv_decimal'', which specifies the character used to represent decimal values in numerical fields. It is essential to configure these parameters according to the settings used by the system and the spreadsheet software (e.g Excel) to ensure proper data interpretation. Using an incorrect delimiter or decimal separator may result in formatting issues when opening the file.

==Technical== 
This groups all the more advanced administration functionalities.
They are available only for the system administration.

===Summary of instances=== 
[[File:Summaryofinstancessmol.PNG|right|250px|thumb|Summary of instances]]
This tab displays information about the different existing instances in the application.
Some examples are: the number of patients, users, requests or genders.
This information comes directly from the database and is automatically updated after every modification in the system.
It can be useful to investigate potential performance problems in case of extremely large numbers.
To facilitate the reading and identification of the different kinds of instances, the information is divided into three sections: ''Data'', ''Administration'' and ''Configuration''.

===Roles=== 
This tab is displayed and works, in the same way as the [[Configuration#State of the request|State of the request]] tab in the [[Configuration|Configuration]] functionality.
The roles are unchangeable, but their labels (not the corresponding functionality) can be customized.


Each role has different actions allowed within the application, chosen due to the tasks the people are expected to carry out.
Thus, there are five roles within the system, which indicate the functionalities that a user can perform, as can be seen in the following table.


{| class="wikitable" style="margin:auto; text-align: center;"
|+ Allowed functionalities per role
|-
!colspan="2"| Functionalities !! Patient Manager !! Laboratory Technician !! Laboratory Technician with Validation !! Laboratory Supervisor !! System administrator
|-
| style="text-align:left;" rowspan="2" | Patient || style="text-align:left;" | Create || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Search || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="6" | Request || style="text-align:left;" | Create || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Change information || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Deliver samples || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Introduce results || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Validate results || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" | Search historic || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" colspan="2" | Data analysis || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="2" | Configuration || style="text-align:left;" | Generic || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|-
| style="text-align:left;" | Technical || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Cross.png|frameless|25px]]
|-
| style="text-align:left;" rowspan="2" | Administration || style="text-align:left;"| Generic || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|-
| style="text-align:left;" | Technical || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Cross.png|frameless|25px]] || [[File:Tick.png|frameless|25px]]
|}

===Parameters=== 
Parameters determine the behaviour of some functionalities.
Thus, they cannot be created or deleted.
However, their values can be updated to customize the system.
At this point it is important to highlight the on updating them, the data type must be respected.
Providing a value of the wrong data type (e.g., a string instead of an integer) can provoke the malfunction of the whole application.


The following table contains the list of existing parameters together with the corresponding data type and a brief description.


{| class="wikitable" style="margin:auto; text-align: left;"
|+ System parameters
|-
! Name !! Data type !! Description
|-
| ''attribute_reserved1'' || String || Label of the first field of free use in the requests (write 'DoNotShow' to hide it)
|-
| ''attribute_reserved2'' || String || Label of the second field of free use in the requests (write 'DoNotShow' to hide it)
|-
| ''attribute_reserved3'' || String || Label of the third field of free use in the requests (write 'DoNotShow' to hide it)
|-
| ''backup_frequency'' || Integer || Minimum amount of hours that need to pass for the system to generate a new copy of the database
|-
| ''backup_history'' || Integer || Maximum number of copies of the database kept (once reached, the oldest copy in the folder is deleted)
|-
| ''bluetooth_enabler'' || String || Indicates the availability of automatic tests through Bluetooth connection (accepted values are 'Enabled' and 'Disabled'), which is only used in the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page IMAGING project]
|-
| ''csv_decimal'' || String || Specifies the character used to represent the decimal point in numerical values in the generated csv file (accepted values are ''.'' and '','')
|-
| ''csv_delimiter'' || String || Specifies the character used to separate fields in the generated csv file (accepted values are '';'' and '','')
|-
| ''default_language'' || String || Language set by default on logging in (the same for all users)
|-
| ''filename_background'' || String || File containing the image displayed in the background
|-
| ''filename_favicon'' || String || Icon of the system used in the browser tab
|-
| ''filename_sidebarlogo'' || String || File containing the logo displayed at the bottom of the sidebar
|-
| ''filename_worklistlogo'' || String || Logo used in the worklist reports
|-
| ''groups_profiles'' || String || Shows groups and profiles for analytical tests (accepted values are 'Enabled' and 'Disabled')
|-
| ''log_history'' || Integer || Maximum number of days to keep registries in the access log (those older than this will be automatically deleted)
|-
| ''max_image_volume'' || Integer || Maximum number of megabytes used to store images (once reached, the oldest ones in the folder are deleted)
|-
| ''name'' || String || Caption to appear at the top of the screen (in the navigation bar), as well as in the worklist and reports
|-
| ''report_subtitle'' || String || Subtitle to be used in the worklist and reports
|-
| ''set_sample_delivery_default'' || String || It indicates whether samples are assumed to be delivered or not by default (accepted values are 'True' and 'False'.
|-
| ''table_default_paging'' || Integer || This indicates the initial paging of all the tables (accepted values are 5, 10 or 25)
|-
| ''table_min_rows_for_search'' || Integer || This is the minimum number of rows a table must have to show the corresponding search field
|-
| ''timeout'' || Integer || Time (in minutes) after which the connection to the backend requires a new log in
|-
| ''version'' || String || Version of the system
|-
| ''zip_password'' || String || This is the password that will be used to generate the downloaded zip file
|}
</translate>

Define new language

2026-01-08T16:42:57Z

Alberto:

[[Category:Define new language]]
<languages/>
<translate>

In this section you will find the information that will help you to add new languages to the ARIS application.


__TOC__

==Introducction== 
The multilanguage system of ARIS is implemented through some files, but to add a new language you will only need to know about two of them: ''languageList.json'' and the language JSON files.
You will find these files in the ''lang'' folder in ARIS system files (under "C:\Users\Public\ARIS\Frontend\build" by default in MSWindows).

===''languageList.json''=== 
This file contains a list of all the languages that the multilanguage system of the ARIS application can handle. All the languages it contains will appear in the dropdown menu on the ARIS navigation bar.
[[File:LanguageList.PNG|none|400px|thumb| ''languageList.json'']]

===Language JSON files=== 
By default, the ARIS system contains language JSON files that correspond to the Spanish, Portuguese, and English languages.
These files contain all the translations of the messages displayed in ARIS interface, following a JSON structure where the key has to be the same in all the language files, you can see the example in the images below.
[[File:EnJson.png|none|400px|thumb| English JSON file]]
[[File:EsJson.png|none|400px|thumb| Spanish JSON file. Notice that the keys for the same words are the same as in both files]]

==How to add a new language?== 
Thanks to how the multilanguage system is implemented, in order to add a new language not provided by default in the distribution, you only have to follow two simple steps that we explain below.


· '''Step 1:''' Add a new language JSON file. Remember that it must follow the same structure as the files for other languages, so they must all contain the same keys. We recommend naming the new files as the [https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1] code of the new language.


· '''Step 2:''' Add the new language to the ''languageList.json'' file just as the other languages already listed.
''{"fileName": "NewLanguageCode", "label": "NewLanguageName"},''


You don't have to worry about modifying any other file, if you have followed the above two steps you have successfully added a new language to the ARIS system, that will automatically be added to the Language in the [[User Guide#Navigation bar|Navigation bar]].
</translate>

Define new language

2026-01-08T16:42:31Z

Alberto:

[[Category:Define new language]]
<languages/>
<translate>

In this section you will find the information that will help you to add new languages to the ARIS application.


__TOC__

==Introducction== 
The multilanguage system of ARIS is implemented through some files, but to add a new language you will only need to know about two of them: ''languageList.json'' and the language JSON files.
You will find these files in the ''lang'' folder in ARIS system files (under "C:\Users\Public\ARIS\Frontend\build" by default in MSWindows).

===''languageList.json''=== 
This file contains a list of all the languages that the multilanguage system of the ARIS application can handle. All the languages it contains will appear in the dropdown menu on the ARIS navigation bar.
[[File:LanguageList.PNG|none|400px|thumb| ''languageList.json'']]

===Language JSON files=== 
By default, the ARIS system contains language JSON files that correspond to the Spanish, Potuguese, and English languages.
These files contain all the translations of the messages displayed in ARIS interface, following a JSON structure where the key has to be the same in all the language files, you can see the example in the images below.
[[File:EnJson.png|none|400px|thumb| English JSON file]]
[[File:EsJson.png|none|400px|thumb| Spanish JSON file. Notice that the keys for the same words are the same as in both files]]

==How to add a new language?== 
Thanks to how the multilanguage system is implemented, in order to add a new language not provided by default in the distribution, you only have to follow two simple steps that we explain below.


· '''Step 1:''' Add a new language JSON file. Remember that it must follow the same structure as the files for other languages, so they must all contain the same keys. We recommend naming the new files as the [https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1] code of the new language.


· '''Step 2:''' Add the new language to the ''languageList.json'' file just as the other languages already listed.
''{"fileName": "NewLanguageCode", "label": "NewLanguageName"},''


You don't have to worry about modifying any other file, if you have followed the above two steps you have successfully added a new language to the ARIS system, that will automatically be added to the Language in the [[User Guide#Navigation bar|Navigation bar]].
</translate>

Translations:Configuration/27/es

2025-05-24T08:27:41Z

Alberto: Created page with "El orden en el que apareceran más tarde los valores en los desplegables no será alfabético, sinó el orden de inserción en la lista de valores (esto puede ser útil para fijar un orden, en caso de que hayan muchos valores)."

El orden en el que apareceran más tarde los valores en los desplegables no será alfabético, sinó el orden de inserción en la lista de valores (esto puede ser útil para fijar un orden, en caso de que hayan muchos valores).

Configuration

2025-05-24T08:25:56Z

Alberto: Marked this version for translation

[[Category:Configuration]]
<languages/>
<translate>

The configuration functionality allows the user to manipulate ARIS, adding or changing some of its aspects for a better customization.
These have been divided into two groups, depending on the knowledge needed to use them.
The first group is absolutely generic and both laboratory supervisor and system administrator should be able to provide the required information.
However, for the second group, more specific biomedical knowledge will be needed, and consequently only the laboratory supervisor is allowed to do it.


<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph ConfigurationDiagram {
nodesep=0.05;
node [shape=oval style=filled fillcolor=orange fontsize="9pt" margin="0.01, 0.01"];
Configuration [label="Configuration"];
ConfGeneric [label="Generic", URL="#Generic_configuration"];
ConfTechnical [label="Technical", URL="#Technical_configuration"];
Configuration -> ConfGeneric;
Configuration -> ConfTechnical;
Regions [label="Regions", shape=tab, URL="#Generic_configuration"];
Locations [label="Locations", shape=tab, URL="#Generic_configuration"];
Units [label="Units", shape=tab, URL="#Generic_configuration"];
HealthFacilities [label="Health, Facilities" shape=tab, URL="#Generic_configuration"];
Physicians [label="Physicians", shape=tab, URL="#Generic_configuration"];
Gender [label="Gender", shape=tab, URL="#Generic_configuration"];
IdentificationCards [label="Identification Cards", shape=tab, URL="#Generic_configuration"];
StateOfTheRequest [label="State of the Request", shape=tab URL="#State_of_the_request"];
ConfGeneric -> Regions;
ConfGeneric -> Locations;
ConfGeneric -> Units;
ConfGeneric -> HealthFacilities;
ConfGeneric -> Physicians;
ConfGeneric -> Gender;
ConfGeneric -> IdentificationCards;
ConfGeneric -> StateOfTheRequest;
LaboratoryAreas [label="Laboratory Areas", shape=tab, URL="#Technical_configuration"];
AnalyticalTests [label="Analytical Tests", shape=tab URL="#Analytical_tests"];
AnalyticalTestsGroups [label="Analytical Tests Groups", shape=tab URL="#Analytical_tests_groups"];
AnalyticalProfiles [label="Analytical Profiles", shape=tab URL="#Analytical_profiles"];
KindsOfSamples [label="Kinds of Samples", shape=tab, URL="#Technical_configuration"];
SampleIncidents [label="Sample Incidents", shape=tab, URL="#Technical_configuration"];
SampleOrigins [label="Sample Origins", shape=tab, URL="#Technical_configuration"];
PregnancyPhases [label="Pregnancy Phases", shape=tab, URL="#Technical_configuration"];
DataTypes [label="Datatypes", shape=tab, URL="#Datatypes"];
ReportingOrder [label="Reporting Order", shape=tab, URL="#Reporting_order"];
ConfTechnical -> LaboratoryAreas;
ConfTechnical -> AnalyticalTests;
ConfTechnical -> AnalyticalTestsGroups;
ConfTechnical -> AnalyticalProfiles;
ConfTechnical -> KindsOfSamples;
ConfTechnical -> SampleIncidents;
ConfTechnical -> SampleOrigins;
ConfTechnical -> PregnancyPhases;
ConfTechnical -> DataTypes;
ConfTechnical -> ReportingOrder;
{ rank=same; Regions Units Physicians IdentificationCards LaboratoryAreas AnalyticalTestsGroups KindsOfSamples SampleOrigins DataTypes}
{ rank=same; ConfGeneric ConfTechnical}
{ rank=sink; Locations HealthFacilities Gender StateOfTheRequest AnalyticalTests AnalyticalProfiles SampleIncidents PregnancyPhases ReportingOrder}}
</graphviz>
</div>


__TOC__


==Generic configuration==
[[File:Genericconfiguration.PNG|right|600px|thumb|Editing the labels used for the states]]
This form controls the values of all non-free text fields (i.e., those that appear when clicking on an [[User Guide#General features|arrow]]) within the system. Through each tab, the user is able to create, edit and delete the values of one of these fields.
If the laboratory is not interested in one of the values, but the user does not wish to delete the information from the system, it can be simply disabled, so it will not be shown in the corresponding drop-down menu. This is done by unticking the ''Active'' checkbox.
This is a very important feature, since deleting some configuration value will produce a cascade effect that will delete all other configuration records pointing to the deleted one (e.g., deleting a region will delete all its locations).
Patients or requests will not be deleted, but the corresponding information will not be displayed any more (e.g., after deleting a region, this information in the patient will become empty).</br>
[[File:Activecheckbox.PNG|75px|Activated checkbox]] ⇔ [[File:Deactivatedcheckbox.PNG|75px|Deactivated checkbox]] </br>
List of tabs:
*Regions (initially empty)
*Locations (initially empty)
*Units
*Health Facilities (initially empty)
*Physicians (initially empty)
*Gender
*Identification cards
*State of the request


Some of them also include hierarchical information. Thus, physicians point to health facilities, health facilities point to locations and these to regions. This information is used in the forms to show the right available values depending on the parent choice in the hierarchy.


===State of the request===
From the ''state of the request'' tab, only the ''label'' field can be edited. Notice that this indicates the different phases a request goes through in the application during its lifecycle, and not only a passive value to be stored.


==Technical configuration==
The ''Laboratory areas'', ''Kinds of sample'', ''Sample incidents'', ''Sample origins'' and ''Pregnancy phases'' tabs, have exactly the same effect as the ones under the [[#Generic configuration|generic configuration]] (i.e., they simply provide the available values in drop boxes).
However, the following tabs have further effects in the behaviour of the forms.


===Analytical tests===
[[File:Analyticalprofile.PNG|right|thumb|700px| Editing analytical profiles]]
This is without doubt the most crucial concept in the configuration, since it defines the available kinds of tests in the laboratory.
They are identified by a name, but also contain a code that will always be shown next to the name.
To facilitate the management of the laboratory, kinds of tests are assigned to a laboratory area, which will be used both in the generation of reports for the patients, and in the analysis of data regarding the performance of the laboratory itself.


Each kind of test is then related to a kind of sample.
Only after that kind of sample is provided by the patient, the corresponding test will be allowed to have an associated result.


Each test must have a [[#Datatypes|datatype]], which indicates the kind of result it will accept, this being either numerical (integer or real) or enumerate.
For numerical test results, units of the test can be indicated for informative purposes, together with upper and lower bounds of the result can be defined.
These will be automatically checked.
Only results within the declared boundaries will get a green tick next to them.
Those outside the boundaries will be detected and automatically marked with a red cross.
Validating the value will rely anyway on the laboratory supervisor.
However, a note can be provided here to indicate exceptions to the boundaries or any information that is considered relevant to either the technician or the supervisor.


Finally, there are two specific boolean fields:
* Referred → Indicates that an action or test is performed in another hospital. The option marked in the configuration only determines the default of this field for each test. It does not impede the laboratory supervisor from choosing differently in the [[Requests|Requests]] forms.
* Automatic → Enables the kind of test to be partially automated. The result of the test is not manually obtained by a person, but by an AI. If this option is disabled in the configuration, the laboratory supervisor will not be able to mark it otherwise in the [[Requests|Requests]] forms. However, if it is enabled, the laboratory supervisor will be able to choose if they desire for the test to be done automatically or not in the [[Requests|Requests]] forms.


===Analytical tests groups===
In this tab, groups of tests can be formed for a quicker selection when choosing which tests to perform on a patient. When creating or editing a new group, a ''Group Of Tests Information'' form must be filled in or modified. In this form, the group must be given a name and the laboratory supervisor must choose the tests included in the group from the box provided. In the left-hand side list, the groups are in alphabetical order and if the laboratory supervisor wishes for a quicker option, there is a search bar on top of the box to write down and filter the tests.
Simply clicking on the name of a test adds it to the group, hence appearing in the right-hand side list.


The analytical tests groups are also used to sort the tests in the generated report of a request.


===Analytical profiles===
In this tab, profiles of tests can be formed for a quicker selection when choosing which groups of tests or individual tests to perform on a patient.
When creating or editing a new profile, an ''Analytical Profile Information'' form must be filled in or modified.
In this form, the profile must be given a name and the laboratory supervisor must choose the tests and the groups included in the profile from the lists provided.
The groups and tests are in alphabetical order and if the laboratory supervisor wishes for a quicker option, there is a search bar on top of the box to write down and filter the tests and groups.


Choosing a group selects in the corresponding list all the tests belonging to it.
Then, these cannot be individually removed from the profile, but only by removing the group.
Moreover, a test added later to the group will automatically appear as part of any profile containing that group, which is indicated by a lock icon next to the test name.


Analytical profiles do not have any effect in the report generated for a request.

===Datatypes=== 


Enumerate datatypes can be defined here (integer and real numbers are always available).
These are simply lists of potential results that can be used in any kind of test.


The order of the values later in the dropdown lists will not be alphabetical, but their order of insertion in the value list (this can be useful to fix an order, if there are many values).


===Reporting order===
[[File:Reportingorder.PNG|Centre|500px|thumb|Editing the laboratory areas order from the reporting areas tab]]
This tab allows ordering the elements in the PDF worklist and in the report of a request.
The tests appearing in them will be firstly sorted by laboratory area, then groups of tests, and finally individual tests.
This is done by choosing one of the three elements, which will lead to another form with a list and two vertical arrows on the left side of the image.
Any number of elements can be simultaneously selected by simply clicking on them.
Then, the arrows will allow moving them up or down in the list, and hence in the generated PDF documents.
</translate>

Configuration

2025-05-24T08:25:36Z

Alberto:

[[Category:Configuration]]
<languages/>
<translate>

The configuration functionality allows the user to manipulate ARIS, adding or changing some of its aspects for a better customization.
These have been divided into two groups, depending on the knowledge needed to use them.
The first group is absolutely generic and both laboratory supervisor and system administrator should be able to provide the required information.
However, for the second group, more specific biomedical knowledge will be needed, and consequently only the laboratory supervisor is allowed to do it.


<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph ConfigurationDiagram {
nodesep=0.05;
node [shape=oval style=filled fillcolor=orange fontsize="9pt" margin="0.01, 0.01"];
Configuration [label="Configuration"];
ConfGeneric [label="Generic", URL="#Generic_configuration"];
ConfTechnical [label="Technical", URL="#Technical_configuration"];
Configuration -> ConfGeneric;
Configuration -> ConfTechnical;
Regions [label="Regions", shape=tab, URL="#Generic_configuration"];
Locations [label="Locations", shape=tab, URL="#Generic_configuration"];
Units [label="Units", shape=tab, URL="#Generic_configuration"];
HealthFacilities [label="Health, Facilities" shape=tab, URL="#Generic_configuration"];
Physicians [label="Physicians", shape=tab, URL="#Generic_configuration"];
Gender [label="Gender", shape=tab, URL="#Generic_configuration"];
IdentificationCards [label="Identification Cards", shape=tab, URL="#Generic_configuration"];
StateOfTheRequest [label="State of the Request", shape=tab URL="#State_of_the_request"];
ConfGeneric -> Regions;
ConfGeneric -> Locations;
ConfGeneric -> Units;
ConfGeneric -> HealthFacilities;
ConfGeneric -> Physicians;
ConfGeneric -> Gender;
ConfGeneric -> IdentificationCards;
ConfGeneric -> StateOfTheRequest;
LaboratoryAreas [label="Laboratory Areas", shape=tab, URL="#Technical_configuration"];
AnalyticalTests [label="Analytical Tests", shape=tab URL="#Analytical_tests"];
AnalyticalTestsGroups [label="Analytical Tests Groups", shape=tab URL="#Analytical_tests_groups"];
AnalyticalProfiles [label="Analytical Profiles", shape=tab URL="#Analytical_profiles"];
KindsOfSamples [label="Kinds of Samples", shape=tab, URL="#Technical_configuration"];
SampleIncidents [label="Sample Incidents", shape=tab, URL="#Technical_configuration"];
SampleOrigins [label="Sample Origins", shape=tab, URL="#Technical_configuration"];
PregnancyPhases [label="Pregnancy Phases", shape=tab, URL="#Technical_configuration"];
DataTypes [label="Datatypes", shape=tab, URL="#Datatypes"];
ReportingOrder [label="Reporting Order", shape=tab, URL="#Reporting_order"];
ConfTechnical -> LaboratoryAreas;
ConfTechnical -> AnalyticalTests;
ConfTechnical -> AnalyticalTestsGroups;
ConfTechnical -> AnalyticalProfiles;
ConfTechnical -> KindsOfSamples;
ConfTechnical -> SampleIncidents;
ConfTechnical -> SampleOrigins;
ConfTechnical -> PregnancyPhases;
ConfTechnical -> DataTypes;
ConfTechnical -> ReportingOrder;
{ rank=same; Regions Units Physicians IdentificationCards LaboratoryAreas AnalyticalTestsGroups KindsOfSamples SampleOrigins DataTypes}
{ rank=same; ConfGeneric ConfTechnical}
{ rank=sink; Locations HealthFacilities Gender StateOfTheRequest AnalyticalTests AnalyticalProfiles SampleIncidents PregnancyPhases ReportingOrder}}
</graphviz>
</div>


__TOC__

==Generic configuration== 
[[File:Genericconfiguration.PNG|right|600px|thumb|Editing the labels used for the states]]
This form controls the values of all non-free text fields (i.e., those that appear when clicking on an [[User Guide#General features|arrow]]) within the system. Through each tab, the user is able to create, edit and delete the values of one of these fields.
If the laboratory is not interested in one of the values, but the user does not wish to delete the information from the system, it can be simply disabled, so it will not be shown in the corresponding drop-down menu. This is done by unticking the ''Active'' checkbox.
This is a very important feature, since deleting some configuration value will produce a cascade effect that will delete all other configuration records pointing to the deleted one (e.g., deleting a region will delete all its locations).
Patients or requests will not be deleted, but the corresponding information will not be displayed any more (e.g., after deleting a region, this information in the patient will become empty).</br>
[[File:Activecheckbox.PNG|75px|Activated checkbox]] ⇔ [[File:Deactivatedcheckbox.PNG|75px|Deactivated checkbox]] </br>
List of tabs:
*Regions (initially empty)
*Locations (initially empty)
*Units
*Health Facilities (initially empty)
*Physicians (initially empty)
*Gender
*Identification cards
*State of the request


Some of them also include hierarchical information. Thus, physicians point to health facilities, health facilities point to locations and these to regions. This information is used in the forms to show the right available values depending on the parent choice in the hierarchy.

===State of the request=== 
From the ''state of the request'' tab, only the ''label'' field can be edited. Notice that this indicates the different phases a request goes through in the application during its lifecycle, and not only a passive value to be stored.

==Technical configuration== 
The ''Laboratory areas'', ''Kinds of sample'', ''Sample incidents'', ''Sample origins'' and ''Pregnancy phases'' tabs, have exactly the same effect as the ones under the [[#Generic configuration|generic configuration]] (i.e., they simply provide the available values in drop boxes).
However, the following tabs have further effects in the behaviour of the forms.

===Analytical tests=== 
[[File:Analyticalprofile.PNG|right|thumb|700px| Editing analytical profiles]]
This is without doubt the most crucial concept in the configuration, since it defines the available kinds of tests in the laboratory.
They are identified by a name, but also contain a code that will always be shown next to the name.
To facilitate the management of the laboratory, kinds of tests are assigned to a laboratory area, which will be used both in the generation of reports for the patients, and in the analysis of data regarding the performance of the laboratory itself.


Each kind of test is then related to a kind of sample.
Only after that kind of sample is provided by the patient, the corresponding test will be allowed to have an associated result.


Each test must have a [[#Datatypes|datatype]], which indicates the kind of result it will accept, this being either numerical (integer or real) or enumerate.
For numerical test results, units of the test can be indicated for informative purposes, together with upper and lower bounds of the result can be defined.
These will be automatically checked.
Only results within the declared boundaries will get a green tick next to them.
Those outside the boundaries will be detected and automatically marked with a red cross.
Validating the value will rely anyway on the laboratory supervisor.
However, a note can be provided here to indicate exceptions to the boundaries or any information that is considered relevant to either the technician or the supervisor.


Finally, there are two specific boolean fields:
* Referred → Indicates that an action or test is performed in another hospital. The option marked in the configuration only determines the default of this field for each test. It does not impede the laboratory supervisor from choosing differently in the [[Requests|Requests]] forms.
* Automatic → Enables the kind of test to be partially automated. The result of the test is not manually obtained by a person, but by an AI. If this option is disabled in the configuration, the laboratory supervisor will not be able to mark it otherwise in the [[Requests|Requests]] forms. However, if it is enabled, the laboratory supervisor will be able to choose if they desire for the test to be done automatically or not in the [[Requests|Requests]] forms.

===Analytical tests groups=== 
In this tab, groups of tests can be formed for a quicker selection when choosing which tests to perform on a patient. When creating or editing a new group, a ''Group Of Tests Information'' form must be filled in or modified. In this form, the group must be given a name and the laboratory supervisor must choose the tests included in the group from the box provided. In the left-hand side list, the groups are in alphabetical order and if the laboratory supervisor wishes for a quicker option, there is a search bar on top of the box to write down and filter the tests.
Simply clicking on the name of a test adds it to the group, hence appearing in the right-hand side list.


The analytical tests groups are also used to sort the tests in the generated report of a request.

===Analytical profiles=== 
In this tab, profiles of tests can be formed for a quicker selection when choosing which groups of tests or individual tests to perform on a patient.
When creating or editing a new profile, an ''Analytical Profile Information'' form must be filled in or modified.
In this form, the profile must be given a name and the laboratory supervisor must choose the tests and the groups included in the profile from the lists provided.
The groups and tests are in alphabetical order and if the laboratory supervisor wishes for a quicker option, there is a search bar on top of the box to write down and filter the tests and groups.


Choosing a group selects in the corresponding list all the tests belonging to it.
Then, these cannot be individually removed from the profile, but only by removing the group.
Moreover, a test added later to the group will automatically appear as part of any profile containing that group, which is indicated by a lock icon next to the test name.


Analytical profiles do not have any effect in the report generated for a request.

===Datatypes=== 


Enumerate datatypes can be defined here (integer and real numbers are always available).
These are simply lists of potential results that can be used in any kind of test.

The order of the values later in the dropdown lists will not be alphabetical, but their order of insertion in the value list (this can be useful to fix an order, if there are many values).

===Reporting order=== 
[[File:Reportingorder.PNG|Centre|500px|thumb|Editing the laboratory areas order from the reporting areas tab]]
This tab allows ordering the elements in the PDF worklist and in the report of a request.
The tests appearing in them will be firstly sorted by laboratory area, then groups of tests, and finally individual tests.
This is done by choosing one of the three elements, which will lead to another form with a list and two vertical arrows on the left side of the image.
Any number of elements can be simultaneously selected by simply clicking on them.
Then, the arrows will allow moving them up or down in the list, and hence in the generated PDF documents.
</translate>

Printed Manual

2025-05-08T08:39:35Z

Alberto:

__TOC__

<div class="print-pagebreak"></div>

= User Guide =
{{:User Guide}}

<div class="print-pagebreak"></div>

= Patients =
{{:Patients}}

<div class="print-pagebreak"></div>

= Requests =
{{:Requests}}

Printed Manual

2025-05-08T08:38:24Z

Alberto:

__TOC__

= User Guide =
{{:User Guide}}

= Patients =
{{:Patients}}

= Requests =
{{:Requests}}

Printed Manual

2025-05-08T08:36:44Z

Alberto:

= User Guide =
{{:User Guide}}

= Patients =
{{:Patients}}

= Requests =
{{:Requests}}

Printed Manual

2025-05-08T08:35:24Z

Alberto:

= Chapter 1 =
{{:User Guide}}

= Chapter 2 =
{{:Patients}}

= Chapter 3 =
{{:Requests}}

Patients

2025-05-08T07:17:49Z

Alberto:

[[Category:Patients]]
<languages/>
<translate>

The basic information unit is the patient.
Before creating any analytical request, the corresponding patient record must exist.
This will survive the livespan of the request, and will contain all their history.


<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg' rendered='dot'>
digraph FunctionalitiesDiagram {
node [shape=oval style=filled fillcolor=orange fontsize="9pt"];
//----- Patients graph
// Nodes
Patients [label="Patients"];
P_Create [label="Create", URL="#Create"];
P_Search [label="Search", URL="#Search"];
P_BasicInformation [label="Basic Information", shape="tab", URL="#Create"];
P_DocumentationInformation [label="Documentation", shape="tab", URL="#Create"];
P_BirthData [label="Birth", shape="tab", URL="#Create"];
P_ContactData [label="Contact", shape="tab", URL="#Create"];
P_ResidenceData [label="Residency", shape="tab", URL="#Create"];
P_AdditionalInformation [label="Extra Information", shape="tab", URL="#Create"];
P_Requests [label="Requests", shape="tab", URL="#Create"];
// Edges
Patients -> P_Create;
Patients -> P_Search;
P_Create -> P_BasicInformation;
P_Search -> P_BasicInformation;
P_Search -> P_Requests;
P_BasicInformation -> P_DocumentationInformation [dir=both minlen=2];
P_DocumentationInformation -> P_BirthData [dir=both minlen=2];
P_BirthData -> P_ContactData [dir=both minlen=2];
P_ContactData -> P_ResidenceData [dir=both minlen=2];
P_ResidenceData -> P_AdditionalInformation [dir=both minlen=2];
{ rank=same; P_BasicInformation P_DocumentationInformation P_BirthData P_ContactData P_ResidenceData P_AdditionalInformation P_Requests}
}
</graphviz>
</div>


__TOC__

==Create== 


This page is divided in a form with the basic information of the patient, involving the obligatory ([[File:Asterisk.PNG|30px]]) entry of the ''name'', ''last name'', ''gender'', ''birth date'' and ''phone'', as well as multiple tabs with additional non-mandatory information.


#Documentation information → Information such as the ''number of clinical history'' or the ''type'' and ''number of an identifier card''.
#Birth information → Complementary information such as the ''birth region'' and ''locality''. Added to the previously introduced ''birth date'' and the automatically calculated ''age'' of the patient.
#Contact information → Additional contact information.
#Residency information → Apart from the basic residency information, it contains a checkbox at the bottom, ''Add provenance region?''. This option is for when a patient, although local, has come from outside the country. When the box is ticked, two more boxes appear on the forms, ''Provenance region'' and ''Provenance city''. [[File:Addprovenanceregion.PNG|750px]]
#Extra information → Other data such as parent's names. The ''Reserved 1, 2 and 3'' are boxes whose names can be modified through the [[System administration|System administration]] if the laboratory requires any specific information from the patients.
#Requests → This actually not a step in the creation or update of the patient, but just a read-only tab containing all the requests of the patient.


Once the mandatory information is entered, the ''Save values'' button at the bottom right of the page will be available.

==Search and Edition== 


{| class="wikitable" style="margin:auto"
|+ Table found in the Search function of the system
|-
! Name !! Phone !! Identification !! Creation Date !! Last Modification Date
|-
| The first column shows the patient's name || The patient's contact number is listed in this column || Here, the internal, automatically generated identification number can be found || This column informs about when the patient's information was first inputted into the system || The last time the patient's information was altered in the system is shown here
|}


Arrows appear next to each heading in the table when the mouse is hovered over them to manipulate the order the information is showed in for each heading.


On clicking on any row, a new form will appear with the age, gender, phone and internal identifier of the patient as well as tabs with the information on the patient's documentation information, birth information, contact information, residency information, extra information and requests. From this page, the patient manager or laboratory technician can also edit the patient through the edit patient button at the bottom right of the page. To return to the search patients page, there is a Return button at the bottom left of the screen.


Notice that to avoid inconsistences in the system, patients once created cannot be deleted.

==Duplicate Detection== 


[[File:Duplicate_patient.mp4|right|500px]]
The e-mail address as well as the Identifier document number are optional. Nevertheless, if provided, they identify a patient (i.e., they do not allow repetitions).
Besides this, to guarantee the existence of an identifier for each patient, a consecutive number is always automatically generated and internally assigned by the system.


Moreover, patients of similar name, parent names, age and telephone number are detected as potential duplicates at creation time.
On happening this, a warning is displayed, and the patient manager or laboratory technician can either modify the corresponding data or move ahead with the creation.


Notice that two patients are not considered similar (i.e., they are considered different) if either:
* Their age difference is greater than ten years, or
* Their name is different enough (more than 50% characters), or
* Their parent names are provided and at least one of them is different enough (more than 30% characters differ considering the three names together), or
* Their telephone numbers are different enough (more than 50% of the digits).
</translate>

User Guide

2025-05-08T07:16:27Z

Alberto:

[[Category:User Guide]]
<languages/>
<translate>

This is a step-by-step user guide on the ARIS system. It contains information on what each functionality does and instructions on how to use them.
<div style="float:right; margin: 0px 0px 0px 0px">
<graphviz border='frame' format='svg'>
digraph FunctionalitiesDiagram {
node [shape="oval" style=filled fillcolor="orange" fontsize="9pt"];
//----- Main graph
// Nodes
ARIS [label="ARIS"];
//----- Patients graph
// Nodes
Patients [label="Patients" URL="[[Patients]]"];
// Edges
ARIS -> Patients;
//----- Requests graph
// Nodes
Requests [label="Requests" URL="[[Requests]]"];
// Edges
ARIS -> Requests;
//----- Data Analysis graph
// Nodes
DataAnalysis [label="Data Analysis" URL="[[Data_analysis]]"];
// Edges
ARIS -> DataAnalysis;
//----- Configuration graph
// Nodes
Configuration [label="Configuration" URL="[[Configuration]]"];
// Edges
ARIS -> Configuration;
//----- System Administration graph
// Nodes
SystemAdministration [label="System Administration" URL="[[System_administration]]"];
// Edges
ARIS -> SystemAdministration;
//----- System Information graph
// Nodes
SystemInformation [label="System Information"];
// Edges
ARIS -> SystemInformation;}
</graphviz>
</div>


__TOC__


==Log in page==
[[File:Login_-_Made_with_Clipchamp.mp4|right|500px]]


The first step to work with ARIS, once the software is properly downloaded and installed (see [[Installation and Upgrades|Installation and Upgrades]]), the users have to create each an identity (username and password). Entering these both credentials will allow the access to the software and the screen will show now the main page of the system.
If the username or password is incorrect, a red information box will pop up above the ''log in now'' button.


It is crucial to remember that the system has three different [[System administration#Roles|roles]] with different and complementary functionalities.
Consequently, at least three users need to exist, one with each different role ''System Administrator'', ''Laboratory Technician'' and ''Laboratory Supervisor''.


Since the interface is through a browser, we have all of its typical features.
Among others saving usernames and passwords (some browsers even do it by default).
Notice that in this case, this is not a good practice and should be avoided.
</br>
</br>


==Sidebar==
[[File:Sidebar.PNG|right|thumb|Sidebar found on the left side of the interface]]
The sidebar contains information about the user's account and is a tool to navigate between the different functionalities of the system. </br>
At the very top of the orange sidebar, the software's name is displayed in a bold white font.


Just below the title, there is a small box that informs the user of the account currently in use, by means of the user's name and role corresponding to this username. </br>
Underneath, there is a list of the different functionalities listed below.


{| class="wikitable" style="margin:auto"
|+ Functionalities of the system
|-
! Functionality !! Description
|-
| [[Patients|Patients]] [[File:Patients.PNG|25px|right]] || Create and edit patients, as well as navigate through the patients list.
|-
| [[Requests|Requests]] [[File:Requests.PNG|25px|right]] || Create and edit requests, as well as different types of search.
|-
| [[Data analysis|Data analysis]] [[File:Data_Analysis.PNG|25px|right]] || Basic statistics on the performance of the laboratory.
|-
| [[Configuration|Configuration]] [[File:Configuration.PNG|25px|right]] || Options offered by the system in the different dropboxes of the forms.
|-
| [[System administration|System administration]] [[File:System_administration.PNG|25px|right]] || User administration and edition of software parameters.
|-
| System information [[File:System_Information.PNG|25px|right]] || Software license, version and credits.
|}


Most of these functionalities have subsets of actions that can be accessed through the small downward arrow to the right of the name. To change between actions, simply click on the desired functionality and the display will change.


==General features==
; Arrow
:[[File:Arrow.PNG|left|50px]] This downward <u>arrow</u> is present when there is a menu with different options to choose from. The user can filter the options by typing out normally in the box. The options displayed can be manipulated through the [[Configuration|Configuration]] functionality.<BR/>


; Asterisk
:[[File:Asterisk.PNG|left|50px]] The red <u>asterisk</u> represents a mandatory field. In other words, if a box contains an asterisk, it must be filled in order to keep doing the desired task. The current action in progress will not conclude until all the corresponding fields are filled.<BR/>


; Delete
:[[File:Delete.PNG|left|50px]] This button is generally found in the [[Configuration|Configuration]] functionality. It allows the user to delete predefined instances of the different concepts, such as the regions or locations available in the creation of patients. There are exceptions to this action, the instances of some concepts are not deletable. For example, it is not possible to delete patients, requests or users.<BR/>


; Editing
:In general, there is not any icon associated to the edition of elements. By simply clinking on the corresponding row, its details are displayed. These are then editable, except in the case of patients, that are read-only until a button to enable modifications is pressed.<BR/>


:[[File:Patientinfo.PNG|left|50px]] The exception to this rule is the details of a test. In this case, this icon corresponds to the possibility of showing and potentially changing the results and notes of the test, as well as more information about the corresponding sample. This happens in the ''Analytical tests'' tab reached through either [[Requests#Introduce results|Introduce results]], [[Requests#Validate results|Validate results]] or [[Requests#Search historic|Historical requests]].<BR/>


; Search bar
:[[File:Searchpatients.PNG|centre|750px]] There is a search box at the top of most of the forms that contain tables with lists of elements, like the [[Patients#Search and Edition|''search patients'']] or [[Requests#Create|''create requests'']] tabs. This search box allows the user to filter by different fields like name, phone, health facility ID, creation date or last modification date. To choose one of these, the user must click on the downwards arrow found to the right of ''search field'' and pick the desired field (this possibility is not available if the table contains only one column to be searched). Once the field is chosen, the user can type out the information corresponding to the search field in the box on the left.<BR/>


:There is a system parameter that establishes the minimum number of elements required for the search box to be shown (i.e., tables with a small number of elements may not require a search functionality).


; Locked item
:[[File:Lock.PNG|left|50px]] This icon appears attached to elements of a list that cannot be directly selected or deselected. This happens with groups of tests or profiles. Thus, choosing a group of tests does not allow removing any of its components, as they are an indivisible set.<BR/>

==Navigation bar== 


; Language
[[File:Language1.PNG|left|50px]]
:The <u>language</u> in use is displayed in the top right corner of the page, the user is able to change it depending on their preference by clicking on the text and choosing the language desired. There are currently two options of language for the system; English and Spanish.


; Profile
[[File:Profile.PNG|left|50px]]
:When clicking on this icon, found in the top right corner of the page, two options will show up. The first, is the <u>log-out</u> option, when pressing on this option, the page will change to the [[#Log in page|log in]] page, through which the user will be able to change the account they are using. The second icon, called <u>change password</u>, when clicked will produce a pop-up window where the user might change their password.
:; ''Change password''
::There are two ways of changing the password associated with the username:
::# The password can be changed by the user. All they have to do is press on the [[#Navigation bar|profile]] icon, click on change password, and a screen will come up with the title '''Change password'''. Next, the user must just fill in the required boxes with their current password, their desired password and, finally, confirm their new password.
::# Another method to change the password would involve accessing the [[System administration|system administration]] functionality and going to the [[System administration#Users|users]] tab. Once in this tab, the administrator can choose any other user, and click on edit user. Then, at the bottom of the page, the administrator can find two non-obligatory fields named ''password'' and ''repeat password''. These must be filled in order to change the password.


; Bluetooth (not visible by default)
[[File:Bluetooth.PNG|left|50px]]
:By default, this icon is hidden, because most laboratories are not going to use this functionality (only those participating in the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/Main_Page IMAGING project]).
To make it visible, the value of the corresponding system parameter needs to be modified.
For this, a ''System Administrator'' needs to log in and go to [[System_administration#Parameters|Parameters]].
There, they need to set 'bluetooth_enabler' to ''Enable''.
This will make the icon visible to all 'Laboratory Technicians'.


:When a ''Laboratory Technician'' clicks this icon, the system will enable the [[Bluetooth|Bluetooth connection]] of the system, and the users will be able to connect their mobile device to ARIS. This capability is used to transfer images from the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/MobileApp:Main Mobile App] in case of automatic tests. When Bluetooth is active, the icon will turn orange. From the moment the icon is orange, all the behaviour is managed from the [http://dl-prod.essi.upc.edu/IMAGINGwiki/index.php/MobileApp:Main Mobile App] (i.e., from ARIS interface, you can only enable or disable the Bluetooth and everything happens in the background). On clicking again, the feature will be disabled and the icon will be grey.
</translate>

Printed Manual

2025-05-08T07:08:12Z

Alberto:

* [[User Guide]]
* [[Patients]]
* [[Requests]]