| Document title | CapApp Scope Document |
| Version | 0.1 (Draft for review) |
| Date | 18 June 2026 |
| Author / owner | Dr Joseph Lim — Patient Programme Advisor |
| Development vendor | 8DGE |
| Distribution | 8DGE; HC project stakeholders (HM, Chu S Tan, Joey Ch’ng, Sunny, Wongks) |
| Status | Draft — not yet approved |
| Published location | panax.pcsilly.com/capappscope.html (pending approval) |
Change log to be maintained from v0.2 onward (date, version, author, summary of change).
CapApp is the patient-facing mobile application for Health Capitol (HC). It is the patient’s entry point to registration, appointments, invoicing, loyalty points and partner integrations, and connects to the HC Clinical Information System (CIS) and selected third parties.
This document defines what CapApp must deliver for the 10.10.2026 soft opening (Phase 1), and records the intended direction for Phase 2 (2027) and Phase 3 (2028) so that Phase 1 work is built on an extensible foundation. Its specific aim is to make the 10.10 deliverables concrete, owned, dependency-mapped and testable.
| CapApp Phase | Target | Theme |
|---|---|---|
| Phase 1 (“Ten Ten”) | 10.10.2026 — soft opening | Core patient journey: identity, appointments, invoices, loyalty, initial AA Pharmacy QR. |
| Phase 2 | 2027 — date TBC; likely multiple launch points (2A, 2B, 2C…) | Deeper integrations: pharmacy tracking, results viewing, partner rewards, 1 Utama nutrition. |
| Phase 3 | 2028 | Complex scope: AI agent for patient health management. |
Owner key: 8DGE vendor build JL Joseph Lim OPEN owner unassigned TBC not confirmed for Phase 1. Acceptance criteria below are proposed and to be confirmed.
| ID | Capability | Owner | Status |
|---|---|---|---|
| CA-P1-01 | CapApp app name & icon | JL | Due |
| CA-P1-02 | Loyalty points naming & 2-tier scheme | JL | Due |
| CA-P1-03 | Patient registration & account linking | 8DGE | In scope |
| CA-P1-04 | Appointments — registered patients | 8DGE | In scope |
| CA-P1-05 | Appointments — non-registered patients | 8DGE | In scope |
| CA-P1-06 | Invoices & LHDN e-invoice request | 8DGE | In scope |
| CA-P1-07 | View 2-tier loyalty points | 8DGE | In scope |
| CA-P1-08 | Link 1 Utama App account | 8DGE | In scope |
| CA-P1-09 | Exchange external points → 1Points | 8DGE | In scope |
| CA-P1-10 | QMS integration | 8DGE | TBC |
| CA-P1-11 | AA Pharmacy e-prescription (QR) — Phase 1 | JL | In scope |
Finalise the published name of the CapApp mobile app and its app icon, for use on the iOS App Store and Google Play, and across in-app branding.
Define the name of the Health Capitol loyalty points and the two tiers — internal and external points — including how they are earned, their relationship, and the “1Points” conversion target referenced in CA-P1-09.
Until confirmed, points display (CA-P1-07) and exchange (CA-P1-09) cannot be finalised by 8DGE.
Pull patient information from the CIS to populate the app, and link the app to that patient record so that on every launch the app loads for that specific account (persistent authenticated session). Passkey login to be evaluated — see open item OI-3.
Blocked by: outstanding CIS Mobile App API list (see §6).
For already-registered patients: view existing appointments, request new appointments, and request modification of appointments, all reflected in the CIS.
Confirm whether requests are real-time bookings or request-and-confirm.
For patients who are not registered: view available doctors and call up to request an appointment.
Patients can view their invoices and request an LHDN e-invoice.
Confirm the e-invoicing mechanism and which system is system-of-record for MyInvois submission.
Display the patient’s balance across both loyalty tiers (internal and external).
Allow a patient to link their 1 Utama App account to their current CapApp user.
Requires confirmed API/credentials and partnership agreement with 1 Utama.
Allow patients to exchange external loyalty points into 1Points.
Queue Management System integration. Scope and inclusion for Phase 1 not yet confirmed.
Initial capability: show a QR code in the app that a pharmacist at an AA Pharmacy outside HC can scan to access the patient’s prescription.
Confirm AA Pharmacy side can read the QR and what data standard is used.
The following are explicitly not part of the 10.10.2026 release and must not be assumed by the vendor or stakeholders. They are Phase 2/3 items unless promoted by written change request.
Most 8DGE Phase 1 items (registration CA-P1-03, appointments CA-P1-04, invoices CA-P1-06, points CA-P1-07) depend on APIs exposed by the CIS/HIS. The Mobile App API list from the CIS side is still outstanding. Until this is delivered and agreed, these items cannot be fully specified, estimated, or built. This is the single biggest risk to the 10.10 date and should be escalated.
| Dependency | Needed for | Owner / source |
|---|---|---|
| CIS Mobile App API list & specs | CA-P1-03, 04, 06, 07 | CIS vendor (via Wongks) — outstanding |
| LHDN / MyInvois e-invoicing mechanism | CA-P1-06 | HC billing + CIS |
| 1 Utama App API & partnership terms | CA-P1-08, 09 | 1 Utama / HC partnerships |
| 1Points conversion rules | CA-P1-02, 09 | JL / loyalty programme |
| QMS product & API | CA-P1-10 | TBC |
| AA Pharmacy prescription read capability | CA-P1-11 | AA Pharmacy + HC |
| App store accounts (Apple / Google) | Publishing | HC / 8DGE |
Proposed minimum bar for Phase 1 — to be confirmed.
| Ref | Decision needed | Owner |
|---|---|---|
| OI-1 | Is QMS integration (CA-P1-10) in or out for 10.10? | JL / project lead |
| OI-2 | Resolved — owners assigned: CA-P1-04 → 8DGE, CA-P1-11 → JL. | JL |
| OI-3 | Is passkey login in Phase 1 scope or deferred? | JL / 8DGE |
| OI-4 | Finalise app name + icon (CA-P1-01) and loyalty naming/tiers + 1Points rules (CA-P1-02). | JL |
| OI-5 | Deliver CIS Mobile App API list — critical path. | CIS vendor / Wongks |
| OI-6 | Confirm appointment workflow: real-time booking vs request-and-confirm. | HC operations |
| OI-7 | Confirm LHDN e-invoice mechanism & system of record. | HC billing |
| OI-8 | Set per-item target dates working back from 10.10 (build / integration / UAT / go-live). | JL / 8DGE |
Tracking of prescription volumes and timings, building on the Phase 1 QR capability.
In-app viewing of radiology, lab, pathology and other results.
Nutrition tracking and other offers via the 1 Utama App.
Third-party reward points such as BonusLink and similar programmes.
An AI agent integrated into CapApp to help manage patient health. Scope to be defined closer to the time; the more complex integrations are intentionally deferred here.
| Risk | Impact | Mitigation |
|---|---|---|
| CIS Mobile App API list not delivered in time | High — blocks most 8DGE items; threatens 10.10 | Escalate now; agree delivery date; identify a reduced fallback scope. |
| Owner clarity on assigned items | Low — owners now assigned (CA-P1-04 → 8DGE, CA-P1-11 → JL) | Confirm capacity with assigned owners; track delivery (OI-2 resolved). |
| JL naming items (app/loyalty) delayed | Medium — blocks branding & points features | Treat as “due now”; set hard internal deadline. |
| Third-party readiness (1 Utama, AA Pharmacy, LHDN) | Medium/High | Confirm agreements & APIs early; descope to placeholder if not ready. |
| No per-item dates / no UAT window | Medium | Build backward schedule from 10.10 incl. UAT (OI-8). |
| Role | Name | Approval | Date |
|---|---|---|---|
| Patient Programme Advisor | Dr Joseph Lim | ||
| Vendor (8DGE) | |||
| HC stakeholder |