THE HUMAN CORE / ONE SHARED PURPOSE
The people who chose to build for life.
Moz Tech Developers is driven by a core team of three people united by service, engineering and a belief that technology should improve the human condition. Luis Esteves is a philanthropist and humanitarian whose commitment to meaningful social impact helps anchor the company’s purpose. Shaun Venter is a software developer whose work is guided by ethical responsibility, human dignity and the conviction that innovation must serve people. Deon Rossouw is a software developer focused on modular, durable systems and practical humanitarian innovation. Together, they apply software architecture, clinical informatics and artificial intelligence to the environments that sustain human life.
Behind this focused development core is an international, multidisciplinary advisory network of more than 130 medical professionals, extending from professors and senior physicians to doctors and specialists across the diagnostic, therapeutic and operational continuum. The network includes expertise from nursing, biomedical laboratory science, radiology and medical imaging, pathology, haematology, molecular diagnostics, pharmacy, psychology, nutrition, paediatrics, neonatal care, surgery, anaesthesia, transfusion medicine, hospital operations and public health. This is not ceremonial endorsement. Their knowledge enters requirements elicitation, clinical-state modelling, terminology governance, reference-range logic, escalation thresholds, workflow simulation, human-factors review and safety validation.
Professorial advisers contribute international academic scrutiny, evidence appraisal and systems-level challenge across the development lifecycle. Practising doctors and specialist teams contribute the edge cases that determine whether software remains safe under real clinical pressure: incomplete histories, unstable patients, contaminated specimens, critical results, urgent imaging, contraindications, medicine substitutions, resource constraints and interrupted connectivity. Their combined input helps convert physiology, diagnostic uncertainty, professional accountability and institutional policy into explicit software behaviour that can be tested, audited and improved.
This is participatory medical engineering. We do not design a generic product in isolation and ask healthcare professionals to adapt themselves to it. We develop with people: observing workflow, modelling clinical states, identifying failure points, testing terminology, validating escalation logic and refining interfaces around cognitive load at the bedside. A laboratory professional can expose where specimen provenance is lost. A radiologist can define when image availability becomes clinically urgent. A nurse can identify the difference between a recorded observation and an actionable deterioration signal. A pharmacist can trace the safety relationship between prescription, batch, stock movement, expiry and administration. These contributions become data structures, state machines, permission boundaries, audit events and decision-support rules.
Our ambition is to build solutions that last for generations. That requires architecture capable of evolving without destroying longitudinal meaning: modular clinical domains, controlled vocabularies, durable identifiers, auditable event histories, interoperable interfaces, configurable policy, offline continuity and migration pathways that protect provenance. It also requires governance beyond code—clinical review, human-factors evaluation, security controls, backup and recovery testing, change management, training and measurable outcomes. We engineer for new modalities, new assays, new public-health requirements and future models of care while protecting the integrity of every historical decision.
For Moz Tech Developers, longevity and humanity are the same engineering commitment. Technology lasts when institutions can understand it, govern it, extend it and trust it. Our systems are therefore architected to enhance and protect human life, not to displace the human relationships at the centre of medicine. Every schema, validation rule, alert threshold, synchronisation decision and workflow transition must answer a clinical question: does this enable a person to receive safer, faster and better-informed care today, while leaving a stronger healthcare foundation for the generations that follow?
Our position: software must understand medicine
Healthcare software fails when it digitises documents but leaves clinical work fragmented. A consultation may be recorded in one application, a specimen in another, an image in a third and a medicine issue in a fourth. The patient appears repeatedly, yet the clinical episode never becomes computationally whole. Moz Tech Developers exists to challenge that failure. We engineer every admission, observation, order, result, image, medicine, theatre event, blood component, invoice and public-health notification as a state change in one continuous model of care.
We are small by design and international in ambition. Our developers work close to clinicians, biomedical scientists, radiographers, nurses, pharmacists, administrators and public-health teams. That proximity has produced an engineering estate of 367 base tables and 368 verified database objects: not a prototype, but evidence of sustained work across admissions and transfers, wards and beds, clinical notes, diagnoses, ICD-10 and SNOMED mappings, observations, prescriptions, procedures, laboratory orders, imaging studies, blood-bank operations, surgery, paediatrics, mental health, nutrition, outbreak surveillance, pharmacy costing, billing, equipment and facility communications.
Our passion is safety through continuity. We want the patient journey to remain traceable across departments while every specialist retains the depth required to practise properly. A radiologist needs image-native structures; a biomedical scientist needs specimen and assay states; a surgeon needs peri-operative readiness and safety gates; a psychologist needs scored assessments, risk flags and safety planning. Our work connects those spaces without flattening their clinical meaning.
Our method: event-linked clinical truth
Our information architecture combines longitudinal patient identity with encounter references, departmental workspaces and auditable event histories. Recurrent reference pairs—encounter type and encounter identifier—allow specialised modules to attach their records to the correct clinical context without forcing every discipline into one generic form. Patient, admission, outpatient visit, emergency episode, active-list and clinical-record entities establish the care context; orders and departmental workflows then extend it.
This architecture supports both structured medicine and narrative judgement. Coded diagnosis models coexist with SOAP records, history, complaint, finding and clinician-note structures. Reference catalogues for ICD-10, SNOMED, medicines, routes, frequencies, dose units, procedures, specialties, countries, provinces, districts and health units provide controlled vocabulary where consistency is essential. Text and structured JSON fields retain the nuance required for complex histories and specialty examinations. The result is a model capable of machine aggregation without removing the clinician’s ability to describe uncertainty.
We treat operational metadata as clinical context. Creator, updater and timestamp fields recur throughout our engineering. Workflow-event tables record transitions from one state to another, sometimes with structured payloads. Status, priority, review, validation and activity fields make the lifecycle explicit. This is foundational for audit reconstruction: healthcare software must explain not only what the latest record says, but how an order, result or case arrived at its present state.
Diagnostic imaging: accelerating CT, MRI and multimodality care
One of our clearest goals is to shorten the distance between acquisition and clinical action. We replace archive-centred imaging fragmentation with a native diagnostic imaging fabric. Study and series entities preserve globally unique study and series identifiers, accession numbers, modality, manufacturer, body part, study description and instance counts. This is the technical substrate required to organise CT, MRI, radiography, ultrasound and other DICOM-producing modalities as clinical objects connected directly to the patient and originating order.
Ingestion is treated as a governed pipeline. Upload records track original file identity, size, storage path, cryptographic SHA-1 fingerprint, validation state and error condition. Hardware-gateway records describe device manufacturer, model, department, modality, protocol, network endpoint, application-entity title, receiver, storage target, viewer route, status and last-seen timestamp. This allows modality connectivity and clinical availability to be observed as infrastructure, not guessed from user reports.
The imaging workspace extends beyond viewing. Annotation entities capture coordinates, marker colour, clinical note, urgency, visibility and lifecycle status. Assignment structures support collaboration and accountability. AI findings are stored as reviewable propositions with finding type, label, anatomical region, severity, confidence, bounding geometry, source, review state and reviewing clinician. The design keeps algorithmic output subordinate to clinical governance: a machine finding is not silently converted into truth; it is anchored, reviewed, accepted, contextualised or rejected inside the diagnostic workflow.
Laboratory medicine: reducing time from specimen to decision
Across SADC, diagnostic delay can become clinical deterioration. Our laboratory engineering begins with the clinical order and continues through collection, reception, processing, result interpretation and review. Orders carry department, patient, priority, test group, collection state, collector, referral context and examination date. Workflow cases and event logs then model progression between statuses. Specimen records preserve label, type, anatomical site, collection method, fixative, container count, volume, collection and fixation times, receipt condition, storage location and barcode. This chain of custody is critical in pathology, microbiology, haematology and chemistry because a technically correct result attached to the wrong or compromised specimen remains clinically unsafe.
Interpretation rules introduce a controlled decision-support layer. Rules can define qualitative terminology, numerical low and high thresholds, critical limits, unit hints, severity, normal or attention summaries, recommendations and cautions. These structures allow the interface to highlight a critical potassium, abnormal haematology parameter or positive qualitative assay while retaining human verification. Reader uploads, diagnostic audit records and microscopy capture structures support instrument or image-derived evidence. Microscopy annotations and measurements transform the microscopic field into an inspectable diagnostic artifact rather than an untraceable visual impression.
Molecular genetics is implemented as a genuine technical workspace. Extraction runs record instrument, extraction mode, plate barcode, kit and reagent lots, input and elution volumes, controls, run status and QC state. Assay runs capture platform, assay name and version, sample count, control and metric summaries, QC and interpretation status. Variant records support gene, transcript, HGVS coding and protein descriptions, zygosity, variant allele frequency, copy number, classification, evidence summary, technical translation, clinical translation and recommendation. Configurable molecular QC rules connect assay type and metric to operator, threshold, severity and required action—making quality control computable and reviewable.
Specialist medicine: blood, mind, nutrition and early life
We represent transfusion medicine as an end-to-end safety chain: donor profiles and call-up, screening policies and responses, ELISA runs and quality control, collection, preparation batches, component genealogy, stock location and movement, minimum stock, delivery temperature, patient requests, ABO workup, detailed serology, crossmatch and dual verification. At the bedside, patient and unit scans, pre- and post-transfusion observations, nurse identity, second checker and reaction status establish the final safety barrier. Hemovigilance captures reaction type, severity, outcome, serial vital observations, clinical signs, laboratory and product investigation, responsible staff and closure state.
Mental-health care is structured without reducing psychology to a single score. Assessment records identify scale, version, total and maximum score, severity, risk level, suicide flag, licensing state, action plan, follow-up date, safety plan and clinician narrative. Item-level responses preserve the prompt, response, score and risk flag. This enables repeatable screening and longitudinal comparison while maintaining the clinical note and safety response required when risk is detected.
Nutrition and paediatric workspaces encode high-consequence bedside measurements. Nutrition screening includes age, sex, pregnancy and lactation state, mid-upper-arm circumference and arm, tape colour category, oedema and grade, weight, height, BMI, weight-for-height z-score, appetite, complications, referral, feeding programme, supplementation, follow-up and outcome. Paediatric growth assessment adds weight-for-age, height-for-age, BMI-for-age, head-circumference and arm-circumference z-scores. Paediatric triage explicitly records general danger signs—failure to drink, persistent vomiting, convulsions and lethargy—alongside respiratory distress, stridor, dehydration, malnutrition, fever or malaria risk, diarrhoea, anaemia and HIV/TB risk.
Maternal and neonatal continuity links mother and child records, gestational age, birth weight and APGAR observations at one, five and ten minutes. Paediatric history preserves prenatal, developmental, feeding, antecedent, social-environmental and systems-examination domains with completion and finalisation controls. These are not decorative forms; they are structured clinical instruments designed to identify deterioration early and preserve developmental context over time.
Hospital operations: theatre, medicines, beds and economics
Peri-operative software must coordinate risk before incision and accountability after transfer. Our developers link operation orders, location, room, procedure, surgical diagnosis, pre-anaesthetic evaluation, intra-operative record, post-operative care and monitoring. The case workflow exposes readiness states for blood, equipment, sterility, antibiotic administration and counts; anaesthetic type, ASA state, airway and complications; post-anaesthesia score, destination and readiness; and specimen and implant status. WHO checklist phases are represented as independently checked, timestamped events. Delay logs and workflow audits support service improvement and governance.
Medication management connects clinical intent with physical inventory and cost. Prescriptions, prescribed items, routes, dose units, frequency, administration and dispensing coexist with batch, expiry, stock and movement structures. The pharmacy cost ledger assigns a unique reference to each movement and records direction, medicine code, batch, expiry, source and destination department, patient and encounter, prescriber, quantity, unit cost and total cost. Dispatches, patient charges, invoices, payments, cost centres and billing structures allow the institution to follow the economic consequence of care without severing it from the clinical event.
Admissions, transfers, ward rooms and beds establish the inpatient topology. Department and service structures organise accountability; chat, occupancy, reservation, staff-assignment and presence models support coordination around that topology. Equipment acquisition, inventory, supplier and location structures extend visibility into the physical estate. In this model, a bed, device, medicine, staff interaction and clinical order all participate in one operating picture.
Resilience, interoperability and sovereign governance
We engineer for environments where connectivity cannot be assumed. Offline queues, node state, synchronisation logs and explicit conflict records provide a foundation for continuity across distributed facilities. Conflict structures retain remote node, entity identity, local and incoming cursors, resolution, both payloads and creation time. This is materially different from blind replication: it recognises that concurrent clinical updates require deterministic handling and later audit.
Interoperability operates at several levels. Diagnostic imaging uses study and series identifiers and modality gateway metadata. Clinical terminology structures include ICD-10 and SNOMED mapping. Device gateways abstract protocol, endpoint and destination. Telehealth sessions connect calls, meetings, availability, presence, signalling, messages and patient vitals including pulse, oxygen saturation, temperature, blood pressure and respiration. National-health queues, hub snapshots and health-unit reference hierarchies create paths from bedside activity to management intelligence.
Sovereignty is architectural, not rhetorical. The institution must retain operational access to its identities, terminology, histories, results, images, inventory movements and audit evidence. Role, group, permission, departmental scope, electronic signatures and user-presence events create the basis for least-privilege access and attribution. Data protection still requires deployment-specific security controls, policy, encryption, backup testing, disaster recovery, retention, consent and independent assurance; no database design alone constitutes certification. We build the granular clinical and operational substrate upon which those controls can be enforced and evidenced.
Public-health capability closes the loop between individual care and population response. Outbreak surveillance records suspected or confirmed state, notification status, onset, isolation, symptoms, exposures, laboratory evidence, infection-prevention actions, contacts identified and traced, travel history and action plan. Patient tracking includes respiratory indicators and outbreak flags for conditions such as COVID-19, Ebola and mpox. Aggregated responsibly, these events support situational awareness while the source clinical episode remains traceable.
Our international direction: one goal, measurable clinical change
Moz Tech Developers enters its international phase with the experience expected of serious health-infrastructure engineers: breadth across the care continuum, depth inside specialist domains, event-level auditability, infrastructure awareness, distributed-operation patterns and explicit links between clinical work and institutional economics. Our origin in Mozambique is a technical advantage. We learned where resilience, resource stewardship, disease surveillance and clinical usability are immediate operating requirements rather than future roadmap items.
International deployment should proceed as governed localisation, not superficial translation. Each implementation must map national identifiers, facility hierarchies, terminology, medicine catalogues, laboratory reference intervals, reporting obligations, privacy law, retention policy and clinical escalation rules. Interfaces to modalities, analysers and external systems require conformance testing. Role matrices require validation with clinical leadership. Migration requires provenance, reconciliation and sign-off. Go-live requires downtime procedures, training, observability, incident response and measurable safety outcomes.
Our engineering objective remains constant: one patient, one longitudinal truth, many specialised workspaces and no loss of clinical meaning between them. We create the connective tissue through which a sample, image, medicine, bed, decision, risk signal and financial event become part of the same accountable healthcare environment. We push for change because faster laboratory routing can shorten treatment delay, faster image availability can change an emergency decision, and a correctly surfaced risk flag can save a life.
We do not believe a small company must think small. Our scale keeps us close to the problem, direct in our accountability and fast in our engineering. Our ambition is international because the need is international; our immediate commitment is SADC because this is our region, our context and our responsibility. We want every line of code to remove friction from care, return time to clinicians and make high-quality medical infrastructure possible wherever it is needed.
Developing the future. Accelerating care. Saving lives.
TECHNICAL BASIS
This company profile is grounded in Moz Tech Developers’ July 2026 medical-software architecture: 368 verified database objects, including 367 base tables, and the clinical workflows engineered across the development estate. No patient records were inspected or reproduced in preparing this public technical overview.