Skip to Content
0 Votes

Wiki source code of Friday 14 February 2025

Version 4.22 by Haekal Yusril Faizin on 2025/02/13 12:28
Show last authors
1 = Weekly Report 14 February 2025 =
2
3
4 == (% id="cke_bm_29973S" style="display:none" %) (%%)Data Engineer ==
5
6 >What Have You Done in This Week?
7
8 (((
9 {{success}}
10 What Have You Done?
11 {{/success}}
12
13 1. xxx
14 1. xxx
15 1. xxx
16
17 {{warning}}
18 What Issues You Have?
19 {{/warning}}
20
21 1. xxx
22 1. xxx
23 1. xxx
24
25 {{info}}
26 What Next You Will Do? (Optional)
27 {{/info}}
28
29 1. xxx
30 1. xxx
31 1. xxx
32
33 **What Support You Need? (Optional)**
34
35
36 ----
37
38
39 )))
40
41
42 == (% id="cke_bm_29973S" style="display:none" %) (%%)Data Analyst ==
43
44 >What Have You Done in This Week?
45
46 (((
47 {{success}}
48 What Have You Done?
49 {{/success}}
50
51 1. **Dharma Dexa Phase 2** – Completed the second phase of Dharma Dexa.
52 1. **Migration from Looker to Metabase** – Transitioning data visualization and analytics from Looker to Metabase.
53 1. **Redesigned DKonsul Data** – Improved the structure and organization of DKonsul data.
54 1. **Ad-hoc Requests** – Handled various on-demand data requests.
55
56 {{warning}}
57 What Issues You Have?
58 {{/warning}}
59
60 1. **Metabase Limitations** – Limited chart options and flexibility in customization, particularly a lack of aggregation functions.
61
62 {{info}}
63 What Next You Will Do? (Optional)
64 {{/info}}
65
66 1. **Continue Redesigning DKonsul Data**
67 1*. Refining the data funnel from consultation → prescription → transaction.
68 1. **Continue Migration to Metabase** – Ensuring a smooth transition from Looker to Metabase.
69 1. **Dharma Dexa Phase 3** – Proceeding with the next phase of the Dharma Dexa project.
70 1. **AppSheet MCN Visit Tracker Dashboard** – Developing and optimizing the dashboard.
71
72 **What Support You Need? (Optional)**
73
74 1. **Data Validation** – Ensuring data accuracy and consistency.
75 1. **Dharma Dexa Screening Enhancements**
76 1*. Assigning a **new screening ID** for each event, especially if different questions and inputs are involved.
77 1*. Adding **location input (province, city)** for better analysis.
78 )))
79
80
81 ----
82
83 == Data Analyst & AI ==
84
85 >What Have You Done in This Week?
86
87 (((
88 {{success}}
89 What Have You Done?
90 {{/success}}
91
92 **AUTOMARK**
93
94 1. Deploy, evaluate and making documentation of **Screening Dharma Dexa API** to be accessed by Tech team. The API is deployed at [[https:~~/~~/datalake.ptgue.com/v1/users_dd>>https://datalake.ptgue.com/v1/users_dd]] and the **documentation is already sent to Tech team**. **The API could be accessed using prompt** to retrieve user that relevant to the prompt. Per 13 Feb 2024, **the RAG Accuracy is 87,50%**
95 1. Deploy, evaluate and making documentation of **master user GUE Ecosystem** to be accessed by Tech team. The API is deployed at [[https:~~/~~/datalake.ptgue.com/v1/users>>https://datalake.ptgue.com/v1/users_dd]] and the **documentation is already sent to Tech team**. **The API is already tested by Tech team and have no issues.**
96
97 **MCN**
98
99 1. Fixing resource spike issue caused by scraping schedule. The issue is already fixed and pass the test for 3 days (wednesday, thursday, and friday). **Scraping time is decreased from 1 minute per user to the maximum of +-20 seconds per user.** **(Pairing with Syifa-DE)**
100 1. **Repoint, re-align, and redesign the pipeline and database** that being consumed for scrapping.** (Pairing with Syifa-DE)**
101
102 **Automation**
103
104 1. **Implement compliance mapping** with the newest data from compliance team
105 1. Data, flow, and script validation for user report performance doctor. **The sample report is already validated by dr.Astrid**
106
107 **Others**
108
109 1. Reqeust + enhance dashboard merck
110 1. Request dkonsul data for online doctors, transactions, prescriptions, Dexa prescriptions, comparison new users january
111 1. Request data ICD-10
112
113 {{warning}}
114 What Issues You Have?
115 {{/warning}}
116
117 1. There is no info regarding database repointing of MCN from tech team. So, the data is not updated. Already solved by coordinating with Product Team
118 1. Need to enhance the accuracy to around
119
120 {{info}}
121 What Next You Will Do? (Optional)
122 {{/info}}
123
124 1. xxx
125 1. xxx
126 1. xxx
127
128 **What Support You Need? (Optional)**
129
130
131 )))