{"id":2107,"date":"2021-08-13T10:12:26","date_gmt":"2021-08-13T10:12:26","guid":{"rendered":"https:\/\/support.mrdm.com\/?post_type=batch&#038;p=2107"},"modified":"2021-09-21T09:27:56","modified_gmt":"2021-09-21T09:27:56","slug":"set-operational-agreement-define-upload-scenario","status":"publish","type":"batch","link":"https:\/\/support.mrdm.com\/en\/batch\/manual\/batch-process\/set-operational-agreement-define-upload-scenario\/","title":{"rendered":"Phase 2: Set operational agreement"},"content":{"rendered":"\n<p>To&nbsp;process&nbsp;the uploaded data, MRDM&nbsp;will&nbsp;configure&nbsp;your&nbsp;organization&#8217;s&nbsp;settings,&nbsp;such as the upload scenario, the chosen file format and quality control. The data will be processed with an \u201cupdate without NULL values scenario\u201d (see \u201cupdate scenario\u201d below). This enables&nbsp;you&nbsp;to upload new dataset-records as well as existing dataset-records (changed or unchanged) without the risk of creating duplicates.&nbsp;<\/p>\n\n\n\n<p><strong>Update scenario<\/strong>&nbsp;<\/p>\n\n\n\n<p>An \u2018<strong>update<\/strong>\u2019 allows you to upload new and existing dataset-records (changed or unchanged).&nbsp;&nbsp;<\/p>\n\n\n\n<p>General principles of the \u2018<strong>update<\/strong>\u2019 scenario:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Existing dataset-records in the registry will be updated&nbsp;<\/li><\/ul>\n\n\n\n<ul class=\"wp-block-list\"><li>New records will be added to the database of the&nbsp;Standard&nbsp;Set&nbsp;<\/li><li>The &gt;dataset name&lt;-id and id variables&nbsp;must be included in each upload&nbsp;as&nbsp;these&nbsp;id-variables contain the code that refers to your organization&nbsp;<\/li><li>The latest&nbsp;delivered value (via batch or manual entry) on a variable is considered the truth and will be the value in the database&nbsp;<\/li><li>Records that are already in the database&nbsp;cannot&nbsp;be overwritten with a NULL value (empty value). If you want to empty or delete a record you can delete this manually in the manual entry application.&nbsp;<\/li><\/ul>\n\n\n\n<p>Processing the batch data with an update means that it is also possible to simultaneously enter data manually. This&nbsp;can&nbsp;be useful&nbsp;if&nbsp;part of the data&nbsp;cannot&nbsp;be extracted from the&nbsp;EMR.&nbsp;&nbsp;&nbsp;&nbsp;<\/p>\n\n\n\n<p><em>Note: do you manually change the data you have delivered in batch? This needs to be changed in the source system as well (e.g.&nbsp;EMR). This will prevent manual changes to be overwritten in a new batch upload with the (wrong\/unchanged) value in the source system.<\/em>&nbsp;<\/p>\n","protected":false},"parent":2103,"menu_order":2,"template":"","class_list":["post-2107","batch","type-batch","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/support.mrdm.com\/en\/wp-json\/wp\/v2\/batch\/2107","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/support.mrdm.com\/en\/wp-json\/wp\/v2\/batch"}],"about":[{"href":"https:\/\/support.mrdm.com\/en\/wp-json\/wp\/v2\/types\/batch"}],"version-history":[{"count":5,"href":"https:\/\/support.mrdm.com\/en\/wp-json\/wp\/v2\/batch\/2107\/revisions"}],"predecessor-version":[{"id":4091,"href":"https:\/\/support.mrdm.com\/en\/wp-json\/wp\/v2\/batch\/2107\/revisions\/4091"}],"up":[{"embeddable":true,"href":"https:\/\/support.mrdm.com\/en\/wp-json\/wp\/v2\/batch\/2103"}],"wp:attachment":[{"href":"https:\/\/support.mrdm.com\/en\/wp-json\/wp\/v2\/media?parent=2107"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}