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:
- Business Processes;
- External Interfaces Availability;
- Data Collection;
- Information Architecture and Terminology;
- 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:
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 NAME||FUNCTIONAL DESCRIPTION||FUNCTIONAL NAME|
|DT_FETCHING||Date of fetching of JIRA_DATASET||EXTRACTION DATE|
|TX_PROJ||Fully name of the project (to validate with the planning sheet)||PROJECT NAME|
|TX_KEY||Unique identification of a ticket in JIRA||JIRA IDENTIFCATION|
|TX_ISSUE_TYPE*||Define the ticket being a task or document, that impact the possible values of the field TX_STATUS||TASK TYPE|
|TX_SUMMARY||Title of the ticket, i.e. the task or document||TASK 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, CANCELLED||STATUS|
|TX_ASSIGN||Responsible of the task||TASK ASSIGNEE|
|DT_DATE_DUE||The deadline of the ticket||DUE DATE|
|TX_MAND||Define whether a task is mandatory||MANDATORY|
|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=Evaluate||PHASE|
|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 deleted||REPORTER|
|TX_TSK_ID||Task id from wiki BP||TASK IDENTIFICATION|
|TX_TRACK||The track code which contains the possible values from A1 to A4, B1 to B3||PROJECT TYPE|
|TX_WAVE||For 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|| |
|TX_SERVICE||The service provided by HD extracted of a list containing 4 values : ‘None’, ‘Data Collection’, ‘DWH Exploitation’, ‘DWH External (reporting)’||SERVICE|
|TX_PRIVATE||Field to specify whether the project is private or public||PRIVACY|
|TX_SPONSOR||Field to specify the project funder||SPONSOR|
|TX_COMMISSIONER||Field to specify the project requester||COMMISSIONNER|