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
| Official URL: http://moh.bw.org/ValueSet/vs-requirements-type-codes | Version: 1.0.0 | |||
| Active as of 2025-08-20 | Computable Name: VSRequirementsTypeCodes | |||
A coded value that represents the type of requirements contained in the Resource.
References
Expansion performed internally based on codesystem Requirements Type Codes v1.0.0 (CodeSystem)
This value set contains 2 concepts
| Code | System | Display | Definition |
| functional | http://moh.bw.org/CodeSystem/cs-requirements-type-codes | Functional Requirements | Functional requirements define the specific behaviors, features, and functions a system or product must perform. They describe what the system should do, including tasks, processes, and interactions. |
| non-functional | http://moh.bw.org/CodeSystem/cs-requirements-type-codes | Non-Functional Requirements | Non-functional requirements specify the quality attributes, performance, and constraints of a system, such as reliability, scalability, security, and usability, rather than specific behaviors or functions. |
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance) |
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |