Da Vinci - Coverage Requirements Discovery
2.2.1 - STU 2.2

Da Vinci - Coverage Requirements Discovery, published by HL7 International / Financial Management. This guide is not an authorized publication; it is the continuous build for version 2.2.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/davinci-crd/ and changes regularly. See the Directory of published versions

## : CRD Temporary Codes

Page standards status: Trial-use | Maturity Level: 4

Raw xml | Download

    <CodeSystem xmlns="http://hl7.org/fhir">
      <id value="temp"/>
      <language value="en"/>
      <text>
        <status value="generated"/>
        <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CodeSystem temp</b></p><a name="temp"> </a><a name="hctemp"> </a><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://hl7.org/fhir/us/davinci-crd/CodeSystem/temp</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">gold-card<a name="temp-gold-card"> </a></td><td>Gold card</td><td>Ordering Practitioner has been granted 'gold card' status with this payer/coverage type.</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">no-member-found<a name="temp-no-member-found"> </a></td><td>Member not found</td><td>The server was unable to find a matching member or was unable to resolve to a single member, so no coverage information can be provided.</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">no-active-coverage<a name="temp-no-active-coverage"> </a></td><td>Coverage not active</td><td>The referenced coverage for the member was found but is not in force during the relevant time period for which the coverage is being evaluated.</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">coverage-not-found<a name="temp-coverage-not-found"> </a></td><td>Coverage not found</td><td>The payer is not available to resolve the provided coverage information to an existing coverage record, or it is not specific enough to resolve to a single coverage.</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">auth-out-network<a name="temp-auth-out-network"> </a></td><td>Authorization needed out-of-network</td><td>Authorization is necessary if out-of-network.</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">technical<a name="temp-technical"> </a></td><td>Technical issues</td><td>The server encountered technical issues either internally or with their interaction with the client.  It is possible these issues are transient and later calls might provide more information.</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">_limitation<a name="temp-_limitation"> </a></td><td>Limitation details</td><td>Identifies detail codes that define limitations of coverage.  (Category should be 'cat-limitation')</td><td>true</td></tr><tr><td>2</td><td style="white-space:nowrap">  allowed-quantity<a name="temp-allowed-quantity"> </a></td><td>Maximum quantity</td><td>Indicates limitations on the number of services/products allowed (possibly per time period).  Value should be a Quantity</td><td/></tr><tr><td>2</td><td style="white-space:nowrap">  allowed-period<a name="temp-allowed-period"> </a></td><td>Maximum allowed period</td><td>Indicates the maximum period of time that can be covered in a single order.  Value should be a Period</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">_decisional<a name="temp-_decisional"> </a></td><td>Decisional details</td><td>Identifies detail codes that may impact patient and clinician decision making  (Category should be 'cat-decisional')</td><td>true</td></tr><tr><td>2</td><td style="white-space:nowrap">  in-network-copay<a name="temp-in-network-copay"> </a></td><td>Copay for in-network</td><td>Indicates a percentage co-pay to expect if delivered in-network.  Value should be a Quantity.</td><td/></tr><tr><td>2</td><td style="white-space:nowrap">  out-network-copay<a name="temp-out-network-copay"> </a></td><td>Copay for out-of-network</td><td>Indicates a percentage co-pay to expect if delivered out-of-network.  Value should be a Quantity.</td><td/></tr><tr><td>2</td><td style="white-space:nowrap">  concurrent-review<a name="temp-concurrent-review"> </a></td><td>Concurrent review</td><td>Additional payer-defined documentation will be required prior to claim payment.  Value should be a boolean.</td><td/></tr><tr><td>2</td><td style="white-space:nowrap">  appropriate-use-needed<a name="temp-appropriate-use-needed"> </a></td><td>Appropriate use</td><td>Payer-defined appropriate use process must be invoked to determine coverage.  Value should be a boolean.</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">_other<a name="temp-_other"> </a></td><td>Other details</td><td>Identifies detail codes that are generally not relevant to clinicians/patients  (Category should be 'cat-other')</td><td>true</td></tr><tr><td>2</td><td style="white-space:nowrap">  policy-link<a name="temp-policy-link"> </a></td><td>Policy Link</td><td>A URL pointing to the specific portion of a payer policy, coverage agreement or similar authoritative document that provides a portion of the basis for the decision documented in the coverage-information.  Value should be a url.</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">instructions<a name="temp-instructions"> </a></td><td>Instructions</td><td>Information to display to the user that gives guidance about what steps to take in achieving the recommended actions identified by this coverage-information (e.g. special instructions about requesting authorization, details about information needed, details about data retention, etc.).  Value should be a string.  (Category may vary.)</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">_cardType<a name="temp-_cardType"> </a></td><td>Card Type (abstract)</td><td>A collector for different profiles on CDS Hooks card</td><td>true</td></tr><tr><td>2</td><td style="white-space:nowrap">  coverage-info<a name="temp-coverage-info"> </a></td><td>Coverage Information</td><td>Information related to the patient's coverage, including whether a service is covered, requires prior authorization, is approved without seeking prior authorization, and/or requires additional documentation or data collection</td><td/></tr><tr><td>3</td><td style="white-space:nowrap">    unsolicited-determ<a name="temp-unsolicited-determ"> </a></td><td>Unsolicited Determination</td><td>An unsolicited approval of the service as having prior authorization requirements met without a formal submission of a prior authorization request</td><td/></tr><tr><td>2</td><td style="white-space:nowrap">  claim<a name="temp-claim"> </a></td><td>Claim</td><td>Information about what steps need to be taken to submit a claim for the service</td><td/></tr><tr><td>2</td><td style="white-space:nowrap">  insurance<a name="temp-insurance"> </a></td><td>Insurance</td><td>Allows a provider to update the patient's coverage information with additional details from the payer (e.g. expiry date, coverage extensions)</td><td/></tr><tr><td>2</td><td style="white-space:nowrap">  limits<a name="temp-limits"> </a></td><td>Limits</td><td>Messages warning about the patient approaching or exceeding their limits for a particular type of coverage or expiry date for coverage in general</td><td/></tr><tr><td>2</td><td style="white-space:nowrap">  network<a name="temp-network"> </a></td><td>Network</td><td>Providing information about in-network providers that could deliver the order (or in-network alternatives for an order directed out-of-network)</td><td/></tr><tr><td>2</td><td style="white-space:nowrap">  appropriate-use<a name="temp-appropriate-use"> </a></td><td>Appropriate Use</td><td>Guidance on whether appropriate-use documentation is needed</td><td/></tr><tr><td>2</td><td style="white-space:nowrap">  cost<a name="temp-cost"> </a></td><td>Cost</td><td>What is the anticipated cost to the patient based on their coverage</td><td/></tr><tr><td>2</td><td style="white-space:nowrap">  therapy-alternatives-opt<a name="temp-therapy-alternatives-opt"> </a></td><td>Optional Therapy Alternatives</td><td>Are there alternative therapies that have better coverage and/or are lower-cost for the patient</td><td/></tr><tr><td>2</td><td style="white-space:nowrap">  therapy-alternatives-req<a name="temp-therapy-alternatives-req"> </a></td><td>Required Therapy Alternatives</td><td>Are there alternative therapies that must be tried first prior to coverage being available for the proposed therapy</td><td/></tr><tr><td>2</td><td style="white-space:nowrap">  clinical-reminder<a name="temp-clinical-reminder"> </a></td><td>Clinical Reminder</td><td>Reminders that a patient is due for certain screening or other therapy (based on payer recorded date of last intervention)</td><td/></tr><tr><td>2</td><td style="white-space:nowrap">  duplicate-therapy<a name="temp-duplicate-therapy"> </a></td><td>Duplicate Therapy</td><td>Notice that the proposed intervention has already recently occurred with a different provider when that information is not already available in the provider system</td><td/></tr><tr><td>2</td><td style="white-space:nowrap">  contraindication<a name="temp-contraindication"> </a></td><td>Contraindication</td><td>Notice that the proposed intervention may be contraindicated based on information the payer has in their record that the provider does not have in theirs</td><td/></tr><tr><td>2</td><td style="white-space:nowrap">  guideline<a name="temp-guideline"> </a></td><td>Guideline</td><td>Indication that there is a guideline available for the proposed therapy (with an option to view)</td><td/></tr><tr><td>2</td><td style="white-space:nowrap">  off-guideline<a name="temp-off-guideline"> </a></td><td>Off Guideline</td><td>Notice that the proposed therapy may be contrary to best-practice guidelines, typically with an option to view the relevant guideline</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">_reqcat<a name="temp-_reqcat"> </a></td><td>Requirements Categories</td><td>Codes that help to categorize requirements statements</td><td>true</td></tr><tr><td>2</td><td style="white-space:nowrap">  behavioral<a name="temp-behavioral"> </a></td><td>Behavioral</td><td>Categories related to how the system behaves</td><td>true</td></tr><tr><td>3</td><td style="white-space:nowrap">    business<a name="temp-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>3</td><td style="white-space:nowrap">    functional<a name="temp-functional"> </a></td><td>Functional</td><td>Requirements related to what the system does (inputs turned into outputs)</td><td/></tr><tr><td>4</td><td style="white-space:nowrap">      exchange<a name="temp-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>4</td><td style="white-space:nowrap">      processing<a name="temp-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>4</td><td style="white-space:nowrap">      storage<a name="temp-storage"> </a></td><td>Storage</td><td>Requirements related to if or how data is persisted in a system</td><td/></tr><tr><td>3</td><td style="white-space:nowrap">    non-functional<a name="temp-non-functional"> </a></td><td>Non-functional</td><td>Requirements related to how the system accomplishes functional requirements</td><td/></tr><tr><td>4</td><td style="white-space:nowrap">      availability<a name="temp-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>4</td><td style="white-space:nowrap">      ui<a name="temp-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>5</td><td style="white-space:nowrap">        ui-accessibility<a name="temp-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>5</td><td style="white-space:nowrap">        ui-consistency<a name="temp-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>5</td><td style="white-space:nowrap">        ui-usability<a name="temp-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>4</td><td style="white-space:nowrap">      security<a name="temp-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>4</td><td style="white-space:nowrap">      safety<a name="temp-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>4</td><td style="white-space:nowrap">      performance<a name="temp-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>2</td><td style="white-space:nowrap">  source<a name="temp-source"> </a></td><td>Source</td><td>Categories related to where the requirement came from</td><td>true</td></tr><tr><td>3</td><td style="white-space:nowrap">    user<a name="temp-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>3</td><td style="white-space:nowrap">    legal<a name="temp-legal"> </a></td><td>Legal Requirements</td><td>Requirements originating from regulation or law</td><td/></tr><tr><td>3</td><td style="white-space:nowrap">    design<a name="temp-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="4">
          <extension
                     url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
            <valueCanonical
                            value="http://hl7.org/fhir/us/davinci-crd/ImplementationGuide/davinci-crd"/>
          </extension>
        </valueInteger>
      </extension>
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
        <valueCode value="trial-use">
          <extension
                     url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
            <valueCanonical
                            value="http://hl7.org/fhir/us/davinci-crd/ImplementationGuide/davinci-crd"/>
          </extension>
        </valueCode>
      </extension>
      <url value="http://hl7.org/fhir/us/davinci-crd/CodeSystem/temp"/>
      <identifier>
        <system value="urn:ietf:rfc:3986"/>
        <value value="urn:oid:2.16.840.1.113883.4.642.40.18.16.1"/>
      </identifier>
      <version value="2.2.1"/>
      <name value="CRDTempCodes"/>
      <title value="CRD Temporary Codes"/>
      <status value="active"/>
      <experimental value="false"/>
      <date value="2026-03-26T15:54:25+00:00"/>
      <publisher value="HL7 International / Financial Management"/>
      <contact>
        <telecom>
          <system value="url"/>
          <value value="http://www.hl7.org/Special/committees/fm"/>
        </telecom>
      </contact>
      <description
                   value="Codes temporarily defined as part of the CRD implementation guide.  These will eventually migrate into an officially maintained terminology (likely either SNOMED CT or HL7's UTG code systems)."/>
      <jurisdiction>
        <coding>
          <system value="urn:iso:std:iso:3166"/>
          <code value="US"/>
        </coding>
      </jurisdiction>
      <caseSensitive value="true"/>
      <hierarchyMeaning value="is-a"/>
      <content value="complete"/>
      <count value="53"/>
      <property>
        <code value="abstract"/>
        <uri value="http://hl7.org/fhir/concept-properties#notSelectable"/>
        <type value="boolean"/>
      </property>
      <concept>
        <code value="gold-card"/>
        <display value="Gold card"/>
        <definition
                    value="Ordering Practitioner has been granted 'gold card' status with this payer/coverage type."/>
      </concept>
      <concept>
        <code value="no-member-found"/>
        <display value="Member not found"/>
        <definition
                    value="The server was unable to find a matching member or was unable to resolve to a single member, so no coverage information can be provided."/>
      </concept>
      <concept>
        <code value="no-active-coverage"/>
        <display value="Coverage not active"/>
        <definition
                    value="The referenced coverage for the member was found but is not in force during the relevant time period for which the coverage is being evaluated."/>
      </concept>
      <concept>
        <code value="coverage-not-found"/>
        <display value="Coverage not found"/>
        <definition
                    value="The payer is not available to resolve the provided coverage information to an existing coverage record, or it is not specific enough to resolve to a single coverage."/>
      </concept>
      <concept>
        <code value="auth-out-network"/>
        <display value="Authorization needed out-of-network"/>
        <definition value="Authorization is necessary if out-of-network."/>
      </concept>
      <concept>
        <code value="technical"/>
        <display value="Technical issues"/>
        <definition
                    value="The server encountered technical issues either internally or with their interaction with the client.  It is possible these issues are transient and later calls might provide more information."/>
      </concept>
      <concept>
        <code value="_limitation"/>
        <display value="Limitation details"/>
        <definition
                    value="Identifies detail codes that define limitations of coverage.  (Category should be 'cat-limitation')"/>
        <property>
          <code value="abstract"/>
          <valueBoolean value="true"/>
        </property>
        <concept>
          <code value="allowed-quantity"/>
          <display value="Maximum quantity"/>
          <definition
                      value="Indicates limitations on the number of services/products allowed (possibly per time period).  Value should be a Quantity"/>
        </concept>
        <concept>
          <code value="allowed-period"/>
          <display value="Maximum allowed period"/>
          <definition
                      value="Indicates the maximum period of time that can be covered in a single order.  Value should be a Period"/>
        </concept>
      </concept>
      <concept>
        <code value="_decisional"/>
        <display value="Decisional details"/>
        <definition
                    value="Identifies detail codes that may impact patient and clinician decision making  (Category should be 'cat-decisional')"/>
        <property>
          <code value="abstract"/>
          <valueBoolean value="true"/>
        </property>
        <concept>
          <code value="in-network-copay"/>
          <display value="Copay for in-network"/>
          <definition
                      value="Indicates a percentage co-pay to expect if delivered in-network.  Value should be a Quantity."/>
        </concept>
        <concept>
          <code value="out-network-copay"/>
          <display value="Copay for out-of-network"/>
          <definition
                      value="Indicates a percentage co-pay to expect if delivered out-of-network.  Value should be a Quantity."/>
        </concept>
        <concept>
          <code value="concurrent-review"/>
          <display value="Concurrent review"/>
          <definition
                      value="Additional payer-defined documentation will be required prior to claim payment.  Value should be a boolean."/>
        </concept>
        <concept>
          <code value="appropriate-use-needed"/>
          <display value="Appropriate use"/>
          <definition
                      value="Payer-defined appropriate use process must be invoked to determine coverage.  Value should be a boolean."/>
        </concept>
      </concept>
      <concept>
        <code value="_other"/>
        <display value="Other details"/>
        <definition
                    value="Identifies detail codes that are generally not relevant to clinicians/patients  (Category should be 'cat-other')"/>
        <property>
          <code value="abstract"/>
          <valueBoolean value="true"/>
        </property>
        <concept>
          <code value="policy-link"/>
          <display value="Policy Link"/>
          <definition
                      value="A URL pointing to the specific portion of a payer policy, coverage agreement or similar authoritative document that provides a portion of the basis for the decision documented in the coverage-information.  Value should be a url."/>
        </concept>
      </concept>
      <concept>
        <code value="instructions"/>
        <display value="Instructions"/>
        <definition
                    value="Information to display to the user that gives guidance about what steps to take in achieving the recommended actions identified by this coverage-information (e.g. special instructions about requesting authorization, details about information needed, details about data retention, etc.).  Value should be a string.  (Category may vary.)"/>
      </concept>
      <concept>
        <code value="_cardType"/>
        <display value="Card Type (abstract)"/>
        <definition value="A collector for different profiles on CDS Hooks card"/>
        <property>
          <code value="abstract"/>
          <valueBoolean value="true"/>
        </property>
        <concept>
          <code value="coverage-info"/>
          <display value="Coverage Information"/>
          <definition
                      value="Information related to the patient's coverage, including whether a service is covered, requires prior authorization, is approved without seeking prior authorization, and/or requires additional documentation or data collection"/>
          <concept>
            <code value="unsolicited-determ"/>
            <display value="Unsolicited Determination"/>
            <definition
                        value="An unsolicited approval of the service as having prior authorization requirements met without a formal submission of a prior authorization request"/>
          </concept>
        </concept>
        <concept>
          <code value="claim"/>
          <display value="Claim"/>
          <definition
                      value="Information about what steps need to be taken to submit a claim for the service"/>
        </concept>
        <concept>
          <code value="insurance"/>
          <display value="Insurance"/>
          <definition
                      value="Allows a provider to update the patient's coverage information with additional details from the payer (e.g. expiry date, coverage extensions)"/>
        </concept>
        <concept>
          <code value="limits"/>
          <display value="Limits"/>
          <definition
                      value="Messages warning about the patient approaching or exceeding their limits for a particular type of coverage or expiry date for coverage in general"/>
        </concept>
        <concept>
          <code value="network"/>
          <display value="Network"/>
          <definition
                      value="Providing information about in-network providers that could deliver the order (or in-network alternatives for an order directed out-of-network)"/>
        </concept>
        <concept>
          <code value="appropriate-use"/>
          <display value="Appropriate Use"/>
          <definition
                      value="Guidance on whether appropriate-use documentation is needed"/>
        </concept>
        <concept>
          <code value="cost"/>
          <display value="Cost"/>
          <definition
                      value="What is the anticipated cost to the patient based on their coverage"/>
        </concept>
        <concept>
          <code value="therapy-alternatives-opt"/>
          <display value="Optional Therapy Alternatives"/>
          <definition
                      value="Are there alternative therapies that have better coverage and/or are lower-cost for the patient"/>
        </concept>
        <concept>
          <code value="therapy-alternatives-req"/>
          <display value="Required Therapy Alternatives"/>
          <definition
                      value="Are there alternative therapies that must be tried first prior to coverage being available for the proposed therapy"/>
        </concept>
        <concept>
          <code value="clinical-reminder"/>
          <display value="Clinical Reminder"/>
          <definition
                      value="Reminders that a patient is due for certain screening or other therapy (based on payer recorded date of last intervention)"/>
        </concept>
        <concept>
          <code value="duplicate-therapy"/>
          <display value="Duplicate Therapy"/>
          <definition
                      value="Notice that the proposed intervention has already recently occurred with a different provider when that information is not already available in the provider system"/>
        </concept>
        <concept>
          <code value="contraindication"/>
          <display value="Contraindication"/>
          <definition
                      value="Notice that the proposed intervention may be contraindicated based on information the payer has in their record that the provider does not have in theirs"/>
        </concept>
        <concept>
          <code value="guideline"/>
          <display value="Guideline"/>
          <definition
                      value="Indication that there is a guideline available for the proposed therapy (with an option to view)"/>
        </concept>
        <concept>
          <code value="off-guideline"/>
          <display value="Off Guideline"/>
          <definition
                      value="Notice that the proposed therapy may be contrary to best-practice guidelines, typically with an option to view the relevant guideline"/>
        </concept>
      </concept>
      <concept>
        <code value="_reqcat"/>
        <display value="Requirements Categories"/>
        <definition
                    value="Codes that help to categorize requirements statements"/>
        <property>
          <code value="abstract"/>
          <valueBoolean value="true"/>
        </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>
      </concept>
    </CodeSystem>