Mobile JKN: online queues at thousands of facilities, but available is not the same as used
Solution case studies are scenarios based on common industry problem patterns. They do not refer to any client and are not MarkasDev project portfolio items. Our client portfolio is published separately.
Industry context
MarkasDev neither built nor runs Mobile JKN. We compiled this page from news, studies, and documents published openly. Mobile JKN and the online queue are built and run by BPJS Kesehatan, Indonesia's national health insurance agency, together with its partner health facilities. We read official statements and reputable media (ANTARA, Liputan6, TopBusiness, RM.id, JawaPos), the Mobile JKN manual on the BPJS Kesehatan website, a Universitas Gadjah Mada study, and a public copy of the online queue bridging manual. All sources are listed at the end.
The National Health Insurance programme (JKN) has run since 1 January 2014. By 31 December 2025 it covered 282.7 million people, or 98.62 percent of the population, with more than 725.3 million uses of health services during 2025 (Liputan6, 2 July 2026, reporting the BPJS Kesehatan Public Expose). At that coverage, almost every family in Indonesia deals with BPJS Kesehatan.
The Mobile JKN app was officially launched on 15 November 2017. The then President Director, Fachmi Idris, called it a digital transformation of the business model: administrative tasks once handled at branch offices or health facilities moved into an app people can use at any time (ANTARA, 15 November 2017). Since then it has grown from a digital card and membership tasks into online queueing, teleconsultation, health-history screening, bed availability, surgery schedules and, in 2026, an AI assistant.
Why this matters to leaders of companies, regional governments, regional SOEs, and financial institutions: Mobile JKN is a real example of moving a service for hundreds of millions of people from the counter to the phone, and of how a new digital channel only works when the partner systems behind it are connected too.
Problem
Before digital channels, almost every member task meant showing up in person: registering, changing a primary clinic, checking contributions, or updating data happened at a branch office (ANTARA, 15 November 2017). At health facilities, patients had to arrive early to get a queue number without knowing the doctor's schedule or how long they would wait. For day labourers, traders, or parents bringing a child, every hour of waiting is lost income or lost working time.
That load keeps growing. JKN service use reached 673.9 million visits in 2024 (ANTARA, 14 July 2025) and more than 725.3 million in 2025 (Liputan6). That averages about 1.99 million uses a day, the figure TopBusiness also reports (26 August 2026). On the cost side, health benefit expenses rose from Rp176.11 trillion (2024) to Rp191.33 trillion (2025), with a claims ratio of 108.27 percent (TopBusiness). Every administrative efficiency and every claim verified faster feeds directly into the programme's sustainability.
The other problem is technical and organisational. An online queue cannot live only in the member's app: queue numbers, doctor schedules, and service status sit in each facility's own information system. There are more than 23,000 primary care facilities and more than 3,000 partner hospitals, each with different systems. BPJS Kesehatan's IT Director, Edwin Aristiawan, described the journey as a shift from manual, fragmented processes to integrated, real-time systems (JawaPos, 17 January 2026).
Constraints
- Scale: 282.7 million members and more than 725.3 million service uses a year (2025)
- Thousands of partner systems: 23,770 primary care facilities (FKTP) and 3,194 referral facilities (FKRTL), each with its own information system to connect via API
- Schedule data readiness: primary-care queues only appear when the branch office updates the facility profile and practice schedule (Mobile JKN manual)
- Varied digital literacy; the Selong branch study names digital literacy, SOPs, and staff readiness as deciding factors
- Non-app channels must remain: PANDAWA (WhatsApp), Care Center 165, and in-person service
- Health data is sensitive, so identity verification (such as FRISTA face recognition) and secure data exchange are prerequisites
- Limit of our evidence: no national per-visit online queue usage rate in the sources we opened
Approach
Diagnose
This section is our analysis of how a Diagnose phase shows up in the Mobile JKN case. It is not a claim that MarkasDev did this work.
The Diagnose starting point visible in public sources is clear: the administrative transactions that most often forced members to visit a branch (registration, changing clinic, checking contributions, updating data) moved to the app first, in 2017. Services that touch facility processes, such as online queueing and teleconsultation, came later.
Good Diagnose also separates two kinds of waiting. A UGM study in the BPJS Kesehatan Selong branch area found that Mobile JKN users waited 17–21 minutes less, mostly at admission, but waiting at the outpatient clinic did not always fall because of limited clinical capacity. That is an important Diagnose lesson: an app can cut administrative queues, but it does not add doctors.
For your organisation the Diagnose questions are similar: which transactions most often force customers to come in, how much of the waiting is administration and how much is capacity, and which partner systems must connect for the digital channel to actually work. See our Diagnose approach for mapping this before a large budget is committed.
Deliver
This is analysis too. Deliver means building in stages with testable acceptance criteria.
The staged pattern is clear. The app was introduced in July 2017 and officially launched in November 2017 with more than one million Android downloads and more than two thousand on iOS (ANTARA, 15 November 2017). The online queue was then connected to facilities through API bridges: for primary care through the Antrean Faskes app and P-Care (Mobile JKN manual), and for hospitals through Online Queue bridging version 2.0, whose service catalogue is provided in the Trustmark app.
The version 2.0 bridging manual shows an interesting integration design. Each hospital exposes its own web services (take a queue number, status, remaining queue, cancel, check-in, new patient info), while BPJS provides clinic and doctor-schedule reference services. Hospitals also send a timestamp for each service step (task id) to BPJS, which makes daily and monthly waiting-time dashboards possible. This two-way integration lets both systems work without reaching directly into each other's databases.
Reasonable acceptance criteria for a similar project (our analysis, not official SLAs): the share of facilities with synchronised doctor schedules, check-in success rate, admission waiting time for users versus non-users, and completeness of per-step timestamps. See also system integration & APIs and mobile applications.
Operate
This is analysis as well. Once the digital channel is live, Operate decides whether people actually use it.
The most interesting data in this case shows the gap between available and used. The online queue has been deployed at 22,613 primary care facilities and 3,170 referral facilities (TopBusiness, 26 August 2026). Yet in the Selong branch area, Mobile JKN use for hospital outpatient queues averaged only 1.52 percent, rising from 0.60 percent (2024) to 2.14 percent (2025), according to the UGM study using BPJS online queue system data. Its qualitative findings name member digital literacy, organisational support, clear SOPs, and system and staff readiness as the deciding factors.
BPJS Kesehatan responded with operating mechanisms, not just new features. One example is the 2025 Digital Transformation Award for 27 facilities and for branch offices that pushed online queue use (JawaPos, 17 January 2026). In 2026 BPJS added SISCA JKN, an AI-based assistant inside Mobile JKN for information and first responses, which Edwin Aristiawan said will be refined in stages to improve answer accuracy (RM.id, 3 February 2026). SmartClaim JKN, AI-assisted claim verification, still requires active involvement from human verifiers at this early stage.
Under the Operate frame, the routine work is monitoring usage per facility, following up facilities whose schedules are out of sync, keeping APIs available, measuring the AI assistant's accuracy, and keeping non-digital channels running.
High-level architecture
This diagram is our simplification of the Mobile JKN manual on the BPJS Kesehatan website and a public copy of the Online Queue bridging 2.0 manual, not an architecture we audited. Integration runs through web services/APIs so neither system reaches directly into the other's database, as the bridging manual describes. The AI features (SISCA JKN, SmartClaim JKN) are described only as far as BPJS Kesehatan states, and we did not verify models or accuracy. We did not open the official Trustmark documentation directly, as it requires registered access.
Typical outcomes
Every figure below comes from sources we opened. Scopes and units differ, so do not add them into a single impact number.
| Indicator | Figure | Source |
|---|---|---|
| Mobile JKN uses, 2025 | 81.95 million | TopBusiness, 26 Aug 2026 |
| PANDAWA (WhatsApp) transactions, 2025 | 36.1 million | TopBusiness |
| Care Center 165 transactions, 2025 | 2.2 million | TopBusiness |
| Online queue deployed | 22,613 FKTP and 3,170 FKRTL | TopBusiness |
| Online queue (end of 2024) | more than 22,000 FKTP and 3,132 hospitals | ANTARA, 14 Jul 2025 |
| Teleconsultation via Mobile JKN (2024) | 17.2 million members at 21,929 FKTP | ANTARA, 14 Jul 2025 |
| Health-history screening | 43.99 million (2024) to 79.57 million (2025) | TopBusiness |
| Member satisfaction, 2025 | 92.9 | TopBusiness |
Online queue coverage. Comparing 22,613 FKTP and 3,170 FKRTL with the partner totals of 23,770 FKTP and 3,194 FKRTL (Liputan6) gives roughly 95 percent of primary care facilities and 99 percent of referral facilities. This is our calculation from two different sources, and TopBusiness does not state the reference date explicitly.
Waiting time. In the Selong branch area, Mobile JKN users waited 17–21 minutes less than non-users, mostly at admission, but usage was only 2.14 percent in 2025 (UGM study). We found no national waiting-time saving in the sources we opened.
Channel comparison. Among the channels named in the same presentation, Mobile JKN (81.95 million uses) is far ahead of PANDAWA (36.1 million transactions), Care Center 165 (2.2 million), and VIOLA (421,812). "Uses" and "transactions" may not be identical units, so read this as an indication of scale only. Of 132,319 member complaints in 2025, all were reported as handled (TopBusiness).
What we did not find: rupiah operating-cost savings from Mobile JKN, monthly active users, a national per-visit online queue usage rate, and measured results for SISCA JKN or SmartClaim JKN.
Typical or expected outcomes, not claims about MarkasDev project results.About this analysis
This page is compiled from open sources and is not a MarkasDev client project. We did not interview BPJS Kesehatan or facilities, did not test the APIs, and did not open raw queue data. Figures come from reporting on the BPJS Kesehatan 2024 and 2025 Public Expose, a BPJS presentation at the TOP GRC Awards 2026, the UGM study, and the official manual plus a copy of the bridging manual. Some figures are inconsistent between sources (for example the share of costs for catastrophic illness, 26.42 percent in Liputan6 and 26.28 percent in TopBusiness), so we do not use them.
Why this case matters beyond healthcare
The same pattern applies to regional banks, rural banks, insurers, multifinance companies, water utilities, and regional government services: customers want to handle things from their phone, while data and service capacity sit across many systems and branches. Mobile JKN shows a sensible order. Move the most frequent administrative transactions first, connect partner systems through APIs, measure the time of every step, then drive adoption with operating mechanisms.
Reading the case through Diagnose, Deliver, Operate
Three questions in order. Which part of the wait is caused by administration and which by capacity? That is Diagnose. How is integration with partner systems tested against acceptance criteria? That is Deliver. Who monitors usage and follows up branches or partners that lag behind? That is Operate. For an early conversation, see IT consulting or contact us.
Sources
Accessed on 5 October 2026 (WIB). Source titles are in Indonesian.
- ANTARA, BPJS kesehatan luncurkan aplikasi "Mobile JKN", 15 November 2017.
- ANTARA Megapolitan, BPJS Kesehatan buktikan pemerataan layanan JKN hingga ke pedalaman, 14 July 2025.
- Liputan6, Program JKN Makin Kuat, BPJS Kesehatan Catat 725 Juta Pemanfaatan Layanan pada 2025, 2 July 2026.
- TopBusiness, BPJS Kesehatan Konsisten Perkuat GRC untuk Menjaga Keberlanjutan JKN, 26 August 2026.
- Elly Widiani et al., Universitas Gadjah Mada, Implementasi Mobile JKN dan Waktu Tunggu Rawat Jalan Rumah Sakit di BPJS Kesehatan Cabang Selong.
- RM.id, BPJS Kesehatan Luncurkan SISCA JKN, Inovasi Layanan Berbasis AI, 3 February 2026.
- ANTARA, BPJS Kesehatan jalankan transformasi digital untuk tingkatkan layanan, 1 November 2025.
- JawaPos, 27 Faskes ini Konsisten Lakukan Transformasi Digital Layanan Peserta JKN, 17 January 2026.
- BPJS Kesehatan, Mobile JKN manual: JKN programme services.
- Online Queue Bridging Version 2.0 development manual, public copy on Scribd (third-party copy, used for the general technical flow).