FHIR CI-Build

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

4.4.1.190 ValueSet http://hl7.org/fhir/ValueSet/requirement-category

Responsible Owner: FHIR Infrastructure icon Work Group Normative Use Context: Country: World
Official URL: http://hl7.org/fhir/ValueSet/requirement-category Version: 6.0.0-ballot4
active as of 2026-07-10 Computable Name: RequirementCategory
Flags: OID:

This value set is used in the following places:

4.4.1.190.1 Definition

Requirement Category

4.4.1.190.2 Content Logical Definition

Generated Narrative: ValueSet requirement-category

Last updated: 2026-07-10T15:41:34.935Z

 

4.4.1.190.3 Expansion

This expansion generated 10 Jul 2026

ValueSet

Expansion performed internally based on codesystem Requirement Category v6.0.0-ballot4 (CodeSystem)

This value set contains 19 concepts

LevelSystemCodeDisplayDefinition
1 http://hl7.org/fhir/requirement-category   behavioral Categories related to how the system behaves
2 http://hl7.org/fhir/requirement-category     business Business Requirements relating to the business operations of the entities responsible for a system
2 http://hl7.org/fhir/requirement-category     functional Functional Requirements related to what the system does (inputs turned into outputs)
3 http://hl7.org/fhir/requirement-category       exchange Exchange Requirements relating to when, how, or what data is exchanged with other systems
3 http://hl7.org/fhir/requirement-category       processing Processing Requirements related to how data must be analyzed, transformed, considered, or otherwise used within a system
3 http://hl7.org/fhir/requirement-category       storage Storage Requirements related to if or how data is persisted in a system
2 http://hl7.org/fhir/requirement-category     non-functional Non-functional Requirements related to how the system accomplishes functional requirements
3 http://hl7.org/fhir/requirement-category       availability Availability Requirements related to how and when a system needs to be reachable and useable
3 http://hl7.org/fhir/requirement-category       ui User Interface Requirements related to how information is collected from and exposed to humans (or animals)
4 http://hl7.org/fhir/requirement-category         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 http://hl7.org/fhir/requirement-category         ui-consistency UI Consistency Requirements around ensuring that different implementations have sufficiently aligned appearance and mechanisms of interaction
4 http://hl7.org/fhir/requirement-category         ui-usability UI Usability Requirements related to the intuitiveness, simplicity, and ease-of-use of a user-interface
3 http://hl7.org/fhir/requirement-category       security Security/Privacy Requirements that ensure that data is appropriately protected from threats and respects rules around what parties are permitted to access or manipulate
3 http://hl7.org/fhir/requirement-category       safety Safety Requirements that ensure that system operation does not negatively impact the wellbeing of people or assets
3 http://hl7.org/fhir/requirement-category       performance Performance/Scalability Requirements that deal with timeliness of processing and/or responsiveness under differing levels of load/volume
1 http://hl7.org/fhir/requirement-category   source Categories related to where the requirement came from
2 http://hl7.org/fhir/requirement-category     user User Requirements originating from the community of individuals expected to use the system/solution
2 http://hl7.org/fhir/requirement-category     legal Legal Requirements originating from regulation or law
2 http://hl7.org/fhir/requirement-category     design Design decision Requirements documenting decisions made in the design of the solution

 

See the full registry of value sets defined as part of FHIR.

Explanation of the columns that may appear on this page:

Lvl A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
Source 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). If the code is in italics, this indicates that the code is not selectable ('Abstract')
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