HL7 Terminology (THO)
7.0.0 - Continuous Process Integration (ci build) International flag

HL7 Terminology (THO) - Local Development build (v7.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

CodeSystem: RequirementsCategories

Official URL: http://terminology.hl7.org/CodeSystem/requirements-categories Version:
Standards status: Trial-use Maturity Level: 1 Computable Name: RequirementsCategories

Codes used to categorize requirements statements.

This Code system is referenced in the content logical definition of the following value sets:

  • This CodeSystem is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Language: en

Properties

This code system defines the following properties for its concepts

NameCodeURIType
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:

LvlCodeDisplayDefinitionNot 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 parties are permitted to access or manipulate
3     safety Safety Requirements that ensure that system operation does not negatively impact the wellbeing of people or assets
3     performance Performance/Scalability Requirements that deal with timeliness of processing and/or responsiveness under differing levels of load/volume
1 source Source Categories related to where the requirement came from true
2   user User Requirements Requirements originating from the community of individuals expected to use the system/solution
2   legal Legal Requirements Requirements originating from regulation or law
2   design Design Decisions Requirements documenting decisions made in the design of the solution