SMART Base
0.2.0 - ci-build

SMART Base, published by WHO. This guide is not an authorized publication; it is the continuous build for version 0.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/WorldHealthOrganization/smart-base/tree/main and changes regularly. See the Directory of published versions
Built from commit d97caff5.

: Can author functional requirements - XML Representation

Draft as of 2026-03-20

Raw xml | Download


<Requirements xmlns="http://hl7.org/fhir">
  <id value="SGAuthoring.Skills.AuthorFunctionalRequirements"/>
  <meta>
    <profile
             value="http://smart.who.int/base/StructureDefinition/SGRequirements"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><div xml:lang="en" lang="en"><hr/><p><b>English</b></p><hr/><p class="res-header-id"><b>Generated Narrative: Requirements SGAuthoring.Skills.AuthorFunctionalRequirements</b></p><a name="SGAuthoring.Skills.AuthorFunctionalRequirements"> </a><a name="hcSGAuthoring.Skills.AuthorFunctionalRequirements"> </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"/><p style="margin-bottom: 0px">Profile: <a href="StructureDefinition-SGRequirements.html">SMART Guidelines Requirements</a></p></div><p>These requirements apply to the actor <a href="ActorDefinition-SGAuthoring.Persona.BusinessAnalyst.html">Business Analyst</a></p><table class="grid"><tr><td><b><a name="FREQ-01"> </a></b>Define functional requirements from L1</td><td>SHALL</td><td><div><p>Can define functional requirements based on L1 recommendations in terms of health content, decision-support, and scheduling logic.</p>
</div></td></tr><tr><td><b><a name="FREQ-02"> </a></b>Define non-functional requirements</td><td>SHALL</td><td><div><p>Can define non-functional requirements including user-friendliness and cybersecurity, informed by implementer best practices.</p>
</div></td></tr><tr><td><b><a name="FREQ-03"> </a></b>Link requirements to personas</td><td>SHALL</td><td><div><p>Can link each functional requirement to the correct persona and business process activity.</p>
</div></td></tr><tr><td><b><a name="FREQ-04"> </a></b>Verify scenario coverage</td><td>SHALL</td><td><div><p>Can verify that functionalities depicted in user scenarios are captured in the requirements list.</p>
</div></td></tr></table></div><div xml:lang="fr" lang="fr"><hr/><p><b>French</b></p><hr/><p class="res-header-id"><b>Narratif généré : Requirements SGAuthoring.Skills.AuthorFunctionalRequirements</b></p><a name="fr-SGAuthoring.Skills.AuthorFunctionalRequirements"> </a><a name="fr-hcSGAuthoring.Skills.AuthorFunctionalRequirements"> </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"/><p style="margin-bottom: 0px">Profil: <a href="StructureDefinition-SGRequirements.html">SMART Guidelines Requirements</a></p></div><p>Ces exigences s'appliquent à l'acteur <a href="ActorDefinition-SGAuthoring.Persona.BusinessAnalyst.html">Business Analyst</a></p><table class="grid"><tr><td><b><a name="fr-FREQ-01"> </a></b>Define functional requirements from L1</td><td>SHALL</td><td><div><p>Can define functional requirements based on L1 recommendations in terms of health content, decision-support, and scheduling logic.</p>
</div></td></tr><tr><td><b><a name="fr-FREQ-02"> </a></b>Define non-functional requirements</td><td>SHALL</td><td><div><p>Can define non-functional requirements including user-friendliness and cybersecurity, informed by implementer best practices.</p>
</div></td></tr><tr><td><b><a name="fr-FREQ-03"> </a></b>Link requirements to personas</td><td>SHALL</td><td><div><p>Can link each functional requirement to the correct persona and business process activity.</p>
</div></td></tr><tr><td><b><a name="fr-FREQ-04"> </a></b>Verify scenario coverage</td><td>SHALL</td><td><div><p>Can verify that functionalities depicted in user scenarios are captured in the requirements list.</p>
</div></td></tr></table></div><div xml:lang="ar" lang="ar"><hr/><p><b>Arabic</b></p><hr/><p class="res-header-id"><b>السرد المُنشأ: Requirements SGAuthoring.Skills.AuthorFunctionalRequirements</b></p><a name="ar-SGAuthoring.Skills.AuthorFunctionalRequirements"> </a><a name="ar-hcSGAuthoring.Skills.AuthorFunctionalRequirements"> </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"/><p style="margin-bottom: 0px">الملف الشخصي: <a href="StructureDefinition-SGRequirements.html">SMART Guidelines Requirements</a></p></div><p>تنطبق هذه المتطلبات على الممثل <a href="ActorDefinition-SGAuthoring.Persona.BusinessAnalyst.html">Business Analyst</a></p><table class="grid"><tr><td><b><a name="ar-FREQ-01"> </a></b>Define functional requirements from L1</td><td>SHALL</td><td><div><p>Can define functional requirements based on L1 recommendations in terms of health content, decision-support, and scheduling logic.</p>
</div></td></tr><tr><td><b><a name="ar-FREQ-02"> </a></b>Define non-functional requirements</td><td>SHALL</td><td><div><p>Can define non-functional requirements including user-friendliness and cybersecurity, informed by implementer best practices.</p>
</div></td></tr><tr><td><b><a name="ar-FREQ-03"> </a></b>Link requirements to personas</td><td>SHALL</td><td><div><p>Can link each functional requirement to the correct persona and business process activity.</p>
</div></td></tr><tr><td><b><a name="ar-FREQ-04"> </a></b>Verify scenario coverage</td><td>SHALL</td><td><div><p>Can verify that functionalities depicted in user scenarios are captured in the requirements list.</p>
</div></td></tr></table></div><div xml:lang="zh" lang="zh"><hr/><p><b>Chinese</b></p><hr/><p class="res-header-id"><b>Generated Narrative: Requirements SGAuthoring.Skills.AuthorFunctionalRequirements</b></p><a name="zh-SGAuthoring.Skills.AuthorFunctionalRequirements"> </a><a name="zh-hcSGAuthoring.Skills.AuthorFunctionalRequirements"> </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"/><p style="margin-bottom: 0px">Profile: <a href="StructureDefinition-SGRequirements.html">SMART Guidelines Requirements</a></p></div><p>These requirements apply to the actor <a href="ActorDefinition-SGAuthoring.Persona.BusinessAnalyst.html">Business Analyst</a></p><table class="grid"><tr><td><b><a name="zh-FREQ-01"> </a></b>Define functional requirements from L1</td><td>SHALL</td><td><div><p>Can define functional requirements based on L1 recommendations in terms of health content, decision-support, and scheduling logic.</p>
</div></td></tr><tr><td><b><a name="zh-FREQ-02"> </a></b>Define non-functional requirements</td><td>SHALL</td><td><div><p>Can define non-functional requirements including user-friendliness and cybersecurity, informed by implementer best practices.</p>
</div></td></tr><tr><td><b><a name="zh-FREQ-03"> </a></b>Link requirements to personas</td><td>SHALL</td><td><div><p>Can link each functional requirement to the correct persona and business process activity.</p>
</div></td></tr><tr><td><b><a name="zh-FREQ-04"> </a></b>Verify scenario coverage</td><td>SHALL</td><td><div><p>Can verify that functionalities depicted in user scenarios are captured in the requirements list.</p>
</div></td></tr></table></div><div xml:lang="ru" lang="ru"><hr/><p><b>Russian</b></p><hr/><p class="res-header-id"><b>Сгенерированный нарратив: Requirements SGAuthoring.Skills.AuthorFunctionalRequirements</b></p><a name="ru-SGAuthoring.Skills.AuthorFunctionalRequirements"> </a><a name="ru-hcSGAuthoring.Skills.AuthorFunctionalRequirements"> </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"/><p style="margin-bottom: 0px">Профиль: <a href="StructureDefinition-SGRequirements.html">SMART Guidelines Requirements</a></p></div><p>Эти требования распространяются и на актера <a href="ActorDefinition-SGAuthoring.Persona.BusinessAnalyst.html">Business Analyst</a></p><table class="grid"><tr><td><b><a name="ru-FREQ-01"> </a></b>Define functional requirements from L1</td><td>SHALL</td><td><div><p>Can define functional requirements based on L1 recommendations in terms of health content, decision-support, and scheduling logic.</p>
</div></td></tr><tr><td><b><a name="ru-FREQ-02"> </a></b>Define non-functional requirements</td><td>SHALL</td><td><div><p>Can define non-functional requirements including user-friendliness and cybersecurity, informed by implementer best practices.</p>
</div></td></tr><tr><td><b><a name="ru-FREQ-03"> </a></b>Link requirements to personas</td><td>SHALL</td><td><div><p>Can link each functional requirement to the correct persona and business process activity.</p>
</div></td></tr><tr><td><b><a name="ru-FREQ-04"> </a></b>Verify scenario coverage</td><td>SHALL</td><td><div><p>Can verify that functionalities depicted in user scenarios are captured in the requirements list.</p>
</div></td></tr></table></div><div xml:lang="es" lang="es"><hr/><p><b>Spanish</b></p><hr/><p class="res-header-id"><b>Generated Narrative: Requirements SGAuthoring.Skills.AuthorFunctionalRequirements</b></p><a name="es-SGAuthoring.Skills.AuthorFunctionalRequirements"> </a><a name="es-hcSGAuthoring.Skills.AuthorFunctionalRequirements"> </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"/><p style="margin-bottom: 0px">Profile: <a href="StructureDefinition-SGRequirements.html">SMART Guidelines Requirements</a></p></div><p>These requirements apply to the actor <a href="ActorDefinition-SGAuthoring.Persona.BusinessAnalyst.html">Business Analyst</a></p><table class="grid"><tr><td><b><a name="es-FREQ-01"> </a></b>Define functional requirements from L1</td><td>SHALL</td><td><div><p>Can define functional requirements based on L1 recommendations in terms of health content, decision-support, and scheduling logic.</p>
</div></td></tr><tr><td><b><a name="es-FREQ-02"> </a></b>Define non-functional requirements</td><td>SHALL</td><td><div><p>Can define non-functional requirements including user-friendliness and cybersecurity, informed by implementer best practices.</p>
</div></td></tr><tr><td><b><a name="es-FREQ-03"> </a></b>Link requirements to personas</td><td>SHALL</td><td><div><p>Can link each functional requirement to the correct persona and business process activity.</p>
</div></td></tr><tr><td><b><a name="es-FREQ-04"> </a></b>Verify scenario coverage</td><td>SHALL</td><td><div><p>Can verify that functionalities depicted in user scenarios are captured in the requirements list.</p>
</div></td></tr></table></div></div>
  </text>
  <extension url="http://smart.who.int/base/StructureDefinition/SGTask">
    <valueCoding>
      <system value="http://smart.who.int/base/CodeSystem/SGTasks"/>
      <code value="userTask"/>
      <display value="User Task"/>
    </valueCoding>
  </extension>
  <extension url="http://smart.who.int/base/StructureDefinition/SGTask">
    <valueCoding>
      <system value="http://smart.who.int/base/CodeSystem/SGTasks"/>
      <code value="userTask"/>
      <display value="User Task"/>
    </valueCoding>
  </extension>
  <extension url="http://smart.who.int/base/StructureDefinition/SGTask">
    <valueCoding>
      <system value="http://smart.who.int/base/CodeSystem/SGTasks"/>
      <code value="userTask"/>
      <display value="User Task"/>
    </valueCoding>
  </extension>
  <extension url="http://smart.who.int/base/StructureDefinition/SGTask">
    <valueCoding>
      <system value="http://smart.who.int/base/CodeSystem/SGTasks"/>
      <code value="userTask"/>
      <display value="User Task"/>
    </valueCoding>
  </extension>
  <extension url="http://smart.who.int/base/StructureDefinition/SGUserStory">
    <extension url="http://smart.who.int/base/StructureDefinition/SGString">
      <valueString
                   value="define functional and non-functional requirements linked to personas and business processes"/>
    </extension>
    <extension url="http://smart.who.int/base/StructureDefinition/SGString">
      <valueString
                   value="implementation requirements are traceable to clinical guidance and user workflows"/>
    </extension>
  </extension>
  <url
       value="http://smart.who.int/base/Requirements/SGAuthoring.Skills.AuthorFunctionalRequirements"/>
  <version value="0.2.0"/>
  <name value="SkillAuthorFunctionalRequirements"/>
  <title value="Can author functional requirements"/>
  <status value="draft"/>
  <experimental value="true"/>
  <date value="2026-03-20T00:42:00+00:00"/>
  <publisher value="WHO"/>
  <contact>
    <name value="WHO"/>
    <telecom>
      <system value="url"/>
      <value value="http://who.int"/>
    </telecom>
  </contact>
  <description
               value="Capability to define high-level functional and non-functional requirements linked to personas and business processes."/>
  <actor
         value="http://smart.who.int/base/ActorDefinition/SGAuthoring.Persona.BusinessAnalyst"/>
  <statement>
    <key value="FREQ-01"/>
    <label value="Define functional requirements from L1"/>
    <conformance value="SHALL"/>
    <requirement
                 value="Can define functional requirements based on L1 recommendations in terms of health content, decision-support, and scheduling logic."/>
  </statement>
  <statement>
    <key value="FREQ-02"/>
    <label value="Define non-functional requirements"/>
    <conformance value="SHALL"/>
    <requirement
                 value="Can define non-functional requirements including user-friendliness and cybersecurity, informed by implementer best practices."/>
  </statement>
  <statement>
    <key value="FREQ-03"/>
    <label value="Link requirements to personas"/>
    <conformance value="SHALL"/>
    <requirement
                 value="Can link each functional requirement to the correct persona and business process activity."/>
  </statement>
  <statement>
    <key value="FREQ-04"/>
    <label value="Verify scenario coverage"/>
    <conformance value="SHALL"/>
    <requirement
                 value="Can verify that functionalities depicted in user scenarios are captured in the requirements list."/>
  </statement>
</Requirements>