requirements-categories
type: CodeSystem
node role: treeRoot
id:
  v: requirements-categories
language:
  v: en
text:
  status:
    v: generated
  div:
    v: Generated Narrative: CodeSystem requirements-categories Language: en Properties This code system defines the following properties for its concepts Name Code URI Type Not Selectable abstract http://hl7.org/fhir/concept-properties#notSelectable boolean Concepts This case-sensitive code system http://terminology.hl7.org/CodeSystem/requirements-categories defines the following codes in a Is-A hierarchy: Lvl Code Display Definition Not Selectable 1 behavioral Behavioral Categories related to how the system behaves true 2 business Business Requirements relating to the business operations of the entities responsible for a system 2 functional Functional Requirements related to what the system does (inputs turned into outputs) 3 exchange Exchange Requirements relating to when, how, or what data is exchanged with other systems 3 processing Processing Requirements related to how data must be analyzed, transformed, considered, or otherwise used within a system 3 storage Storage Requirements related to if or how data is persisted in a system 2 non-functional Non-functional Requirements related to how the system accomplishes functional requirements 3 availability Availability Requirements related to how and when a system needs to be reachable and useable 3 ui User Interface Requirements related to how information is collected from and exposed to humans (or animals) 4 ui-accessibility UI Accessibility Requirements around user interface that ensure a satisfactory experience for users from different backgrounds or with varying physical, cognitive, and/or sensory abilities 4 ui-consistency UI Consistency Requirements around ensuring that different implementations have sufficiently aligned appearance and mechanisms of interaction 4 ui-usability UI Usability Requirements related to the intuitiveness, simplicity, and ease-of-use of a user-interface 3 security Security/Privacy Requirements that ensure that data is appropriately protected from threats and respects rules around what partie…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fm
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 1
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
url:
  v: http://terminology.hl7.org/CodeSystem/requirements-categories
name:
  v: RequirementsCategories
title:
  v: RequirementsCategories
status:
  v: active
experimental:
  v: false
date:
  v: 2026-02-23T04:46:23+00:00
description:
  v: Codes used to categorize requirements statements.
case sensitive:
  v: true
hierarchy meaning:
  v: is-a
content:
  v: complete
property:
  code:
    v: abstract
  uri:
    v: http://hl7.org/fhir/concept-properties#notSelectable
    l: notSelectable
  type:
    v: boolean
concept:
  code:
    v: behavioral
  display:
    v: Behavioral
  definition:
    v: Categories related to how the system behaves
  property:
    code:
      v: abstract
    value: Boolean
      v: true
  concept:
    code:
      v: business
    display:
      v: Business
    definition:
      v: Requirements relating to the business operations of the entities responsible for a system
  concept:
    code:
      v: functional
    display:
      v: Functional
    definition:
      v: Requirements related to what the system does (inputs turned into outputs)
    concept:
      code:
        v: exchange
      display:
        v: Exchange
      definition:
        v: Requirements relating to when, how, or what data is exchanged with other systems
    concept:
      code:
        v: processing
      display:
        v: Processing
      definition:
        v: Requirements related to how data must be analyzed, transformed, considered, or otherwise used within a system
    concept:
      code:
        v: storage
      display:
        v: Storage
      definition:
        v: Requirements related to if or how data is persisted in a system
  concept:
    code:
      v: non-functional
    display:
      v: Non-functional
    definition:
      v: Requirements related to how the system accomplishes functional requirements
    concept:
      code:
        v: availability
      display:
        v: Availability
      definition:
        v: Requirements related to how and when a system needs to be reachable and useable
    concept:
      code:
        v: ui
      display:
        v: User Interface
      definition:
        v: Requirements related to how information is collected from and exposed to humans (or animals)
    concept:
      code:
        v: security
      display:
        v: Security/Privacy
      definition:
        v: Requirements that ensure that data is appropriately protected from threats and respects rules around what parties are permitted to access or manipulate
    concept:
      code:
        v: safety
      display:
        v: Safety
      definition:
        v: Requirements that ensure that system operation does not negatively impact the wellbeing of people or assets
    concept:
      code:
        v: performance
      display:
        v: Performance/Scalability
      definition:
        v: Requirements that deal with timeliness of processing and/or responsiveness under differing levels of load/volume
concept:
  code:
    v: source
  display:
    v: Source
  definition:
    v: Categories related to where the requirement came from
  property:
    code:
      v: abstract
    value: Boolean
      v: true
  concept:
    code:
      v: user
    display:
      v: User Requirements
    definition:
      v: Requirements originating from the community of individuals expected to use the system/solution
  concept:
    code:
      v: legal
    display:
      v: Legal Requirements
    definition:
      v: Requirements originating from regulation or law
  concept:
    code:
      v: design
    display:
      v: Design Decisions
    definition:
      v: Requirements documenting decisions made in the design of the solution

v: ui-accessibility

v: UI Accessibility

v: Requirements around user interface that ensure a satisfactory experience for users from different backgrounds or with varying physical, cognitive, and/or sensory abilities

v: ui-consistency

v: UI Consistency

v: Requirements around ensuring that different implementations have sufficiently aligned appearance and mechanisms of interaction

v: ui-usability

v: UI Usability

v: Requirements related to the intuitiveness, simplicity, and ease-of-use of a user-interface