healthstat.be

healthstat.be admin Wed, 12/22/2021 - 05:35

General healthstat.be usage

General healthstat.be usage

IMPORTANT:

Before you can have access to reports in healthstat the Responsable for Access Entities (VTE/RAE) of your organisation needs to create you as a user in UMAN.

If you are a VTE/RAE please follow these guidelines:

There is access to healthstat.be at the top of each page:

  • Search through all accessible reports
  • Link through towards the healthdata.be knowledge base
  • Contact the healthstat.be support team
  • Change the display language
admin Sun, 10/03/2021 - 21:53

Log in to healthstat.be

Log in to healthstat.be

Use eID to use healthstat.be

There is a link at the top right of the main “Sign in with eID”

Once the link is accessed, you are automatically forwarded to the eHealth platform where you should authenticate using your eID. On the first screen select the language.

On the next screen select “Ga verder met e-ID via eHealth/Continuer avec carte d'Identité électronique”

Enter the eID pin code. You will be redirected to the 3rd step of the eHealth authentication. On the page select the organization for login.  Multiple organizations are possible so, select the correct one when consulting healthstat.be. In case no organization is available consult the VTE of your organization.

Once “Aanmelden/Inscription” is clicked, you will be automatically redirected to the healthstat.be homepage. On the top right your name and organization is seen.

Access already received to certain reports will be automatically visible on the left side of the screen.

Note: If there are no reports it means the necessary rights to access them has not been given yet. Please consult your VTE and ask him/her to assign the necessary data collections from within the healthstat.be application.

admin Sun, 10/03/2021 - 21:57

Consulting reports

Consulting reports

On the left side of the screen, different reports are seen. All different reports (or folders containing reports) are allowed to be viewed.

The small lock icon indicates that this is a private reports to which only a limited number of people have access to these. After selecting one of the reports, it could be possible that you are presented with a parameters page. This page will allow the report to be generated with the parameters you request.

Please select a value for all the required parameters. 

If all the parameters are correctly entered a report will be generated and it's directed to a page containing the output. Depending on the type of report, it could be a graph or a table.

admin Sun, 10/03/2021 - 22:01

User management

User management

If you are VTE responsible for your organization, use User management to access screens.

Through this interface it is possible to add users of your organization to the healthstat.be application

Note : Aaready connected people to healthstat.be will be visible in the user management page. Go directly go to their name and assign data collections.

Use the following information to fill in and add a user manually:

Once a user has been created, data collections can be assigned to a profile so private reports can be consulted.

admin Sun, 10/03/2021 - 22:08

Reports - Business Process - Project Phase

Reports - Business Process - Project Phase

The article describes the requirements of healthstat.be reports for monitoring projects by healthdata.be.

1. Introduction

The article explains the requirements of a report about the status of projects managed by healthdata.be (HD.be).This document includes 4 points:

  • the description of the HD.be internal project named METRICS behind these reports;
  • the description of management of projects within HD.be
  • the description of the dataset used to build the report
  • the report requirements.
  • the keys to analyze the reports

2. Project metrics

The aim of the Metrics project is to develop a data driven approach for steering all activities of HD.be. Currently, that implies the assessment of metrics grouped in 6 categories:

  1. Business Processes;
  2. External Interfaces Availability;
  3. Data Collection;
  4. Operations;
  5. Information Architecture and Terminology;
  6. Data Warehouse.

Each metrics category concerns a specific sub-project within the Metrics project. This document deals only with the Business Processes (BP) category. It focuses of status of projects by HD.be.

3. Project management within healthdata.be

Healthdata.be manages projects using 8 phases listed below:

  1. Request;
  2. Define;
  3. Propose;
  4. Build
  5. Test;
  6. Deploy;
  7. Run;
  8. Evaluate.

The  project management is implemented within a software tool named JIRA. Each phase of projects implies several tasks, sub-tasks or documents. Each issue related a project should be recorded in JIRA regarding the 7 phases previously described.
The phase 4 to 7 contains 3 sub-categories named:

  • Data Collection : data capture
  • DWH Exploitation : data management;
  • DWH External(reporting): data reporting.

4. Dataset used for the reporting

The data linked to the implementation of Business Processes for managing HD.be projects in JIRA are hosted in a cloud. An Extraction Transformation Loading (ETL) procedure has been designed to get these data named JIRA_DATASET. The structure of the JIRA_DATASET is shown in the Table 1. Each record fetched from JIRA_ DATASET corresponds to a task, a subtask or an EPIC in JIRA.

VARIABLE NAMEFUNCTIONAL DESCRIPTIONFUNCTIONAL NAME
DT_FETCHINGDate of fetching of JIRA_DATASETEXTRACTION DATE
TX_PROJ Fully name of the project (to validate with the planning sheet)PROJECT NAME
TX_KEY Unique identification of a ticket in JIRAJIRA IDENTIFCATION
TX_ISSUE_TYPE* Define the ticket being a task or document, that impact the possible values of the field TX_STATUSTASK TYPE
TX_SUMMARY Title of the ticket, i.e. the task or documentTASK SUMMARY
TX_STATUS* If TX_ISSUE_TYPE is task or sub-task, then TX_STATUS possible values are TO DO, IN PROGRESS, DONE, CANCELLED  and TX_ISSUE_TYPE takes value Document, it can be TO DO, IN PROGRESS, IN REVIEW, SUBMITTED, APPROVE, ARCHIVE, DONE, CANCELLEDSTATUS
TX_ASSIGN Responsible of the taskTASK ASSIGNEE
DT_DATE_DUE The deadline of the ticketDUE DATE
TX_MAND Define whether a task is mandatoryMANDATORY
TX_PHAS The name of the corresponding phase of the EPIC (01 = Request ; 02 = Approval ; 03=Define, 04=Build ; 05=Test; 06=Deploy; 07=Run; 08=EvaluatePHASE
TX_PRIOR Priority of the task with 3 levels : ‘High’, ‘Medium’, ‘Low’PRIORITY
TX_REPORT Reporter of the task completed for all fields, not really in useà to be deletedREPORTER
TX_TSK_ID Task id from wiki BPTASK IDENTIFICATION
TX_TRACK The track code which contains the possible values from A1 to A4, B1 to B3PROJECT TYPE
TX_WAVEFor The 8 wave of HD projects : WAVE 1 (2014-2015), WAVE 2 (2015-2016), WAVE 3 (2016-2017), WAVE 4 (2017-2018), WAVE 5 (2018-2019), WAVE 6 (2019-2020), WAVE 7 (2020-2021), Wave:Cancelled, Wave : TBD 
WAVE
TX_SERVICEThe service provided by HD extracted of a list containing 4 values : ‘None’, ‘Data Collection’, ‘DWH Exploitation’, ‘DWH External (reporting)’SERVICE
TX_PRIVATEField to specify whether the project is private or publicPRIVACY
TX_SPONSORField to specify the project funderSPONSOR
TX_COMMISSIONERField to specify the project requesterCOMMISSIONNER
Table 1 : : Description of the JIRA dataset used to build the report by displaying the : VARIABLE NAME, FUNCTIONAL DESCRIPTION and FUNCTIONAL NAME
admin Sun, 10/03/2021 - 22:12