HL7 Terminology (THO)
7.0.0 - Continuous Process Integration (ci build)
HL7 Terminology (THO)
7.0.0 - Continuous Process Integration (ci build)
HL7 Terminology (THO) - Local Development build (v7.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 1 |
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="requirements-categories"/>
<language value="en"/>
<text>
<status value="generated"/>
<div xml:lang="en" xmlns="http://www.w3.org/1999/xhtml" lang="en"><p class="res-header-id"><b>Generated Narrative: CodeSystem requirements-categories</b></p><a name="requirements-categories"> </a><a name="hcrequirements-categories"> </a><div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px">Language: en</p></div><p><b>Properties</b></p><p><b>This code system defines the following properties for its concepts</b></p><table class="grid"><tr><td><b>Name</b></td><td><b>Code</b></td><td><b>URI</b></td><td><b>Type</b></td></tr><tr><td>Not Selectable</td><td>abstract</td><td>http://hl7.org/fhir/concept-properties#notSelectable</td><td>boolean</td></tr></table><p><b>Concepts</b></p><p>This case-sensitive code system <code> http://terminology.hl7.org/CodeSystem/requirements-categories</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><td><b>Not Selectable</b></td></tr><tr><td>1</td><td style="white-space:nowrap">behavioral<a name="requirements-categories-behavioral"> </a></td><td>Behavioral</td><td>Categories related to how the system behaves</td><td>true</td></tr><tr><td>2</td><td style="white-space:nowrap"> business<a name="requirements-categories-business"> </a></td><td>Business</td><td>Requirements relating to the business operations of the entities responsible for a system</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> functional<a name="requirements-categories-functional"> </a></td><td>Functional</td><td>Requirements related to what the system does (inputs turned into outputs)</td><td/></tr><tr><td>3</td><td style="white-space:nowrap"> exchange<a name="requirements-categories-exchange"> </a></td><td>Exchange</td><td>Requirements relating to when, how, or what data is exchanged with other systems</td><td/></tr><tr><td>3</td><td style="white-space:nowrap"> processing<a name="requirements-categories-processing"> </a></td><td>Processing</td><td>Requirements related to how data must be analyzed, transformed, considered, or otherwise used within a system</td><td/></tr><tr><td>3</td><td style="white-space:nowrap"> storage<a name="requirements-categories-storage"> </a></td><td>Storage</td><td>Requirements related to if or how data is persisted in a system</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> non-functional<a name="requirements-categories-non-functional"> </a></td><td>Non-functional</td><td>Requirements related to how the system accomplishes functional requirements</td><td/></tr><tr><td>3</td><td style="white-space:nowrap"> availability<a name="requirements-categories-availability"> </a></td><td>Availability</td><td>Requirements related to how and when a system needs to be reachable and useable</td><td/></tr><tr><td>3</td><td style="white-space:nowrap"> ui<a name="requirements-categories-ui"> </a></td><td>User Interface</td><td>Requirements related to how information is collected from and exposed to humans (or animals)</td><td/></tr><tr><td>4</td><td style="white-space:nowrap"> ui-accessibility<a name="requirements-categories-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><td/></tr><tr><td>4</td><td style="white-space:nowrap"> ui-consistency<a name="requirements-categories-ui-consistency"> </a></td><td>UI Consistency</td><td>Requirements around ensuring that different implementations have sufficiently aligned appearance and mechanisms of interaction</td><td/></tr><tr><td>4</td><td style="white-space:nowrap"> ui-usability<a name="requirements-categories-ui-usability"> </a></td><td>UI Usability</td><td>Requirements related to the intuitiveness, simplicity, and ease-of-use of a user-interface</td><td/></tr><tr><td>3</td><td style="white-space:nowrap"> security<a name="requirements-categories-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><td/></tr><tr><td>3</td><td style="white-space:nowrap"> safety<a name="requirements-categories-safety"> </a></td><td>Safety</td><td>Requirements that ensure that system operation does not negatively impact the wellbeing of people or assets</td><td/></tr><tr><td>3</td><td style="white-space:nowrap"> performance<a name="requirements-categories-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><td/></tr><tr><td>1</td><td style="white-space:nowrap">source<a name="requirements-categories-source"> </a></td><td>Source</td><td>Categories related to where the requirement came from</td><td>true</td></tr><tr><td>2</td><td style="white-space:nowrap"> user<a name="requirements-categories-user"> </a></td><td>User Requirements</td><td>Requirements originating from the community of individuals expected to use the system/solution</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> legal<a name="requirements-categories-legal"> </a></td><td>Legal Requirements</td><td>Requirements originating from regulation or law</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> design<a name="requirements-categories-design"> </a></td><td>Design Decisions</td><td>Requirements documenting decisions made in the design of the solution</td><td/></tr></table></div>
</text>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="fm"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
<valueInteger value="1"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
<valueCode value="trial-use"/>
</extension>
<url
value=" http://terminology.hl7.org/CodeSystem/requirements-categories"/>
<name value="RequirementsCategories"/>
<title value="RequirementsCategories"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-02-23T04:46:23+00:00"/>
<description value="Codes used to categorize requirements statements."/>
<caseSensitive value="true"/>
<hierarchyMeaning value="is-a"/>
<content value="complete"/>
<property>
<code value="abstract"/>
<uri value="http://hl7.org/fhir/concept-properties#notSelectable"/>
<type value="boolean"/>
</property>
<concept>
<code value="behavioral"/>
<display value="Behavioral"/>
<definition value="Categories related to how the system behaves"/>
<property>
<code value="abstract"/>
<valueBoolean value="true"/>
</property>
<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"/>
<display value="Source"/>
<definition
value="Categories related to where the requirement came from"/>
<property>
<code value="abstract"/>
<valueBoolean value="true"/>
</property>
<concept>
<code value="user"/>
<display value="User Requirements"/>
<definition
value="Requirements originating from the community of individuals expected to use the system/solution"/>
</concept>
<concept>
<code value="legal"/>
<display value="Legal Requirements"/>
<definition value="Requirements originating from regulation or law"/>
</concept>
<concept>
<code value="design"/>
<display value="Design Decisions"/>
<definition
value="Requirements documenting decisions made in the design of the solution"/>
</concept>
</concept>
</CodeSystem>
IG © 2020+ HL7 International - Vocabulary Work Group. Package hl7.terminology#7.0.0 based on FHIR 5.0.0. Generated 2026-02-23
Links: Table of Contents |
QA Report
| Version History 
|
|
Propose a change