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.3.9 Manage Information Views (Function) - JSON Representation

Active as of 2024-01-31

Raw json | Download

    {
      "resourceType" : "Requirements",
      "id" : "PHRSFMR2-S.3.9",
      "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>S.3.9#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 for a PHR Account Holder to manage personal views of PHR information.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>S.3.9#02</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 render role-based views of PHR information.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>S.3.9#03</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 for a PHR Account Holder to determine content of role-based views.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>S.3.9#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 render purpose-of-use/intention-of-use-based views of PHR information.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>S.3.9#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 for a PHR Account Holder to determine content of purpose-of-use/intention-of-use-based views.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>S.3.9#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 provide the ability for the PHR Account Holder to manage multiple customized views for more rapid display of information by the PHR Account Holder.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>S.3.9#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 provide the ability to for a PHR Account Holder or Authorized PHR User to maintain individual custom views for future access.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n    </table>\n</div>"
      },
      "url" : "http://hl7.org/ehrs/Requirements/PHRSFMR2-S.3.9",
      "version" : "0.1.0",
      "name" : "S_3_9_Manage_Information_Views",
      "title" : "S.3.9 Manage Information Views (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" : "Views of information can be tailored for or by the PHR Account Holder (PHR Account Holder, caregiver or other authorized PHR account user) for their presentation preferences and to support personal or role-based workflows and purpose-of-use / intention-of-use requirements.\r\n\r\nExample(s): A PHR Account Holder may prefer to see summary information about medications, while a provider’s view may include detailed information about current dosage and the PHR Account Holder’s response to the medication over time.",
      "statement" : [
        {
          "key" : "PHRSFMR2-S.3.9-01",
          "label" : "S.3.9#01",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability for a PHR Account Holder to manage personal views of PHR information."
        },
        {
          "key" : "PHRSFMR2-S.3.9-02",
          "label" : "S.3.9#02",
          "conformance" : [
            "MAY"
          ],
          "conditionality" : false,
          "requirement" : "The system MAY provide the ability to render role-based views of PHR information."
        },
        {
          "key" : "PHRSFMR2-S.3.9-03",
          "label" : "S.3.9#03",
          "conformance" : [
            "MAY"
          ],
          "conditionality" : false,
          "requirement" : "The system MAY provide the ability for a PHR Account Holder to determine content of role-based views."
        },
        {
          "key" : "PHRSFMR2-S.3.9-04",
          "label" : "S.3.9#04",
          "conformance" : [
            "MAY"
          ],
          "conditionality" : false,
          "requirement" : "The system MAY provide the ability to render purpose-of-use/intention-of-use-based views of PHR information."
        },
        {
          "key" : "PHRSFMR2-S.3.9-05",
          "label" : "S.3.9#05",
          "conformance" : [
            "MAY"
          ],
          "conditionality" : false,
          "requirement" : "The system MAY provide the ability for a PHR Account Holder to determine content of purpose-of-use/intention-of-use-based views."
        },
        {
          "key" : "PHRSFMR2-S.3.9-06",
          "label" : "S.3.9#06",
          "conformance" : [
            "MAY"
          ],
          "conditionality" : false,
          "requirement" : "The system MAY provide the ability for the PHR Account Holder to manage multiple customized views for more rapid display of information by the PHR Account Holder."
        },
        {
          "key" : "PHRSFMR2-S.3.9-07",
          "label" : "S.3.9#07",
          "conformance" : [
            "MAY"
          ],
          "conditionality" : false,
          "requirement" : "The system MAY provide the ability to for a PHR Account Holder or Authorized PHR User to maintain individual custom views for future access."
        }
      ]
    }