PACIO Personal Functioning and Engagement Implementation Guide, published by HL7 International / Patient Care. This guide is not an authorized publication; it is the continuous build for version 3.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-pacio-pfe/ and changes regularly. See the Directory of published versions

• Narrative Content
• XML
• JSON
• TTL

: Narrative Conformance Statements

Raw xml | Download

<Requirements xmlns="http://hl7.org/fhir">
  <id value="fromNarrative"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: Requirements fromNarrative</b></p><a name="fromNarrative"> </a><a name="hcfromNarrative"> </a><table class="grid"><tr><td><b><a name="CONF-1"> </a></b>CONF-1</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>PACIO Personal Functioning and Engagement Servers <strong>SHALL</strong> support the capabilities described in the US Core Server CapabilityStatement.</p>
</div></td></tr><tr><td><b><a name="CONF-2"> </a></b>CONF-2</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>These collection observations represent structured instruments and panels with multiple questions. The hasMember element <strong>SHALL</strong> be used to point to child Observation instances that contain the specific questions and answers, represented by <a href="StructureDefinition-pfe-observation-single.html">Single Observations</a> or nested panels represented by this profile.</p>
</div></td></tr><tr><td><b><a name="CONF-3"> </a></b>CONF-3</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>The Observation.value and Observation.component elements <strong>SHALL</strong> be empty.</p>
</div></td></tr><tr><td><b><a name="CONF-4"> </a></b>CONF-4</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>When a health or health-related domain is specified as an additional <a href="ValueSet-pfe-category-vs.html">category value</a>, Observation.code <strong>SHOULD</strong> be drawn from the corresponding domain-based value set as discussed below and on the <a href="domains.html">domains</a> page.</p>
</div></td></tr><tr><td><b><a name="CONF-5"> </a></b>CONF-5</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><strong>SHALL</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html"><code>category</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-6"> </a></b>CONF-6</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><strong>SHALL</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-code.html"><code>code</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-7"> </a></b>CONF-7</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p><strong>SHOULD</strong> support search by multiple report codes.</p>
</div></td></tr><tr><td><b><a name="CONF-8"> </a></b>CONF-8</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><strong>SHALL</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html"><code>category</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-date.html"><code>date</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-9"> </a></b>CONF-9</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p><strong>SHOULD</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html"><code>category</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-status.html"><code>status</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-10"> </a></b>CONF-10</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p><strong>SHOULD</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-code.html"><code>code</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-date.html"><code>date</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-11"> </a></b>CONF-11</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p><strong>SHOULD</strong> support search by multiple report codes.</p>
</div></td></tr><tr><td><b><a name="CONF-12"> </a></b>CONF-12</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>Implementations <strong>SHALL</strong> follow the <a href="https://hl7.org/fhir/us/core/STU9/StructureDefinition-us-core-device.html#profile-specific-implementation-guidance">US Core Device Profile UDI Specific Implementation Guidance</a> when exchanging Unique Device Identifier (UDI) information.</p>
</div></td></tr><tr><td><b><a name="CONF-13"> </a></b>CONF-13</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-MAY">MAY</a></td><td><div><p>FHIR R4 DeviceRequest.requester allows Device, Practitioner, PractitionerRole, and Organization. FHIR R6 DeviceRequest.requester also allows CareTeam, Group, Patient, and RelatedPerson. Implementer <strong>MAY</strong> use the <a href="StructureDefinition-pfe-device-request-additional-requester.html">additional-requester</a> extension for these additional requester types added in FHIR R6.</p>
</div></td></tr><tr><td><b><a name="CONF-14"> </a></b>CONF-14</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>When a health or health-related domain is specified as an additional <a href="ValueSet-pfe-category-vs.html">category value</a>, DiagnosticReport.code <strong>SHOULD</strong> be drawn from the corresponding domain-based value set as discussed on the <a href="domains.html">domains</a> page.</p>
</div></td></tr><tr><td><b><a name="CONF-15"> </a></b>CONF-15</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><strong>SHALL</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-category.html"><code>category</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-16"> </a></b>CONF-16</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><strong>SHALL</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-code.html"><code>code</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-17"> </a></b>CONF-17</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p><strong>SHOULD</strong> support search by multiple report codes.</p>
</div></td></tr><tr><td><b><a name="CONF-18"> </a></b>CONF-18</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><strong>SHALL</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-category.html"><code>category</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-date.html"><code>date</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-19"> </a></b>CONF-19</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p><strong>SHOULD</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-category.html"><code>category</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-status.html"><code>status</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-20"> </a></b>CONF-20</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p><strong>SHOULD</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-code.html"><code>code</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-date.html"><code>date</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-21"> </a></b>CONF-21</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p><strong>SHOULD</strong> support search by multiple report codes.</p>
</div></td></tr><tr><td><b><a name="CONF-22"> </a></b>CONF-22</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>An Observation without a value, <strong>SHALL</strong> include a reason why the data is absent unless there are component observations. Systems that never provide an observation without a value are not required to support Observation.dataAbsentReason.</p>
</div></td></tr><tr><td><b><a name="CONF-23"> </a></b>CONF-23</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>When a health or health-related domain is specified as an additional <a href="ValueSet-pfe-category-vs.html">category value</a>, Observation.code <strong>SHOULD</strong> be drawn from the corresponding domain-based value set as discussed <a href="StructureDefinition-pfe-observation-clinicaltest.html#domain-specific-value-set-bindings">below</a> and on the <a href="domains.html">domains</a> page.</p>
</div></td></tr><tr><td><b><a name="CONF-24"> </a></b>CONF-24</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><strong>SHALL</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html"><code>category</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-25"> </a></b>CONF-25</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><strong>SHALL</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-code.html"><code>code</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-26"> </a></b>CONF-26</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p><strong>SHOULD</strong> support search by multiple report codes.</p>
</div></td></tr><tr><td><b><a name="CONF-27"> </a></b>CONF-27</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><strong>SHALL</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html"><code>category</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-date.html"><code>date</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-28"> </a></b>CONF-28</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p><strong>SHOULD</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html"><code>category</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-status.html"><code>status</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-29"> </a></b>CONF-29</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p><strong>SHOULD</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-code.html"><code>code</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-date.html"><code>date</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-30"> </a></b>CONF-30</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p><strong>SHOULD</strong> support search by multiple report codes.</p>
</div></td></tr><tr><td><b><a name="CONF-31"> </a></b>CONF-31</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a>, <a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>These observations represent a specific question or observation, so the Observation.value element <strong>SHOULD</strong> be populated and the hasMember list <strong>SHALL</strong> be empty.</p>
</div></td></tr><tr><td><b><a name="CONF-32"> </a></b>CONF-32</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>An Observation without a value, <strong>SHALL</strong> include a reason why the data is absent unless there are component observations. Systems that never provide an observation without a value are not required to support Observation.dataAbsentReason.</p>
</div></td></tr><tr><td><b><a name="CONF-33"> </a></b>CONF-33</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>When a health or health-related domain is specified as an additional <a href="ValueSet-pfe-category-vs.html">category value</a>, Observation.code <strong>SHOULD</strong> be drawn from the corresponding domain-based value set as discussed below and on the <a href="domains.html">domains</a> page.</p>
</div></td></tr><tr><td><b><a name="CONF-34"> </a></b>CONF-34</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>Where a preferred value set contains a code to describe a needed concept, servers <strong>SHOULD</strong> use that code.</p>
</div></td></tr><tr><td><b><a name="CONF-35"> </a></b>CONF-35</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><strong>SHALL</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html"><code>category</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-36"> </a></b>CONF-36</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><strong>SHALL</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-code.html"><code>code</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-37"> </a></b>CONF-37</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p><strong>SHOULD</strong> support search by multiple report codes.</p>
</div></td></tr><tr><td><b><a name="CONF-38"> </a></b>CONF-38</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><strong>SHALL</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html"><code>category</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-date.html"><code>date</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-39"> </a></b>CONF-39</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p><strong>SHOULD</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html"><code>category</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-status.html"><code>status</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-40"> </a></b>CONF-40</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p><strong>SHOULD</strong> support searching using the combination of the <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html"><code>patient</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-code.html"><code>code</code></a></strong> and <strong><a href="https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-date.html"><code>date</code></a></strong> search parameters:</p>
</div></td></tr><tr><td><b><a name="CONF-41"> </a></b>CONF-41</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p><strong>SHOULD</strong> support search by multiple report codes.</p>
</div></td></tr><tr><td><b><a name="CONF-42"> </a></b>CONF-42</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>Implementers of this IG <strong>SHOULD</strong> include at least one category from the <a href="ValueSet-pfe-category-vs.html">Domain Category value set</a> on each observation instance conformant to this guide.</p>
</div></td></tr><tr><td><b><a name="CONF-43"> </a></b>CONF-43</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>Additionally, the code of the instance <strong>SHOULD</strong> come from the value set associated with the indicated category or categories.</p>
</div></td></tr><tr><td><b><a name="CONF-44"> </a></b>CONF-44</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>PAC assessment observations <strong>SHOULD</strong> be categorized into the ICF domain within the “Activities and Participation” category only when the question focuses on a specific activity.</p>
</div></td></tr><tr><td><b><a name="CONF-45"> </a></b>CONF-45</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>PAC assessment observations that are part of a specific group of questions (e.g.,PHQ-9 or BIMS) or part of a group of questions listed all under the same header question <strong>SHOULD</strong> be categorized according to the main focus of the grouping header.</p>
</div></td></tr><tr><td><b><a name="CONF-46"> </a></b>CONF-46</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>All available assessment item resources, such as the question’s available responses, the question text, and the question short name, <strong>SHOULD</strong> be considered when making categorization decisions.</p>
</div></td></tr><tr><td><b><a name="CONF-47"> </a></b>CONF-47</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><strong>SHALL</strong> be able to populate all Profile data elements that have a minimum cardinality &gt;= 1 and/or flagged as Must Support as defined by that profile’s StructureDefinition.</p>
</div></td></tr><tr><td><b><a name="CONF-48"> </a></b>CONF-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><strong>SHALL</strong> conform to the <a href="CapabilityStatement-pacio-pfe-cap.html">Personal Functioning and Engagement Capability Statement</a> expectations for that Profile’s type.</p>
</div></td></tr><tr><td><b><a name="CONF-49"> </a></b>CONF-49</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>Data Sources Systems <strong>SHALL</strong> be capable of populating all data elements as part of the query results as specified by the <a href="CapabilityStatement-pacio-pfe-cap.html">Personal Functioning and Engagement Capability Statement</a>.</p>
</div></td></tr><tr><td><b><a name="CONF-50"> </a></b>CONF-50</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>Data Consumer Systems <strong>SHALL</strong> be capable of displaying the data elements for human use.</p>
</div></td></tr><tr><td><b><a name="CONF-51"> </a></b>CONF-51</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>Data Consumer Systems <strong>SHOULD</strong> be capable of storing the data elements for other uses (such as record keeping of data used for clinical use).</p>
</div></td></tr><tr><td><b><a name="CONF-52"> </a></b>CONF-52</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>Data Consumer Systems <strong>SHALL</strong> be capable of processing resource instances containing the data element without generating an error or causing the application to fail.</p>
</div></td></tr><tr><td><b><a name="CONF-53"> </a></b>CONF-53</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>Data Consumer Systems <strong>SHALL</strong> interpret missing data elements within resources instances as not being present on the Data Sources system’s or as being withheld for privacy or business reasons.</p>
</div></td></tr><tr><td><b><a name="CONF-54"> </a></b>CONF-54</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>When one of the below assessments is being recorded as an observation, systems <strong>SHOULD</strong> use the <a href="artifacts.html#artifacts-table">LOINC to ICF Mapping ConceptMaps</a> to populate the <code>PFEDomain</code> category slice with the appropriate ICF code(s).</p>
</div></td></tr><tr><td><b><a name="CONF-55"> </a></b>CONF-55</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>If the assessment is not in the list, systems <strong>SHOULD</strong> implement their own mapping for those assessments.</p>
</div></td></tr><tr><td><b><a name="CONF-56"> </a></b>CONF-56</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>Systems <strong>SHOULD</strong> retain the original LOINC-coded observation while using the mapped ICF code(s) for <code>PFEDomain</code> categorization.</p>
</div></td></tr><tr><td><b><a name="CONF-57"> </a></b>CONF-57</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>All implementers of the Personal Functioning and Engagement IG <strong>SHOULD</strong> follow the HL7® FHIR® Security guidance, Security and Privacy Module, the FHIR Implementer’s Safety Checklist guidance as defined in the FHIR standard, and US Core security recommendations where applicable and not otherwise superseded by this section of the Personal Functioning and Engagement IG.</p>
</div></td></tr><tr><td><b><a name="CONF-58"> </a></b>CONF-58</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>In order to protect sensitive patient data while in transit between systems, the exchange of information using the Personal Functioning and Engagement IG <strong>SHALL</strong> support <a href="https://tools.ietf.org/html/rfc5246">Transport Layer Security (TLS) Protocol Version 1.2 (RFC5246)</a> or a more recent version of TLS for transport layer security.</p>
</div></td></tr><tr><td><b><a name="CONF-59"> </a></b>CONF-59</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>Server implementations that expect to support browser-based javascript applications <strong>SHOULD</strong> enable <a href="https://www.w3.org/TR/cors/">Cross-Origin Resource Sharing (CORS)</a> for REST operations.</p>
</div></td></tr><tr><td><b><a name="CONF-60"> </a></b>To prevent unauthorized access to sensitive data, implementers SHALL use at least one of the following</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>To prevent unauthorized access to sensitive data, implementers SHALL use at least one of the following:</p>
<ol>
<li>The security requirements from the<a href="http://hl7.org/FHIR/us/core/security.html">US Core Implementation Guide</a>,</li>
<li>The<a href="http://hl7.org/FHIR/smart-app-launch/index.html">SMART on FHIR App Launch Framework</a>,</li>
<li><a href="http://www.hl7.org/FHIR/smart-app-launch/backend-services.html">SMART on FHIR Backend Services</a>,</li>
<li>Mutually authenticated TLS, or</li>
<li><a href="https://www.udap.org/">Unified Data Access Profiles (UDAP)</a>recommended by the ONC FHIR At Scale Taskforce (FAST) security tiger team.</li>
</ol>
</div></td></tr><tr><td><b><a name="CONF-61"> </a></b>CONF-61</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-MAY">MAY</a></td><td><div><p>The <a href="http://hl7.org/fhir/uv/sdc/">Structured Data Capture FHIR IG</a> provides a methodology for capturing this information within FHIR both in its raw and in its discrete structured form. This page provides guidance on how tools like the <a href="https://hl7.org/fhir/uv/sdc/StructureDefinition-sdc-questionnaire.html">SDC Questionnaire</a> and <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-questionnaireresponse.html">US Core QuestionnaireResponse</a> resources <strong>MAY</strong> be used with this IG.</p>
</div></td></tr><tr><td><b><a name="CONF-62"> </a></b>CONF-62</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>When representing formal assessments with complex structures as FHIR Observations, each panel and question <strong>SHALL</strong> be mapped to an individual Observation instance, with panels represented using the <a href="StructureDefinition-pfe-collection.html">collection</a> profile and questions represented using the <a href="StructureDefinition-pfe-observation-single.html">single observation</a> profile.</p>
</div></td></tr><tr><td><b><a name="CONF-63"> </a></b>CONF-63</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><strong>Parent-child links</strong>: parent observations <strong>SHALL</strong> contain references to each child observation instance, including nested panels and specific questions using the <code>hasMember</code> element.</p>
</div></td></tr><tr><td><b><a name="CONF-64"> </a></b>CONF-64</td><td><a href="http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p><strong>Derivation links</strong>: observations derived from other questions, such as summary scores, <strong>SHOULD</strong> point to the observations that the result is derived from using the <code>derivedFrom</code> element.</p>
</div></td></tr></table></div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="pc"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="3">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical
                        value="http://hl7.org/fhir/us/pacio-pfe/ImplementationGuide/hl7.fhir.us.pacio-pfe"/>
      </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/pacio-pfe/ImplementationGuide/hl7.fhir.us.pacio-pfe"/>
      </extension>
    </valueCode>
  </extension>
  <url value="http://hl7.org/fhir/us/pacio-pfe/Requirements/fromNarrative"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.4.642.40.67.36.1"/>
  </identifier>
  <version value="3.0.0-ballot"/>
  <name value="FromNarrative"/>
  <title value="Narrative Conformance Statements"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2026-10-06T16:48:35+00:00"/>
  <publisher value="HL7 International / Patient Care"/>
  <contact>
    <name value="HL7 International / Patient Care"/>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/patientcare"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="patientcare@lists.HL7.org"/>
    </telecom>
  </contact>
  <contact>
    <name value="PACIO project"/>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/patientcare"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="info@pacioproject.org"/>
    </telecom>
  </contact>
  <description
               value="Conformance statements found throughout the narrative of the IG consolidated into this computable resource for traceability purposes"/>
  <jurisdiction>
    <coding>
      <system value="urn:iso:std:iso:3166"/>
      <code value="US"/>
    </coding>
  </jurisdiction>
  <statement>
    <key value="CONF-1"/>
    <conformance value="SHALL"/>
    <requirement
                 value="PACIO Personal Functioning and Engagement Servers **SHALL** support the capabilities described in the US Core Server CapabilityStatement."/>
  </statement>
  <statement>
    <key value="CONF-2"/>
    <conformance value="SHALL"/>
    <requirement
                 value="These collection observations represent structured instruments and panels with multiple questions. The hasMember element **SHALL** be used to point to child Observation instances that contain the specific questions and answers, represented by [Single Observations](StructureDefinition-pfe-observation-single.html) or nested panels represented by this profile."/>
  </statement>
  <statement>
    <key value="CONF-3"/>
    <conformance value="SHALL"/>
    <requirement
                 value="The Observation.value and Observation.component elements **SHALL** be empty."/>
  </statement>
  <statement>
    <key value="CONF-4"/>
    <conformance value="SHOULD"/>
    <conditionality value="true"/>
    <requirement
                 value="When a health or health-related domain is specified as an additional [category value](ValueSet-pfe-category-vs.html), Observation.code **SHOULD** be drawn from the corresponding domain-based value set as discussed below and on the [domains](domains.html) page."/>
  </statement>
  <statement>
    <key value="CONF-5"/>
    <conformance value="SHALL"/>
    <requirement
                 value="**SHALL** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html)** and **[`category`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-6"/>
    <conformance value="SHALL"/>
    <requirement
                 value="**SHALL** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html)** and **[`code`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-code.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-7"/>
    <conformance value="SHOULD"/>
    <requirement value="**SHOULD** support search by multiple report codes."/>
  </statement>
  <statement>
    <key value="CONF-8"/>
    <conformance value="SHALL"/>
    <requirement
                 value="**SHALL** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html)** and **[`category`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html)** and **[`date`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-date.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-9"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="**SHOULD** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html)** and **[`category`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html)** and **[`status`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-status.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-10"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="**SHOULD** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html)** and **[`code`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-code.html)** and **[`date`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-date.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-11"/>
    <conformance value="SHOULD"/>
    <requirement value="**SHOULD** support search by multiple report codes."/>
  </statement>
  <statement>
    <key value="CONF-12"/>
    <conformance value="SHALL"/>
    <requirement
                 value="Implementations **SHALL** follow the [US Core Device Profile UDI Specific Implementation Guidance](https://hl7.org/fhir/us/core/STU9/StructureDefinition-us-core-device.html#profile-specific-implementation-guidance) when exchanging Unique Device Identifier (UDI) information."/>
  </statement>
  <statement>
    <key value="CONF-13"/>
    <conformance value="MAY"/>
    <requirement
                 value="FHIR R4 DeviceRequest.requester allows Device, Practitioner, PractitionerRole, and Organization. FHIR R6 DeviceRequest.requester also allows CareTeam, Group, Patient, and RelatedPerson. Implementer **MAY** use the [additional-requester](StructureDefinition-pfe-device-request-additional-requester.html) extension for these additional requester types added in FHIR R6."/>
  </statement>
  <statement>
    <key value="CONF-14"/>
    <conformance value="SHOULD"/>
    <conditionality value="true"/>
    <requirement
                 value="When a health or health-related domain is specified as an additional [category value](ValueSet-pfe-category-vs.html), DiagnosticReport.code **SHOULD** be drawn from the corresponding domain-based value set as discussed on the [domains](domains.html) page."/>
  </statement>
  <statement>
    <key value="CONF-15"/>
    <conformance value="SHALL"/>
    <requirement
                 value="**SHALL** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-patient.html)** and **[`category`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-category.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-16"/>
    <conformance value="SHALL"/>
    <requirement
                 value="**SHALL** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-patient.html)** and **[`code`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-code.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-17"/>
    <conformance value="SHOULD"/>
    <requirement value="**SHOULD** support search by multiple report codes."/>
  </statement>
  <statement>
    <key value="CONF-18"/>
    <conformance value="SHALL"/>
    <requirement
                 value="**SHALL** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-patient.html)** and **[`category`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-category.html)** and **[`date`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-date.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-19"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="**SHOULD** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-patient.html)** and **[`category`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-category.html)** and **[`status`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-status.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-20"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="**SHOULD** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-patient.html)** and **[`code`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-code.html)** and **[`date`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-diagnosticreport-date.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-21"/>
    <conformance value="SHOULD"/>
    <requirement value="**SHOULD** support search by multiple report codes."/>
  </statement>
  <statement>
    <key value="CONF-22"/>
    <conformance value="SHALL"/>
    <requirement
                 value="An Observation without a value, **SHALL** include a reason why the data is absent unless there are component observations. Systems that never provide an observation without a value are not required to support Observation.dataAbsentReason."/>
  </statement>
  <statement>
    <key value="CONF-23"/>
    <conformance value="SHOULD"/>
    <conditionality value="true"/>
    <requirement
                 value="When a health or health-related domain is specified as an additional [category value](ValueSet-pfe-category-vs.html), Observation.code **SHOULD** be drawn from the corresponding domain-based value set as discussed [below](StructureDefinition-pfe-observation-clinicaltest.html#domain-specific-value-set-bindings) and on the [domains](domains.html) page."/>
  </statement>
  <statement>
    <key value="CONF-24"/>
    <conformance value="SHALL"/>
    <requirement
                 value="**SHALL** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html)** and **[`category`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-25"/>
    <conformance value="SHALL"/>
    <requirement
                 value="**SHALL** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html)** and **[`code`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-code.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-26"/>
    <conformance value="SHOULD"/>
    <requirement value="**SHOULD** support search by multiple report codes."/>
  </statement>
  <statement>
    <key value="CONF-27"/>
    <conformance value="SHALL"/>
    <requirement
                 value="**SHALL** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html)** and **[`category`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html)** and **[`date`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-date.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-28"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="**SHOULD** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html)** and **[`category`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html)** and **[`status`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-status.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-29"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="**SHOULD** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html)** and **[`code`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-code.html)** and **[`date`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-date.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-30"/>
    <conformance value="SHOULD"/>
    <requirement value="**SHOULD** support search by multiple report codes."/>
  </statement>
  <statement>
    <key value="CONF-31"/>
    <conformance value="SHALL"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="These observations represent a specific question or observation, so the Observation.value element **SHOULD** be populated and the hasMember list **SHALL** be empty."/>
  </statement>
  <statement>
    <key value="CONF-32"/>
    <conformance value="SHALL"/>
    <requirement
                 value="An Observation without a value, **SHALL** include a reason why the data is absent unless there are component observations. Systems that never provide an observation without a value are not required to support Observation.dataAbsentReason."/>
  </statement>
  <statement>
    <key value="CONF-33"/>
    <conformance value="SHOULD"/>
    <conditionality value="true"/>
    <requirement
                 value="When a health or health-related domain is specified as an additional [category value](ValueSet-pfe-category-vs.html), Observation.code **SHOULD** be drawn from the corresponding domain-based value set as discussed below and on the [domains](domains.html) page."/>
  </statement>
  <statement>
    <key value="CONF-34"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="Where a preferred value set contains a code to describe a needed concept, servers **SHOULD** use that code."/>
  </statement>
  <statement>
    <key value="CONF-35"/>
    <conformance value="SHALL"/>
    <requirement
                 value="**SHALL** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html)** and **[`category`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-36"/>
    <conformance value="SHALL"/>
    <requirement
                 value="**SHALL** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html)** and **[`code`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-code.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-37"/>
    <conformance value="SHOULD"/>
    <requirement value="**SHOULD** support search by multiple report codes."/>
  </statement>
  <statement>
    <key value="CONF-38"/>
    <conformance value="SHALL"/>
    <requirement
                 value="**SHALL** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html)** and **[`category`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html)** and **[`date`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-date.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-39"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="**SHOULD** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html)** and **[`category`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-category.html)** and **[`status`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-status.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-40"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="**SHOULD** support searching using the combination of the **[`patient`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-patient.html)** and **[`code`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-code.html)** and **[`date`](https://hl7.org/fhir/us/core/STU9/SearchParameter-us-core-observation-date.html)** search parameters:"/>
  </statement>
  <statement>
    <key value="CONF-41"/>
    <conformance value="SHOULD"/>
    <requirement value="**SHOULD** support search by multiple report codes."/>
  </statement>
  <statement>
    <key value="CONF-42"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="Implementers of this IG **SHOULD** include at least one category from the [Domain Category value set](ValueSet-pfe-category-vs.html) on each observation instance conformant to this guide."/>
  </statement>
  <statement>
    <key value="CONF-43"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="Additionally, the code of the instance **SHOULD** come from the value set associated with the indicated category or categories."/>
  </statement>
  <statement>
    <key value="CONF-44"/>
    <conformance value="SHOULD"/>
    <conditionality value="true"/>
    <requirement
                 value="PAC assessment observations **SHOULD** be categorized into the ICF domain within the “Activities and Participation” category only when the question focuses on a specific activity."/>
  </statement>
  <statement>
    <key value="CONF-45"/>
    <conformance value="SHOULD"/>
    <conditionality value="true"/>
    <requirement
                 value="PAC assessment observations that are part of a specific group of questions (e.g.,PHQ-9 or BIMS) or part of a group of questions listed all under the same header question **SHOULD** be categorized according to the main focus of the grouping header."/>
  </statement>
  <statement>
    <key value="CONF-46"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="All available assessment item resources, such as the question’s available responses, the question text, and the question short name, **SHOULD** be considered when making categorization decisions."/>
  </statement>
  <statement>
    <key value="CONF-47"/>
    <conformance value="SHALL"/>
    <requirement
                 value="**SHALL** be able to populate all Profile data elements that have a minimum cardinality &gt;= 1 and/or flagged as Must Support as defined by that profile’s StructureDefinition."/>
  </statement>
  <statement>
    <key value="CONF-48"/>
    <conformance value="SHALL"/>
    <requirement
                 value="**SHALL** conform to the [Personal Functioning and Engagement Capability Statement](CapabilityStatement-pacio-pfe-cap.html) expectations for that Profile’s type."/>
  </statement>
  <statement>
    <key value="CONF-49"/>
    <conformance value="SHALL"/>
    <requirement
                 value="Data Sources Systems **SHALL** be capable of populating all data elements as part of the query results as specified by the [Personal Functioning and Engagement Capability Statement](CapabilityStatement-pacio-pfe-cap.html)."/>
  </statement>
  <statement>
    <key value="CONF-50"/>
    <conformance value="SHALL"/>
    <requirement
                 value="Data Consumer Systems **SHALL** be capable of displaying the data elements for human use."/>
  </statement>
  <statement>
    <key value="CONF-51"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="Data Consumer Systems **SHOULD** be capable of storing the data elements for other uses (such as record keeping of data used for clinical use)."/>
  </statement>
  <statement>
    <key value="CONF-52"/>
    <conformance value="SHALL"/>
    <requirement
                 value="Data Consumer Systems **SHALL** be capable of processing resource instances containing the data element without generating an error or causing the application to fail."/>
  </statement>
  <statement>
    <key value="CONF-53"/>
    <conformance value="SHALL"/>
    <requirement
                 value="Data Consumer Systems **SHALL** interpret missing data elements within resources instances as not being present on the Data Sources system’s or as being withheld for privacy or business reasons."/>
  </statement>
  <statement>
    <key value="CONF-54"/>
    <conformance value="SHOULD"/>
    <conditionality value="true"/>
    <requirement
                 value="When one of the below assessments is being recorded as an observation, systems **SHOULD** use the [LOINC to ICF Mapping ConceptMaps](artifacts.html#artifacts-table) to populate the `PFEDomain` category slice with the appropriate ICF code(s)."/>
  </statement>
  <statement>
    <key value="CONF-55"/>
    <conformance value="SHOULD"/>
    <conditionality value="true"/>
    <requirement
                 value="If the assessment is not in the list, systems **SHOULD** implement their own mapping for those assessments."/>
  </statement>
  <statement>
    <key value="CONF-56"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="Systems **SHOULD** retain the original LOINC-coded observation while using the mapped ICF code(s) for `PFEDomain` categorization."/>
  </statement>
  <statement>
    <key value="CONF-57"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="All implementers of the Personal Functioning and Engagement IG **SHOULD** follow the HL7® FHIR® Security guidance, Security and Privacy Module, the FHIR Implementer’s Safety Checklist guidance as defined in the FHIR standard, and US Core security recommendations where applicable and not otherwise superseded by this section of the Personal Functioning and Engagement IG."/>
  </statement>
  <statement>
    <key value="CONF-58"/>
    <conformance value="SHALL"/>
    <requirement
                 value="In order to protect sensitive patient data while in transit between systems, the exchange of information using the Personal Functioning and Engagement IG **SHALL** support [Transport Layer Security (TLS) Protocol Version 1.2 (RFC5246)](https://tools.ietf.org/html/rfc5246) or a more recent version of TLS for transport layer security."/>
  </statement>
  <statement>
    <key value="CONF-59"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="Server implementations that expect to support browser-based javascript applications **SHOULD** enable [Cross-Origin Resource Sharing (CORS)](https://www.w3.org/TR/cors/) for REST operations."/>
  </statement>
  <statement>
    <key value="CONF-60"/>
    <label
           value="To prevent unauthorized access to sensitive data, implementers SHALL use at least one of the following"/>
    <conformance value="SHALL"/>
    <requirement
                 value="To prevent unauthorized access to sensitive data, implementers SHALL use at least one of the following:

1. The security requirements from the[US Core Implementation Guide](http://hl7.org/FHIR/us/core/security.html),
1. The[SMART on FHIR App Launch Framework](http://hl7.org/FHIR/smart-app-launch/index.html),
1. [SMART on FHIR Backend Services](http://www.hl7.org/FHIR/smart-app-launch/backend-services.html),
1. Mutually authenticated TLS, or
1. [Unified Data Access Profiles (UDAP)](https://www.udap.org/)recommended by the ONC FHIR At Scale Taskforce (FAST) security tiger team."/>
  </statement>
  <statement>
    <key value="CONF-61"/>
    <conformance value="MAY"/>
    <requirement
                 value="The [Structured Data Capture FHIR IG](http://hl7.org/fhir/uv/sdc/) provides a methodology for capturing this information within FHIR both in its raw and in its discrete structured form. This page provides guidance on how tools like the [SDC Questionnaire](https://hl7.org/fhir/uv/sdc/StructureDefinition-sdc-questionnaire.html) and [US Core QuestionnaireResponse](http://hl7.org/fhir/us/core/StructureDefinition-us-core-questionnaireresponse.html) resources **MAY** be used with this IG."/>
  </statement>
  <statement>
    <key value="CONF-62"/>
    <conformance value="SHALL"/>
    <conditionality value="true"/>
    <requirement
                 value="When representing formal assessments with complex structures as FHIR Observations, each panel and question **SHALL** be mapped to an individual Observation instance, with panels represented using the [collection](StructureDefinition-pfe-collection.html) profile and questions represented using the [single observation](StructureDefinition-pfe-observation-single.html) profile."/>
  </statement>
  <statement>
    <key value="CONF-63"/>
    <conformance value="SHALL"/>
    <requirement
                 value="**Parent-child links**: parent observations **SHALL** contain references to each child observation instance, including nested panels and specific questions using the `hasMember` element."/>
  </statement>
  <statement>
    <key value="CONF-64"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="**Derivation links**: observations derived from other questions, such as summary scores, **SHOULD** point to the observations that the result is derived from using the `derivedFrom` element."/>
  </statement>
</Requirements>