Sprint 5.3 · MyKad NRIC + KKM eHIS Bridge

1. 🎯 Sprint Summary

2. 🔄 Integration Flow

Patient ──MyKad──► JPN reader ──► Identity verified
                                       │
                                       ▼
                            ┌──────────────────────┐
                            │  Patient consents to │
                            │  link KKM eHIS       │
                            └──────┬───────────────┘
                                   │ Yes
                                   ▼
KKM eHIS ◄───── Fetch patient history ─── MediEco
   │                                        │
   ├── Allergies (FHIR AllergyIntolerance) ►│
   ├── Medications (FHIR MedicationStatement)│
   ├── Conditions (FHIR Condition)         ►│
   ├── Encounters (FHIR Encounter)         ►│
   └── Immunisations (FHIR Immunisation)   ►│
                                            │
                                            ▼
                              MediEco encounter happens
                                            │
                                            ▼
KKM eHIS ◄───── Post encounter back ────── MediEco
   ├── New encounter
   ├── New allergy (if any)
   └── New ADR (if any)

Audit log: every read + write logged · M9 verifies hash chain

3. 🚦 Pre-Sprint Gate Checklist

• Sprint 5.2 demoed and signed off
• JPN MyKad reader SDK procured · 5 readers per pilot tenant
• KKM eHIS partnership agreement signed (sandbox + production access)
• eHIS API specs reviewed · FHIR R4-aligned read + write
• PDPA cross-system data sharing legal opinion obtained
• Patient consent flow drafted (BM/EN/CN/TA · matches 5.2)
• Government data residency requirements confirmed (must stay on Malaysian soil)
• Audit log extension for cross-system events ready

4. 🧩 Sprint Scope

• MyKad Reader Integration: JPN PKCS#11 SDK · USB reader · biometric verify · NRIC + name + DOB · session token
• Identity Bridge: Map MyKad NRIC → MediEco patient record · auto-create or merge with existing
• KKM eHIS Read API: Fetch FHIR bundle (Patient · Encounter · MedicationStatement · AllergyIntolerance · Condition · Immunisation) per consented patient
• Pre-Consult Briefing Extension (M2): If linked, briefing surfaces "KKM eHIS history" section · last 5 encounters · all allergies · all active meds
• KKM eHIS Write API: Post encounter back · new allergies · ADRs · immunisations · only on patient consent
• Conflict Resolution: Merge MediEco vs eHIS data · timestamp-aware · doctor reviews disagreements
• Patient Consent UI: Granular per-resource consent (read/write each type) · revocable · per-tenant scope
• Cross-System Audit: Every read + write logged · NRIC + tenant + resource type + timestamp
• Tenant Admin: eHIS link enable/disable per tenant · activity dashboard · error rate monitoring

5. 📅 Day-by-Day Plan (15 days)

6. 📦 Deliverables

7. 👥 Team Capacity

8. 🔔 Sprint Ceremonies

• Mon 16 Aug 9am — Sprint Planning (90 min)
• Daily 9am — Standup (15 min)
• Fri 20 Aug + Fri 27 Aug 4pm — Mid-sprint demos (45 min each)
• Wed 1 Sep 4pm — Compliance + audit review (60 min)
• Mon 5 Sep 9am — Sprint Demo (60 min)
• Mon 5 Sep 11am — Sprint Retro (60 min)

9. 🩺 Sign-off Items

• MyKad reader integration legally compliant (JPN approval)
• KKM eHIS API integration sandbox-passed + production-tested
• Patient consent flow legally + clinically defensible · 4 languages
• Conflict resolution UX clinically appropriate
• Cross-system audit log complete · every read + write captured
• PDPA + government data residency verified
• Compliance pack updated · external consultant review
• 3 real patients linked successfully on production
• Final demo (5 Sep) — written sign-off

10. 🎬 Demo Agenda — 5 Sep 9am (60 min)

11. 🛡️ Contingency