Kenya Patient Summary FHIR Implementation Guide
0.1.0 - ci-build
KE
Kenya Patient Summary FHIR Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
This section presents the business requirements for the Kenya Patient Summary (KPS) Digital Adaptation Kit (DAK). These requirements describe what the digital system must be able to do in order to support the workflows and use cases defined for the KPS.
The business requirements are organized into the following subsections:
| Section | Description |
|---|---|
| Concepts | Key abbreviations and glossary terms used throughout this guide. |
| Generic Personas | Descriptions of the health worker roles and stakeholders involved in KPS workflows. |
| User Scenarios | Narrative descriptions of how end users interact with the digital system across different care contexts. |
| Business Processes & Workflows | Visual and textual representations of the core clinical and administrative processes supported by the KPS. |
| Decision Support Logic | Structured decision tables that encode the clinical rules and logic to be embedded in digital systems. |
| Functional Requirements | Capabilities the system must have to meet end-user needs and support tasks within the business process. |
| Non-Functional Requirements | General attributes ensuring the system's usability, security, performance, and technical constraints. |
The business requirements documented in this DAK are scoped to the following KPS-supported clinical domains and processes:
All business requirements in this guide are grounded in Kenya's national health policy and digital health frameworks, including:
Each business requirement maps to one or more FHIR profiles defined in this Implementation Guide. The traceability matrix between requirements and profiles is documented in the Conformance section.