FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Example CodeSystem/requirement-category (XML)

Responsible Owner: FHIR Infrastructure Work GroupStandards Status: Informative

Raw XML (canonical form + also see XML Format Specification)

Definition for Code SystemRequirementCategory

<?xml version="1.0" encoding="UTF-8"?>

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="requirement-category"/> 
  <meta> 
    <lastUpdated value="2026-07-10T17:27:55.758+00:00"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p class="res-header-id">
        <b> Generated Narrative: CodeSystem requirement-category</b> 
      </p> 
      <a name="requirement-category"> </a> 
      <a name="hcrequirement-category"> </a> 
      <p> This case-sensitive code system 
        <code> http://hl7.org/fhir/requirement-category</code>  defines the following codes in a Is-A hierarchy:
      </p> 
      <table class="codes">
        <tr> 
          <td> 
            <b> Lvl</b> 
          </td> 
          <td style="white-space:nowrap">
            <b> Code</b> 
          </td> 
          <td> 
            <b> Display</b> 
          </td> 
          <td> 
            <b> Definition</b> 
          </td> 
        </tr> 
        <tr> 
          <td> 1</td> 
          <td style="white-space:nowrap">behavioral
            <a name="requirement-category-behavioral"> </a> 
          </td> 
          <td/>  
          <td> Categories related to how the system behaves</td> 
        </tr> 
        <tr> 
          <td> 2</td> 
          <td style="white-space:nowrap">  business
            <a name="requirement-category-business"> </a> 
          </td> 
          <td> Business</td> 
          <td> Requirements relating to the business operations of the entities responsible for
             a system</td> 
        </tr> 
        <tr> 
          <td> 2</td> 
          <td style="white-space:nowrap">  functional
            <a name="requirement-category-functional"> </a> 
          </td> 
          <td> Functional</td> 
          <td> Requirements related to what the system does (inputs turned into outputs)</td> 
        </tr> 
        <tr> 
          <td> 3</td> 
          <td style="white-space:nowrap">    exchange
            <a name="requirement-category-exchange"> </a> 
          </td> 
          <td> Exchange</td> 
          <td> Requirements relating to when, how, or what data is exchanged with other systems</td> 
        </tr> 
        <tr> 
          <td> 3</td> 
          <td style="white-space:nowrap">    processing
            <a name="requirement-category-processing"> </a> 
          </td> 
          <td> Processing</td> 
          <td> Requirements related to how data must be analyzed, transformed, considered, or
             otherwise used within a system</td> 
        </tr> 
        <tr> 
          <td> 3</td> 
          <td style="white-space:nowrap">    storage
            <a name="requirement-category-storage"> </a> 
          </td> 
          <td> Storage</td> 
          <td> Requirements related to if or how data is persisted in a system</td> 
        </tr> 
        <tr> 
          <td> 2</td> 
          <td style="white-space:nowrap">  non-functional
            <a name="requirement-category-non-functional"> </a> 
          </td> 
          <td> Non-functional</td> 
          <td> Requirements related to how the system accomplishes functional requirements</td> 
        </tr> 
        <tr> 
          <td> 3</td> 
          <td style="white-space:nowrap">    availability
            <a name="requirement-category-availability"> </a> 
          </td> 
          <td> Availability</td> 
          <td> Requirements related to how and when a system needs to be reachable and useable</td> 
        </tr> 
        <tr> 
          <td> 3</td> 
          <td style="white-space:nowrap">    ui
            <a name="requirement-category-ui"> </a> 
          </td> 
          <td> User Interface</td> 
          <td> Requirements related to how information is collected from and exposed to humans
             (or animals)</td> 
        </tr> 
        <tr> 
          <td> 4</td> 
          <td style="white-space:nowrap">      ui-accessibility
            <a name="requirement-category-ui-accessibility"> </a> 
          </td> 
          <td> UI Accessibility</td> 
          <td> Requirements around user interface that ensure a satisfactory experience for users
             from different backgrounds or with varying physical, cognitive, and/or sensory
             abilities</td> 
        </tr> 
        <tr> 
          <td> 4</td> 
          <td style="white-space:nowrap">      ui-consistency
            <a name="requirement-category-ui-consistency"> </a> 
          </td> 
          <td> UI Consistency</td> 
          <td> Requirements around ensuring that different implementations have sufficiently aligned
             appearance and mechanisms of interaction</td> 
        </tr> 
        <tr> 
          <td> 4</td> 
          <td style="white-space:nowrap">      ui-usability
            <a name="requirement-category-ui-usability"> </a> 
          </td> 
          <td> UI Usability</td> 
          <td> Requirements related to the intuitiveness, simplicity, and ease-of-use of a user-interface</td> 
        </tr> 
        <tr> 
          <td> 3</td> 
          <td style="white-space:nowrap">    security
            <a name="requirement-category-security"> </a> 
          </td> 
          <td> Security/Privacy</td> 
          <td> Requirements that ensure that data is appropriately protected from threats and
             respects rules around what parties are permitted to access or manipulate</td> 
        </tr> 
        <tr> 
          <td> 3</td> 
          <td style="white-space:nowrap">    safety
            <a name="requirement-category-safety"> </a> 
          </td> 
          <td> Safety</td> 
          <td> Requirements that ensure that system operation does not negatively impact the wellbeing
             of people or assets</td> 
        </tr> 
        <tr> 
          <td> 3</td> 
          <td style="white-space:nowrap">    performance
            <a name="requirement-category-performance"> </a> 
          </td> 
          <td> Performance/Scalability</td> 
          <td> Requirements that deal with timeliness of processing and/or responsiveness under
             differing levels of load/volume</td> 
        </tr> 
        <tr> 
          <td> 1</td> 
          <td style="white-space:nowrap">source
            <a name="requirement-category-source"> </a> 
          </td> 
          <td/>  
          <td> Categories related to where the requirement came from</td> 
        </tr> 
        <tr> 
          <td> 2</td> 
          <td style="white-space:nowrap">  user
            <a name="requirement-category-user"> </a> 
          </td> 
          <td> User</td> 
          <td> Requirements originating from the community of individuals expected to use the
             system/solution</td> 
        </tr> 
        <tr> 
          <td> 2</td> 
          <td style="white-space:nowrap">  legal
            <a name="requirement-category-legal"> </a> 
          </td> 
          <td> Legal</td> 
          <td> Requirements originating from regulation or law</td> 
        </tr> 
        <tr> 
          <td> 2</td> 
          <td style="white-space:nowrap">  design
            <a name="requirement-category-design"> </a> 
          </td> 
          <td> Design decision</td> 
          <td> Requirements documenting decisions made in the design of the solution</td> 
        </tr> 
      </table> 
    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="normative"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="fhir"/> 
  </extension> 
  <url value="http://hl7.org/fhir/requirement-category"/> 
  <version value="6.0.0-ballot4"/> 
  <name value="RequirementCategory"/> 
  <title value="Requirement Category"/> 
  <status value="active"/> 
  <experimental value="false"/> 
  <publisher value="HL7 International"/> 
  <description value="Requirement Category"/> 
  <jurisdiction> 
    <coding> 
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/> 
      <code value="001"/> 
      <display value="World"/> 
    </coding> 
  </jurisdiction> 
  <caseSensitive value="true"/> 
  <hierarchyMeaning value="is-a"/> 
  <content value="complete"/> 
  <count value="19"/> 
  <concept> 
    <code value="behavioral"/> 
    <definition value="Categories related to how the system behaves"/> 
    <concept> 
      <code value="business"/> 
      <display value="Business"/> 
      <definition value="Requirements relating to the business operations of the entities responsible for
       a system"/> 
    </concept> 
    <concept> 
      <code value="functional"/> 
      <display value="Functional"/> 
      <definition value="Requirements related to what the system does (inputs turned into outputs)"/> 
      <concept> 
        <code value="exchange"/> 
        <display value="Exchange"/> 
        <definition value="Requirements relating to when, how, or what data is exchanged with other systems"/> 
      </concept> 
      <concept> 
        <code value="processing"/> 
        <display value="Processing"/> 
        <definition value="Requirements related to how data must be analyzed, transformed, considered, or
         otherwise used within a system"/> 
      </concept> 
      <concept> 
        <code value="storage"/> 
        <display value="Storage"/> 
        <definition value="Requirements related to if or how data is persisted in a system"/> 
      </concept> 
    </concept> 
    <concept> 
      <code value="non-functional"/> 
      <display value="Non-functional"/> 
      <definition value="Requirements related to how the system accomplishes functional requirements"/> 
      <concept> 
        <code value="availability"/> 
        <display value="Availability"/> 
        <definition value="Requirements related to how and when a system needs to be reachable and useable"/> 
      </concept> 
      <concept> 
        <code value="ui"/> 
        <display value="User Interface"/> 
        <definition value="Requirements related to how information is collected from and exposed to humans
         (or animals)"/> 
        <concept> 
          <code value="ui-accessibility"/> 
          <display value="UI Accessibility"/> 
          <definition value="Requirements around user interface that ensure a satisfactory experience for users
           from different backgrounds or with varying physical, cognitive, and/or sensory
           abilities"/> 
        </concept> 
        <concept> 
          <code value="ui-consistency"/> 
          <display value="UI Consistency"/> 
          <definition value="Requirements around ensuring that different implementations have sufficiently aligned
           appearance and mechanisms of interaction"/> 
        </concept> 
        <concept> 
          <code value="ui-usability"/> 
          <display value="UI Usability"/> 
          <definition value="Requirements related to the intuitiveness, simplicity, and ease-of-use of a user-interface"/> 
        </concept> 
      </concept> 
      <concept> 
        <code value="security"/> 
        <display value="Security/Privacy"/> 
        <definition value="Requirements that ensure that data is appropriately protected from threats and
         respects rules around what parties are permitted to access or manipulate"/> 
      </concept> 
      <concept> 
        <code value="safety"/> 
        <display value="Safety"/> 
        <definition value="Requirements that ensure that system operation does not negatively impact the wellbeing
         of people or assets"/> 
      </concept> 
      <concept> 
        <code value="performance"/> 
        <display value="Performance/Scalability"/> 
        <definition value="Requirements that deal with timeliness of processing and/or responsiveness under
         differing levels of load/volume"/> 
      </concept> 
    </concept> 
  </concept> 
  <concept> 
    <code value="source"/> 
    <definition value="Categories related to where the requirement came from"/> 
    <concept> 
      <code value="user"/> 
      <display value="User"/> 
      <definition value="Requirements originating from the community of individuals expected to use the
       system/solution"/> 
    </concept> 
    <concept> 
      <code value="legal"/> 
      <display value="Legal"/> 
      <definition value="Requirements originating from regulation or law"/> 
    </concept> 
    <concept> 
      <code value="design"/> 
      <display value="Design decision"/> 
      <definition value="Requirements documenting decisions made in the design of the solution"/> 
    </concept> 
  </concept> 
</CodeSystem> 

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.