Personal Health Record System Functional Model, Release 2
0.1.0 - CI Build

Personal Health Record System Functional Model, Release 2 - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

: S.4.1.1 Capture Genomic/Proteomic Data and Documentation from External Clinical Sources (Function) - XML Representation

Active as of 2024-01-31

Raw xml | Download



<Requirements xmlns="http://hl7.org/fhir">
  <id value="PHRSFMR2-S.4.1.1"/>
  <meta>
    <profile value="http://hl7.org/ehrs/StructureDefinition/FMFunction"/>
  </meta>
  <text>
    <status value="extensions"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
    <table id="statements" class="grid dict">
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>S.4.1.1#01</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                <span>SHOULD</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>The system SHOULD provide the ability to capture relevant family genomic history.</p>
</div></span>
                

                
                Satisfied by:<ol>
                
                    <li><a href="https://www.hl7.org/fhir/molecularsequence.html">https://www.hl7.org/fhir/molecularsequence.html</a></li>
                
                </ol>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>S.4.1.1#02</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                <span>MAY</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>The system MAY capture and maintain genomic/proteomic information through interaction with other systems, applications, and modules.</p>
</div></span>
                

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>S.4.1.1#03</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                <span>SHALL</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>IF laboratory results are received through an electronic interface, THEN the system SHALL render the data elements upon request.</p>
</div></span>
                

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>S.4.1.1#04</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                <span>SHALL</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>IF laboratory results are received through an electronic interface, THEN the system SHALL capture and maintain the data elements in the PHR Account Holder record.</p>
</div></span>
                

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>S.4.1.1#05</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                <span>MAY</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>The system MAY provide the ability to store imaged documents.</p>
</div></span>
                

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>S.4.1.1#06</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                <span>SHOULD</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>The system SHOULD provide the ability to manage text-based externally-sourced documents and reports.</p>
</div></span>
                

                
            </td>
        </tr>
        
    </table>
</div>
  </text>
  <url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-S.4.1.1"/>
  <version value="0.1.0"/>
  <name
        value="S_4_1_1_Capture_Genomic_Proteomic_Data_and_Documentation_from_External_Clinical_Sources"/>
  <title
         value="S.4.1.1 Capture Genomic/Proteomic Data and Documentation from External Clinical Sources (Function)"/>
  <status value="active"/>
  <date value="2024-01-31T14:45:34+00:00"/>
  <publisher value="EHR WG"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/ehr"/>
    </telecom>
  </contact>
  <description
               value="Mechanisms for incorporating external genomic/proteomic data and documentation (including identification of source) such as image documents, reports and other clinically relevant electronic data are available."/>
  <statement>
    <key value="PHRSFMR2-S.4.1.1-01"/>
    <label value="S.4.1.1#01"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to capture relevant family genomic history."/>
    <satisfiedBy value="https://www.hl7.org/fhir/molecularsequence.html"/>
  </statement>
  <statement>
    <key value="PHRSFMR2-S.4.1.1-02"/>
    <label value="S.4.1.1#02"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system MAY capture and maintain genomic/proteomic information through interaction with other systems, applications, and modules."/>
  </statement>
  <statement>
    <key value="PHRSFMR2-S.4.1.1-03"/>
    <label value="S.4.1.1#03"/>
    <conformance value="SHALL"/>
    <conditionality value="true"/>
    <requirement
                 value="IF laboratory results are received through an electronic interface, THEN the system SHALL render the data elements upon request."/>
  </statement>
  <statement>
    <key value="PHRSFMR2-S.4.1.1-04"/>
    <label value="S.4.1.1#04"/>
    <conformance value="SHALL"/>
    <conditionality value="true"/>
    <requirement
                 value="IF laboratory results are received through an electronic interface, THEN the system SHALL capture and maintain the data elements in the PHR Account Holder record."/>
  </statement>
  <statement>
    <key value="PHRSFMR2-S.4.1.1-05"/>
    <label value="S.4.1.1#05"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system MAY provide the ability to store imaged documents."/>
  </statement>
  <statement>
    <key value="PHRSFMR2-S.4.1.1-06"/>
    <label value="S.4.1.1#06"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to manage text-based externally-sourced documents and reports."/>
  </statement>
</Requirements>