Ngoane Health
Backend systems powering RxKonet (community-pharmacy inventory and dispensing) and myRx (patient health management and prescription fulfillment).
PRODUCT & DOMAIN CONTEXT
Ngoane Health builds digital healthcare infrastructure in Africa. RxKonet enables community pharmacies to manage inventory, fulfill digital prescriptions, and connect with healthcare networks. myRx empowers patients to access prescription records, schedule refills, and interact with healthcare providers.
THE CORE ENGINEERING PROBLEM
Healthcare applications demand strict privacy boundaries, HIPAA/GDPR-conscious data handling, role separation between pharmacists, doctors, and patients, and reliable auditing of prescription fulfillment states.
SYSTEM ARCHITECTURE MAP
Data Flow & Boundary Topology
Pharmacy web portals and patient mobile apps interact with a central backend API. Requests pass through strict authentication and role-checking middleware before accessing encrypted patient records and medication catalogs in PostgreSQL.
Pharmacist Dashboard
Patient Health Portal
Node.js / Express
Encrypted Records & Stock
SMS / Email Refill Alerts
Integration Boundaries & Protocols
SYSTEMS & SERVICES BUILT
Core Backend Modules & Responsibility
RxKonet Pharmacy Inventory & Fulfillment API
Services managing pharmaceutical stock levels, batch numbers, expiry dates, and dispensing audit trails.
myRx Patient Prescription Gateway
Patient-facing REST APIs for viewing digital prescriptions, tracking fulfillment status, and requesting medication refills.
Role-Based Patient Data Isolation Engine
Access control layer enforcing strict data ownership boundaries so health records are strictly scoped to verified patient IDs.
Detailed Technical Responsibilities
- •Contributed backend APIs for pharmacy inventory tracking, medication catalog search, and prescription fulfillment lifecycle.
- •Engineered role-based access controls ensuring patients can only view their own health records while pharmacists access authorized dispensing queues.
- •Implemented validation pipelines for prescription intake, dosage parameters, and drug interaction warnings.
- •Built secure authentication and profile management services with sanitized error responses.
ENGINEERING DECISIONS & TRADE-OFFS
Architectural Choices & Rationale
Zero Personal Identifiable Data in Unencrypted Log Streams
Slightly higher debugging complexity requiring correlation IDs instead of direct user lookups.
RELIABILITY & SAFETY MECHANISMS
- •Strict column-level data sanitization preventing unauthorized PHI exposure.
- •Database transactions for inventory deducts upon prescription fulfillment.
CHALLENGES & RESOLUTION
Regulatory rules required an immutable history of who dispensed each medication item. Implemented append-only dispensing log tables with foreign keys tied to licensed pharmacist user accounts.
VERIFIED OUTCOMES
- •Successfully contributed backend infrastructure powering RxKonet and myRx platforms.
- •Strengthened data privacy isolation through role-scoped record access and sanitized logs.
NEXT SYSTEM IMPROVEMENTS
- •Implement real-time WebSocket notifications for instant pharmacy order alerts.
Interested in discussing this architecture or an open backend role?
Reach out via email or review my full experience on my resume.