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.2 Manage Account Holder Implemented Care Plans (Function) - TTL Representation

Active as of 2024-01-31

Raw ttl | Download

    @prefix fhir: <http://hl7.org/fhir/> .
    @prefix owl: <http://www.w3.org/2002/07/owl#> .
    @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
    @prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

    # - resource -------------------------------------------------------------------

     a fhir:Requirements ;
      fhir:nodeRole fhir:treeRoot ;
      fhir:id [ fhir:v "PHRSFMR2-PH.3.2"] ; #
      fhir:meta [
        ( fhir:profile [
    fhir:v "http://hl7.org/ehrs/StructureDefinition/FMFunction"^^xsd:anyURI ;
    fhir:link <http://hl7.org/ehrs/StructureDefinition/FMFunction>     ] )
      ] ; #
      fhir:text [
    fhir:status [ fhir:v "extensions" ] ;
    fhir: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.2#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 manage the PHR Account Holder's self-generated care plans.  Note: self-generated care plans can be constructed based on external recommendations from sources such as an established relationship with a care provider, an educational tool, or another informational resource.</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.2#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 maintain structured templates for the PHR Account Holder or the PHR Account Holder Proxy to design specific wellness care plans.</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.2#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 manage self-developed care plans 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.2#04</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 compliance with self-generated care plans and render notifications or alerts 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.2#05</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, maintain, and render information regarding the effectiveness of self-generated care plans.</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.2#06</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 integrate all care plans into one set of tasks, 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.2#07</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 conform to function PH.6.7 (Manage Patient-Specific Care and Treatment Plans) in order to enable the PHR Account Holder to manage care plans that support treatments (e.g., treatments that need to be adjusted based on geographic location such as warm versus cold climate), physical body conditions (e.g., weight increases or decreases), long-term illnesses (e.g., diabetes), or health and wellness goals. Furthermore, provider-generated care plans might need to be adjusted when the PHR Account Holder alters a self-generated care plan. Finally, the providers who generated care plans might need to be notified when a certain care plan has been added, changed, or deleted.</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.2#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 conform to function PH.6.8 (Patient-Specific Care, Instructions, Treatment Plans, Guidelines and Protocols) in order to enable the PHR Account Holder to manage care plans that support treatments (e.g., treatments that need to be adjusted based on geographic location such as warm versus cold climate), physical body conditions (e.g., weight increases or decreases), long-term illnesses (e.g., diabetes), or health and wellness goals. Furthermore, provider-generated care plans might need to be adjusted when the PHR Account Holder alters a self-generated care plan. Finally, the providers who generated care plans might need to be notified when a certain care plan has been added, changed, or deleted.</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.2#09</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 conform to PH.3.3 (Manage Provider Implemented Care Plans) to accommodate the inclusion of the consumer-generated care plan with provider-generated care plans.</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.2#10</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 conform to PH.6.3 (Communications Between Provider and PHR Account Holder and/or PHR Account Holder Proxy) in order to promote the effective coordination of care plan elements and to communicate care plan changes to selected providers.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n    </table>\n</div>"
      ] ; #
      fhir:url [ fhir:v "http://hl7.org/ehrs/Requirements/PHRSFMR2-PH.3.2"^^xsd:anyURI] ; #
      fhir:version [ fhir:v "0.1.0"] ; #
      fhir:name [ fhir:v "PH_3_2_Manage_Account_Holder_Implemented_Care_Plans"] ; #
      fhir:title [ fhir:v "PH.3.2 Manage Account Holder Implemented Care Plans (Function)"] ; #
      fhir:status [ fhir:v "active"] ; #
      fhir:date [ fhir:v "2024-01-31T14:45:34+00:00"^^xsd:dateTime] ; #
      fhir:publisher [ fhir:v "EHR WG"] ; #
      fhir:contact ( [
        ( fhir:telecom [
    fhir:system [ fhir:v "url" ] ;
    fhir:value [ fhir:v "http://www.hl7.org/Special/committees/ehr" ]     ] )
      ] ) ; #
      fhir:description [ fhir:v "The PHR Account Holder may develop care plans related to health and wellness (such as training programs for sports) as well as to ameliorate a health condition. Self-developed care plans can be integrated into a comprehensive health and wellness plan.\r\n\r\nExample(s): Develop and implement an exercise program for optimizing cardiac fitness based on age, gender, and other health risks."] ; #
      fhir:statement ( [
    fhir:key [ fhir:v "PHRSFMR2-PH.3.2-01" ] ;
    fhir:label [ fhir:v "PH.3.2#01" ] ;
        ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system SHOULD provide the ability to manage the PHR Account Holder's self-generated care plans.  Note: self-generated care plans can be constructed based on external recommendations from sources such as an established relationship with a care provider, an educational tool, or another informational resource." ] ;
        ( fhir:satisfiedBy [ fhir:v "https://www.hl7.org/fhir/careplan.html"^^xsd:anyURI ] )
      ] [
    fhir:key [ fhir:v "PHRSFMR2-PH.3.2-02" ] ;
    fhir:label [ fhir:v "PH.3.2#02" ] ;
        ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system SHOULD provide the ability to maintain structured templates for the PHR Account Holder or the PHR Account Holder Proxy to design specific wellness care plans." ]
      ] [
    fhir:key [ fhir:v "PHRSFMR2-PH.3.2-03" ] ;
    fhir:label [ fhir:v "PH.3.2#03" ] ;
        ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system SHOULD provide the ability to manage self-developed care plans with tasks, alerts, reminders, and calendar entries." ]
      ] [
    fhir:key [ fhir:v "PHRSFMR2-PH.3.2-04" ] ;
    fhir:label [ fhir:v "PH.3.2#04" ] ;
        ( fhir:conformance [ fhir:v "MAY" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system MAY provide the ability to capture compliance with self-generated care plans and render notifications or alerts when the PHR Account Holder is out of compliance." ]
      ] [
    fhir:key [ fhir:v "PHRSFMR2-PH.3.2-05" ] ;
    fhir:label [ fhir:v "PH.3.2#05" ] ;
        ( fhir:conformance [ fhir:v "MAY" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system MAY provide the ability to capture, maintain, and render information regarding the effectiveness of self-generated care plans." ]
      ] [
    fhir:key [ fhir:v "PHRSFMR2-PH.3.2-06" ] ;
    fhir:label [ fhir:v "PH.3.2#06" ] ;
        ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system SHOULD provide the ability to integrate all care plans into one set of tasks, reminders, and calendar entries." ]
      ] [
    fhir:key [ fhir:v "PHRSFMR2-PH.3.2-07" ] ;
    fhir:label [ fhir:v "PH.3.2#07" ] ;
        ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system SHOULD conform to function PH.6.7 (Manage Patient-Specific Care and Treatment Plans) in order to enable the PHR Account Holder to manage care plans that support treatments (e.g., treatments that need to be adjusted based on geographic location such as warm versus cold climate), physical body conditions (e.g., weight increases or decreases), long-term illnesses (e.g., diabetes), or health and wellness goals. Furthermore, provider-generated care plans might need to be adjusted when the PHR Account Holder alters a self-generated care plan. Finally, the providers who generated care plans might need to be notified when a certain care plan has been added, changed, or deleted." ]
      ] [
    fhir:key [ fhir:v "PHRSFMR2-PH.3.2-08" ] ;
    fhir:label [ fhir:v "PH.3.2#08" ] ;
        ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system SHOULD conform to function PH.6.8 (Patient-Specific Care, Instructions, Treatment Plans, Guidelines and Protocols) in order to enable the PHR Account Holder to manage care plans that support treatments (e.g., treatments that need to be adjusted based on geographic location such as warm versus cold climate), physical body conditions (e.g., weight increases or decreases), long-term illnesses (e.g., diabetes), or health and wellness goals. Furthermore, provider-generated care plans might need to be adjusted when the PHR Account Holder alters a self-generated care plan. Finally, the providers who generated care plans might need to be notified when a certain care plan has been added, changed, or deleted." ]
      ] [
    fhir:key [ fhir:v "PHRSFMR2-PH.3.2-09" ] ;
    fhir:label [ fhir:v "PH.3.2#09" ] ;
        ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system SHOULD conform to PH.3.3 (Manage Provider Implemented Care Plans) to accommodate the inclusion of the consumer-generated care plan with provider-generated care plans." ]
      ] [
    fhir:key [ fhir:v "PHRSFMR2-PH.3.2-10" ] ;
    fhir:label [ fhir:v "PH.3.2#10" ] ;
        ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system SHOULD conform to PH.6.3 (Communications Between Provider and PHR Account Holder and/or PHR Account Holder Proxy) in order to promote the effective coordination of care plan elements and to communicate care plan changes to selected providers." ]
      ] ) . #