docs: summarize BisOne support and feature activity
- Add summaries for BisOne Supporter, BisOne Next Level, and ACCOne - Categorize implemented work into support and feature enhancement - Add Indonesian combined summary
This commit is contained in:
95
summary-bisone-supporter/accone-sum.md
Normal file
95
summary-bisone-supporter/accone-sum.md
Normal file
@@ -0,0 +1,95 @@
|
||||
# Percepatan One-Accounting Summary Since 2026-01
|
||||
|
||||
## Source
|
||||
|
||||
- Source file: `wa-accone.zip`
|
||||
- Chat export: `WhatsApp Chat with Percepatan One-Accounting.txt`
|
||||
- Parsed messages: 531
|
||||
- Parsed range: 2024-05-31 17:11 to 2026-05-19 14:50
|
||||
- 2026 message range: 2026-02-23 08:51 to 2026-05-19 14:50
|
||||
- 2026 parsed messages: 64
|
||||
|
||||
## Method
|
||||
|
||||
This group is coordination-focused and does not use a ticket bot format. Counts are based on
|
||||
manual thread grouping from the 2026 chat export.
|
||||
|
||||
Classification:
|
||||
|
||||
- **Issue:** access problem, missing master data, or visible setup problem.
|
||||
- **Feature request:** showing, rollout, bridging, master data setup, or new workflow request.
|
||||
- **Implemented:** the chat contains a clear fix, answer, or working confirmation.
|
||||
- **Intake:** request was raised or scheduled, but no clear completion evidence appears.
|
||||
|
||||
## 2026 Activity by Month
|
||||
|
||||
| Month | Messages |
|
||||
| :--- | ---: |
|
||||
| 2026-01 | 0 |
|
||||
| 2026-02 | 10 |
|
||||
| 2026-03 | 0 |
|
||||
| 2026-04 | 4 |
|
||||
| 2026-05 | 50 |
|
||||
| **Total** | **64** |
|
||||
|
||||
## Implemented Count by Month
|
||||
|
||||
| Month | Issues Implemented | Feature Requests Implemented | Total |
|
||||
| :--- | ---: | ---: | ---: |
|
||||
| 2026-01 | 0 | 0 | 0 |
|
||||
| 2026-02 | 0 | 0 | 0 |
|
||||
| 2026-03 | 0 | 0 | 0 |
|
||||
| 2026-04 | 0 | 0 | 0 |
|
||||
| 2026-05 | 1 | 1 | 2 |
|
||||
| **Total** | **1** | **1** | **2** |
|
||||
|
||||
## Intake by Month
|
||||
|
||||
| Month | Issue Threads | Feature Request Threads | Total Threads |
|
||||
| :--- | ---: | ---: | ---: |
|
||||
| 2026-01 | 0 | 0 | 0 |
|
||||
| 2026-02 | 1 | 1 | 2 |
|
||||
| 2026-03 | 0 | 0 | 0 |
|
||||
| 2026-04 | 0 | 1 | 1 |
|
||||
| 2026-05 | 1 | 3 | 4 |
|
||||
| **Total** | **2** | **5** | **7** |
|
||||
|
||||
## Implemented Threads
|
||||
|
||||
### 2026-05
|
||||
|
||||
| Type | Summary | Evidence |
|
||||
| :--- | :--- | :--- |
|
||||
| Feature | ACCOne staff master data mapping | STFF_ID continue; NIK uses KTP |
|
||||
| Issue | Gading Serpong branch not visible | Confirmed `udah muncul` |
|
||||
|
||||
## Intake and Coordination Threads
|
||||
|
||||
### 2026-02
|
||||
|
||||
| Type | Summary | Status |
|
||||
| :--- | :--- | :--- |
|
||||
| Feature | Showing ACC One pembelian inventaris dan jasa | Zoom scheduled |
|
||||
| Issue | Zoom host missing during showing | No clear fix in export |
|
||||
|
||||
### 2026-04
|
||||
|
||||
| Type | Summary | Status |
|
||||
| :--- | :--- | :--- |
|
||||
| Feature | Showing monitoring and update ACC One | Coordination started |
|
||||
|
||||
### 2026-05
|
||||
|
||||
| Type | Summary | Status |
|
||||
| :--- | :--- | :--- |
|
||||
| Feature | Showing ACC One chapter follow-up | Zoom scheduled |
|
||||
| Feature | Running bridging pendapatan ACC One 3 kota | Coordination meeting scheduled |
|
||||
| Feature | Staff import from ACCOne `M_staff` CSV | Mapping clarified |
|
||||
| Issue | Gading Serpong branch missing | Fixed in chat |
|
||||
|
||||
## Notes
|
||||
|
||||
- There is no 2026-01 activity in this export.
|
||||
- The group has very few implementation confirmations compared with planning messages.
|
||||
- Most content is meeting scheduling, rollout coordination, and data setup discussion.
|
||||
- Counts are thread-level estimates, not bot-ticket counts.
|
||||
108
summary-bisone-supporter/bisone.next-level-sum.md
Normal file
108
summary-bisone-supporter/bisone.next-level-sum.md
Normal file
@@ -0,0 +1,108 @@
|
||||
# BisOne Next Level Summary Since 2026-01
|
||||
|
||||
## Source
|
||||
|
||||
- Source file: `wa-sum-next-level.zip`
|
||||
- Chat export: `WhatsApp Chat with BisOne Next Level.txt`
|
||||
- Parsed messages: 4,245
|
||||
- Parsed range: 2021-03-02 16:18 to 2026-06-30 12:25
|
||||
- 2026 message range: 2026-01-28 08:00 to 2026-06-30 12:25
|
||||
- 2026 parsed messages: 184
|
||||
|
||||
## Method
|
||||
|
||||
This group does not use the same `Sas Support` ticket closure format as
|
||||
`BisOne Supporter`. Counts below are based on manual thread grouping from the
|
||||
2026 chat export.
|
||||
|
||||
Classification:
|
||||
|
||||
- **Issue:** reported bug, wrong output, access problem, blank code, missing data.
|
||||
- **Feature request:** new module, report support, integration, security policy, or rollout.
|
||||
- **Implemented:** the thread has an explicit update, working config, ready-to-test note,
|
||||
or practical fix in the chat.
|
||||
- **Intake:** request or issue was raised, but no clear completed update appears in export.
|
||||
|
||||
## Implemented Count by Month
|
||||
|
||||
| Month | Issues Implemented | Feature Requests Implemented | Total |
|
||||
| :--- | ---: | ---: | ---: |
|
||||
| 2026-01 | 1 | 0 | 1 |
|
||||
| 2026-02 | 1 | 0 | 1 |
|
||||
| 2026-03 | 1 | 0 | 1 |
|
||||
| 2026-04 | 0 | 0 | 0 |
|
||||
| 2026-05 | 0 | 0 | 0 |
|
||||
| 2026-06 | 2 | 3 | 5 |
|
||||
| **Total** | **5** | **3** | **8** |
|
||||
|
||||
## Intake by Month
|
||||
|
||||
| Month | Issue Threads | Feature Request Threads | Total Threads |
|
||||
| :--- | ---: | ---: | ---: |
|
||||
| 2026-01 | 1 | 0 | 1 |
|
||||
| 2026-02 | 2 | 1 | 3 |
|
||||
| 2026-03 | 1 | 0 | 1 |
|
||||
| 2026-04 | 1 | 2 | 3 |
|
||||
| 2026-05 | 0 | 1 | 1 |
|
||||
| 2026-06 | 2 | 5 | 7 |
|
||||
| **Total** | **7** | **9** | **16** |
|
||||
|
||||
## Implemented Threads
|
||||
|
||||
### 2026-01
|
||||
|
||||
| Type | Summary | Evidence |
|
||||
| :--- | :--- | :--- |
|
||||
| Issue | Resume MCU mismatch between result and conclusion | New version update advised |
|
||||
|
||||
### 2026-02
|
||||
|
||||
| Type | Summary | Evidence |
|
||||
| :--- | :--- | :--- |
|
||||
| Issue | Toha server access/password issue | Password shared in group |
|
||||
|
||||
### 2026-03
|
||||
|
||||
| Type | Summary | Evidence |
|
||||
| :--- | :--- | :--- |
|
||||
| Issue | Agreement download shows mapping error | Nat code mapping guidance given |
|
||||
|
||||
### 2026-06
|
||||
|
||||
| Type | Summary | Evidence |
|
||||
| :--- | :--- | :--- |
|
||||
| Feature | Affiliator module ready for Surabaya trial | Ready to implement note on 2026-06-23 |
|
||||
| Feature | Bandung Raya replacement server/domain setup | Domain active and login URL confirmed |
|
||||
| Issue | Pramita Mobile booking code blank | QR code stock reloaded, code generated |
|
||||
| Issue | Sunday booking setting for HR Muhammad | Branch open-day setting explained |
|
||||
| Feature | Affiliator reports MR04, MR05, MR07, MR09 | Reports confirmed applicable |
|
||||
|
||||
## Open or Intake-Only Threads
|
||||
|
||||
### 2026-02
|
||||
|
||||
- Server credential list requested for BisOne servers in Google Sheet.
|
||||
- Cik Ditiro flag `*` sometimes missing in result output.
|
||||
|
||||
### 2026-04
|
||||
|
||||
- MR02 and MR06 data synchronization between MisPram and BisOne was discussed.
|
||||
- Showing session for App Doctor / DokLink web desktop was scheduled.
|
||||
- Regional Bandung summary data difference needed coordination.
|
||||
|
||||
### 2026-05
|
||||
|
||||
- WA hasil Halosis Sima showing and validation was scheduled.
|
||||
|
||||
### 2026-06
|
||||
|
||||
- OTP Pramita Mobile requested to return from FPN to Integrasi.
|
||||
- BisOne password expiry policy requested for ISO 27001 audit.
|
||||
- Affiliator finance and marketing reports still needed test examples and snapshots.
|
||||
|
||||
## Notes
|
||||
|
||||
- The first 2026 activity in this export is 2026-01-28.
|
||||
- This group is more planning and coordination oriented than ticket based.
|
||||
- Counts are thread-level estimates, not bot-ticket counts.
|
||||
- Items without explicit completion evidence are counted as intake only.
|
||||
117
summary-bisone-supporter/bisone.supporter-sum.md
Normal file
117
summary-bisone-supporter/bisone.supporter-sum.md
Normal file
@@ -0,0 +1,117 @@
|
||||
# BisOne Supporter Summary Since 2026-01
|
||||
|
||||
## Source
|
||||
|
||||
- Source file: `wa-summary.zip`
|
||||
- Chat export: `WhatsApp Chat with BisOne Supporter.txt`
|
||||
- Parsed messages: 25,518
|
||||
- Parsed range: 2021-01-07 19:08 to 2026-06-30 10:27
|
||||
- 2026 message range: 2026-01-03 12:35 to 2026-06-30 10:27
|
||||
- 2026 parsed messages: 1,717
|
||||
|
||||
## Method
|
||||
|
||||
Implemented items are counted from explicit `Sas Support` closure messages containing
|
||||
`Status : Selesai`. Duplicate closure posts with the same ticket number are counted once.
|
||||
|
||||
Classification is conservative:
|
||||
|
||||
- **Issue:** bug, error, operational problem, data mismatch, stuck process, missing output.
|
||||
- **Feature request:** new report/menu/automation/validation/change request that is explicitly
|
||||
closed as `Status : Selesai`.
|
||||
|
||||
## Implemented Count by Month
|
||||
|
||||
| Month | Issues Implemented | Feature Requests Implemented | Total |
|
||||
| :--- | ---: | ---: | ---: |
|
||||
| 2026-01 | 9 | 0 | 9 |
|
||||
| 2026-02 | 0 | 0 | 0 |
|
||||
| 2026-03 | 2 | 0 | 2 |
|
||||
| 2026-04 | 4 | 0 | 4 |
|
||||
| 2026-05 | 3 | 0 | 3 |
|
||||
| 2026-06 | 2 | 0 | 2 |
|
||||
| **Total** | **20** | **0** | **20** |
|
||||
|
||||
## Ticket Intake by Month
|
||||
|
||||
These are tickets created in the group, not necessarily completed in the same month.
|
||||
|
||||
| Month | Issue Tickets Created | Feature Requests Created | Total Created |
|
||||
| :--- | ---: | ---: | ---: |
|
||||
| 2026-01 | 36 | 0 | 36 |
|
||||
| 2026-02 | 48 | 0 | 48 |
|
||||
| 2026-03 | 23 | 0 | 23 |
|
||||
| 2026-04 | 27 | 1 | 28 |
|
||||
| 2026-05 | 25 | 7 | 32 |
|
||||
| 2026-06 | 29 | 3 | 32 |
|
||||
| **Total** | **188** | **11** | **199** |
|
||||
|
||||
## Implemented Tickets
|
||||
|
||||
### 2026-01
|
||||
|
||||
| Ticket | Type | Summary |
|
||||
| :--- | :--- | :--- |
|
||||
| 32NSST | Issue | Rujukan Ngagel ke Kendangsari tidak bisa diterima |
|
||||
| RJJE35 | Issue | Agreement tidak muncul |
|
||||
| FVJCN6 | Issue | Salah pelunasan Keuangan Regional Medan |
|
||||
| 1Z9535 | Issue | Magelang tidak bisa terima rujukan dari Gading Serpong |
|
||||
| LUWF0P | Issue | Nomor lab tidak bisa dilunaskan |
|
||||
| CD348R | Issue | Agreement tidak turun ke lokal harga pemeriksaan |
|
||||
| ROE0ED | Issue | Tidak bisa dilakukan pelunasan |
|
||||
| JVD26Y | Issue | Hasil rujukan tidak masuk ke cabang perujuk |
|
||||
| L2BBNG | Issue | Error menu Satu Sehat monitoring laboratorium encounter |
|
||||
|
||||
### 2026-03
|
||||
|
||||
| Ticket | Type | Summary |
|
||||
| :--- | :--- | :--- |
|
||||
| 0S071T | Issue | List pelanggan kosong di registrasi v37 |
|
||||
| J8EWKZ | Issue | Menu Verif Ulang V-2 agreement tidak muncul |
|
||||
|
||||
### 2026-04
|
||||
|
||||
| Ticket | Type | Summary |
|
||||
| :--- | :--- | :--- |
|
||||
| YYJK1L | Issue | Agreement Aksi Edit tidak muncul |
|
||||
| YEU0G1 | Issue | Kendala re-edit Rekam Medis dan update Cetak Resep |
|
||||
| 9N57EU | Issue | Pelunasan terinput double |
|
||||
| LYF8LC | Issue | Terima Agreement Nasional tidak ada keterangan peringatan |
|
||||
|
||||
### 2026-05
|
||||
|
||||
| Ticket | Type | Summary |
|
||||
| :--- | :--- | :--- |
|
||||
| L6FSWX | Issue | Pembatalan pelunasan |
|
||||
| XEY1TU | Issue | Membatalkan pelunasan pasien |
|
||||
| HOR70N | Issue | Piutang muncul akibat format koma pelunasan transfer otomatis |
|
||||
|
||||
### 2026-06
|
||||
|
||||
| Ticket | Type | Summary |
|
||||
| :--- | :--- | :--- |
|
||||
| 2R1UEX | Issue | Nomor tagihan BL26-03016 minus |
|
||||
| SFMKPT | Issue | Monitoring Kirim Hasil WA SUPER tidak bisa cek status pending |
|
||||
|
||||
## Feature Request Notes
|
||||
|
||||
No feature request had an explicit `Status : Selesai` closure in the parsed group export.
|
||||
Feature-like requests were mostly created in May and June, for example:
|
||||
|
||||
- Update Framingham, JAKVAS, fisik dasar, and fisik MCU.
|
||||
- Validasi dan parsing nomor HP pasien sebelum mapping ke HalosisPhone.
|
||||
- Penambahan Report KEU10B for BisOne branches.
|
||||
- Generate ulang laporan MR07 berdasarkan kelompok pelanggan.
|
||||
- Permintaan perubahan status pelunasan menjadi belum lunas.
|
||||
|
||||
Because the objective is implemented count, those are listed as intake only unless a matching
|
||||
closure message exists.
|
||||
|
||||
## Caveats
|
||||
|
||||
- WhatsApp export starts 2026 activity on 2026-01-03, not 2026-01-01.
|
||||
- Counts are based on text export and `Sas Support` bot format only.
|
||||
- Manual confirmations such as `sudah bisa`, `done`, or `sudah update` are not counted as
|
||||
implemented tickets unless they include a ticket closure with `Status : Selesai`.
|
||||
- `BisOne Next Level` was not present in the provided zip, so this file covers only
|
||||
`BisOne Supporter`.
|
||||
110
summary-bisone-supporter/combined-support-feature-summary-id.md
Normal file
110
summary-bisone-supporter/combined-support-feature-summary-id.md
Normal file
@@ -0,0 +1,110 @@
|
||||
# Ringkasan Gabungan Support dan Feature Enhancement Sejak 2026-01
|
||||
|
||||
## Sumber Data
|
||||
|
||||
| Sumber | Grup Chat | Pesan 2026 |
|
||||
| :--- | :--- | ---: |
|
||||
| `bisone.supporter-sum.md` | BisOne Supporter | 1.717 |
|
||||
| `bisone.next-level-sum.md` | BisOne Next Level | 184 |
|
||||
| `accone-sum.md` | Percepatan One-Accounting | 64 |
|
||||
| **Total** | **3 export WhatsApp** | **1.965** |
|
||||
|
||||
## Kategori
|
||||
|
||||
- **Support:** perbaikan bug, kendala operasional, selisih data, masalah akses,
|
||||
proses nyangkut, output tidak muncul, dan penyelesaian support harian.
|
||||
- **Feature Enhancement:** modul baru, report baru, integrasi, validasi, rollout,
|
||||
perubahan workflow, setup master data, atau peningkatan kebijakan keamanan.
|
||||
|
||||
## Ringkasan Implementasi per Bulan
|
||||
|
||||
| Bulan | Support | Feature Enhancement | Total Implementasi |
|
||||
| :--- | ---: | ---: | ---: |
|
||||
| 2026-01 | 10 | 0 | 10 |
|
||||
| 2026-02 | 1 | 0 | 1 |
|
||||
| 2026-03 | 3 | 0 | 3 |
|
||||
| 2026-04 | 4 | 0 | 4 |
|
||||
| 2026-05 | 4 | 1 | 5 |
|
||||
| 2026-06 | 4 | 3 | 7 |
|
||||
| **Total** | **26** | **4** | **30** |
|
||||
|
||||
## Ringkasan Intake per Bulan
|
||||
|
||||
Intake adalah tiket atau thread permintaan yang masuk. Belum tentu selesai pada bulan yang sama.
|
||||
|
||||
| Bulan | Intake Support | Intake Feature Enhancement | Total Intake |
|
||||
| :--- | ---: | ---: | ---: |
|
||||
| 2026-01 | 37 | 0 | 37 |
|
||||
| 2026-02 | 51 | 2 | 53 |
|
||||
| 2026-03 | 24 | 0 | 24 |
|
||||
| 2026-04 | 28 | 4 | 32 |
|
||||
| 2026-05 | 26 | 11 | 37 |
|
||||
| 2026-06 | 31 | 8 | 39 |
|
||||
| **Total** | **197** | **25** | **222** |
|
||||
|
||||
## Implementasi per Sumber
|
||||
|
||||
| Sumber | Support | Feature Enhancement | Total |
|
||||
| :--- | ---: | ---: | ---: |
|
||||
| BisOne Supporter | 20 | 0 | 20 |
|
||||
| BisOne Next Level | 5 | 3 | 8 |
|
||||
| Percepatan One-Accounting | 1 | 1 | 2 |
|
||||
| **Total** | **26** | **4** | **30** |
|
||||
|
||||
## Highlight Implementasi Support
|
||||
|
||||
### BisOne Supporter
|
||||
|
||||
- Rujukan Ngagel ke Kendangsari tidak bisa diterima.
|
||||
- Agreement tidak muncul atau tidak turun ke lokal cabang.
|
||||
- Salah pelunasan dan pembatalan pelunasan.
|
||||
- Hasil rujukan tidak masuk ke cabang perujuk.
|
||||
- Error monitoring laboratorium encounter Satu Sehat.
|
||||
- List pelanggan kosong di registrasi v37.
|
||||
- Kendala re-edit Rekam Medis dan update Cetak Resep.
|
||||
- Pelunasan terinput double.
|
||||
- Monitoring Kirim Hasil WA tidak bisa cek status pending.
|
||||
|
||||
### BisOne Next Level
|
||||
|
||||
- Resume MCU tidak sesuai antara hasil dan kesimpulan.
|
||||
- Kendala akses/password server Toha.
|
||||
- Error mapping saat download agreement.
|
||||
- Booking code Pramita Mobile blank karena stok QR habis.
|
||||
- Setting booking hari Minggu untuk HR Muhammad.
|
||||
|
||||
### Percepatan One-Accounting
|
||||
|
||||
- Cabang Gading Serpong belum muncul, lalu dikonfirmasi sudah muncul.
|
||||
|
||||
## Highlight Implementasi Feature Enhancement
|
||||
|
||||
### BisOne Next Level
|
||||
|
||||
- Modul Affiliator siap diuji coba di Surabaya.
|
||||
- Setup server/domain pengganti Bandung Raya.
|
||||
- Dukungan report Affiliator untuk MR04, MR05, MR07, dan MR09.
|
||||
|
||||
### Percepatan One-Accounting
|
||||
|
||||
- Mapping master data staff ACCOne diklarifikasi.
|
||||
- STFF_ID melanjutkan urutan data yang sudah ada.
|
||||
- NIK memakai nilai KTP untuk ACCOne.
|
||||
|
||||
## Highlight Intake Feature Enhancement
|
||||
|
||||
- Update Framingham, JAKVAS, fisik dasar, dan fisik MCU.
|
||||
- Validasi dan parsing nomor HP sebelum mapping ke HalosisPhone.
|
||||
- Penambahan Report KEU10B untuk cabang BisOne.
|
||||
- Generate ulang laporan MR07 berdasarkan kelompok pelanggan.
|
||||
- OTP Pramita Mobile diminta kembali dari FPN ke Integrasi.
|
||||
- Kebijakan masa berlaku password BisOne untuk kebutuhan audit ISO 27001.
|
||||
- Bridging pendapatan ACC One untuk 3 kota.
|
||||
- Showing dan koordinasi rollout ACC One.
|
||||
|
||||
## Catatan
|
||||
|
||||
- `BisOne Supporter` memakai closure bot tiket, sehingga hitungan implementasi lebih ketat.
|
||||
- `BisOne Next Level` dan `Percepatan One-Accounting` dihitung berdasarkan thread diskusi.
|
||||
- Intake lebih besar dari implementasi karena banyak permintaan masih berupa planning atau follow-up.
|
||||
- Konfirmasi manual tanpa bukti selesai yang jelas tidak dihitung sebagai implementasi.
|
||||
110
summary-bisone-supporter/combined-support-feature-summary.md
Normal file
110
summary-bisone-supporter/combined-support-feature-summary.md
Normal file
@@ -0,0 +1,110 @@
|
||||
# Combined Support and Feature Enhancement Summary Since 2026-01
|
||||
|
||||
## Sources
|
||||
|
||||
| Source | Chat | 2026 Messages |
|
||||
| :--- | :--- | ---: |
|
||||
| `bisone.supporter-sum.md` | BisOne Supporter | 1,717 |
|
||||
| `bisone.next-level-sum.md` | BisOne Next Level | 184 |
|
||||
| `accone-sum.md` | Percepatan One-Accounting | 64 |
|
||||
| **Total** | **3 WhatsApp exports** | **1,965** |
|
||||
|
||||
## Categorization
|
||||
|
||||
- **Support:** bug fixes, operational issues, data mismatch, access problems, stuck process,
|
||||
missing output, and day-to-day support resolution.
|
||||
- **Feature Enhancement:** new module, report, integration, validation, rollout, workflow
|
||||
change, master data setup, or security policy enhancement.
|
||||
|
||||
## Implemented Summary by Month
|
||||
|
||||
| Month | Support | Feature Enhancement | Total Implemented |
|
||||
| :--- | ---: | ---: | ---: |
|
||||
| 2026-01 | 10 | 0 | 10 |
|
||||
| 2026-02 | 1 | 0 | 1 |
|
||||
| 2026-03 | 3 | 0 | 3 |
|
||||
| 2026-04 | 4 | 0 | 4 |
|
||||
| 2026-05 | 4 | 1 | 5 |
|
||||
| 2026-06 | 4 | 3 | 7 |
|
||||
| **Total** | **26** | **4** | **30** |
|
||||
|
||||
## Intake Summary by Month
|
||||
|
||||
These are raised tickets or request threads, not necessarily completed in the same month.
|
||||
|
||||
| Month | Support Intake | Feature Enhancement Intake | Total Intake |
|
||||
| :--- | ---: | ---: | ---: |
|
||||
| 2026-01 | 37 | 0 | 37 |
|
||||
| 2026-02 | 51 | 2 | 53 |
|
||||
| 2026-03 | 24 | 0 | 24 |
|
||||
| 2026-04 | 28 | 4 | 32 |
|
||||
| 2026-05 | 26 | 11 | 37 |
|
||||
| 2026-06 | 31 | 8 | 39 |
|
||||
| **Total** | **197** | **25** | **222** |
|
||||
|
||||
## Implemented by Source
|
||||
|
||||
| Source | Support | Feature Enhancement | Total |
|
||||
| :--- | ---: | ---: | ---: |
|
||||
| BisOne Supporter | 20 | 0 | 20 |
|
||||
| BisOne Next Level | 5 | 3 | 8 |
|
||||
| Percepatan One-Accounting | 1 | 1 | 2 |
|
||||
| **Total** | **26** | **4** | **30** |
|
||||
|
||||
## Implemented Support Highlights
|
||||
|
||||
### BisOne Supporter
|
||||
|
||||
- Rujukan Ngagel to Kendangsari could not be accepted.
|
||||
- Agreement not appearing or not syncing to local branch.
|
||||
- Wrong payment settlement and payment cancellation cases.
|
||||
- Referral result not received by referring branch.
|
||||
- Satu Sehat monitoring laboratory encounter error.
|
||||
- Empty customer list in registration v37.
|
||||
- Re-edit Rekam Medis and Cetak Resep issue.
|
||||
- Double payment settlement.
|
||||
- WA result monitoring could not check pending status.
|
||||
|
||||
### BisOne Next Level
|
||||
|
||||
- Resume MCU mismatch between result and conclusion.
|
||||
- Toha server access/password issue.
|
||||
- Agreement download mapping error.
|
||||
- Pramita Mobile booking code blank due to QR stock.
|
||||
- Sunday booking setting for HR Muhammad.
|
||||
|
||||
### Percepatan One-Accounting
|
||||
|
||||
- Gading Serpong branch was missing and later confirmed visible.
|
||||
|
||||
## Implemented Feature Enhancement Highlights
|
||||
|
||||
### BisOne Next Level
|
||||
|
||||
- Affiliator module ready for Surabaya trial.
|
||||
- Bandung Raya replacement server/domain setup.
|
||||
- Affiliator reporting support for MR04, MR05, MR07, and MR09.
|
||||
|
||||
### Percepatan One-Accounting
|
||||
|
||||
- ACCOne staff master data mapping clarified.
|
||||
- STFF_ID continues from existing sequence.
|
||||
- NIK uses KTP value for ACCOne.
|
||||
|
||||
## Feature Enhancement Intake Highlights
|
||||
|
||||
- Update Framingham, JAKVAS, fisik dasar, and fisik MCU.
|
||||
- Validasi and parsing nomor HP before mapping to HalosisPhone.
|
||||
- Penambahan Report KEU10B for BisOne branches.
|
||||
- Generate ulang laporan MR07 by customer group.
|
||||
- OTP Pramita Mobile requested to return from FPN to Integrasi.
|
||||
- BisOne password expiry policy requested for ISO 27001 audit.
|
||||
- ACC One bridging pendapatan for 3 cities.
|
||||
- ACC One showing and rollout coordination.
|
||||
|
||||
## Notes
|
||||
|
||||
- `BisOne Supporter` uses bot ticket closures, so implemented counts are stricter.
|
||||
- `BisOne Next Level` and `Percepatan One-Accounting` are thread-based summaries.
|
||||
- Intake is higher than implemented because many requests were planning or follow-up only.
|
||||
- Manual confirmations without clear completion evidence were not counted as implemented.
|
||||
Reference in New Issue
Block a user