Botswana FHIR Implementation Guide
1.0.0 - ci-build Botswana flag

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

: Requirements Type Codes - TTL Representation

Active as of 2025-08-20

Raw ttl | Download


@prefix fhir: <http://hl7.org/fhir/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

# - resource -------------------------------------------------------------------

 a fhir:CodeSystem ;
  fhir:nodeRole fhir:treeRoot ;
  fhir:id [ fhir:v "cs-requirements-type-codes"] ; # 
  fhir:text [
fhir:status [ fhir:v "generated" ] ;
fhir:div "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: CodeSystem cs-requirements-type-codes</b></p><a name=\"cs-requirements-type-codes\"> </a><a name=\"hccs-requirements-type-codes\"> </a><p>This case-sensitive code system <code>http://moh.bw.org/CodeSystem/cs-requirements-type-codes</code> defines the following codes:</p><table class=\"codes\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style=\"white-space:nowrap\">functional<a name=\"cs-requirements-type-codes-functional\"> </a></td><td>Functional Requirements</td><td>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.</td></tr><tr><td style=\"white-space:nowrap\">non-functional<a name=\"cs-requirements-type-codes-non-functional\"> </a></td><td>Non-Functional Requirements</td><td>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.</td></tr></table></div>"^^rdf:XMLLiteral
  ] ; # 
  fhir:url [ fhir:v "http://moh.bw.org/CodeSystem/cs-requirements-type-codes"^^xsd:anyURI] ; # 
  fhir:version [ fhir:v "1.0.0"] ; # 
  fhir:name [ fhir:v "CSRequirementsTypeCodes"] ; # 
  fhir:title [ fhir:v "Requirements Type Codes"] ; # 
  fhir:status [ fhir:v "active"] ; # 
  fhir:experimental [ fhir:v false] ; # 
  fhir:date [ fhir:v "2025-08-20T07:21:53+00:00"^^xsd:dateTime] ; # 
  fhir:publisher [ fhir:v "Jembi Health Systems"] ; # 
  fhir:contact ( [
fhir:name [ fhir:v "Jembi Health Systems" ] ;
    ( fhir:telecom [
fhir:system [ fhir:v "url" ] ;
fhir:value [ fhir:v "https://www.jembi.org" ]     ] [
fhir:system [ fhir:v "email" ] ;
fhir:value [ fhir:v "info@jembi.org" ]     ] )
  ] [
fhir:name [ fhir:v "Jembi Health Systems" ] ;
    ( fhir:telecom [
fhir:system [ fhir:v "email" ] ;
fhir:value [ fhir:v "info@jembi.org" ] ;
fhir:use [ fhir:v "work" ]     ] )
  ] ) ; # 
  fhir:description [ fhir:v "A coded value that represents the type of requirements contained in the Resource."] ; # 
  fhir:jurisdiction ( [
    ( fhir:coding [
fhir:system [ fhir:v "urn:iso:std:iso:3166"^^xsd:anyURI ] ;
fhir:code [ fhir:v "BW" ] ;
fhir:display [ fhir:v "Botswana" ]     ] )
  ] ) ; # 
  fhir:caseSensitive [ fhir:v true] ; # 
  fhir:content [ fhir:v "complete"] ; # 
  fhir:count [ fhir:v "2"^^xsd:nonNegativeInteger] ; # 
  fhir:concept ( [
fhir:code [ fhir:v "functional" ] ;
fhir:display [ fhir:v "Functional Requirements" ] ;
fhir:definition [ fhir:v "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." ]
  ] [
fhir:code [ fhir:v "non-functional" ] ;
fhir:display [ fhir:v "Non-Functional Requirements" ] ;
fhir:definition [ fhir:v "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." ]
  ] ) . #