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.3 Manage Provider-Initiated Care Plans (Function) - JSON Representation

Active as of 2024-01-31

Raw json | Download

    {
      "resourceType" : "Requirements",
      "id" : "PHRSFMR2-PH.3.3",
      "meta" : {
        "profile" : [
          🔗 "http://hl7.org/ehrs/StructureDefinition/FMFunction"
        ]
      },
      "text" : {
        "status" : "extensions",
        "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n    <table id=\"statements\" class=\"grid dict\">\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.3.3#01</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>SHOULD</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system SHOULD provide the ability to capture provider-generated PHR Account Holder -specific care plan regimens and/or treatments (e.g., information regarding orders, therapies, wound care, or habit changes).</p>\n</div></span>\n                \n\n                \n                Satisfied by:<ol>\n                \n                    <li><a href=\"https://www.hl7.org/fhir/careplan.html\">https://www.hl7.org/fhir/careplan.html</a></li>\n                \n                </ol>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.3.3#02</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>SHOULD</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system SHOULD provide the ability to track updates to the PHR Account Holder's care plans, regimens, and treatments (e.g., including information regarding authors, creation date, version history, references, and sources as available).</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.3.3#03</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>SHOULD</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system SHOULD provide the ability to present care and treatment plans captured from providers in their original format.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.3.3#04</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>SHOULD</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system SHOULD provide the ability to present a list of care plans and instructions indexed by provider, problem, and date.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.3.3#05</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>SHOULD</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system SHOULD provide the ability to manage care and treatment plans captured from provider(s) with tasks, alerts, reminders, and calendar entries.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.3.3#06</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>MAY</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system MAY capture compliance with provider-generated care plans and render notifications or alerts to the PHR Account Holder when the PHR Account Holder is out of compliance.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.3.3#07</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>MAY</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system MAY transmit out-of-compliance notifications or alerts to the originating provider and/or to a person who is acting in the role of a provider (e.g., a registered dietitian/nutritionist who creates and signs a diet-order).</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.3.3#08</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>SHOULD</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system SHOULD provide the ability to maintain decision support recommendations for care plans and treatment protocols that are sensitive to the context of PHR Account Holder data (e.g., peak flow, weight, blood pressure, food preferences).</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.3.3#09</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>MAY</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system MAY provide the ability to analyze potentially conflicting decision support recommendations for care plans and treatment protocols (including self-generated care-plans) and present those potentially conflicting decision support recommendations for care plans and treatment protocols (e.g., if a provider-generated diabetic foot treatment plan recommends 20 days between formal examinations and an automated PHR system decision support module recommends 90 days between formal examinations, then the provider should be informed of the conflicting recommendations).</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.3.3#10</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>MAY</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>IF the systemhas determined that potentially conflicting decision support recommendations for care plans and treatment protocols, THEN the system MAY provide the ability to transmit a request to a provider to harmonize those potentially conflicting decision support recommendations for care plans and treatment protocols.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.3.3#11</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>MAY</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system MAY provide the ability to capture order details for the PHR Account Holder in a manner that promotes understanding and compliance with an order.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.3.3#12</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>SHOULD</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system SHOULD provide the ability to capture externally-sourced (care plan -related) instructions or references to documents containing those instructions.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.3.3#13</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>SHOULD</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system SHOULD provide the ability to capture details on further care such as follow up, return visits, and appropriate timing of further care.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.3.3#14</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>MAY</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system MAY provide the ability to manage multiple care plans, treatment plans, or health activities (including those care plans, treatment plans, or health activities that are self-generated) according to user preferences and/or consents, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n    </table>\n</div>"
      },
      "url" : "http://hl7.org/ehrs/Requirements/PHRSFMR2-PH.3.3",
      "version" : "0.1.0",
      "name" : "PH_3_3_Manage_Provider_Initiated_Care_Plans",
      "title" : "PH.3.3 Manage Provider-Initiated Care Plans (Function)",
      "status" : "active",
      "date" : "2024-01-31T14:45:34+00:00",
      "publisher" : "EHR WG",
      "contact" : [
        {
          "telecom" : [
            {
              "system" : "url",
              "value" : "http://www.hl7.org/Special/committees/ehr"
            }
          ]
        }
      ],
      "description" : "Care plans may encompass a wide variety of styles, goals, and complexities, grouped into three categories: health maintenance, health restoration, and chronic disease management. Examples of the three categories of care plans include:\r\n\r\n- Health Maintenance: The base care plan is a lifelong wellness plan that may specify age- and/or gender- specific health surveillance, an immunization schedule, and a diet and exercise program. It can be customized to accommodate specific health risks (such as hazardous exposures or genomic indicators).\r\n\r\n- Health Restoration: Natural conditions (such as pregnancy) or acute illnesses may occur that require the management of specific diagnostic and/or therapeutic measures.\r\n\r\n- Chronic Disease Management: Chronic disease care plans cover long term conditions (e.g., Type 1 diabetes).\r\n\r\nMultiple care plans, treatment plans, or health activities (including those that are self-generated) need to be managed/reconciled in order to enable the prioritization/reconciliation of care plans: based on relative health outcomes and risk, based on a timewise ordering of care plans, based on a condition-related ranking of care plans, based on changes to insurance coverage of health care plan services, or based on potential contraindications that arise from conflicting care plans goals or methods.\r\n\r\nThere might also be certain restrictions against sharing health information in the case of infants or teenagers who might require special health information exchange protections.\r\n\r\nExample(s): Capture and maintain a diabetic treatment plan that contains the pertinent staging details and multimodality plans in one place that can better coordinate the care by the diabetes-support team including the PHR Account Holder's Primary Care Provider.",
      "statement" : [
        {
          "key" : "PHRSFMR2-PH.3.3-01",
          "label" : "PH.3.3#01",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability to capture provider-generated PHR Account Holder -specific care plan regimens and/or treatments (e.g., information regarding orders, therapies, wound care, or habit changes).",
          "satisfiedBy" : [
            "https://www.hl7.org/fhir/careplan.html"
          ]
        },
        {
          "key" : "PHRSFMR2-PH.3.3-02",
          "label" : "PH.3.3#02",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability to track updates to the PHR Account Holder's care plans, regimens, and treatments (e.g., including information regarding authors, creation date, version history, references, and sources as available)."
        },
        {
          "key" : "PHRSFMR2-PH.3.3-03",
          "label" : "PH.3.3#03",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability to present care and treatment plans captured from providers in their original format."
        },
        {
          "key" : "PHRSFMR2-PH.3.3-04",
          "label" : "PH.3.3#04",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability to present a list of care plans and instructions indexed by provider, problem, and date."
        },
        {
          "key" : "PHRSFMR2-PH.3.3-05",
          "label" : "PH.3.3#05",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability to manage care and treatment plans captured from provider(s) with tasks, alerts, reminders, and calendar entries."
        },
        {
          "key" : "PHRSFMR2-PH.3.3-06",
          "label" : "PH.3.3#06",
          "conformance" : [
            "MAY"
          ],
          "conditionality" : false,
          "requirement" : "The system MAY capture compliance with provider-generated care plans and render notifications or alerts to the PHR Account Holder when the PHR Account Holder is out of compliance."
        },
        {
          "key" : "PHRSFMR2-PH.3.3-07",
          "label" : "PH.3.3#07",
          "conformance" : [
            "MAY"
          ],
          "conditionality" : false,
          "requirement" : "The system MAY transmit out-of-compliance notifications or alerts to the originating provider and/or to a person who is acting in the role of a provider (e.g., a registered dietitian/nutritionist who creates and signs a diet-order)."
        },
        {
          "key" : "PHRSFMR2-PH.3.3-08",
          "label" : "PH.3.3#08",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability to maintain decision support recommendations for care plans and treatment protocols that are sensitive to the context of PHR Account Holder data (e.g., peak flow, weight, blood pressure, food preferences)."
        },
        {
          "key" : "PHRSFMR2-PH.3.3-09",
          "label" : "PH.3.3#09",
          "conformance" : [
            "MAY"
          ],
          "conditionality" : false,
          "requirement" : "The system MAY provide the ability to analyze potentially conflicting decision support recommendations for care plans and treatment protocols (including self-generated care-plans) and present those potentially conflicting decision support recommendations for care plans and treatment protocols (e.g., if a provider-generated diabetic foot treatment plan recommends 20 days between formal examinations and an automated PHR system decision support module recommends 90 days between formal examinations, then the provider should be informed of the conflicting recommendations)."
        },
        {
          "key" : "PHRSFMR2-PH.3.3-10",
          "label" : "PH.3.3#10",
          "conformance" : [
            "MAY"
          ],
          "conditionality" : true,
          "requirement" : "IF the systemhas determined that potentially conflicting decision support recommendations for care plans and treatment protocols, THEN the system MAY provide the ability to transmit a request to a provider to harmonize those potentially conflicting decision support recommendations for care plans and treatment protocols."
        },
        {
          "key" : "PHRSFMR2-PH.3.3-11",
          "label" : "PH.3.3#11",
          "conformance" : [
            "MAY"
          ],
          "conditionality" : false,
          "requirement" : "The system MAY provide the ability to capture order details for the PHR Account Holder in a manner that promotes understanding and compliance with an order."
        },
        {
          "key" : "PHRSFMR2-PH.3.3-12",
          "label" : "PH.3.3#12",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability to capture externally-sourced (care plan -related) instructions or references to documents containing those instructions."
        },
        {
          "key" : "PHRSFMR2-PH.3.3-13",
          "label" : "PH.3.3#13",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability to capture details on further care such as follow up, return visits, and appropriate timing of further care."
        },
        {
          "key" : "PHRSFMR2-PH.3.3-14",
          "label" : "PH.3.3#14",
          "conformance" : [
            "MAY"
          ],
          "conditionality" : false,
          "requirement" : "The system MAY provide the ability to manage multiple care plans, treatment plans, or health activities (including those care plans, treatment plans, or health activities that are self-generated) according to user preferences and/or consents, organizational policy, and/or jurisdictional law."
        }
      ]
    }