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

## : PH.3.5.1 Manage Health Calendar (Function) - XML Representation

Active as of 2024-01-31

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-PH.3.5.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>PH.3.5.1#01</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system MAY maintain a health calendar function for recording and displaying scheduled health appointments or events.</p>
    </div></span>

                    Satisfied by:<ol>

                        <li>https://www.hl7.org/fhir/argonaut scheduling.html</li>

                    </ol>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>PH.3.5.1#02</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>IF a health calendar function is provided, THEN the system SHOULD present future appointments and other timed events on the health calendar.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>PH.3.5.1#03</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>IF a health calendar function is provided, THEN the system SHOULD provide the ability to annotate directly onto the health calendar as date stamped text entries.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>PH.3.5.1#04</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>IF a health calendar function is provided, THEN the system MAY present care plans (e.g., lifelong immunization schedules or cancer surveillance tests) as health calendar entries.</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-PH.3.5.1"/>
      <version value="0.1.0"/>
      <name value="PH_3_5_1_Manage_Health_Calendar"/>
      <title value="PH.3.5.1 Manage Health Calendar (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="A health calendar provides a method to view time related healthcare activity both in the future as scheduled events and in the past as historic events. It is a handy and well understood format. The calendar can also be used as a data input device, mimicking the paper calendar where clinical observations (such as gallbladder attacks or menstrual periods) can be written directly onto a calendar and captured as a timed note. This idea was put forward from usability studies with lay people how they would like to interact with their PHR.

    Example(s): IF a health calendar function is provided, THEN future appointments and other timed events SHOULD be displayed on the health calendar."/>
      <statement>
        <key value="PHRSFMR2-PH.3.5.1-01"/>
        <label value="PH.3.5.1#01"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY maintain a health calendar function for recording and displaying scheduled health appointments or events."/>
        <satisfiedBy value="https://www.hl7.org/fhir/argonaut scheduling.html"/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.3.5.1-02"/>
        <label value="PH.3.5.1#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="true"/>
        <requirement
                     value="IF a health calendar function is provided, THEN the system SHOULD present future appointments and other timed events on the health calendar."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.3.5.1-03"/>
        <label value="PH.3.5.1#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="true"/>
        <requirement
                     value="IF a health calendar function is provided, THEN the system SHOULD provide the ability to annotate directly onto the health calendar as date stamped text entries."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.3.5.1-04"/>
        <label value="PH.3.5.1#04"/>
        <conformance value="MAY"/>
        <conditionality value="true"/>
        <requirement
                     value="IF a health calendar function is provided, THEN the system MAY present care plans (e.g., lifelong immunization schedules or cancer surveillance tests) as health calendar entries."/>
      </statement>
    </Requirements>