Botswana FHIR Implementation Guide
1.0.0 - ci-build
Botswana FHIR Implementation Guide
1.0.0 - ci-build
Botswana FHIR Implementation Guide, published by Jembi Health Systems. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/jembi/botswana-hie-fhir-ig/ and changes regularly. See the Directory of published versions
This page provides an overview of illustrative non-functional requirements that may be considered to kick-start the process of designing or adapting Botswana's Health Information Exchange to support lab orders.
Non-functional requirements provide the general attributes and features of the digital system to ensure usability and overcome technical and physical constraints.
| Key | Requirement |
|---|---|
| BOTS.NFR.001 | The system should be able to be recovered 1 hour from downtime. |
| BOTS.NFR.002 | The data should be shared/transmitted over a secure layer (Interoperability Layer). |
| BOTS.NFR.003 | The system should be scalable. |
| BOTS.NFR.004 | For performance - On average the system should have a cumulative down time of 1 hour per month. |
| BOTS.NFR.005 | For performance - The system should have 99.9% uptime. |
| BOTS.NFR.006 | For performance - System should have a quick response time to end user queries. |
| BOTS.NFR.007 | For security - The system shall detect and log all users, authorized or not, who access (create, read, update or delete) in accordance to the Botswana Data Protection Act 2018. |
| BOTS.NFR.008 | For browser compatibility - The components of the HIE shall be compatible with Google Chrome version and FireFox version and later. |
| BOTS.NFR.009 | For browser compatibility - If a public user is attempting to access the system without a compatible browser, the system shall display a message to the user that identifies the compatibility requirements necessary to access the system. |
| BOTS.NFR.010 | For maintainability - The software shall exhibit high maintainability to facilitate efficient and timely modifications, updates, and enhancements, ensuring that changes can be made with minimal impact on existing functionality. |