Wiki source code of Friday 14 February 2025
Version 6.1 by Abdurachman Putra on 2025/02/14 00:52
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
| |
1.1 | 1 | = Weekly Report 14 February 2025 = |
| 2 | |||
| 3 | |||
| |
2.4 | 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)** | ||
| |
3.1 | 34 | |
| 35 | |||
| 36 | ---- | ||
| 37 | |||
| 38 | |||
| |
2.4 | 39 | ))) |
| 40 | |||
| 41 | |||
| |
3.2 | 42 | == (% id="cke_bm_29973S" style="display:none" %) (%%)Data Analyst == |
| |
1.1 | 43 | |
| |
2.2 | 44 | >What Have You Done in This Week? |
| 45 | |||
| 46 | ((( | ||
| |
3.1 | 47 | {{success}} |
| |
2.2 | 48 | What Have You Done? |
| |
3.1 | 49 | {{/success}} |
| |
2.2 | 50 | |
| |
3.2 | 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. | ||
| |
1.3 | 55 | |
| |
3.1 | 56 | {{warning}} |
| |
1.3 | 57 | What Issues You Have? |
| |
3.1 | 58 | {{/warning}} |
| |
1.3 | 59 | |
| |
3.2 | 60 | 1. **Metabase Limitations** – Limited chart options and flexibility in customization, particularly a lack of aggregation functions. |
| |
1.3 | 61 | |
| |
3.1 | 62 | {{info}} |
| |
1.3 | 63 | What Next You Will Do? (Optional) |
| |
3.1 | 64 | {{/info}} |
| |
1.3 | 65 | |
| |
3.2 | 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. | ||
| |
1.3 | 71 | |
| |
3.1 | 72 | **What Support You Need? (Optional)** |
| |
3.2 | 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. | ||
| |
1.3 | 78 | ))) |
| 79 | |||
| 80 | |||
| |
3.1 | 81 | ---- |
| |
2.2 | 82 | |
| |
2.1 | 83 | == Data Analyst & AI == |
| 84 | |||
| |
2.2 | 85 | >What Have You Done in This Week? |
| 86 | |||
| 87 | ((( | ||
| |
2.3 | 88 | {{success}} |
| |
2.2 | 89 | What Have You Done? |
| |
2.3 | 90 | {{/success}} |
| |
2.2 | 91 | |
| |
4.3 | 92 | **AUTOMARK** |
| |
2.1 | 93 | |
| |
4.20 | 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%** |
| |
4.17 | 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.** |
| |
4.3 | 96 | |
| |
4.7 | 97 | **MCN** |
| |
4.3 | 98 | |
| |
4.20 | 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)** | ||
| |
4.7 | 101 | |
| |
4.14 | 102 | **Automation** |
| |
4.7 | 103 | |
| |
4.20 | 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** | ||
| |
4.13 | 106 | |
| |
4.15 | 107 | **Others** |
| |
4.14 | 108 | |
| |
4.15 | 109 | 1. Reqeust + enhance dashboard merck |
| 110 | 1. Request dkonsul data for online doctors, transactions, prescriptions, Dexa prescriptions, comparison new users january | ||
| |
4.17 | 111 | 1. Request data ICD-10 |
| |
4.3 | 112 | |
| |
2.3 | 113 | {{warning}} |
| |
2.1 | 114 | What Issues You Have? |
| |
2.3 | 115 | {{/warning}} |
| |
2.1 | 116 | |
| |
4.22 | 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 |
| |
5.1 | 118 | 1. Need to enhance the RAG accuracy to around 90% |
| |
2.1 | 119 | |
| |
2.3 | 120 | {{info}} |
| |
2.1 | 121 | What Next You Will Do? (Optional) |
| |
2.3 | 122 | {{/info}} |
| |
2.1 | 123 | |
| |
5.1 | 124 | 1. Increase RAG accuracy by adding more train query LLM |
| 125 | 1. Start daily recurring scraping for tiktok dashboard | ||
| 126 | 1. Start dkonsul insight next week | ||
| |
2.1 | 127 | |
| |
2.4 | 128 | **What Support You Need? (Optional)** |
| |
2.2 | 129 | |
| |
6.1 | 130 | |
| 131 | === Summary === | ||
| 132 | |||
| 133 | Berikut ringkasan laporan mingguan dari 14 Februari 2025 yang ditulis oleh Haekal Yusril Faizin. Laporan ini merangkum aktivitas dan isu dari tim Data Engineer, Data Analyst, dan Data Analyst & AI. | ||
| 134 | |||
| 135 | **Data Analyst** | ||
| 136 | |||
| 137 | * Menyelesaikan fase kedua Dharma Dexa. | ||
| 138 | * Memindahkan visualisasi data dan analitik dari Looker ke Metabase. | ||
| 139 | * Mendesain ulang data DKonsul untuk struktur dan organisasi yang lebih baik. | ||
| 140 | * Menangani berbagai permintaan data on-demand. | ||
| 141 | |||
| 142 | **Data Analyst & AI** | ||
| 143 | |||
| 144 | * Menerapkan, mengevaluasi, dan mendokumentasikan API Screening Dharma Dexa untuk diakses oleh tim Tech. | ||
| 145 | * Menerapkan, mengevaluasi, dan mendokumentasikan master user GUE Ecosystem untuk diakses oleh tim Tech. | ||
| 146 | * Memperbaiki masalah lonjakan sumber daya yang disebabkan oleh jadwal scraping. | ||
| 147 | * Merepoint, menyelaraskan ulang, dan mendesain ulang pipeline dan database yang digunakan untuk scraping. | ||
| 148 | * Menerapkan pemetaan kepatuhan dengan data terbaru dari tim kepatuhan. | ||
| 149 | * Memvalidasi data, alur, dan skrip untuk kinerja laporan pengguna dokter. | ||
| 150 | |||
| 151 | **Isu** | ||
| 152 | |||
| 153 | * Pilihan bagan dan fleksibilitas yang terbatas dalam kustomisasi Metabase. | ||
| 154 | * Kurangnya informasi mengenai database repointing MCN dari tim teknologi. | ||
| 155 | * Perlu meningkatkan akurasi RAG menjadi sekitar 90%. | ||
| 156 | |||
| 157 | **Langkah Selanjutnya** | ||
| 158 | |||
| 159 | * Melanjutkan desain ulang data DKonsul dan migrasi ke Metabase. | ||
| 160 | * Melanjutkan dengan Dharma Dexa Fase 3 dan mengembangkan Dasbor Pelacak Kunjungan AppSheet MCN. | ||
| 161 | * Meningkatkan akurasi RAG, memulai scraping berulang harian untuk dasbor TikTok, dan memulai wawasan DKonsul minggu depan. | ||
| 162 | |||
| 163 | **Dukungan yang Dibutuhkan** | ||
| 164 | |||
| 165 | * Validasi data dan peningkatan penyaringan Dharma Dexa. | ||
| |
2.1 | 166 | ))) |