HL7 Personal Health Record System Functional Model, Release 2
2.0.1-ballot - Normative Ballot

HL7 Personal Health Record System Functional Model, Release 2, published by EHR WG. This guide is not an authorized publication; it is the continuous build for version 2.0.1-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/phrsfm-ig/ and changes regularly. See the Directory of published versions

: PH.6.8 Manage Patient-Specific Care and Treatment Plans (Function) - TTL Representation

Page standards status: Informative

Raw ttl | Download


@prefix fhir: <http://hl7.org/fhir/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@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.6.8"] ; # 
  fhir:meta [
    ( fhir:profile [
fhir:v "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"^^xsd:anyURI ;
fhir:link <http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction>     ] )
  ] ; # 
  fhir:text [
fhir:status [ fhir:v "extensions" ] ;
fhir:div "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n    <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>The system should facilitate the capture and implementation of the care plan in the PHR-S.</p>\n</div></span>\n\n    \n    <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Once a care plan is developed it should be incorporated into the PHR-S. The care plan may be limited in scope or comprehensive involving multiple providers, encounters, institutions, and years of time.</p>\n<p>Example(s): A comprehensive breast cancer treatment plan may include multiple diagnostic imaging staging studies, surgical procedures, a chemotherapy protocol, details of the radiation therapy plan, plastic surgery reconstruction and long-term post therapy surveillance plan to be posted in the PHR-S and referenced by the cancer care team.</p>\n</div></span>\n    \n\n    \n    \n    \n\n    \n    <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n    \n    <table id=\"statements\" class=\"grid dict\">\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.6.8#01</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                \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 PHR Account Holder-specific plans of care and treatment (e.g., information about orders or therapies).</p>\n</div></span>\n                \n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.6.8#02</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                \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 updates to the PHR Account Holder's plan of care and treatment including authors, creation date, version history, references and sources as available.</p>\n</div></span>\n                \n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.6.8#03</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                \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 adequate order details to promote the PHR Account Holder's understanding and compliance with the order.</p>\n</div></span>\n                \n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.6.8#04</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                \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 plan recommendations in terms of the PHR Account Holder's health-related data (e.g., peak flow, weight, blood pressure, or dietary preferences) at the option or control of the PHR Account Holder or PHR Account Holder Proxy.</p>\n</div></span>\n                \n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.6.8#05</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <i>dependent</i>\n                \n                \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 transmit care plans, care instructions, treatment plans, guidelines, and protocols (or portions of those items) to selected stakeholders (e.g., sharing a new fitness plan with members of the care team, or sharing a care plan with a new member of the care team) according to user preference, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n                \n                \n            </td>\n        </tr>\n        \n    </table>\n</div>"^^rdf:XMLLiteral
  ] ; # 
  fhir:extension ( [
fhir:url [ fhir:v "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"^^xsd:anyURI ] ;
fhir:value [
a fhir:code ;
fhir:v "ehr"     ]
  ] ) ; # 
  fhir:url [ fhir:v "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.6.8"^^xsd:anyURI] ; # 
  fhir:version [ fhir:v "2.0.1-ballot"] ; # 
  fhir:name [ fhir:v "PH_6_8_Manage_Patient_Specific_Care_and_Treatment_Plans"] ; # 
  fhir:title [ fhir:v "PH.6.8 Manage Patient-Specific Care and Treatment Plans (Function)"] ; # 
  fhir:status [ fhir:v "active"] ; # 
  fhir:date [ fhir:v "2025-08-29T14:03:44+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 system should facilitate the capture and implementation of the care plan in the PHR-S."] ; # 
  fhir:purpose [ fhir:v "Once a care plan is developed it should be incorporated into the PHR-S. The care plan may be limited in scope or comprehensive involving multiple providers, encounters, institutions, and years of time.\r\n\r\nExample(s): A comprehensive breast cancer treatment plan may include multiple diagnostic imaging staging studies, surgical procedures, a chemotherapy protocol, details of the radiation therapy plan, plastic surgery reconstruction and long-term post therapy surveillance plan to be posted in the PHR-S and referenced by the cancer care team."] ; # 
  fhir:statement ( [
    ( fhir:extension [
fhir:url [ fhir:v "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent"^^xsd:anyURI ] ;
fhir:value [
a fhir:boolean ;
fhir:v false       ]     ] ) ;
fhir:key [ fhir:v "PHRSFMR2-PH.6.8-01" ] ;
fhir:label [ fhir:v "PH.6.8#01" ] ;
    ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
fhir:conditionality [ fhir:v false ] ;
fhir:requirement [ fhir:v "The system SHOULD provide the ability to capture PHR Account Holder-specific plans of care and treatment (e.g., information about orders or therapies)." ]
  ] [
    ( fhir:extension [
fhir:url [ fhir:v "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent"^^xsd:anyURI ] ;
fhir:value [
a fhir:boolean ;
fhir:v false       ]     ] ) ;
fhir:key [ fhir:v "PHRSFMR2-PH.6.8-02" ] ;
fhir:label [ fhir:v "PH.6.8#02" ] ;
    ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
fhir:conditionality [ fhir:v false ] ;
fhir:requirement [ fhir:v "The system SHOULD provide the ability to capture updates to the PHR Account Holder's plan of care and treatment including authors, creation date, version history, references and sources as available." ]
  ] [
    ( fhir:extension [
fhir:url [ fhir:v "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent"^^xsd:anyURI ] ;
fhir:value [
a fhir:boolean ;
fhir:v false       ]     ] ) ;
fhir:key [ fhir:v "PHRSFMR2-PH.6.8-03" ] ;
fhir:label [ fhir:v "PH.6.8#03" ] ;
    ( fhir:conformance [ fhir:v "MAY" ] ) ;
fhir:conditionality [ fhir:v false ] ;
fhir:requirement [ fhir:v "The system MAY provide the ability to capture adequate order details to promote the PHR Account Holder's understanding and compliance with the order." ]
  ] [
    ( fhir:extension [
fhir:url [ fhir:v "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent"^^xsd:anyURI ] ;
fhir:value [
a fhir:boolean ;
fhir:v false       ]     ] ) ;
fhir:key [ fhir:v "PHRSFMR2-PH.6.8-04" ] ;
fhir:label [ fhir:v "PH.6.8#04" ] ;
    ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
fhir:conditionality [ fhir:v false ] ;
fhir:requirement [ fhir:v "The system SHOULD provide the ability to present care and treatment plan recommendations in terms of the PHR Account Holder's health-related data (e.g., peak flow, weight, blood pressure, or dietary preferences) at the option or control of the PHR Account Holder or PHR Account Holder Proxy." ]
  ] [
    ( fhir:extension [
fhir:url [ fhir:v "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent"^^xsd:anyURI ] ;
fhir:value [
a fhir:boolean ;
fhir:v true       ]     ] ) ;
fhir:key [ fhir:v "PHRSFMR2-PH.6.8-05" ] ;
fhir:label [ fhir:v "PH.6.8#05" ] ;
    ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
fhir:conditionality [ fhir:v false ] ;
fhir:requirement [ fhir:v "The system SHOULD provide the ability to transmit care plans, care instructions, treatment plans, guidelines, and protocols (or portions of those items) to selected stakeholders (e.g., sharing a new fitness plan with members of the care team, or sharing a care plan with a new member of the care team) according to user preference, organizational policy, and/or jurisdictional law." ]
  ] ) . #