EHRS-FM IG

ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.16.0 - CI Build

Publish Box goes here

: CP.1.9 Manage Adverse Events (Function) - JSON Representation

Active as of 2024-08-12

Raw json | Download


{
  "resourceType" : "Requirements",
  "id" : "EHRSFMR2.1-CP.1.9",
  "meta" : {
    "profile" : [
      🔗 "http://hl7.org/ehrs/StructureDefinition/FMFunction"
    ]
  },
  "text" : {
    "status" : "extensions",
    "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>Capture and maintain adverse events.</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>This function is focused on the capture and maintenance of adverse events that have occurred to the patient. The system should capture discrete information about the adverse event to enable the rendering Serious Adverse Event (SAE) reports according to organizational policy, and or jurisdictional law. Reporting may conform to the HL7 Individual Case Safety Reporting (ICSR).</p>\n</div></span>\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>CP.1.9#01</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                \n                \n                <span>SHALL</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system SHALL provide the ability to manage adverse events associated with a patient.</p>\n</div></span>\n                \n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>CP.1.9#02</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <i>dependent</i>\n                \n                \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 and maintain as discrete data an adverse event. For example:a) Patient identificationb) Event date/timec) Event descriptiond) Event severitye) Event category (e.g., medication error, fall)f) Care providers associated with the eventaccording to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n                \n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>CP.1.9#03</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <i>dependent</i>\n                \n                \n                \n                <span>SHALL</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system SHALL provide the ability to capture and render a Serious Adverse Event (SAE) report according to organizational policy, and/or jurisditional law.</p>\n</div></span>\n                \n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>CP.1.9#04</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 render a set of Serious Adverse Event (SAE) data as modeled by the current release of HL7 ICSR (Individual Case Safety Reporting).</p>\n</div></span>\n                \n                \n            </td>\n        </tr>\n        \n    </table>\n</div>"
  },
  "url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.1.9",
  "version" : "0.16.0",
  "name" : "CP_1_9_Manage_Adverse_Events",
  "title" : "CP.1.9 Manage Adverse Events (Function)",
  "status" : "active",
  "date" : "2024-08-12T10:56:01+00:00",
  "publisher" : "EHR WG",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/ehr"
        }
      ]
    }
  ],
  "description" : "Capture and maintain adverse events.",
  "purpose" : "This function is focused on the capture and maintenance of adverse events that have occurred to the patient. The system should capture discrete information about the adverse event to enable the rendering Serious Adverse Event (SAE) reports according to organizational policy, and or jurisdictional law. Reporting may conform to the HL7 Individual Case Safety Reporting (ICSR).",
  "statement" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-CP.1.9-01",
      "label" : "CP.1.9#01",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to manage adverse events associated with a patient.",
      "derivedFrom" : "EHR-S_FM_R1.1 DC.1.3.1#1"
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : true
        }
      ],
      "key" : "EHRSFMR2.1-CP.1.9-02",
      "label" : "CP.1.9#02",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL capture and maintain as discrete data an adverse event. For example:a) Patient identificationb) Event date/timec) Event descriptiond) Event severitye) Event category (e.g., medication error, fall)f) Care providers associated with the eventaccording to scope of practice, organizational policy, and/or jurisdictional law.",
      "derivedFrom" : "EHR-S_FM_R1.1 DC.1.3.1#2"
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : true
        }
      ],
      "key" : "EHRSFMR2.1-CP.1.9-03",
      "label" : "CP.1.9#03",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to capture and render a Serious Adverse Event (SAE) report according to organizational policy, and/or jurisditional law.",
      "derivedFrom" : "EHR-S_FM_R1.1 DC.1.3.1#2"
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-CP.1.9-04",
      "label" : "CP.1.9#04",
      "conformance" : [
        "MAY"
      ],
      "conditionality" : false,
      "requirement" : "The system MAY provide the ability to render a set of Serious Adverse Event (SAE) data as modeled by the current release of HL7 ICSR (Individual Case Safety Reporting).",
      "derivedFrom" : "EHR-S_FM_R1.1 DC.1.3.1#3"
    }
  ]
}