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

• Narrative Content
• XML
• JSON
• TTL

: Requirements Type Codes - XML Representation

Active as of 2025-08-20

Raw xml | Download

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="cs-requirements-type-codes"/>
  <text>
    <status value="generated"/>
    <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>
  </text>
  <url value="http://moh.bw.org/CodeSystem/cs-requirements-type-codes"/>
  <version value="1.0.0"/>
  <name value="CSRequirementsTypeCodes"/>
  <title value="Requirements Type Codes"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2025-08-20T07:21:53+00:00"/>
  <publisher value="Jembi Health Systems"/>
  <contact>
    <name value="Jembi Health Systems"/>
    <telecom>
      <system value="url"/>
      <value value="https://www.jembi.org"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="info@jembi.org"/>
    </telecom>
  </contact>
  <contact>
    <name value="Jembi Health Systems"/>
    <telecom>
      <system value="email"/>
      <value value="info@jembi.org"/>
      <use value="work"/>
    </telecom>
  </contact>
  <description
               value="A coded value that represents the type of requirements contained in the Resource."/>
  <jurisdiction>
    <coding>
      <system value="urn:iso:std:iso:3166"/>
      <code value="BW"/>
      <display value="Botswana"/>
    </coding>
  </jurisdiction>
  <caseSensitive value="true"/>
  <content value="complete"/>
  <count value="2"/>
  <concept>
    <code value="functional"/>
    <display value="Functional Requirements"/>
    <definition
                value="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."/>
  </concept>
  <concept>
    <code value="non-functional"/>
    <display value="Non-Functional Requirements"/>
    <definition
                value="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."/>
  </concept>
</CodeSystem>