Scalable Consent Management, published by HL7 International / Community Based Collaborative Care. This guide is not an authorized publication; it is the continuous build for version 1.0.0-preview built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-consent-management/ and changes regularly. See the Directory of published versions

• Narrative Content
• XML
• JSON
• TTL

: Artifacts Summary Client

Raw xml | Download

<Requirements xmlns="http://hl7.org/fhir">
  <id value="artifacts-summary-client"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: Requirements artifacts-summary-client</b></p><a name="artifacts-summary-client"> </a><a name="hcartifacts-summary-client"> </a><p>These requirements apply to the actor <a href="ActorDefinition-client.html">Client</a></p><table class="grid"><tr><td><b><a name="48"> </a></b>requirement-48</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a></td><td><div><p>Consent Client SHALL implement the client CapabilityStatement&lt;br/&gt;&lt;br/&gt;- Interpreting this as: a client doesn't necessarily have to maintain and make available a client CS, but does have to implement the functionality therein. So specific requirements from the CS are traced to tests that exercise them.</p>
<ul>
<li>Does this mean a conforming system has to reference the &quot;requirements&quot; CS here, or could they just have their own CS that happens to be compatible?</li>
</ul>
</div><p>Links: </p><ul><li>Derived From: <code>HL7 FAST Consent IG</code></li><li>Satisfied By: <a href="https://build.fhir.org/ig/HL7/fhir-consent-management/en/artifacts.html#:~:text=Capabilities%20required%20for%20a%20Consent%20Client%20system%20filing%20and%20reviewing%20consents">https://build.fhir.org/ig/HL7/fhir-consent-management/en/artifacts.html</a></li></ul></td></tr></table></div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="cbcc"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="1">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical
                        value="http://hl7.org/fhir/us/consent-management/ImplementationGuide/hl7.fhir.us.consent-management"/>
      </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/consent-management/ImplementationGuide/hl7.fhir.us.consent-management"/>
      </extension>
    </valueCode>
  </extension>
  <url
       value="http://hl7.org/fhir/us/consent-management/Requirements/artifacts-summary-client"/>
  <version value="1.0.0-preview"/>
  <name value="ArtifactsSummaryClient"/>
  <title value="Artifacts Summary Client"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2026-09-02T22:40:54-04:00"/>
  <publisher value="HL7 International / Community Based Collaborative Care"/>
  <contact>
    <name value="HL7 International / Community Based Collaborative Care"/>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/homehealth"/>
    </telecom>
  </contact>
  <description value="Artifacts Summary Requirements for Client"/>
  <jurisdiction>
    <coding>
      <system value="urn:iso:std:iso:3166"/>
      <code value="US"/>
      <display value="United States of America"/>
    </coding>
  </jurisdiction>
  <actor
         value="http://hl7.org/fhir/us/consent-management/ActorDefinition/client"/>
  <statement>
    <key value="48"/>
    <label value="requirement-48"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="Consent Client SHALL implement the client CapabilityStatement&lt;br/&gt;&lt;br/&gt;- Interpreting this as: a client doesn't necessarily have to maintain and make available a client CS, but does have to implement the functionality therein. So specific requirements from the CS are traced to tests that exercise them.
- Does this mean a conforming system has to reference the &quot;requirements&quot; CS here, or could they just have their own CS that happens to be compatible?"/>
    <derivedFrom value="HL7 FAST Consent IG"/>
    <satisfiedBy
                 value="https://build.fhir.org/ig/HL7/fhir-consent-management/en/artifacts.html#:~:text=Capabilities%20required%20for%20a%20Consent%20Client%20system%20filing%20and%20reviewing%20consents"/>
  </statement>
</Requirements>