Publish Box goes here

• Narrative Content
• XML
• JSON
• TTL

: RI.1.1.19 Merge Record Lifecycle Event (Function) - JSON Representation

Active as of 2024-08-12

Raw json | Download

{
  "resourceType" : "Requirements",
  "id" : "EHRSFMR2.1-RI.1.1.19",
  "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>Merge Record Entries (2 or more instances)</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>Occurs when an agent causes the system to combine or join content from two or more record entries, resulting in a single logical record entry.</p>\n<p>Reference: ISO 21089-2018, Section 15.19.</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>RI.1.1.19#01</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 harmonize or integrate patient Record Entries by logically merging patient Record Entries according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n                \n                \n            </td>\n        </tr>\n        \n    </table>\n</div>"
  },
  "url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-RI.1.1.19",
  "version" : "0.16.0",
  "name" : "RI_1_1_19_Merge_Record_Lifecycle_Event",
  "title" : "RI.1.1.19 Merge Record Lifecycle Event (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" : "Merge Record Entries (2 or more instances)",
  "purpose" : "Occurs when an agent causes the system to combine or join content from two or more record entries, resulting in a single logical record entry. \n\nReference: ISO 21089-2018, Section 15.19.",
  "statement" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : true
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.19-01",
      "label" : "RI.1.1.19#01",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to harmonize or integrate patient Record Entries by logically merging patient Record Entries according to scope of practice, organizational policy, and/or jurisdictional law.",
      "derivedFrom" : "EHR-LM_R1 14.8"
    }
  ]
}