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

: TI.1.5 Non-Repudiation (Function) - JSON Representation

Active as of 2024-01-31

Raw json | Download


{
  "resourceType" : "Requirements",
  "id" : "PHRSFMR2-TI.1.5",
  "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>TI.1.5#01</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 capture the identity of the entity taking the action according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>TI.1.5#02</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 capture time stamp of the initial entry, modification and exchange of data according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>TI.1.5#03</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 function [[TI.2]] (Audit) to prevent repudiation of data origination, transmission and receipt according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>TI.1.5#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 conform to function [[RI.1.1.4]] (Attest Record Entry Content) to ensure integrity of data and data exchange and thus prevent repudiation of data origination, transmission or receipt according to scope of practice, 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-TI.1.5",
  "version" : "0.1.0",
  "name" : "TI_1_5_Non_Repudiation",
  "title" : "TI.1.5 Non-Repudiation (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" : "A PHR-S allows data entry to a patient's electronic health record and it can be a sender or receiver of healthcare information. Non-repudiation is a way to guarantee that the source of the data/record cannot later deny that fact; and that the sender of a message cannot later deny having sent the message; and that the recipient cannot deny having received the message. Components of non-repudiation can include:\r\n- Digital signature, which serves as a unique identifier for an individual (much like a written signature);\r\n- Confirmation service, which utilizes a message transfer agent to create a digital receipt (providing confirmation that a message was sent, and/or received);\r\n- Timestamp, which proves that a document existed at a certain date and time;\r\n- The use of standardized timekeeping protocols (e.g., the Integrating the Healthcare Enterprise (IHE) Consistent Time Profile).",
  "statement" : [
    {
      "key" : "PHRSFMR2-TI.1.5-01",
      "label" : "TI.1.5#01",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL capture the identity of the entity taking the action according to scope of practice, organizational policy, and/or jurisdictional law."
    },
    {
      "key" : "PHRSFMR2-TI.1.5-02",
      "label" : "TI.1.5#02",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL capture time stamp of the initial entry, modification and exchange of data according to scope of practice, organizational policy, and/or jurisdictional law."
    },
    {
      "key" : "PHRSFMR2-TI.1.5-03",
      "label" : "TI.1.5#03",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL conform to function [[TI.2]] (Audit) to prevent repudiation of data origination, transmission and receipt according to scope of practice, organizational policy, and/or jurisdictional law."
    },
    {
      "key" : "PHRSFMR2-TI.1.5-04",
      "label" : "TI.1.5#04",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD conform to function [[RI.1.1.4]] (Attest Record Entry Content) to ensure integrity of data and data exchange and thus prevent repudiation of data origination, transmission or receipt according to scope of practice, organizational policy, and/or jurisdictional law."
    }
  ]
}