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.2.4 Manage Ad Hoc Reporting (Function) - JSON Representation

Active as of 2024-01-31

Raw json | Download

    {
      "resourceType" : "Requirements",
      "id" : "PHRSFMR2-S.2.4",
      "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.2.4#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 the authorized PHR Account Holder to render ad hoc reports of the PHR.</p>\n</div></span>\n                \n\n                \n                Satisfied by:<ol>\n                \n                    <li><a href=\"https://www.hl7.org/fhir/measure.html\">https://www.hl7.org/fhir/measure.html</a></li>\n                \n                </ol>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>S.2.4#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 for the authorized PHR Account Holder to render customized reports of summarized information based on sort and filter controls for date or data range, problem, or other clinical data element or categories (e.g., medications or providers).</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>S.2.4#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 maintain ad hoc reports for future retrieval and use.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>S.2.4#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 maintain summarized information through customized reports based on prioritization of chronology, problem or other pertinent information of importance to the authorized 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.2.4#05</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>SHALL</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system SHALL manage data visibility for PHR Account Holder Proxies using confidentiality-related preferences that were previously established by the PHR Account Holder for all ad hoc reporting capabilities.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>S.2.4#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 to render consolidated reports across family members (e.g., children).</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>S.2.4#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 TI.1.1 (Entity Authorization).</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>S.2.4#08</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>SHALL</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system SHALL conform to TI.2 (Auditable Records).</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>S.2.4#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 (or an external application using data from the PHR-S) MAY provide the ability to capture and maintain parameters for ad hoc reports.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n    </table>\n</div>"
      },
      "url" : "http://hl7.org/ehrs/Requirements/PHRSFMR2-S.2.4",
      "version" : "0.1.0",
      "name" : "S_2_4_Manage_Ad_Hoc_Reporting",
      "title" : "S.2.4 Manage Ad Hoc Reporting (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" : "PHR Account Holders may request ad hoc, non-standard reports. The purpose is not for PHR interchange but rather for PHR Account Holder’s analysis of his/her health related financial and administrative data, and for sharing (if desired).",
      "statement" : [
        {
          "key" : "PHRSFMR2-S.2.4-01",
          "label" : "S.2.4#01",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability for the authorized PHR Account Holder to render ad hoc reports of the PHR.",
          "satisfiedBy" : [
            "https://www.hl7.org/fhir/measure.html"
          ]
        },
        {
          "key" : "PHRSFMR2-S.2.4-02",
          "label" : "S.2.4#02",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability for the authorized PHR Account Holder to render customized reports of summarized information based on sort and filter controls for date or data range, problem, or other clinical data element or categories (e.g., medications or providers)."
        },
        {
          "key" : "PHRSFMR2-S.2.4-03",
          "label" : "S.2.4#03",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability to maintain ad hoc reports for future retrieval and use."
        },
        {
          "key" : "PHRSFMR2-S.2.4-04",
          "label" : "S.2.4#04",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability to maintain summarized information through customized reports based on prioritization of chronology, problem or other pertinent information of importance to the authorized PHR Account Holder."
        },
        {
          "key" : "PHRSFMR2-S.2.4-05",
          "label" : "S.2.4#05",
          "conformance" : [
            "SHALL"
          ],
          "conditionality" : false,
          "requirement" : "The system SHALL manage data visibility for PHR Account Holder Proxies using confidentiality-related preferences that were previously established by the PHR Account Holder for all ad hoc reporting capabilities."
        },
        {
          "key" : "PHRSFMR2-S.2.4-06",
          "label" : "S.2.4#06",
          "conformance" : [
            "MAY"
          ],
          "conditionality" : false,
          "requirement" : "The system MAY provide the ability to render consolidated reports across family members (e.g., children)."
        },
        {
          "key" : "PHRSFMR2-S.2.4-07",
          "label" : "S.2.4#07",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD conform to TI.1.1 (Entity Authorization)."
        },
        {
          "key" : "PHRSFMR2-S.2.4-08",
          "label" : "S.2.4#08",
          "conformance" : [
            "SHALL"
          ],
          "conditionality" : false,
          "requirement" : "The system SHALL conform to TI.2 (Auditable Records)."
        },
        {
          "key" : "PHRSFMR2-S.2.4-09",
          "label" : "S.2.4#09",
          "conformance" : [
            "MAY"
          ],
          "conditionality" : false,
          "requirement" : "The system (or an external application using data from the PHR-S) MAY provide the ability to capture and maintain parameters for ad hoc reports."
        }
      ]
    }