Towards Protecting the Injured Party from Errors... | F1000Research "use strict";function _typeof(t){return(_typeof="function"==typeof Symbol&&"symbol"==typeof Symbol.iterator?function(t){return typeof t}:function(t){return t&&"function"==typeof Symbol&&t.constructor===Symbol&&t!==Symbol.prototype?"symbol":typeof t})(t)}!function(){var t=function(){var t,e,o=[],n=window,r=n;for(;r;){try{if(r.frames.__tcfapiLocator){t=r;break}}catch(t){}if(r===n.top)break;r=r.parent}t||(!function t(){var e=n.document,o=!!n.frames.__tcfapiLocator;if(!o)if(e.body){var r=e.createElement("iframe");r.style.cssText="display:none",r.name="__tcfapiLocator",e.body.appendChild(r)}else setTimeout(t,5);return!o}(),n.__tcfapi=function(){for(var t=arguments.length,n=new Array(t),r=0;r 3&&2===parseInt(n[1],10)&&"boolean"==typeof n[3]&&(e=n[3],"function"==typeof n[2]&&n[2]("set",!0)):"ping"===n[0]?"function"==typeof n[2]&&n[2]({gdprApplies:e,cmpLoaded:!1,cmpStatus:"stub"}):o.push(n)},n.addEventListener("message",(function(t){var e="string"==typeof t.data,o={};if(e)try{o=JSON.parse(t.data)}catch(t){}else o=t.data;var n="object"===_typeof(o)&&null!==o?o.__tcfapiCall:null;n&&window.__tcfapi(n.command,n.version,(function(o,r){var a={__tcfapiReturn:{returnValue:o,success:r,callId:n.callId}};t&&t.source&&t.source.postMessage&&t.source.postMessage(e?JSON.stringify(a):a,"*")}),n.parameter)}),!1))};"undefined"!=typeof module?module.exports=t:t()}(); dataLayer = dataLayer || []; // Standard GTM initialization - Google Consent Mode handles consent automatically (function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= 'https://www.googletagmanager.com/gtm.js?id='+i+dl+ '>m_auth=hzk0Vc3qFsQYhCrIoHz68A>m_preview=env-1>m_cookies_win=x';f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-MWFK8L5J'); ;window.NREUM||(NREUM={});NREUM.init={distributed_tracing:{enabled:true},privacy:{cookies_enabled:true},ajax:{deny_list:["bam.nr-data.net"]}}; ;NREUM.loader_config={accountID:"438030",trustKey:"438030",agentID:"772317073",licenseKey:"97f8f67f26",applicationID:"772317073"} ;NREUM.info={beacon:"bam.nr-data.net",errorBeacon:"bam.nr-data.net",licenseKey:"97f8f67f26",applicationID:"772317073",sa:1} ;/*! For license information please see nr-loader-spa-1.236.0.min.js.LICENSE.txt */ (()=>{"use strict";var e,t,r={5763:(e,t,r)=>{r.d(t,{P_:()=>l,Mt:()=>g,C5:()=>s,DL:()=>v,OP:()=>T,lF:()=>D,Yu:()=>y,Dg:()=>h,CX:()=>c,GE:()=>b,sU:()=>_});var n=r(8632),i=r(9567);const o={beacon:n.ce.beacon,errorBeacon:n.ce.errorBeacon,licenseKey:void 0,applicationID:void 0,sa:void 0,queueTime:void 0,applicationTime:void 0,ttGuid:void 0,user:void 0,account:void 0,product:void 0,extra:void 0,jsAttributes:{},userAttributes:void 0,atts:void 0,transactionName:void 0,tNamePlain:void 0},a={};function s(e){if(!e)throw new Error("All info objects require an agent identifier!");if(!a[e])throw new Error("Info for ".concat(e," was never set"));return a[e]}function c(e,t){if(!e)throw new Error("All info objects require an agent identifier!");a[e]=(0,i.D)(t,o),(0,n.Qy)(e,a[e],"info")}var u=r(7056);const d=()=>{const e={blockSelector:"[data-nr-block]",maskInputOptions:{password:!0}};return{allow_bfcache:!0,privacy:{cookies_enabled:!0},ajax:{deny_list:void 0,enabled:!0,harvestTimeSeconds:10},distributed_tracing:{enabled:void 0,exclude_newrelic_header:void 0,cors_use_newrelic_header:void 0,cors_use_tracecontext_headers:void 0,allowed_origins:void 0},session:{domain:void 0,expiresMs:u.oD,inactiveMs:u.Hb},ssl:void 0,obfuscate:void 0,jserrors:{enabled:!0,harvestTimeSeconds:10},metrics:{enabled:!0},page_action:{enabled:!0,harvestTimeSeconds:30},page_view_event:{enabled:!0},page_view_timing:{enabled:!0,harvestTimeSeconds:30,long_task:!1},session_trace:{enabled:!0,harvestTimeSeconds:10},harvest:{tooManyRequestsDelay:60},session_replay:{enabled:!1,harvestTimeSeconds:60,sampleRate:.1,errorSampleRate:.1,maskTextSelector:"*",maskAllInputs:!0,get blockClass(){return"nr-block"},get ignoreClass(){return"nr-ignore"},get maskTextClass(){return"nr-mask"},get blockSelector(){return e.blockSelector},set blockSelector(t){e.blockSelector+=",".concat(t)},get maskInputOptions(){return e.maskInputOptions},set maskInputOptions(t){e.maskInputOptions={...t,password:!0}}},spa:{enabled:!0,harvestTimeSeconds:10}}},f={};function l(e){if(!e)throw new Error("All configuration objects require an agent identifier!");if(!f[e])throw new Error("Configuration for ".concat(e," was never set"));return f[e]}function h(e,t){if(!e)throw new Error("All configuration objects require an agent identifier!");f[e]=(0,i.D)(t,d()),(0,n.Qy)(e,f[e],"config")}function g(e,t){if(!e)throw new Error("All configuration objects require an agent identifier!");var r=l(e);if(r){for(var n=t.split("."),i=0;i {r.d(t,{D:()=>i});var n=r(50);function i(e,t){try{if(!e||"object"!=typeof e)return(0,n.Z)("Setting a Configurable requires an object as input");if(!t||"object"!=typeof t)return(0,n.Z)("Setting a Configurable requires a model to set its initial properties");const r=Object.create(Object.getPrototypeOf(t),Object.getOwnPropertyDescriptors(t)),o=0===Object.keys(r).length?e:r;for(let a in o)if(void 0!==e[a])try{"object"==typeof e[a]&&"object"==typeof t[a]?r[a]=i(e[a],t[a]):r[a]=e[a]}catch(e){(0,n.Z)("An error occurred while setting a property of a Configurable",e)}return r}catch(e){(0,n.Z)("An error occured while setting a Configurable",e)}}},6818:(e,t,r)=>{r.d(t,{Re:()=>i,gF:()=>o,q4:()=>n});const n="1.236.0",i="PROD",o="CDN"},385:(e,t,r)=>{r.d(t,{FN:()=>a,IF:()=>u,Nk:()=>f,Tt:()=>s,_A:()=>o,il:()=>n,pL:()=>c,v6:()=>i,w1:()=>d});const n="undefined"!=typeof window&&!!window.document,i="undefined"!=typeof WorkerGlobalScope&&("undefined"!=typeof self&&self instanceof WorkerGlobalScope&&self.navigator instanceof WorkerNavigator||"undefined"!=typeof globalThis&&globalThis instanceof WorkerGlobalScope&&globalThis.navigator instanceof WorkerNavigator),o=n?window:"undefined"!=typeof WorkerGlobalScope&&("undefined"!=typeof self&&self instanceof WorkerGlobalScope&&self||"undefined"!=typeof globalThis&&globalThis instanceof WorkerGlobalScope&&globalThis),a=""+o?.location,s=/iPad|iPhone|iPod/.test(navigator.userAgent),c=s&&"undefined"==typeof SharedWorker,u=(()=>{const e=navigator.userAgent.match(/Firefox[/\s](\d+\.\d+)/);return Array.isArray(e)&&e.length>=2?+e[1]:0})(),d=Boolean(n&&window.document.documentMode),f=!!navigator.sendBeacon},1117:(e,t,r)=>{r.d(t,{w:()=>o});var n=r(50);const i={agentIdentifier:"",ee:void 0};class o{constructor(e){try{if("object"!=typeof e)return(0,n.Z)("shared context requires an object as input");this.sharedContext={},Object.assign(this.sharedContext,i),Object.entries(e).forEach((e=>{let[t,r]=e;Object.keys(i).includes(t)&&(this.sharedContext[t]=r)}))}catch(e){(0,n.Z)("An error occured while setting SharedContext",e)}}}},8e3:(e,t,r)=>{r.d(t,{L:()=>d,R:()=>c});var n=r(2177),i=r(1284),o=r(4322),a=r(3325);const s={};function c(e,t){const r={staged:!1,priority:a.p[t]||0};u(e),s[e].get(t)||s[e].set(t,r)}function u(e){e&&(s[e]||(s[e]=new Map))}function d(){let e=arguments.length>0&&void 0!==arguments[0]?arguments[0]:"",t=arguments.length>1&&void 0!==arguments[1]?arguments[1]:"feature";if(u(e),!e||!s[e].get(t))return a(t);s[e].get(t).staged=!0;const r=[...s[e]];function a(t){const r=e?n.ee.get(e):n.ee,a=o.X.handlers;if(r.backlog&&a){var s=r.backlog[t],c=a[t];if(c){for(var u=0;s&&u {let[t,r]=e;return r.staged}))&&(r.sort(((e,t)=>e[1].priority-t[1].priority)),r.forEach((e=>{let[t]=e;a(t)})))}function f(e,t){var r=e[1];(0,i.D)(t[r],(function(t,r){var n=e[0];if(r[0]===n){var i=r[1],o=e[3],a=e[2];i.apply(o,a)}}))}},2177:(e,t,r)=>{r.d(t,{c:()=>f,ee:()=>u});var n=r(8632),i=r(2210),o=r(1284),a=r(5763),s="nr@context";let c=(0,n.fP)();var u;function d(){}function f(e){return(0,i.X)(e,s,l)}function l(){return new d}function h(){u.aborted=!0,u.backlog={}}c.ee?u=c.ee:(u=function e(t,r){var n={},c={},f={},g=!1;try{g=16===r.length&&(0,a.OP)(r).isolatedBacklog}catch(e){}var p={on:b,addEventListener:b,removeEventListener:y,emit:v,get:x,listeners:w,context:m,buffer:A,abort:h,aborted:!1,isBuffering:E,debugId:r,backlog:g?{}:t&&"object"==typeof t.backlog?t.backlog:{}};return p;function m(e){return e&&e instanceof d?e:e?(0,i.X)(e,s,l):l()}function v(e,r,n,i,o){if(!1!==o&&(o=!0),!u.aborted||i){t&&o&&t.emit(e,r,n);for(var a=m(n),s=w(e),d=s.length,f=0;fn,p:()=>i});var n=r(2177).ee.get("handle");function i(e,t,r,i,o){o?(o.buffer([e],i),o.emit(e,t,r)):(n.buffer([e],i),n.emit(e,t,r))}},4322:(e,t,r)=>{r.d(t,{X:()=>o});var n=r(5546);o.on=a;var i=o.handlers={};function o(e,t,r,o){a(o||n.E,i,e,t,r)}function a(e,t,r,i,o){o||(o="feature"),e||(e=n.E);var a=t[o]=t[o]||{};(a[r]=a[r]||[]).push([e,i])}},3239:(e,t,r)=>{r.d(t,{bP:()=>s,iz:()=>c,m$:()=>a});var n=r(385);let i=!1,o=!1;try{const e={get passive(){return i=!0,!1},get signal(){return o=!0,!1}};n._A.addEventListener("test",null,e),n._A.removeEventListener("test",null,e)}catch(e){}function a(e,t){return i||o?{capture:!!e,passive:i,signal:t}:!!e}function s(e,t){let r=arguments.length>2&&void 0!==arguments[2]&&arguments[2],n=arguments.length>3?arguments[3]:void 0;window.addEventListener(e,t,a(r,n))}function c(e,t){let r=arguments.length>2&&void 0!==arguments[2]&&arguments[2],n=arguments.length>3?arguments[3]:void 0;document.addEventListener(e,t,a(r,n))}},4402:(e,t,r)=>{r.d(t,{Ht:()=>u,M:()=>c,Rl:()=>a,ky:()=>s});var n=r(385);const i="xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx";function o(e,t){return e?15&e[t]:16*Math.random()|0}function a(){const e=n._A?.crypto||n._A?.msCrypto;let t,r=0;return e&&e.getRandomValues&&(t=e.getRandomValues(new Uint8Array(31))),i.split("").map((e=>"x"===e?o(t,++r).toString(16):"y"===e?(3&o()|8).toString(16):e)).join("")}function s(e){const t=n._A?.crypto||n._A?.msCrypto;let r,i=0;t&&t.getRandomValues&&(r=t.getRandomValues(new Uint8Array(31)));const a=[];for(var s=0;s {r.d(t,{Bq:()=>n,Hb:()=>o,oD:()=>i});const n="NRBA",i=144e5,o=18e5},7894:(e,t,r)=>{function n(){return Math.round(performance.now())}r.d(t,{z:()=>n})},7243:(e,t,r)=>{r.d(t,{e:()=>o});var n=r(385),i={};function o(e){if(e in i)return i[e];if(0===(e||"").indexOf("data:"))return{protocol:"data"};let t;var r=n._A?.location,o={};if(n.il)t=document.createElement("a"),t.href=e;else try{t=new URL(e,r.href)}catch(e){return o}o.port=t.port;var a=t.href.split("://");!o.port&&a[1]&&(o.port=a[1].split("/")[0].split("@").pop().split(":")[1]),o.port&&"0"!==o.port||(o.port="https"===a[0]?"443":"80"),o.hostname=t.hostname||r.hostname,o.pathname=t.pathname,o.protocol=a[0],"/"!==o.pathname.charAt(0)&&(o.pathname="/"+o.pathname);var s=!t.protocol||":"===t.protocol||t.protocol===r.protocol,c=t.hostname===r.hostname&&t.port===r.port;return o.sameOrigin=s&&(!t.hostname||c),"/"===o.pathname&&(i[e]=o),o}},50:(e,t,r)=>{function n(e,t){"function"==typeof console.warn&&(console.warn("New Relic: ".concat(e)),t&&console.warn(t))}r.d(t,{Z:()=>n})},2587:(e,t,r)=>{r.d(t,{N:()=>c,T:()=>u});var n=r(2177),i=r(5546),o=r(8e3),a=r(3325);const s={stn:[a.D.sessionTrace],err:[a.D.jserrors,a.D.metrics],ins:[a.D.pageAction],spa:[a.D.spa],sr:[a.D.sessionReplay,a.D.sessionTrace]};function c(e,t){const r=n.ee.get(t);e&&"object"==typeof e&&(Object.entries(e).forEach((e=>{let[t,n]=e;void 0===u[t]&&(s[t]?s[t].forEach((e=>{n?(0,i.p)("feat-"+t,[],void 0,e,r):(0,i.p)("block-"+t,[],void 0,e,r),(0,i.p)("rumresp-"+t,[Boolean(n)],void 0,e,r)})):n&&(0,i.p)("feat-"+t,[],void 0,void 0,r),u[t]=Boolean(n))})),Object.keys(s).forEach((e=>{void 0===u[e]&&(s[e]?.forEach((t=>(0,i.p)("rumresp-"+e,[!1],void 0,t,r))),u[e]=!1)})),(0,o.L)(t,a.D.pageViewEvent))}const u={}},2210:(e,t,r)=>{r.d(t,{X:()=>i});var n=Object.prototype.hasOwnProperty;function i(e,t,r){if(n.call(e,t))return e[t];var i=r();if(Object.defineProperty&&Object.keys)try{return Object.defineProperty(e,t,{value:i,writable:!0,enumerable:!1}),i}catch(e){}return e[t]=i,i}},1284:(e,t,r)=>{r.d(t,{D:()=>n});const n=(e,t)=>Object.entries(e||{}).map((e=>{let[r,n]=e;return t(r,n)}))},4351:(e,t,r)=>{r.d(t,{P:()=>o});var n=r(2177);const i=()=>{const e=new WeakSet;return(t,r)=>{if("object"==typeof r&&null!==r){if(e.has(r))return;e.add(r)}return r}};function o(e){try{return JSON.stringify(e,i())}catch(e){try{n.ee.emit("internal-error",[e])}catch(e){}}}},3960:(e,t,r)=>{r.d(t,{K:()=>a,b:()=>o});var n=r(3239);function i(){return"undefined"==typeof document||"complete"===document.readyState}function o(e,t){if(i())return e();(0,n.bP)("load",e,t)}function a(e){if(i())return e();(0,n.iz)("DOMContentLoaded",e)}},8632:(e,t,r)=>{r.d(t,{EZ:()=>u,Qy:()=>c,ce:()=>o,fP:()=>a,gG:()=>d,mF:()=>s});var n=r(7894),i=r(385);const o={beacon:"bam.nr-data.net",errorBeacon:"bam.nr-data.net"};function a(){return i._A.NREUM||(i._A.NREUM={}),void 0===i._A.newrelic&&(i._A.newrelic=i._A.NREUM),i._A.NREUM}function s(){let e=a();return e.o||(e.o={ST:i._A.setTimeout,SI:i._A.setImmediate,CT:i._A.clearTimeout,XHR:i._A.XMLHttpRequest,REQ:i._A.Request,EV:i._A.Event,PR:i._A.Promise,MO:i._A.MutationObserver,FETCH:i._A.fetch}),e}function c(e,t,r){let i=a();const o=i.initializedAgents||{},s=o[e]||{};return Object.keys(s).length||(s.initializedAt={ms:(0,n.z)(),date:new Date}),i.initializedAgents={...o,[e]:{...s,[r]:t}},i}function u(e,t){a()[e]=t}function d(){return function(){let e=a();const t=e.info||{};e.info={beacon:o.beacon,errorBeacon:o.errorBeacon,...t}}(),function(){let e=a();const t=e.init||{};e.init={...t}}(),s(),function(){let e=a();const t=e.loader_config||{};e.loader_config={...t}}(),a()}},7956:(e,t,r)=>{r.d(t,{N:()=>i});var n=r(3239);function i(e){let t=arguments.length>1&&void 0!==arguments[1]&&arguments[1],r=arguments.length>2?arguments[2]:void 0,i=arguments.length>3?arguments[3]:void 0;return void(0,n.iz)("visibilitychange",(function(){if(t)return void("hidden"==document.visibilityState&&e());e(document.visibilityState)}),r,i)}},1214:(e,t,r)=>{r.d(t,{em:()=>v,u5:()=>N,QU:()=>S,_L:()=>I,Gm:()=>L,Lg:()=>M,gy:()=>U,BV:()=>Q,Kf:()=>ee});var n=r(2177);const i="nr@original";var o=Object.prototype.hasOwnProperty,a=!1;function s(e,t){return e||(e=n.ee),r.inPlace=function(e,t,n,i,o){n||(n="");var a,s,c,u="-"===n.charAt(0);for(c=0;c 2?n-2:0),o=2;o {r(A[T],e,w),r(E[T],e,w)})),r(l._A,"fetch",y),t.on(y+"end",(function(e,r){var n=this;if(r){var i=r.headers.get("content-length");null!==i&&(n.rxSize=i),t.emit(y+"done",[null,r],n)}else t.emit(y+"done",[e],n)})),t}const O={},j=["pushState","replaceState"];function S(e){const t=function(e){return(e||n.ee).get("history")}(e);return!l.il||O[t.debugId]++||(O[t.debugId]=1,s(t).inPlace(window.history,j,"-")),t}var P=r(3239);const C={},R=["appendChild","insertBefore","replaceChild"];function I(e){const t=function(e){return(e||n.ee).get("jsonp")}(e);if(!l.il||C[t.debugId])return t;C[t.debugId]=!0;var r=s(t),i=/[?&](?:callback|cb)=([^&#]+)/,o=/(.*)\.([^.]+)/,a=/^(\w+)(\.|$)(.*)$/;function c(e,t){var r=e.match(a),n=r[1],i=r[3];return i?c(i,t[n]):t[n]}return r.inPlace(Node.prototype,R,"dom-"),t.on("dom-start",(function(e){!function(e){if(!e||"string"!=typeof e.nodeName||"script"!==e.nodeName.toLowerCase())return;if("function"!=typeof e.addEventListener)return;var n=(a=e.src,s=a.match(i),s?s[1]:null);var a,s;if(!n)return;var u=function(e){var t=e.match(o);if(t&&t.length>=3)return{key:t[2],parent:c(t[1],window)};return{key:e,parent:window}}(n);if("function"!=typeof u.parent[u.key])return;var d={};function f(){t.emit("jsonp-end",[],d),e.removeEventListener("load",f,(0,P.m$)(!1)),e.removeEventListener("error",l,(0,P.m$)(!1))}function l(){t.emit("jsonp-error",[],d),t.emit("jsonp-end",[],d),e.removeEventListener("load",f,(0,P.m$)(!1)),e.removeEventListener("error",l,(0,P.m$)(!1))}r.inPlace(u.parent,[u.key],"cb-",d),e.addEventListener("load",f,(0,P.m$)(!1)),e.addEventListener("error",l,(0,P.m$)(!1)),t.emit("new-jsonp",[e.src],d)}(e[0])})),t}var k=r(5763);const H={};function L(e){const t=function(e){return(e||n.ee).get("mutation")}(e);if(!l.il||H[t.debugId])return t;H[t.debugId]=!0;var r=s(t),i=k.Yu.MO;return i&&(window.MutationObserver=function(e){return this instanceof i?new i(r(e,"fn-")):i.apply(this,arguments)},MutationObserver.prototype=i.prototype),t}const z={};function M(e){const t=function(e){return(e||n.ee).get("promise")}(e);if(z[t.debugId])return t;z[t.debugId]=!0;var r=n.c,o=s(t),a=k.Yu.PR;return a&&function(){function e(r){var n=t.context(),i=o(r,"executor-",n,null,!1);const s=Reflect.construct(a,[i],e);return t.context(s).getCtx=function(){return n},s}l._A.Promise=e,Object.defineProperty(e,"name",{value:"Promise"}),e.toString=function(){return a.toString()},Object.setPrototypeOf(e,a),["all","race"].forEach((function(r){const n=a[r];e[r]=function(e){let i=!1;[...e||[]].forEach((e=>{this.resolve(e).then(a("all"===r),a(!1))}));const o=n.apply(this,arguments);return o;function a(e){return function(){t.emit("propagate",[null,!i],o,!1,!1),i=i||!e}}}})),["resolve","reject"].forEach((function(r){const n=a[r];e[r]=function(e){const r=n.apply(this,arguments);return e!==r&&t.emit("propagate",[e,!0],r,!1,!1),r}})),e.prototype=a.prototype;const n=a.prototype.then;a.prototype.then=function(){var e=this,i=r(e);i.promise=e;for(var a=arguments.length,s=new Array(a),c=0;c e())),t};function m(e,t){i.inPlace(t,["onreadystatechange"],"fn-",E)}function b(){var e=this,t=r.context(e);e.readyState>3&&!t.resolved&&(t.resolved=!0,r.emit("xhr-resolved",[],e)),i.inPlace(e,f,"fn-",E)}if(function(e,t){for(var r in e)t[r]=e[r]}(o,p),p.prototype=o.prototype,i.inPlace(p.prototype,J,"-xhr-",E),r.on("send-xhr-start",(function(e,t){m(e,t),function(e){h.push(e),a&&(y?y.then(A):u?u(A):(w=-w,x.data=w))}(t)})),r.on("open-xhr-start",m),a){var y=c&&c.resolve();if(!u&&!c){var w=1,x=document.createTextNode(w);new a(A).observe(x,{characterData:!0})}}else t.on("fn-end",(function(e){e[0]&&e[0].type===d||A()}));function A(){for(var e=0;e {r.d(t,{t:()=>n});const n=r(3325).D.ajax},6660:(e,t,r)=>{r.d(t,{A:()=>i,t:()=>n});const n=r(3325).D.jserrors,i="nr@seenError"},3081:(e,t,r)=>{r.d(t,{gF:()=>o,mY:()=>i,t9:()=>n,vz:()=>s,xS:()=>a});const n=r(3325).D.metrics,i="sm",o="cm",a="storeSupportabilityMetrics",s="storeEventMetrics"},4649:(e,t,r)=>{r.d(t,{t:()=>n});const n=r(3325).D.pageAction},7633:(e,t,r)=>{r.d(t,{Dz:()=>i,OJ:()=>a,qw:()=>o,t9:()=>n});const n=r(3325).D.pageViewEvent,i="firstbyte",o="domcontent",a="windowload"},9251:(e,t,r)=>{r.d(t,{t:()=>n});const n=r(3325).D.pageViewTiming},3614:(e,t,r)=>{r.d(t,{BST_RESOURCE:()=>i,END:()=>s,FEATURE_NAME:()=>n,FN_END:()=>u,FN_START:()=>c,PUSH_STATE:()=>d,RESOURCE:()=>o,START:()=>a});const n=r(3325).D.sessionTrace,i="bstResource",o="resource",a="-start",s="-end",c="fn"+a,u="fn"+s,d="pushState"},7836:(e,t,r)=>{r.d(t,{BODY:()=>A,CB_END:()=>E,CB_START:()=>u,END:()=>x,FEATURE_NAME:()=>i,FETCH:()=>_,FETCH_BODY:()=>v,FETCH_DONE:()=>m,FETCH_START:()=>p,FN_END:()=>c,FN_START:()=>s,INTERACTION:()=>l,INTERACTION_API:()=>d,INTERACTION_EVENTS:()=>o,JSONP_END:()=>b,JSONP_NODE:()=>g,JS_TIME:()=>T,MAX_TIMER_BUDGET:()=>a,REMAINING:()=>f,SPA_NODE:()=>h,START:()=>w,originalSetTimeout:()=>y});var n=r(5763);const i=r(3325).D.spa,o=["click","submit","keypress","keydown","keyup","change"],a=999,s="fn-start",c="fn-end",u="cb-start",d="api-ixn-",f="remaining",l="interaction",h="spaNode",g="jsonpNode",p="fetch-start",m="fetch-done",v="fetch-body-",b="jsonp-end",y=n.Yu.ST,w="-start",x="-end",A="-body",E="cb"+x,T="jsTime",_="fetch"},5938:(e,t,r)=>{r.d(t,{W:()=>o});var n=r(5763),i=r(2177);class o{constructor(e,t,r){this.agentIdentifier=e,this.aggregator=t,this.ee=i.ee.get(e,(0,n.OP)(this.agentIdentifier).isolatedBacklog),this.featureName=r,this.blocked=!1}}},9144:(e,t,r)=>{r.d(t,{j:()=>m});var n=r(3325),i=r(5763),o=r(5546),a=r(2177),s=r(7894),c=r(8e3),u=r(3960),d=r(385),f=r(50),l=r(3081),h=r(8632);function g(){const e=(0,h.gG)();["setErrorHandler","finished","addToTrace","inlineHit","addRelease","addPageAction","setCurrentRouteName","setPageViewName","setCustomAttribute","interaction","noticeError","setUserId"].forEach((t=>{e[t]=function(){for(var r=arguments.length,n=new Array(r),i=0;i 1?r-1:0),i=1;i {e.exposed&&e.api[t]&&o.push(e.api[t](...n))})),o.length>1?o:o[0]}(t,...n)}}))}var p=r(2587);function m(e){let t=arguments.length>1&&void 0!==arguments[1]?arguments[1]:{},m=arguments.length>2?arguments[2]:void 0,v=arguments.length>3?arguments[3]:void 0,{init:b,info:y,loader_config:w,runtime:x={loaderType:m},exposed:A=!0}=t;const E=(0,h.gG)();y||(b=E.init,y=E.info,w=E.loader_config),(0,i.Dg)(e,b||{}),(0,i.GE)(e,w||{}),(0,i.sU)(e,x),y.jsAttributes??={},d.v6&&(y.jsAttributes.isWorker=!0),(0,i.CX)(e,y),g();const T=function(e,t){t||(0,c.R)(e,"api");const h={};var g=a.ee.get(e),p=g.get("tracer"),m="api-",v=m+"ixn-";function b(t,r,n,o){const a=(0,i.C5)(e);return null===r?delete a.jsAttributes[t]:(0,i.CX)(e,{...a,jsAttributes:{...a.jsAttributes,[t]:r}}),x(m,n,!0,o||null===r?"session":void 0)(t,r)}function y(){}["setErrorHandler","finished","addToTrace","inlineHit","addRelease"].forEach((e=>h[e]=x(m,e,!0,"api"))),h.addPageAction=x(m,"addPageAction",!0,n.D.pageAction),h.setCurrentRouteName=x(m,"routeName",!0,n.D.spa),h.setPageViewName=function(t,r){if("string"==typeof t)return"/"!==t.charAt(0)&&(t="/"+t),(0,i.OP)(e).customTransaction=(r||"http://custom.transaction")+t,x(m,"setPageViewName",!0)()},h.setCustomAttribute=function(e,t){let r=arguments.length>2&&void 0!==arguments[2]&&arguments[2];if("string"==typeof e){if(["string","number"].includes(typeof t)||null===t)return b(e,t,"setCustomAttribute",r);(0,f.Z)("Failed to execute setCustomAttribute.\nNon-null value must be a string or number type, but a type of was provided."))}else(0,f.Z)("Failed to execute setCustomAttribute.\nName must be a string type, but a type of was provided."))},h.setUserId=function(e){if("string"==typeof e||null===e)return b("enduser.id",e,"setUserId",!0);(0,f.Z)("Failed to execute setUserId.\nNon-null value must be a string type, but a type of was provided."))},h.interaction=function(){return(new y).get()};var w=y.prototype={createTracer:function(e,t){var r={},i=this,a="function"==typeof t;return(0,o.p)(v+"tracer",[(0,s.z)(),e,r],i,n.D.spa,g),function(){if(p.emit((a?"":"no-")+"fn-start",[(0,s.z)(),i,a],r),a)try{return t.apply(this,arguments)}catch(e){throw p.emit("fn-err",[arguments,this,"string"==typeof e?new Error(e):e],r),e}finally{p.emit("fn-end",[(0,s.z)()],r)}}}};function x(e,t,r,i){return function(){return(0,o.p)(l.xS,["API/"+t+"/called"],void 0,n.D.metrics,g),i&&(0,o.p)(e+t,[(0,s.z)(),...arguments],r?null:this,i,g),r?void 0:this}}function A(){r.e(439).then(r.bind(r,7438)).then((t=>{let{setAPI:r}=t;r(e),(0,c.L)(e,"api")})).catch((()=>(0,f.Z)("Downloading runtime APIs failed...")))}return["actionText","setName","setAttribute","save","ignore","onEnd","getContext","end","get"].forEach((e=>{w[e]=x(v,e,void 0,n.D.spa)})),h.noticeError=function(e,t){"string"==typeof e&&(e=new Error(e)),(0,o.p)(l.xS,["API/noticeError/called"],void 0,n.D.metrics,g),(0,o.p)("err",[e,(0,s.z)(),!1,t],void 0,n.D.jserrors,g)},d.il?(0,u.b)((()=>A()),!0):A(),h}(e,v);return(0,h.Qy)(e,T,"api"),(0,h.Qy)(e,A,"exposed"),(0,h.EZ)("activatedFeatures",p.T),T}},3325:(e,t,r)=>{r.d(t,{D:()=>n,p:()=>i});const n={ajax:"ajax",jserrors:"jserrors",metrics:"metrics",pageAction:"page_action",pageViewEvent:"page_view_event",pageViewTiming:"page_view_timing",sessionReplay:"session_replay",sessionTrace:"session_trace",spa:"spa"},i={[n.pageViewEvent]:1,[n.pageViewTiming]:2,[n.metrics]:3,[n.jserrors]:4,[n.ajax]:5,[n.sessionTrace]:6,[n.pageAction]:7,[n.spa]:8,[n.sessionReplay]:9}}},n={};function i(e){var t=n[e];if(void 0!==t)return t.exports;var o=n[e]={exports:{}};return r[e](o,o.exports,i),o.exports}i.m=r,i.d=(e,t)=>{for(var r in t)i.o(t,r)&&!i.o(e,r)&&Object.defineProperty(e,r,{enumerable:!0,get:t[r]})},i.f={},i.e=e=>Promise.all(Object.keys(i.f).reduce(((t,r)=>(i.f[r](e,t),t)),[])),i.u=e=>(({78:"page_action-aggregate",147:"metrics-aggregate",242:"session-manager",317:"jserrors-aggregate",348:"page_view_timing-aggregate",412:"lazy-feature-loader",439:"async-api",538:"recorder",590:"session_replay-aggregate",675:"compressor",733:"session_trace-aggregate",786:"page_view_event-aggregate",873:"spa-aggregate",898:"ajax-aggregate"}[e]||e)+"."+{78:"ac76d497",147:"3dc53903",148:"1a20d5fe",242:"2a64278a",317:"49e41428",348:"bd6de33a",412:"2f55ce66",439:"30bd804e",538:"1b18459f",590:"cf0efb30",675:"ae9f91a8",733:"83105561",786:"06482edd",860:"03a8b7a5",873:"e6b09d52",898:"998ef92b"}[e]+"-1.236.0.min.js"),i.o=(e,t)=>Object.prototype.hasOwnProperty.call(e,t),e={},t="NRBA:",i.l=(r,n,o,a)=>{if(e[r])e[r].push(n);else{var s,c;if(void 0!==o)for(var u=document.getElementsByTagName("script"),d=0;d {s.onerror=s.onload=null,clearTimeout(h);var i=e[r];if(delete e[r],s.parentNode&&s.parentNode.removeChild(s),i&&i.forEach((e=>e(n))),t)return t(n)},h=setTimeout(l.bind(null,void 0,{type:"timeout",target:s}),12e4);s.onerror=l.bind(null,s.onerror),s.onload=l.bind(null,s.onload),c&&document.head.appendChild(s)}},i.r=e=>{"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})},i.j=364,i.p="https://js-agent.newrelic.com/",(()=>{var e={364:0,953:0};i.f.j=(t,r)=>{var n=i.o(e,t)?e[t]:void 0;if(0!==n)if(n)r.push(n[2]);else{var o=new Promise(((r,i)=>n=e[t]=[r,i]));r.push(n[2]=o);var a=i.p+i.u(t),s=new Error;i.l(a,(r=>{if(i.o(e,t)&&(0!==(n=e[t])&&(e[t]=void 0),n)){var o=r&&("load"===r.type?"missing":r.type),a=r&&r.target&&r.target.src;s.message="Loading chunk "+t+" failed.\n("+o+": "+a+")",s.name="ChunkLoadError",s.type=o,s.request=a,n[1](s)}}),"chunk-"+t,t)}};var t=(t,r)=>{var n,o,[a,s,c]=r,u=0;if(a.some((t=>0!==e[t]))){for(n in s)i.o(s,n)&&(i.m[n]=s[n]);if(c)c(i)}for(t&&t(r);u {i.r(o);var e=i(3325),t=i(5763);const r=Object.values(e.D);function n(e){const n={};return r.forEach((r=>{n[r]=function(e,r){return!1!==(0,t.Mt)(r,"".concat(e,".enabled"))}(r,e)})),n}var a=i(9144);var s=i(5546),c=i(385),u=i(8e3),d=i(5938),f=i(3960),l=i(50);class h extends d.W{constructor(e,t,r){let n=!(arguments.length>3&&void 0!==arguments[3])||arguments[3];super(e,t,r),this.auto=n,this.abortHandler,this.featAggregate,this.onAggregateImported,n&&(0,u.R)(e,r)}importAggregator(){let e=arguments.length>0&&void 0!==arguments[0]?arguments[0]:{};if(this.featAggregate||!this.auto)return;const r=c.il&&!0===(0,t.Mt)(this.agentIdentifier,"privacy.cookies_enabled");let n;this.onAggregateImported=new Promise((e=>{n=e}));const o=async()=>{let t;try{if(r){const{setupAgentSession:e}=await Promise.all([i.e(860),i.e(242)]).then(i.bind(i,3228));t=e(this.agentIdentifier)}}catch(e){(0,l.Z)("A problem occurred when starting up session manager. This page will not start or extend any session.",e)}try{if(!this.shouldImportAgg(this.featureName,t))return void(0,u.L)(this.agentIdentifier,this.featureName);const{lazyFeatureLoader:r}=await i.e(412).then(i.bind(i,8582)),{Aggregate:o}=await r(this.featureName,"aggregate");this.featAggregate=new o(this.agentIdentifier,this.aggregator,e),n(!0)}catch(e){(0,l.Z)("Downloading and initializing ".concat(this.featureName," failed..."),e),this.abortHandler?.(),n(!1)}};c.il?(0,f.b)((()=>o()),!0):o()}shouldImportAgg(r,n){return r!==e.D.sessionReplay||!1!==(0,t.Mt)(this.agentIdentifier,"session_trace.enabled")&&(!!n?.isNew||!!n?.state.sessionReplay)}}var g=i(7633),p=i(7894);class m extends h{static featureName=g.t9;constructor(r,n){let i=!(arguments.length>2&&void 0!==arguments[2])||arguments[2];if(super(r,n,g.t9,i),("undefined"==typeof PerformanceNavigationTiming||c.Tt)&&"undefined"!=typeof PerformanceTiming){const n=(0,t.OP)(r);n[g.Dz]=Math.max(Date.now()-n.offset,0),(0,f.K)((()=>n[g.qw]=Math.max((0,p.z)()-n[g.Dz],0))),(0,f.b)((()=>{const t=(0,p.z)();n[g.OJ]=Math.max(t-n[g.Dz],0),(0,s.p)("timing",["load",t],void 0,e.D.pageViewTiming,this.ee)}))}this.importAggregator()}}var v=i(1117),b=i(1284);class y extends v.w{constructor(e){super(e),this.aggregatedData={}}store(e,t,r,n,i){var o=this.getBucket(e,t,r,i);return o.metrics=function(e,t){t||(t={count:0});return t.count+=1,(0,b.D)(e,(function(e,r){t[e]=w(r,t[e])})),t}(n,o.metrics),o}merge(e,t,r,n,i){var o=this.getBucket(e,t,n,i);if(o.metrics){var a=o.metrics;a.count+=r.count,(0,b.D)(r,(function(e,t){if("count"!==e){var n=a[e],i=r[e];i&&!i.c?a[e]=w(i.t,n):a[e]=function(e,t){if(!t)return e;t.c||(t=x(t.t));return t.min=Math.min(e.min,t.min),t.max=Math.max(e.max,t.max),t.t+=e.t,t.sos+=e.sos,t.c+=e.c,t}(i,a[e])}}))}else o.metrics=r}storeMetric(e,t,r,n){var i=this.getBucket(e,t,r);return i.stats=w(n,i.stats),i}getBucket(e,t,r,n){this.aggregatedData[e]||(this.aggregatedData[e]={});var i=this.aggregatedData[e][t];return i||(i=this.aggregatedData[e][t]={params:r||{}},n&&(i.custom=n)),i}get(e,t){return t?this.aggregatedData[e]&&this.aggregatedData[e][t]:this.aggregatedData[e]}take(e){for(var t={},r="",n=!1,i=0;i t.max&&(t.max=e),e 2&&void 0!==arguments[2])||arguments[2];super(e,r,j.t,n),c.il&&((0,t.OP)(e).initHidden=Boolean("hidden"===document.visibilityState),(0,N.N)((()=>(0,s.p)("docHidden",[(0,p.z)()],void 0,j.t,this.ee)),!0),(0,O.bP)("pagehide",(()=>(0,s.p)("winPagehide",[(0,p.z)()],void 0,j.t,this.ee))),this.importAggregator())}}var P=i(3081);class C extends h{static featureName=P.t9;constructor(e,t){let r=!(arguments.length>2&&void 0!==arguments[2])||arguments[2];super(e,t,P.t9,r),this.importAggregator()}}var R,I=i(2210),k=i(1214),H=i(2177),L={};try{R=localStorage.getItem("__nr_flags").split(","),console&&"function"==typeof console.log&&(L.console=!0,-1!==R.indexOf("dev")&&(L.dev=!0),-1!==R.indexOf("nr_dev")&&(L.nrDev=!0))}catch(e){}function z(e){try{L.console&&z(e)}catch(e){}}L.nrDev&&H.ee.on("internal-error",(function(e){z(e.stack)})),L.dev&&H.ee.on("fn-err",(function(e,t,r){z(r.stack)})),L.dev&&(z("NR AGENT IN DEVELOPMENT MODE"),z("flags: "+(0,b.D)(L,(function(e,t){return e})).join(", ")));var M=i(6660);class B extends h{static featureName=M.t;constructor(r,n){let i=!(arguments.length>2&&void 0!==arguments[2])||arguments[2];super(r,n,M.t,i),this.skipNext=0;try{this.removeOnAbort=new AbortController}catch(e){}const o=this;o.ee.on("fn-start",(function(e,t,r){o.abortHandler&&(o.skipNext+=1)})),o.ee.on("fn-err",(function(t,r,n){o.abortHandler&&!n[M.A]&&((0,I.X)(n,M.A,(function(){return!0})),this.thrown=!0,(0,s.p)("err",[n,(0,p.z)()],void 0,e.D.jserrors,o.ee))})),o.ee.on("fn-end",(function(){o.abortHandler&&!this.thrown&&o.skipNext>0&&(o.skipNext-=1)})),o.ee.on("internal-error",(function(t){(0,s.p)("ierr",[t,(0,p.z)(),!0],void 0,e.D.jserrors,o.ee)})),this.origOnerror=c._A.onerror,c._A.onerror=this.onerrorHandler.bind(this),c._A.addEventListener("unhandledrejection",(t=>{const r=function(e){let t="Unhandled Promise Rejection: ";if(e instanceof Error)try{return e.message=t+e.message,e}catch(t){return e}if(void 0===e)return new Error(t);try{return new Error(t+(0,D.P)(e))}catch(e){return new Error(t)}}(t.reason);(0,s.p)("err",[r,(0,p.z)(),!1,{unhandledPromiseRejection:1}],void 0,e.D.jserrors,this.ee)}),(0,O.m$)(!1,this.removeOnAbort?.signal)),(0,k.gy)(this.ee),(0,k.BV)(this.ee),(0,k.em)(this.ee),(0,t.OP)(r).xhrWrappable&&(0,k.Kf)(this.ee),this.abortHandler=this.#e,this.importAggregator()}#e(){this.removeOnAbort?.abort(),this.abortHandler=void 0}onerrorHandler(t,r,n,i,o){"function"==typeof this.origOnerror&&this.origOnerror(...arguments);try{this.skipNext?this.skipNext-=1:(0,s.p)("err",[o||new F(t,r,n),(0,p.z)()],void 0,e.D.jserrors,this.ee)}catch(t){try{(0,s.p)("ierr",[t,(0,p.z)(),!0],void 0,e.D.jserrors,this.ee)}catch(e){}}return!1}}function F(e,t,r){this.message=e||"Uncaught error with no additional information",this.sourceURL=t,this.line=r}let U=1;const q="nr@id";function G(e){const t=typeof e;return!e||"object"!==t&&"function"!==t?-1:e===c._A?0:(0,I.X)(e,q,(function(){return U++}))}function V(e){if("string"==typeof e&&e.length)return e.length;if("object"==typeof e){if("undefined"!=typeof ArrayBuffer&&e instanceof ArrayBuffer&&e.byteLength)return e.byteLength;if("undefined"!=typeof Blob&&e instanceof Blob&&e.size)return e.size;if(!("undefined"!=typeof FormData&&e instanceof FormData))try{return(0,D.P)(e).length}catch(e){return}}}var X=i(7243);class W{constructor(e){this.agentIdentifier=e,this.generateTracePayload=this.generateTracePayload.bind(this),this.shouldGenerateTrace=this.shouldGenerateTrace.bind(this)}generateTracePayload(e){if(!this.shouldGenerateTrace(e))return null;var r=(0,t.DL)(this.agentIdentifier);if(!r)return null;var n=(r.accountID||"").toString()||null,i=(r.agentID||"").toString()||null,o=(r.trustKey||"").toString()||null;if(!n||!i)return null;var a=(0,_.M)(),s=(0,_.Ht)(),c=Date.now(),u={spanId:a,traceId:s,timestamp:c};return(e.sameOrigin||this.isAllowedOrigin(e)&&this.useTraceContextHeadersForCors())&&(u.traceContextParentHeader=this.generateTraceContextParentHeader(a,s),u.traceContextStateHeader=this.generateTraceContextStateHeader(a,c,n,i,o)),(e.sameOrigin&&!this.excludeNewrelicHeader()||!e.sameOrigin&&this.isAllowedOrigin(e)&&this.useNewrelicHeaderForCors())&&(u.newrelicHeader=this.generateTraceHeader(a,s,c,n,i,o)),u}generateTraceContextParentHeader(e,t){return"00-"+t+"-"+e+"-01"}generateTraceContextStateHeader(e,t,r,n,i){return i+"@nr=0-1-"+r+"-"+n+"-"+e+"----"+t}generateTraceHeader(e,t,r,n,i,o){if(!("function"==typeof c._A?.btoa))return null;var a={v:[0,1],d:{ty:"Browser",ac:n,ap:i,id:e,tr:t,ti:r}};return o&&n!==o&&(a.d.tk=o),btoa((0,D.P)(a))}shouldGenerateTrace(e){return this.isDtEnabled()&&this.isAllowedOrigin(e)}isAllowedOrigin(e){var r=!1,n={};if((0,t.Mt)(this.agentIdentifier,"distributed_tracing")&&(n=(0,t.P_)(this.agentIdentifier).distributed_tracing),e.sameOrigin)r=!0;else if(n.allowed_origins instanceof Array)for(var i=0;i 2&&void 0!==arguments[2])||arguments[2];super(r,n,Z.t,i),(0,t.OP)(r).xhrWrappable&&(this.dt=new W(r),this.handler=(e,t,r,n)=>(0,s.p)(e,t,r,n,this.ee),(0,k.u5)(this.ee),(0,k.Kf)(this.ee),function(r,n,i,o){function a(e){var t=this;t.totalCbs=0,t.called=0,t.cbTime=0,t.end=E,t.ended=!1,t.xhrGuids={},t.lastSize=null,t.loadCaptureCalled=!1,t.params=this.params||{},t.metrics=this.metrics||{},e.addEventListener("load",(function(r){_(t,e)}),(0,O.m$)(!1)),c.IF||e.addEventListener("progress",(function(e){t.lastSize=e.loaded}),(0,O.m$)(!1))}function s(e){this.params={method:e[0]},T(this,e[1]),this.metrics={}}function u(e,n){var i=(0,t.DL)(r);i.xpid&&this.sameOrigin&&n.setRequestHeader("X-NewRelic-ID",i.xpid);var a=o.generateTracePayload(this.parsedOrigin);if(a){var s=!1;a.newrelicHeader&&(n.setRequestHeader("newrelic",a.newrelicHeader),s=!0),a.traceContextParentHeader&&(n.setRequestHeader("traceparent",a.traceContextParentHeader),a.traceContextStateHeader&&n.setRequestHeader("tracestate",a.traceContextStateHeader),s=!0),s&&(this.dt=a)}}function d(e,t){var r=this.metrics,i=e[0],o=this;if(r&&i){var a=V(i);a&&(r.txSize=a)}this.startTime=(0,p.z)(),this.listener=function(e){try{"abort"!==e.type||o.loadCaptureCalled||(o.params.aborted=!0),("load"!==e.type||o.called===o.totalCbs&&(o.onloadCalled||"function"!=typeof t.onload)&&"function"==typeof o.end)&&o.end(t)}catch(e){try{n.emit("internal-error",[e])}catch(e){}}};for(var s=0;s 1?e[1]=i:e.push(i)}else e[0]&&e[0].headers&&s(e[0].headers,n)&&(this.dt=n);function s(e,t){var r=!1;return t.newrelicHeader&&(e.set("newrelic",t.newrelicHeader),r=!0),t.traceContextParentHeader&&(e.set("traceparent",t.traceContextParentHeader),t.traceContextStateHeader&&e.set("tracestate",t.traceContextStateHeader),r=!0),r}}function x(e,t){this.params={},this.metrics={},this.startTime=(0,p.z)(),this.dt=t,e.length>=1&&(this.target=e[0]),e.length>=2&&(this.opts=e[1]);var r,n=this.opts||{},i=this.target;"string"==typeof i?r=i:"object"==typeof i&&i instanceof Y?r=i.url:c._A?.URL&&"object"==typeof i&&i instanceof URL&&(r=i.href),T(this,r);var o=(""+(i&&i instanceof Y&&i.method||n.method||"GET")).toUpperCase();this.params.method=o,this.txSize=V(n.body)||0}function A(t,r){var n;this.endTime=(0,p.z)(),this.params||(this.params={}),this.params.status=r?r.status:0,"string"==typeof this.rxSize&&this.rxSize.length>0&&(n=+this.rxSize);var o={txSize:this.txSize,rxSize:n,duration:(0,p.z)()-this.startTime};i("xhr",[this.params,o,this.startTime,this.endTime,"fetch"],this,e.D.ajax)}function E(t){var r=this.params,n=this.metrics;if(!this.ended){this.ended=!0;for(var o=0;o 2&&void 0!==arguments[2])||arguments[2];super(e,t,we.t,r),this.importAggregator()}}new class{constructor(e){let t=arguments.length>1&&void 0!==arguments[1]?arguments[1]:(0,_.ky)(16);c._A?(this.agentIdentifier=t,this.sharedAggregator=new y({agentIdentifier:this.agentIdentifier}),this.features={},this.desiredFeatures=new Set(e.features||[]),this.desiredFeatures.add(m),Object.assign(this,(0,a.j)(this.agentIdentifier,e,e.loaderType||"agent")),this.start()):(0,l.Z)("Failed to initial the agent. Could not determine the runtime environment.")}get config(){return{info:(0,t.C5)(this.agentIdentifier),init:(0,t.P_)(this.agentIdentifier),loader_config:(0,t.DL)(this.agentIdentifier),runtime:(0,t.OP)(this.agentIdentifier)}}start(){const t="features";try{const r=n(this.agentIdentifier),i=[...this.desiredFeatures];i.sort(((t,r)=>e.p[t.featureName]-e.p[r.featureName])),i.forEach((t=>{if(r[t.featureName]||t.featureName===e.D.pageViewEvent){const n=function(t){switch(t){case e.D.ajax:return[e.D.jserrors];case e.D.sessionTrace:return[e.D.ajax,e.D.pageViewEvent];case e.D.sessionReplay:return[e.D.sessionTrace];case e.D.pageViewTiming:return[e.D.pageViewEvent];default:return[]}}(t.featureName);n.every((e=>r[e]))||(0,l.Z)("".concat(t.featureName," is enabled but one or more dependent features has been disabled (").concat((0,D.P)(n),"). This may cause unintended consequences or missing data...")),this.features[t.featureName]=new t(this.agentIdentifier,this.sharedAggregator)}})),(0,T.Qy)(this.agentIdentifier,this.features,t)}catch(e){(0,l.Z)("Failed to initialize all enabled instrument classes (agent aborted) -",e);for(const e in this.features)this.features[e].abortHandler?.();const r=(0,T.fP)();return delete r.initializedAgents[this.agentIdentifier]?.api,delete r.initializedAgents[this.agentIdentifier]?.[t],delete this.sharedAggregator,r.ee?.abort(),delete r.ee?.get(this.agentIdentifier),!1}}}({features:[J,m,S,class extends h{static featureName=oe;constructor(t,r){if(super(t,r,oe,!(arguments.length>2&&void 0!==arguments[2])||arguments[2]),!c.il)return;const n=this.ee;let i;(0,k.QU)(n),this.eventsEE=(0,k.em)(n),this.eventsEE.on(se,(function(e,t){this.bstStart=(0,p.z)()})),this.eventsEE.on(ae,(function(t,r){(0,s.p)("bst",[t[0],r,this.bstStart,(0,p.z)()],void 0,e.D.sessionTrace,n)})),n.on(ce+ne,(function(e){this.time=(0,p.z)(),this.startPath=location.pathname+location.hash})),n.on(ce+ie,(function(t){(0,s.p)("bstHist",[location.pathname+location.hash,this.startPath,this.time],void 0,e.D.sessionTrace,n)}));try{i=new PerformanceObserver((t=>{const r=t.getEntries();(0,s.p)(te,[r],void 0,e.D.sessionTrace,n)})),i.observe({type:re,buffered:!0})}catch(e){}this.importAggregator({resourceObserver:i})}},C,xe,B,class extends h{static featureName=de;constructor(e,r){if(super(e,r,de,!(arguments.length>2&&void 0!==arguments[2])||arguments[2]),!c.il)return;if(!(0,t.OP)(e).xhrWrappable)return;try{this.removeOnAbort=new AbortController}catch(e){}let n,i=0;const o=this.ee.get("tracer"),a=(0,k._L)(this.ee),s=(0,k.Lg)(this.ee),u=(0,k.BV)(this.ee),d=(0,k.Kf)(this.ee),f=this.ee.get("events"),l=(0,k.u5)(this.ee),h=(0,k.QU)(this.ee),g=(0,k.Gm)(this.ee);function m(e,t){h.emit("newURL",[""+window.location,t])}function v(){i++,n=window.location.hash,this[ve]=(0,p.z)()}function b(){i--,window.location.hash!==n&&m(0,!0);var e=(0,p.z)();this[pe]=~~this[pe]+e-this[ve],this[ye]=e}function y(e,t){e.on(t,(function(){this[t]=(0,p.z)()}))}this.ee.on(ve,v),s.on(be,v),a.on(be,v),this.ee.on(ye,b),s.on(ge,b),a.on(ge,b),this.ee.buffer([ve,ye,"xhr-resolved"],this.featureName),f.buffer([ve],this.featureName),u.buffer(["setTimeout"+le,"clearTimeout"+fe,ve],this.featureName),d.buffer([ve,"new-xhr","send-xhr"+fe],this.featureName),l.buffer([me+fe,me+"-done",me+he+fe,me+he+le],this.featureName),h.buffer(["newURL"],this.featureName),g.buffer([ve],this.featureName),s.buffer(["propagate",be,ge,"executor-err","resolve"+fe],this.featureName),o.buffer([ve,"no-"+ve],this.featureName),a.buffer(["new-jsonp","cb-start","jsonp-error","jsonp-end"],this.featureName),y(l,me+fe),y(l,me+"-done"),y(a,"new-jsonp"),y(a,"jsonp-end"),y(a,"cb-start"),h.on("pushState-end",m),h.on("replaceState-end",m),window.addEventListener("hashchange",m,(0,O.m$)(!0,this.removeOnAbort?.signal)),window.addEventListener("load",m,(0,O.m$)(!0,this.removeOnAbort?.signal)),window.addEventListener("popstate",(function(){m(0,i>1)}),(0,O.m$)(!0,this.removeOnAbort?.signal)),this.abortHandler=this.#e,this.importAggregator()}#e(){this.removeOnAbort?.abort(),this.abortHandler=void 0}}],loaderType:"spa"})})(),window.NRBA=o})(); window.jQuery || document.write(' ') CKEDITOR_BASEPATH='https://f1000research.com/js/vendor/ckeditor/' window.reactTheme = 'research'; window.MathJax = { CommonHTML: { linebreaks: { automatic: true } }, 'HTML-CSS': { linebreaks: { automatic: true } }, SVG: { linebreaks: { automatic: true } }, AuthorInit: function() { MathJax.Hub.Register.MessageHook('End Process', function () { let timeout = false; // holder for timeout id const delay = 250; // delay after event is "complete" to run callback const reflowMath = function() { const dispFormulas = document.querySelectorAll('.disp-formula.panel'); if (!dispFormulas) { return; } for (const dispFormula of dispFormulas) { const child = dispFormula.querySelector('.MathJax_Preview').nextSibling.firstChild; const isMultiline = MathJax.Hub.getAllJax(dispFormula)[0].root.isMultiline; if (dispFormula.offsetWidth < child.offsetWidth || isMultiline) { MathJax.Hub.Queue(['Rerender', MathJax.Hub, dispFormula]); } } }; window.addEventListener('resize', function() { clearTimeout(timeout); // clear the timeout timeout = setTimeout(reflowMath, delay); // start timing for event "completion" }); }); }, }; if (window.location.hash == '#_=_'){ window.location = window.location.href.split('#')[0] } !function(f,b,e,v,n,t,s){if(f.fbq)return;n=f.fbq=function() {n.callMethod? n.callMethod.apply(n,arguments):n.queue.push(arguments)} ;if(!f._fbq)f._fbq=n; n.push=n;n.loaded=!0;n.version='2.0';n.queue=[];t=b.createElement(e);t.async=!0; t.src=v;s=b.getElementsByTagName(e)[0];s.parentNode.insertBefore(t,s)}(window, document,'script','https://connect.facebook.net/en_US/fbevents.js'); fbq('init', '1641728616063202'); fbq('track', "PixelInitialized", {}); (function(h,o,t,j,a,r){ h.hj=h.hj||function(){(h.hj.q=h.hj.q||[]).push(arguments)}; h._hjSettings={hjid:2318163,hjsv:6}; a=o.getElementsByTagName('head')[0]; r=o.createElement('script');r.async=1; r.src=t+h._hjSettings.hjid+j+h._hjSettings.hjsv; a.appendChild(r); })(window,document,'https://static.hotjar.com/c/hotjar-','.js?sv='); search file_upload Submit your research search menu close search Browse Gateways & Collections How to Publish Submit your Research My Submissions Article Guidelines Article Guidelines (New Versions) Open Data, Software and Code Guidelines Open Data and Accessible Source Materials Guidelines (HSS) Open Data, Software and Code Guidelines (PSE) Prepublication Checks Production Process Posters and Slides Guidelines Document Guidelines Article Processing Charges Peer Review Finding Article Reviewers About How it Works For Reviewers Our Advisors Policies Glossary FAQs For Developers Newsroom Contact My Research Submissions Content and Tracking Alerts My Details Sign In file_upload Submit your research { "@context": "https://schema.org", "@type": "ScholarlyArticle", "mainEntityOfPage": { "@type": "WebPage", "@id": "https://f1000research.com/articles/15-569" }, "headline": "Towards Protecting the Injured Party from Errors and Hallucinations of Artificial Intelligence: A Contemporary...", "datePublished": "2026-04-18T18:27:56", "dateModified": "2026-04-18T18:27:56", "author": [ { "@type": "Person", "name": "Nagwa Abouhaiba" }, { "@type": "Person", "name": "Saed Ahmed Khouli" }, { "@type": "Person", "name": "Maya Khater" } ], "publisher": { "@type": "Organization", "name": "F1000Research", "logo": { "@type": "ImageObject", "url": "https://f1000research.com/img/AMP/F1000Research_image.png", "height": 480, "width": 60 } }, "image": { "@type": "ImageObject", "url": "https://f1000research.com/img/AMP/F1000Research_image.png", "height": 1200, "width": 150 }, "description": "The world has been witnessing a growing and accelerating expansion in the use of artificial intelligence (AI) systems, as leading worldwide technology businesses compete to develop systems and software that can simulate the human mind, produce technological solutions, and accomplish activities that previously needed human mental effort. This has given rise to a host of new and unfamiliar legal challenges, including those connected to errors and ‘hallucinations’ that may produce inaccurate or misleading outputs. This paper examines the technical and practical risks associated with the use of AI, with a focus on the phenomenon of hallucinations that has recently become widely discussed, and its potential effects on users and third parties. This study adopts a comparative, analytical legal approach by analyzing the current legal framework to determine the extent to which the law protects the injured party, assessing the adequacy of existing civil-liability rules, and emphasizing the difficulties associated with proving fault and causation, as well as identifying the responsible party within the complex smart-transactions ecosystems. Accordingly, the objective of this paper is to determine how civil liability arising from the use of AI systems in numerous fields may be attributed, and to identify the future legal implications of such systems in light of the general rules of the UAE Civil Transactions Law and the substance of the EU regulation. Accordingly, the study presents a contemporary legal perspective on conventional culpability to safeguard the harmed person against AI faults and hallucinations. It concludes by proposing innovative legal mechanisms, such as strict (objective) liability, transparency obligations, and compulsory insurance, to compensate the injured party for ‘digital harm’ caused by AI technologies. The research indicates that legal responsibility and technical innovation must be balanced to safeguard the damaged party." } { "@context": "http://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": "1", "item": { "@id": "https://f1000research.com/", "name": "Home" } }, { "@type": "ListItem", "position": "2", "item": { "@id": "https://f1000research.com/browse/articles", "name": "Browse" } }, { "@type": "ListItem", "position": "3", "item": { "@id": "https://f1000research.com/articles/15-569", "name": "Towards Protecting the Injured Party from Errors and Hallucinations..." } } ] } Home Browse Towards Protecting the Injured Party from Errors and Hallucinations... ALL Metrics - Views Downloads Get PDF Get XML Cite How to cite this article Abouhaiba N, Khouli SA and Khater M. Towards Protecting the Injured Party from Errors and Hallucinations of Artificial Intelligence: A Contemporary Legal Perspective [version 1; peer review: 2 approved] . F1000Research 2026, 15 :569 ( https://doi.org/10.12688/f1000research.179603.1 ) NOTE: If applicable, it is important to ensure the information in square brackets after the title is included in all citations of this article. Close Copy Citation Details Export Export Citation Sciwheel EndNote Ref. Manager Bibtex ProCite Sente EXPORT Select a format first Track Share ▬ ✚ Research Article Towards Protecting the Injured Party from Errors and Hallucinations of Artificial Intelligence: A Contemporary Legal Perspective [version 1; peer review: 2 approved] Nagwa Abouhaiba https://orcid.org/0009-0003-0303-8776 1 , Saed Ahmed Khouli 1 , Maya Khater 2 Nagwa Abouhaiba https://orcid.org/0009-0003-0303-8776 1 , Saed Ahmed Khouli 1 , Maya Khater 2 PUBLISHED 18 Apr 2026 Author details Author details 1 College of Law, Abu Dhabi University, Abu Dhabi, United Arab Emirates 2 College of Law, United Arab Emirates University, Al Ain, United Arab Emirates Nagwa Abouhaiba Roles: Conceptualization, Data Curation, Formal Analysis, Investigation, Methodology, Resources, Software, Validation, Visualization, Writing – Original Draft Preparation Saed Ahmed Khouli Roles: Data Curation, Formal Analysis, Methodology, Resources, Validation, Visualization, Writing – Review & Editing Maya Khater Roles: Data Curation, Funding Acquisition, Project Administration, Supervision, Writing – Review & Editing OPEN PEER REVIEW DETAILS REVIEWER STATUS This article is included in the Artificial Intelligence and Machine Learning gateway. Abstract The world has been witnessing a growing and accelerating expansion in the use of artificial intelligence (AI) systems, as leading worldwide technology businesses compete to develop systems and software that can simulate the human mind, produce technological solutions, and accomplish activities that previously needed human mental effort. This has given rise to a host of new and unfamiliar legal challenges, including those connected to errors and ‘hallucinations’ that may produce inaccurate or misleading outputs. This paper examines the technical and practical risks associated with the use of AI, with a focus on the phenomenon of hallucinations that has recently become widely discussed, and its potential effects on users and third parties. This study adopts a comparative, analytical legal approach by analyzing the current legal framework to determine the extent to which the law protects the injured party, assessing the adequacy of existing civil-liability rules, and emphasizing the difficulties associated with proving fault and causation, as well as identifying the responsible party within the complex smart-transactions ecosystems. Accordingly, the objective of this paper is to determine how civil liability arising from the use of AI systems in numerous fields may be attributed, and to identify the future legal implications of such systems in light of the general rules of the UAE Civil Transactions Law and the substance of the EU regulation. Accordingly, the study presents a contemporary legal perspective on conventional culpability to safeguard the harmed person against AI faults and hallucinations. It concludes by proposing innovative legal mechanisms, such as strict (objective) liability, transparency obligations, and compulsory insurance, to compensate the injured party for ‘digital harm’ caused by AI technologies. The research indicates that legal responsibility and technical innovation must be balanced to safeguard the damaged party. READ ALL READ LESS Keywords Artificial Intelligence; AI Errors and Hallucinations; UAE Civil Transactions Law; Civil Liability and Technology; Protection of the Injured Party; Digital Harm. Corresponding Author(s) Maya Khater ( [email protected] ) Close Corresponding author: Maya Khater Competing interests: No competing interests were disclosed. Grant information: The author(s) declared that no grants were involved in supporting this work. Copyright: © 2026 Abouhaiba N et al . This is an open access article distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. How to cite: Abouhaiba N, Khouli SA and Khater M. Towards Protecting the Injured Party from Errors and Hallucinations of Artificial Intelligence: A Contemporary Legal Perspective [version 1; peer review: 2 approved] . F1000Research 2026, 15 :569 ( https://doi.org/10.12688/f1000research.179603.1 ) First published: 18 Apr 2026, 15 :569 ( https://doi.org/10.12688/f1000research.179603.1 ) Latest published: 18 Apr 2026, 15 :569 ( https://doi.org/10.12688/f1000research.179603.1 ) Introduction The development of AI models has been accompanied by several challenges, chiefly reflected in experts’ skepticism regarding the difficulty of achieving progress in government-funded AI projects and research due to limited computing capabilities, programming difficulties, and expert systems’ failure to meet expectations; such systems were costly to maintain and lacked the flexibility required to address complex real-world problems ( Abou Adel, 2022 ; El Baroudy et al., 2025 ). Interest in AI was renewed in the 1990s and the early twenty-first century as a result of advances in computing, the availability of data, and innovation in algorithms. AI was then deployed across multiple fields, culminating in the revolutionary applications we see today in healthcare, finance, transportation, entertainment, and education ( Qiqieh et al., 2025 ; Mucci, 2026 ). Artificial Intelligence (AI) is a term whose use and circulation has increased rapidly in recent times across diverse forums, in the wake of the scientific, technical, and technological surge witnessed worldwide. AI is an advanced scientific and technical field concerned with designing and developing systems and software capable of simulating the human mind in logical reasoning, learning, decision-making, and inference, with the aim of enhancing efficiency and developing advanced technical solutions that facilitate human life. These features have rendered AI a central and indispensable element in human, scientific, practical, and research fields alike. This rapid technological development has, in turn, imposed complex legal issues relating to responsibility for decisions generated by AI models, with the absence of a clear legislative framework representing one of the most salient challenges. On this basis, many advanced countries, including the United Arab Emirates, began to develop and adopt legislative frameworks and governance principles specifically addressing AI. In 2017, the UAE Government adopted a comprehensive national AI strategy, the ‘UAE Artificial Intelligence Strategy 2031,’ and issued regulatory and ethical charters for AI, while introducing legislative amendments in data protection and digital governance * . Similarly, in 2024, the European Union moved toward issuing the Artificial Intelligence Act (AI Act), regarded as the first legislation to provide a legal definition of an AI system, and comprising a set of rules intended to enhance the trustworthiness of AI in Europe. Key characteristics of AI AI is characterized by numerous features that have contributed to its rapid spread and adoption across various fields. The most significant of which may be summarized as follows: Autonomy: AI’s ability to make decisions and execute complex tasks without human intervention and operating decisions autonomously by determining appropriate means to achieve its objective. Simulation: This characteristic constitutes the foundational basis of AI. The core concept of AI is to simulate the capabilities of the human mind in analysis, comprehension, and problem-solving. AI performs complex functions that typically require direct human intervention to process and execute. Self-learning and adaptation: AI’s capacity to learn and derive lessons is among its most distinguishing features. AI can process information and big data using self-learning algorithms that formulate and test assumptions. The more information AI is exposed to, the more its performance evolves; its ability to detect patterns, infer results, adjust behavior, and autonomously analyze data develops through techniques such as Machine Learning and Deep Learning. (Abou Adel et al., 2024 ; Alhourani et al., 2026 ; Qiqieh et al., 2025 ; Adel, 2022 ; Abdulrahman, n.d. ) Prediction and decision-making: AI enables the processing of vast quantities of data at very high speed, empowering it to predict future outcomes or propose decisions based on statistical and algorithmic inferences. Scalability and development: AI’s flexibility enables expanding its applications by increasing inputs and improving algorithms. This characteristic underscores AI’s dynamic and ever-evolving nature, with capabilities that are variable and constantly growing. ( Norvig, 2010 ). Natural language processing (NLP): AI uses this capability to understand language details which allows it to produce correct answers that meet user requirements. The feature developed through the use of chatbots and voice-assistant applications which includes the virtual assistant ‘Siri’ created by Apple as its most important demonstration ( Nigam, 2024 ). Errors and hallucinations of AI and their impact on civil liability AI systems possess distinct attributes which enable them to operate independently while they learn new information and make future predictions. The implementation of artificial intelligence technology changes the established legal framework because its autonomous systems and self-learning capacities create legal challenges which extend beyond technical matters to affect fundamental tenets of contemporary legal systems ( Qutieshat et al., 2026 ). The most prominent of these issues include the following: First - autonomy (agentic AI) The autonomous capabilities of artificial intelligence systems create legal difficulties because the systems provide incorrect information which leads to incorrect final results and dangerous situations that result in harm to people and property. The key legal challenges arising from autonomy include: - Legal liability: The autonomy of AI and its ability to perform tasks independently and without any human intervention raises a fundamental question: who bears the consequences of the system’s decisions, acts, or errors - the manufacturer, the owner, the operator, the programmer, or the user? This feature has driven some to adopt the hypothesis that a robot, as one of the most important AI applications, should acquire legal personality as an electronic or virtual person, such that it would be liable to compensate third parties ( Ben Othman, 2020 ). In our view, however, this hypothesis is not practically or legally workable; even if an artificial juristic personality could be created for intelligent machines and generative AI systems, such systems do not possess an independent Financial Liability from which compensation could be paid to the injured party. - The AI ‘black box’ problem: It is difficult to detect and remediate the damage caused by AI systems since humans cannot see, forecast, or determine how they process data, assess their algorithms, or make autonomous judgments. Unaddressed injury may lead to increased legal and material damages from autonomous decision-making. - Legality: This issue concerns the extent to which AI systems may be granted powers that affect individuals’ fundamental rights, such as judicial decision-making, legal advice, security matters, and military equipment. Second - ‘AI hallucinations’ Hallucinations are one of the biggest issues facing AI systems, particularly ‘generative AI’ based on deep learning and self-learning. Such systems use mathematical algorithms and complicated internal working processes, making it difficult or impossible to anticipate all outputs or judgments under different conditions. When generative AI algorithms produce outputs that are not grounded in the data on which the system was trained, or when intelligent systems do not follow a recognized or explainable pattern of reasoning, ‘hallucination’ or ‘AI hallucinations’ may occur † . To understand the causes of AI hallucinations, Professor Novotny explains that such hallucinations are a side effect arising from how generative AI operates: intelligent systems use an algorithm to generate outputs by sampling from probability distributions built from large sets of examples. In essence, that algorithm relies on a form of conjecture in arriving at outputs and results; accordingly, it may also produce incorrect statements or acts ( Nasr, 2025 ). The reasons underlying AI hallucinations can be summarized as follows ( Coursera, 2025 ): Limited training data: Biases in the inputs used to train AI models can lead them to produce biased and inaccurate hallucinations presented as if they were reliable facts. Model complexity: If an AI model is so complex that it lacks constraints limiting the type and quality of outputs it can produce, it may generate outputs that are based primarily on conjecture. Data poisoning: Data poisoning occurs when internet hackers inject incorrect, misleading, or biased data into the training datasets of an AI model, which may create a security issues or lead to a cyberattack. Overfitting: An AI model may successfully predict training data but fail to generalize to fresh data. If an AI system is trained to recognize humans and given many images of people, including groups of people standing next to streetlights, the model may incorrectly learn that streetlights are humans and begin to identify them as people. An experimental test conducted by Stanford University in 2024, involving leading legal-AI platforms across over 200 legal queries, revealed that the +LexisNexis Lexis platform reached a hallucination rate of 17% of cases, while the hallucination rates in Westlaw AI-Assisted Research was 33%. The ‘Ask Practical Law AI’ platform provided an accurate responses to queries in only 18% of cases ( POLANI, 2025 ). In short, we consider that the difficulty of predicting AI system outputs due to AI hallucinations is not merely a technical problem; rather, it is a legal problem connected to the rules of civil liability. For this reason, most legal systems tend to impose restrictions on AI outputs and decisions whenever they entail legal or social effects. Third - technical errors The occurrence of technical errors in AI systems is attributed to one of the following causes: • Errors in data or input. • Errors in algorithms. • Errors in self-learning. Beyond the technical domain, such errors trigger multiple legal issues, the most important include: the liability issue of identifying the actor responsible for the error; the transparency issue of explaining the automated decision produced by AI on the basis of that error; and the security issue of preventing intrusion and manipulation that may arise from any vulnerabilities emerging from such technical errors ‡ . Given the legal issues associated with these technical errors, modern legislations - foremost in the UAE - has embedded two general principles governing AI use: (i) the principle of safety, which aims to ensure that all AI systems comply with the highest safety standards and encourages the modification or removal of high-risk systems; and (ii) the principle of transparency, which calls for a clear understanding of AI and how systems operate and make decisions, thereby contributing to building trust and enhancing responsibility and accountability in the use of these technologies. The specificity of harm and liability in the face of AI outputs The harms addressed by civil liability rules differ from those arising from the use of AI systems, as the latter possess a distinct legal character. This creates a point of difficulty in light of the civil liability rules regulated by the UAE Civil Transactions Law ( UAE Civil Transactions Law, Federal Decree-Law No. (25) of 2025 ), which attributes damage and fault to a direct human act or to the custody (guardianship) of specific tangible things ( Article 246 and Article 271 of Federal Decree-Law No. (25) of 2025 ). Today, however, we face harms of a different nature arising from AI outputs, harms that are non-material and intertwined with autonomous capabilities. This reveals a new type of harm that is difficult to subject to the traditional standards for proving fault ( Faqih, 2024 ), or even identifying its source, especially given the overlap among the roles of the developer, operator, and user ( Surden, 2019 ). Comparative trends, especially in Europe, are re-examining civil-liability concepts by expanding strict (objective) liability and linking it to risks associated with use of advanced technologies § , as reflected in legislative proposals regulating AI and liability for its products (European Commission, White Paper on Artificial Intelligence: A European Approach to Excellence and Trust . , 2020 ). These proposals are characterized by taking into account the specificity of digital harm and the need to develop effective legal mechanisms that protect the injured party without stifling technological innovation. The legal system needs to establish civil liability rules which protect injured parties through the identification of persons who bear responsibility for harmful acts through both contract law and tort law. Most legislation does not recognize an independent legal personality for technical systems. A smart system operating under a contractual agreement creates contractual liability when the debtor fails to fulfill his responsibilities which require him to either produce specific outcomes or show proper safety procedures or necessary information disclosure. When harm happens beyond the contractual connection, tort liability emerges on the basis of fault or liability for things;the AI system operator assumes the role of system custodian because he owns control over the system. The custodian becomes responsible for compensating the damaged party when he fails to inform about system dangers or conceals technical details from the public. Many legal scholars view AI systems as harmful and require tougher liability regulations to balance innovation with injury prevention. Most jurisdictions do not consider AI systems as having autonomous legal personality thus civil-liability standards require attribution of the harmful action to an actual person or legal entity for contractual and tort liability. In a contractual connection (e.g., an AI system operating agreement) contractual liability exists when someone proves that a party broke an obligation which included safety duties or responsibilities to inform about important details. When harm occurs outside the contractual relationship tort liability arises on the basis of fault or under the UAE Civil Transactions Law on liability for things and equipment under a person’s control custodianship so the operator may be treated as the custodian when control and supervision are established. Thus, failing to warn of system dangers or hiding technical information from consumers may result in responsibility and compensation. Many legal scholars consider AI systems “dangerous things” which require tougher liability regulations to balance innovation with victim protection. To address these harms, the European Union’s AI law adopted the idea of classifying the risks arising from AI uses into four categories: unacceptable risks, high risks, limited risks, and minimal (or acceptable) risks. This classification yields the following: Unacceptable risk: AI systems that pose unacceptable risks, such as the right to dignity, education, work, privacy, equality, health, safety, and human freedom, are often banned because their severity outweighs their potential benefit. For instance, a school may utilize an AI system to grade pupils depending on their behavior, depriving low-scoring students of one or more of those fundamental rights and vice versa. This is social scoring. This category is illegal and unethical since it violates freedom, privacy, and fundamental rights and discriminates against people. High risk: While this category is dangerous, the EU AI Act did not ban its usage by AI systems. In sensitive sectors involving individuals’ rights, such systems are utilized to screen job candidates’ CVs and provide an automatic acceptance or rejection decision based on prior training. Bias or inaccuracy in the automated decision may reject a qualified person without explanation. The hazard of this issue is its influence on individual rights and unlawful applicant discrimination. Thus, the European legislature required human oversight to ensure openness and bias-free decision-making. Limited risk: This category does not harm human rights, such as when a person is mislead by a company’s website into thinking a human replies to inquiries when they are actually connecting with an AI system. Given the low severity of this risk, the European legislature allowed its usage without control, but required users to be told that they were dealing with an AI system. Minimal (or acceptable) risk: This type is utilized in everyday transactions and does not violate human rights. It is non-binding, thus violating it has no legal consequence, such as when an AI program proposes arranging images on a phone or fixing spelling problems when writing. In such circumstances, the program only assists the user; the user can accept or reject the system’s proposal without legal consequences. The inadequacy of civil liability rules in the UAE civil transactions law in addressing errors and hallucinations of AI The difficulty of proving fault within AI systems The UAE Civil Transactions Law grounds tort liability on its three elements: the harmful act (fault), damage, and causation, as provided by Article 246 of the new UAE Civil Transactions Law No. 25 of 2025 , which stipulates: “Any harm caused to another shall obligate the perpetrator, even if non-discerning, to compensate for the damage.” Liability is thus understood as arising from a harmful act attributable to an identified actor (most often a human being). This traditional conception faces a fundamental challenge when applied to AI systems, particularly given the non-recognition of legal personality for AI ** . The inadequacy of the Civil Transactions Law in addressing AI errors and hallucinations becomes evident. Technical errors arising from the use of an AI system do not result from direct human behavior capable of being assessed by the “reasonable-person standard”; rather, it may result from complex interaction between AI algorithms and self-learning mechanisms. Consequently, it becomes difficult to determine whether the error stems from the programmer, the user, the system provider, or the system itself, leading to difficulty in identifying the legally responsible actor ( Alarie, Niblett, & Yoon, 2018 ; Surden, 2019 ). In this context, some scholars ( Al-Sanhuri, 2018 ; Al-Sahli, 2022 ) have grounded liability for harms generated by AI uses on liability for things, as provided in Article 271of Federal Decree-Law No. (25) of 2025 issuing the Civil Transactions Law, under the subsection titled “Liability of the Custodian of Things, Animals, and Buildings,” which provides: “Whoever has under his control things requiring special care to prevent their harm, or mechanical machines, shall be liable for the harm caused by such things or machines, except what cannot be avoided, without prejudice to any special provisions in this regard.” This is on the basis that AI systems fall within the concept of “things.” However, AI may not correspond to the strict notion of a “thing,” ( Al-Sahli, 2022 ; Marqas, 1995 ; Shannab, 2012 ) as it occupies an intermediate position: it rises above a thing but does not reach the status of a natural or juridical person. The problem of causation in light of the technical nature of AI This deficiency becomes even clearer when proving causation, which the law requires for liability. Article 255 of the Civil Transactions Law No. 25 of 2025 provides: “Compensation shall, in all cases, be assessed according to the damage suffered by the injured party and the profit lost, provided that this is a natural consequence of the harmful act.”Accordingly, liability is established only where the damage is a natural consequence of the harmful act. This requirement conflicts with the non-linear and the opacity of some AI systems, known as the “black box” problem, which has been previously explained, making it difficult for the injured party to prove that the damage arose as a direct result of the smart system’s decision. It may become impossible to establish the link between act and outcome, which may negate causation, or render legal causation presumed yet exceedingly complex, thereby practically depriving the injured party of protection ( European Commission, 2022 ; Pagallo, 2018 ). The impact of the deficiencies of traditional liability elements on protecting the injured party It follows from the foregoing that the traditional civil liability rules, in their current formulation within the UAE Civil Transactions Law, as well as the rules set out in the Consumer Protection Law, are insufficient or ill-equipped to deal effectively with the risks arising from AI errors and hallucinations ( Issa, 2022 ). Where the Civil Transactions Law requires proof of fault and causation in their classical sense, this does not align with the technical specificity of AI systems or the nature of their outputs. Thus, despite the actual occurrence of damage, the injured party may be unable to obtain compensation because they cannot meet the burden of proof imposed by the general rules. This reveals a genuine legislative gap: rules originally designed for traditional human acts are being applied to technological risks of an entirely different nature, which may conflict with the principle of compensatory justice, one of the core foundations of civil liability, and ultimately leads to weakened legal protection for the injured party ( European Commission, 2020 ). The need to reframe liability rules in light of AI risks In view of this deficiency, doctrinal calls are increasing to reconsider the traditional concepts of fault and causation when dealing with AI systems, by adopting more flexible legal models, such as presumed liability or risk-based liability ( Khater et al., 2025 ). This direction is regarded as a means of achieving a necessary balance between encouraging technological innovation, on the one hand, and ensuring effective protection for the injured party, on the other, without undermining the general rules of the UAE Civil Transactions Law ( Imad et al., 2026 ). Strict liability and the risk theory (Liability accompanies benefit) There is also a trend toward adopting strict liability, grounded in risk theory, as a legal mechanism to address damages arising from AI systems. This theory is premised on assigning liability to the person who benefits from the hazardous activity they have created, without requiring proof of a harmful act (fault). It is rooted in the principle of “liability accompanies benefit”, meaning that whoever derives benefit from a given activity must bear the consequences of its risks. When applied to AI uses, this concept implies that entities operating intelligent systems or deriving benefit from them would bear responsibility for compensating resulting damages ( Pagallo, 2018 ; Surden, 2019 ). However, this theory encounters a significant difficulty: the multiplicity of actors involved in the design, operation, and distribution of AI systems, from the manufacturer to the programmer, then the developer, to the supplier, the authorized representative, or even the distributor. Identifying the producer of an AI-related system is therefore difficult and surrounded by ambiguity and complexity ( Faqih, 2024 ). Given the European Commission’s conviction that traditional liability rules are insufficient to address AI risks, it adopted the idea of easing the injured party’s burden of proof with respect to AI liability, alongside establishing legal presumptions that assume causation where technical or organizational obligations imposed on smart-system operators are breached ( European Commission, 2022 ). The proposed legal vision for protecting the injured party from errors and hallucinations of AI systems In light of the inadequacy of civil liability rules to confront the risks of AI systems, including errors and hallucinations, it has become necessary to seek a legal solution to protect society from these risks, by moving from total reliance on traditional civil liability rules to adopting an innovative, flexible, and comprehensive legal vision that ensures full protection and compensation for those dealing with AI systems, in a way that fulfills one of the most important objectives of the UAE Civil Transactions Law, which is to compensate for the damage and prevent harm to others ( El-Erian et al., 2026 ; Nggilu et al., 2025 ). This requires considering the establishment of a set of preventive legal obligations that achieve a balance between encouraging innovation and, at the same time, considering the more important requirement of protecting the injured party. This solution proposes a legal vision based on strengthening the duty of transparency combined with the duty of warning, to reduce the risks associated with the use of AI: “Towards a flexible legislative framework that combines preventive obligations and compensatory liability,” as follows: Transparency obligation for self-operating systems This study believes that AI-powered technical systems must be transparent, as transparency is one of the most significant legal requirements to safeguard the harmed party from errors or hallucinations. Transparency helps the injured party and judicial authorities understand how the system operates, its correctness, and its hazards as much as feasible. This requirement follows the UAE Civil Transactions Law’s principles of good faith and non-harm. Transparency lets the judge assess fault and deduce it from the totality of facts and indicia, as well as identify the level of automated behavior’s causation and damage. Since concealing crucial information that prevents evaluation of the intelligent system’s detrimental behavior is proof of error, developers or operators are accountable if such opacity causes actual injury to others ( European Commission,2022 ; Surden, 2019 ). A Chinese court has ruled that a developer is not legally responsible for an AI “hallucination”, establishing a precedent for how such cases may be handled under Chinese law. The ruling, issued by the Hangzhou Internet Court, classifies AI-generated content as a service rather than a product in cases involving hallucinations. As a result, users must prove that a developer was at fault in the content-generation process and that the error caused actual harm. The court said AI-generated content generally does not constitute high-risk activity and that developers have limited ability to control AI responses. Imposing strict liability, it said, could hinder technological innovation ( Qitong, 2026 ). The duty to warn of hallucinations as an independent legal obligation UAE legal doctrine and case law require AI system operators to warn of AI-generated hallucinations and output mistakes. AI system operators must warn of the likelihood of hallucinations or inaccuracies in its outputs as part of UAE law’s responsibility of disclosure and warning. Activities with novel dangers, like AI systems, increase its importance. If the developer or operator knows of deceptive or hazardous outcomes, failing to notify users is negligence and civil culpability. UAE courts consider failure of duty to warn a defect that harms others. In sensitive sectors, where technical trust alone is insufficient, unambiguous warnings about the system’s limits and risks are crucial ( Al-Rai et al., 2026 ; Pagallo, 2018 ). Compulsory insurance for AI systems to compensate the injured party Among the elements of the proposed legal vision is the proposal to impose a compulsory insurance system on the use of any high-risk AI systems, to ensure that the injured party obtains compensation without requiring them to bear the burden of proving errors and hallucinations of this complex technology. This proposal is consistent with the logic of guarantee under the UAE Civil Transactions Law, particularly in relation to activities involving special risks, as compulsory insurance contributes to a fair distribution of risk among multiple parties. Developers and users may purchase insurance against damages caused by AI, and this system is considered, in the opinion of jurisprudence, an appropriate solution to cover unexpected damages caused by AI ( Fadel, 2023 ). Compensation funds for persons harmed by AI errors The idea of establishing compensation funds emerged in several fields, such as compensating victims of traffic accidents where the perpetrator is unknown, and other accidents. Therefore, this idea emerged in the context of compensating persons harmed by AI errors and hallucinations, as a complementary solution to the current civil liability system, especially in cases where identifying the responsible person is difficult or where proving fault and causation is not feasible. Accordingly, compensation funds may be a mechanism that the legislator can adopt in exceptional circumstances, or last resort, to redress harm and compensate injured in a manner that achieves social justice and prevents leaving the injured party without effective protection. Such funds may be financed by developers and users of AI systems. The expansion and flexibility of the judge’s authority in assessing technical error and drawing legal presumptions This view highlights the need to strengthen the civil judge’s role in assessing technical error and extending larger jurisdiction in presuming error or causation if damage is demonstrated. Since AI systems cannot be subjected to the fault standard used to human conduct, expanding the judge’s ability to determine technical error is one of the best ways to address their complexity. Thus, jurisprudence and the judiciary strengthen the judge’s ability to infer fault from facts and indicia, allowing the court to conclude fault or causation if damage is linked to a high-risk technical activity. Given the insufficiency of civil liability rules and the growing interaction with AI systems, this strategy may be the current solution until new legislation regulates AI-related injuries ( Surden, 2019 ). Do we need special legislative intervention or an independent legal model of liability? In light of the foregoing, and with the increasing harms caused by AI, the question arises as to whether the current reliance on the general rules of civil liability along with corporate policies and AI ethics charters is sufficient to address these problems. The jurisprudence has been echoed between supporters and opponents, while voices calling for the need for special legislation regulating these matters have grown louder. The European experience has clearly confirmed that effective protection for the injured party is achieved only through binding legislative regulation that complements the jurisprudential and judicial roles. Accordingly, society awaits the issuance of a special and independent UAE legislation on the liability of AI, based on both prevention and compensation, in line with the country’s directions toward supporting responsible innovation while protecting individuals’ rights at the same time. Conclusion The study concludes that AI systems, despite the efficiency, speed, and support they provide for decision-making, are simultaneously a source of legal risks that cause harm to their users. While AI applications and systems have delivered significant services across many fields of life, including health, education, law, engineering, security, defense … etc., the world is still facing many legal challenges and issues related to liability, transparency, safety of use, and compensation. and it has been found that these damages are of a new type in nature that cannot be accommodated by the current rules of the Civil Transactions Law. Those rules have been unable to address the harms of AI systems, especially the damages resulting from errors and hallucinations of AI outputs. The study also demonstrates that civil liability rules, despite their flexibility and broad concepts, face real difficulties when applied to AI harms, particularly with respect to proving fault and causation. Accordingly, the study proposes several solutions to avoid these difficulties through a legal vision for protecting the injured party from AI errors and hallucinations. This vision combines preventive obligations, such as transparency and a duty to warn of hallucinations, with effective compensation mechanisms, such as compulsory insurance and compensation funds, together with proposing to expand the judge’s role in assessing technical fault. This achieves a balance between supporting technological innovation and ensuring effective protection for the injured party. The study concludes with a set of findings and recommendations, including the following: 1. The distinctive characteristics of AI systems themselves constitute a set of legal challenges and issues relating to liability, transparency, safety of use, and security. 2. AI errors and hallucinations represent a real legal risk that may often lead to serious harms and damages, notwithstanding the absence of traditional human fault. 3. The civil liability rules in the UAE Civil Transactions Law, in their current form, even after the issuance of the new Civil Transactions Law No. 25 of 2025, still face practical difficulties in accommodating the technical specificity of smart systems, particularly in proving fault and causation in the field of AI. 4. The UAE judiciary has shown remarkable flexibility in addressing technical harms, by expanding judicial presumptions and assuming fault in high-risk activities. 5. Relaying on AI ethics charters or corporate policies alone is not enough to protect the injured. 6. Comparative approaches, particularly the European experience, confirm the trend toward special or semi-independent legal models of liability for AI, based on easing the burden of proof and ensuring compensation. Recommendations 1. Calling for developing a specific UAE legislative framework for AI, or introducing qualitative amendments to the general rules, taking into account the technical nature and newly emerging risks of these systems. 2. Explicitly stipulating preventive obligations that include transparency and the duty to warn against hallucinations, especially in high-risk applications. 3. Adopting a compulsory insurance for AI systems, alongside establishing compensation funds, to ensure redress in cases where identifying the liable party is not possible. 4. The use of AI should be accompanied by a set of laws and charters that ensure optimal benefit to humanity from these systems, while simultaneously developing controls, charters and determinants that contribute to reducing its risks. 5. Supporting and enhancing the role of the UAE judge in assessing technical fault, expand the scope of judicial presumptions, and rely on specialized technical expertise. 6. Benefiting from the European experience in AI liability, while adapting it to the UAE legal environment, in a manner that promotes responsible innovation and protects rights at the same time. Ethical considerations Not applicable. Data availability No datasets were analyzed or generated during the current study. All sources used in this manuscript are publicly available and are cited in the References section. Acknowledgements The authors express their thanks to reviewers and proofreaders who contributed in the preparation of this manuscript. References Abdulrahman O: Artificial Intelligence and Its Risks. Dar Zuhour Al-Ma‘rifa wa Al-Baraka; 1st edn.d. Abou Adel M: Towards an advanced interactive E-learning for the language. Arab World English Journal (AWEJ). 2022; ( 8 ): 330–340. Special Issue on CALL. Publisher Full Text Adel MA, Boudjadi K, Abouelnour MM, et al. : The contribution of smartphone apps to develop teaching the Arabic language “Arabic Is My Language’s App” as a sample. Forum Linguist Stud. 2024; 6 (6): 1175–1190. Publisher Full Text Alarie B, Niblett A, Yoon AH: How artificial intelligence will affect the practice of law. Univ Toronto Law J. 2018; 68 (1). Alhourani MI, Abazoglu M, Abou Adel MA, et al. : The impact of xenophobia on foreign language learning anxiety among Turkish university students: The case of Arabic. Res J Adv Humanit. 2026; 7 (1). Publisher Full Text Al-Rai A, Maala N, Khater M: The authority of Jordanian criminal judge in evaluating evidence derived from artificial intelligence systems. Sci Cult. 2026; 12 (2.1). Publisher Full Text Al-Sahli MH: The Basis of Civil Accountability for Independent Artificial Intelligence: Traditional Templates or a New Vision?. Al-Huquq Journal for Legal and Economic Research. 2022; 2 (1). Al-Sanhuri AR: Al-Wasit in Commentary on Civil Law – Sources of Obligations. Dar Ihya’ Al-Turath Al-‘Arabi; 2018. Article 246 and Article 271 of Federal Decree-Law No. (25) of 2025. Ben Othman F: Artificial Intelligence: A Legal Approach. Daftar Al-Siyasa Wa Al-Qanun Journal. 2020; 12 (2). Coursera: AI Hallucinations—Understanding the Phenomenon and Its Implications. Coursera; 2025. Reference Source El Baroudy J, Albakjaji M, Khater M: Between Protection and Destruction: The Legal Tension Between Military Necessity and Cultural Heritage Protection in International Humanitarian Law. F1000Res. 2025; 14 : 1032. Publisher Full Text El-Erian M, Imad D, Sulaiman S, et al. : The role of artificial intelligence in enhancing corporate governance and achieving sustainable development. Access Just East Eur. 2026; 9 (1): 208–232. Publisher Full Text European Commission: White paper on artificial intelligence: A European approach to excellence and trust.2020. European Commission: Proposal for a Directive on liability for defective products (COM/2022/495 final).2022. Fadel BM: Alternative Means of Compensation for AI Damages: A Comparative Analytical Study. Dar al-Fikr al-Jami‘i; 2023. Faqih HMA: The Legal Basis for Compensation for Damages of AI Systems. Al-Qarar J. 2024; 1 (1). Imad D, Khater M, Abouhaiba N, et al. : Doctrinal and Comparative Assessment of GMO Liability Laws in the UAE. J Hum Rights Cult Legal Syst. 2026; 6 (1): 31–58. Publisher Full Text Issa MAM: The Adequacy of the General Rules of Civil Liability in Compensating AI Damages: A Comparative Analytical and Foundational Study. Damietta Rights Journal for Legal and Economic Studies. 2022; 5 . Khater M, Chami Y, Albakjaji M: Legal Environmental Protection and Sustainable Development in the United Arab Emirates. J Hum Rights Cult Legal Syst. 2025; 5 (2): 378–411. Publisher Full Text Marqas S: Civil Liability in Civil Law. Dar Al-Fikr Al-‘Arabi; 1995. Mucci T: The History of AI. IBM; 2026. Nasr S: Hallucinations of AI: What Causes Them? And Can They Be Overcome?. BBC NEWS; 2025. Reference Source Nggilu NM, Yassine C, Khater M: Constructing Humanitarian-Based Law: A Philosophical Analysis of the Philanthropic Legal Paradigm. Yustisia Jurnal Hukum. 2025; 14 (3): 283. Publisher Full Text Nigam A: Virtu Box. Top 11 Characteristics of Artificial Intelligence (AI) in 2026.2024. Reference Source Norvig SJR, P: Artificial Intelligence: A Modern Approach. Pearson Education; 3rd editio2010. Pagallo U: The laws of robots: Crimes, contracts, and torts. Springer; 2018. Polani SEAL: VERDICT. AI’s Limitations in the Practice of Law.2025. Reference Source Qiqieh S, Hussein E, Abou Adel M: The impact of WhatsApp on first-year students’ transition to university life. Frontiers in Education. 2025; 10 . Publisher Full Text Qitong H: AI developer not liable for hallucination errors: Chinese court. SixthTone.2026, January 28. Retrieved March 26, 2026. Reference Source Qutieshat E, Al Adwan M, Alshibli A, et al. : Governing Legal Chatbots: Ethics, Professional Responsibility, and Liability in Comparative Perspective. Res J Adv Humanit. 2026; 7 (1). Publisher Full Text Shannab ML: Liability for Acts of Inanimate Things. Dar Al-Nahda Al-‘Arabiyya; 2012. Surden H: Artificial intelligence and law: An overview. Ga State Univ Law Rev. 2019; 35 (4): 1305–1337. UAE Civil Transactions Law, Federal Decree-Law No. (25) of 2025. Footnotes * Among the most important: the UAE Charter for the Development and Use of Artificial Intelligence; the “AI Adoption Guide in Government Services” issued by the UAE Ministry of Cabinet Affairs (2023); and Federal Decree-Law No. (45) of 2021 on the Protection of Personal Data. † Generative AI hallucinations may take several forms: factual hallucinations (where the AI model produces incorrect information); hallucinated citations and sources (where the model provides fictitious sources to support its claims); contextual hallucinations (where the model misconstrues a context or invents incorrect details); inferential hallucinations (where AI infers incorrect information from the data presented to it); content-expansion hallucinations (where the AI adds unnecessary information or expands beyond the original context); and bias-driven hallucinations (where the AI produces answers reflecting biases present in its training data). ‡ Article 18 (1) of the UAE Federal Decree-Law on the Protection of Personal Data provides: “The Data Subject shall have the right to object to decisions issued through automated processing that have legal consequences or significantly affect the Data Subject, including profiling.” Article 18 (4) further provides: “The Controller shall introduce a human element in reviewing automated processing decisions upon the Data Subject’s request.”. The EU AI act, Article 50 (2) provides that providers of AI systems, including general-purpose AI systems that generate synthetic audio, image, video, or text content, must ensure that AI outputs are marked in a machine-readable format and are detectable as artificially generated or manipulated; providers must ensure their technical solutions are effective, compatible, robust, and reliable, to the extent technically feasible. § The European guidance on robots concluded that the problem of not imposing liability on the robot lies in the current legal framework rather than in the robot itself. Therefore, the prevailing view tends toward the need for a legislative amendment to the UAE Civil Transactions Law to regulate the civil liability of the robot’s designer, operator, and user. ** Regarding giving AI systems legal personality, scholars have differing opinions. One group opposes recognition, arguing that it would amount to the extinction of humanity in favor of AI and that it might absolve potential culpable parties (like the manufacturer, programmer, and developer) of liability for AI-related damages, thereby escalating those damages. Based on resolutions by the European Parliament regarding the significance of recognizing legal personality for AI and robotics, another group believes that AI must be granted legal personality ( Faqih, 2024 ). Comments on this article Comments (0) Version 1 VERSION 1 PUBLISHED 18 Apr 2026 ADD YOUR COMMENT Comment Author details Author details 1 College of Law, Abu Dhabi University, Abu Dhabi, United Arab Emirates 2 College of Law, United Arab Emirates University, Al Ain, United Arab Emirates Nagwa Abouhaiba Roles: Conceptualization, Data Curation, Formal Analysis, Investigation, Methodology, Resources, Software, Validation, Visualization, Writing – Original Draft Preparation Saed Ahmed Khouli Roles: Data Curation, Formal Analysis, Methodology, Resources, Validation, Visualization, Writing – Review & Editing Maya Khater Roles: Data Curation, Funding Acquisition, Project Administration, Supervision, Writing – Review & Editing Competing interests No competing interests were disclosed. Grant information The author(s) declared that no grants were involved in supporting this work. Article Versions (1) version 1 Published: 18 Apr 2026, 15:569 https://doi.org/10.12688/f1000research.179603.1 Copyright © 2026 Abouhaiba N et al . This is an open access article distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. Download Export To Sciwheel Bibtex EndNote ProCite Ref. Manager (RIS) Sente metrics Views Downloads F1000Research - - PubMed Central info_outline Data from PMC are received and updated monthly. - - Citations open_in_new 0 open_in_new 0 open_in_new SEE MORE DETAILS CITE how to cite this article Abouhaiba N, Khouli SA and Khater M. Towards Protecting the Injured Party from Errors and Hallucinations of Artificial Intelligence: A Contemporary Legal Perspective [version 1; peer review: 2 approved] . F1000Research 2026, 15 :569 ( https://doi.org/10.12688/f1000research.179603.1 ) NOTE: If applicable, it is important to ensure the information in square brackets after the title is included in all citations of this article. COPY CITATION DETAILS track receive updates on this article Track an article to receive email alerts on any updates to this article. TRACK THIS ARTICLE Share Open Peer Review Current Reviewer Status: ? Key to Reviewer Statuses VIEW HIDE Approved The paper is scientifically sound in its current form and only minor, if any, improvements are suggested Approved with reservations A number of small changes, sometimes more significant revisions are required to address specific details and improve the papers academic merit. Not approved Fundamental flaws in the paper seriously undermine the findings and conclusions Version 1 VERSION 1 PUBLISHED 18 Apr 2026 Views 0 Cite How to cite this report: Barafi J. Reviewer Report For: Towards Protecting the Injured Party from Errors and Hallucinations of Artificial Intelligence: A Contemporary Legal Perspective [version 1; peer review: 2 approved] . F1000Research 2026, 15 :569 ( https://doi.org/10.5256/f1000research.198134.r476859 ) The direct URL for this report is: https://f1000research.com/articles/15-569/v1#referee-response-476859 NOTE: it is important to ensure the information in square brackets after the title is included in this citation. Close Copy Citation Details Reviewer Report 24 Apr 2026 Jamal Barafi , University of Sharjah, Sharjah, United Arab Emirates Approved VIEWS 0 https://doi.org/10.5256/f1000research.198134.r476859 The manuscript addresses a timely and relevant legal issue concerning liability for artificial intelligence errors and hallucinations, with a particular focus on the UAE legal framework and comparative European approaches. The work is generally well-structured and adopts an appropriate doctrinal ... Continue reading READ ALL The manuscript addresses a timely and relevant legal issue concerning liability for artificial intelligence errors and hallucinations, with a particular focus on the UAE legal framework and comparative European approaches. The work is generally well-structured and adopts an appropriate doctrinal and analytical methodology; however, it is only partly clear and accurate in its presentation due to noticeable language weaknesses and grammatical errors. While the study design is appropriate and technically sound for a legal analysis, the explanation of the methodology remains insufficient. The paper does not rely on statistical analysis, which is not required for this type of research, and no underlying datasets are necessary. The conclusions are supported by the analysis. To strengthen the scientific quality of the article, several improvements are recommended: First, a thorough linguistic revision is necessary to ensure clarity and academic precision. Second, the paper would benefit from incorporating additional relevant legal cases & recent references to reinforce the analytical framework and support the arguments presented. Finally, the author should clearly outline the structure and division of the paper in the introduction to improve readability and logical flow. Addressing these points would significantly enhance the rigor, clarity, and applicability of the research. Is the work clearly and accurately presented and does it cite the current literature? Yes Is the study design appropriate and is the work technically sound? Yes Are sufficient details of methods and analysis provided to allow replication by others? Partly If applicable, is the statistical analysis and its interpretation appropriate? Not applicable Are all the source data underlying the results available to ensure full reproducibility? Yes Are the conclusions drawn adequately supported by the results? Yes References 1. The Legal Nature of Contracts Concluded by Artificial Intelligence According to The Uae Electronic Transactions and E-Commerce Law No. (46) of 2021 Al-Obeidi, A. , Hussein, S. 2023 24th International Arab Conference on Information Technology Acit 2023Open source preview, 2023. 2. Robotics and AI Systems: Legal Personality for AI System Under UAE Law and Islamic Jurisprudence Hussein, S. , Al-Obeidi, A. 2023 24th International Arab Conference on Information Technology Acit 2023Open source preview, 2023. Competing Interests: No competing interests were disclosed. Reviewer Expertise: International human rights law, international organizations law, environmental law, and cybercrime. I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard. Close READ LESS CITE CITE HOW TO CITE THIS REPORT Barafi J. Reviewer Report For: Towards Protecting the Injured Party from Errors and Hallucinations of Artificial Intelligence: A Contemporary Legal Perspective [version 1; peer review: 2 approved] . F1000Research 2026, 15 :569 ( https://doi.org/10.5256/f1000research.198134.r476859 ) The direct URL for this report is: https://f1000research.com/articles/15-569/v1#referee-response-476859 NOTE: it is important to ensure the information in square brackets after the title is included in all citations of this article. COPY CITATION DETAILS Report a concern Author Response 27 Apr 2026 Maya Khater , $usrAffiliation 27 Apr 2026 Author Response We sincerely thank the reviewer, Dr. Jamal Barafi, for the careful reading of our manuscript and for the constructive and insightful comments. We greatly appreciate the overall positive evaluation of ... Continue reading We sincerely thank the reviewer, Dr. Jamal Barafi, for the careful reading of our manuscript and for the constructive and insightful comments. We greatly appreciate the overall positive evaluation of our work. We sincerely thank the reviewer, Dr. Jamal Barafi, for the careful reading of our manuscript and for the constructive and insightful comments. We greatly appreciate the overall positive evaluation of our work. Competing Interests: No competing interests were disclosed. Close Report a concern Respond or Comment COMMENTS ON THIS REPORT Author Response 27 Apr 2026 Maya Khater , $usrAffiliation 27 Apr 2026 Author Response We sincerely thank the reviewer, Dr. Jamal Barafi, for the careful reading of our manuscript and for the constructive and insightful comments. We greatly appreciate the overall positive evaluation of ... Continue reading We sincerely thank the reviewer, Dr. Jamal Barafi, for the careful reading of our manuscript and for the constructive and insightful comments. We greatly appreciate the overall positive evaluation of our work. We sincerely thank the reviewer, Dr. Jamal Barafi, for the careful reading of our manuscript and for the constructive and insightful comments. We greatly appreciate the overall positive evaluation of our work. Competing Interests: No competing interests were disclosed. Close Report a concern COMMENT ON THIS REPORT Views 0 Cite How to cite this report: Muhtar MH. Reviewer Report For: Towards Protecting the Injured Party from Errors and Hallucinations of Artificial Intelligence: A Contemporary Legal Perspective [version 1; peer review: 2 approved] . F1000Research 2026, 15 :569 ( https://doi.org/10.5256/f1000research.198134.r476864 ) The direct URL for this report is: https://f1000research.com/articles/15-569/v1#referee-response-476864 NOTE: it is important to ensure the information in square brackets after the title is included in this citation. Close Copy Citation Details Reviewer Report 22 Apr 2026 Mohamad Hidayat Muhtar , Universitas Negeri Gorontalo, Gorontalo, Indonesia Approved VIEWS 0 https://doi.org/10.5256/f1000research.198134.r476864 The article adopts a comparative and analytical legal approach, focusing primarily on the UAE Civil Transactions Law and relevant European legal developments. Its central argument, that traditional civil liability rules are not fully adequate to address AI-related harms because of ... Continue reading READ ALL The article adopts a comparative and analytical legal approach, focusing primarily on the UAE Civil Transactions Law and relevant European legal developments. Its central argument, that traditional civil liability rules are not fully adequate to address AI-related harms because of the difficulties of proving fault, causation, and identifying the responsible actor within complex AI ecosystems, is both relevant and persuasive. The paper also offers several forward-looking legal responses, including strict liability, transparency obligations, compulsory insurance, compensation funds, and a stronger judicial role in assessing technical fault. Overall, the manuscript is relevant, well structured in broad terms, and suitable for publication subject to minor revision. The work is generally clear and engages with recent literature, including current legal and policy materials. I answered “Partly” to the first question because the presentation is uneven in some sections, several passages are somewhat repetitive, and a few references appear only loosely connected to the specific issue of AI liability and hallucination-based harm. The paper would be strengthened if the authors relied more consistently on literature directly relevant to civil liability for AI systems, product and technology liability, algorithmic opacity, and evidentiary burdens in civil claims. I answered “Yes” to the question on study design because, for a doctrinal and comparative legal article, the overall design is appropriate and technically sound. The manuscript identifies a clear legal problem and advances a coherent normative discussion. I answered “Partly” to the question on methods and analysis because the methodology remains somewhat general. The manuscript states that it adopts a comparative and analytical legal approach, but it would benefit from a clearer explanation of how legal sources were selected, why the UAE and EU frameworks were chosen as the primary comparison, and how the comparative legal analysis was structured. I answered “Not applicable” to the statistical analysis question because no statistical analysis was undertaken, and none is necessary for this type of legal article. I answered “No source data required” because the article is based on publicly available legal materials and secondary sources rather than datasets. I also answered “Partly” to the question of whether the conclusions are adequately supported by the results. The article does support its core claim that conventional civil liability rules face difficulty when applied to AI-related harms. However, some of the proposed solutions, particularly compulsory insurance, compensation funds, and broader judicial presumptions, would benefit from being framed more explicitly as normative policy recommendations or supported through somewhat fuller comparative legal reasoning. These are relatively limited points and can be addressed through minor revision. In particular, the authors should clarify the methodology and comparative framework, strengthen the relevance of some cited literature, distinguish more carefully between different liability models such as fault-based liability, strict liability, contractual liability, product liability, and liability for things, and revise the language for greater clarity and academic precision. Subject to these small revisions, I consider the manuscript acceptable for indexing and believe it can make a useful contribution to the literature. Is the work clearly and accurately presented and does it cite the current literature? Partly Is the study design appropriate and is the work technically sound? Yes Are sufficient details of methods and analysis provided to allow replication by others? Yes If applicable, is the statistical analysis and its interpretation appropriate? Not applicable Are all the source data underlying the results available to ensure full reproducibility? No source data required Are the conclusions drawn adequately supported by the results? Yes Competing Interests: No competing interests were disclosed. Reviewer Expertise: Law I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard. Close READ LESS CITE CITE HOW TO CITE THIS REPORT Muhtar MH. Reviewer Report For: Towards Protecting the Injured Party from Errors and Hallucinations of Artificial Intelligence: A Contemporary Legal Perspective [version 1; peer review: 2 approved] . F1000Research 2026, 15 :569 ( https://doi.org/10.5256/f1000research.198134.r476864 ) The direct URL for this report is: https://f1000research.com/articles/15-569/v1#referee-response-476864 NOTE: it is important to ensure the information in square brackets after the title is included in all citations of this article. COPY CITATION DETAILS Report a concern Author Response 27 Apr 2026 Maya Khater , $usrAffiliation 27 Apr 2026 Author Response We sincerely thank the reviewer, Mohamad Hidayat Muhtar, for the careful reading of our manuscript and for the constructive and insightful comments. We greatly appreciate the overall positive evaluation of ... Continue reading We sincerely thank the reviewer, Mohamad Hidayat Muhtar, for the careful reading of our manuscript and for the constructive and insightful comments. We greatly appreciate the overall positive evaluation of our work. We sincerely thank the reviewer, Mohamad Hidayat Muhtar, for the careful reading of our manuscript and for the constructive and insightful comments. We greatly appreciate the overall positive evaluation of our work. Competing Interests: No competing interests were disclosed. Close Report a concern Respond or Comment COMMENTS ON THIS REPORT Author Response 27 Apr 2026 Maya Khater , $usrAffiliation 27 Apr 2026 Author Response We sincerely thank the reviewer, Mohamad Hidayat Muhtar, for the careful reading of our manuscript and for the constructive and insightful comments. We greatly appreciate the overall positive evaluation of ... Continue reading We sincerely thank the reviewer, Mohamad Hidayat Muhtar, for the careful reading of our manuscript and for the constructive and insightful comments. We greatly appreciate the overall positive evaluation of our work. We sincerely thank the reviewer, Mohamad Hidayat Muhtar, for the careful reading of our manuscript and for the constructive and insightful comments. We greatly appreciate the overall positive evaluation of our work. Competing Interests: No competing interests were disclosed. Close Report a concern COMMENT ON THIS REPORT Comments on this article Comments (0) Version 1 VERSION 1 PUBLISHED 18 Apr 2026 ADD YOUR COMMENT Comment keyboard_arrow_left keyboard_arrow_right Open Peer Review Reviewer Status info_outline Alongside their report, reviewers assign a status to the article: Approved The paper is scientifically sound in its current form and only minor, if any, improvements are suggested Approved with reservations A number of small changes, sometimes more significant revisions are required to address specific details and improve the papers academic merit. Not approved Fundamental flaws in the paper seriously undermine the findings and conclusions Reviewer Reports Invited Reviewers 1 2 Version 1 18 Apr 26 read read Mohamad Hidayat Muhtar , Universitas Negeri Gorontalo, Gorontalo, Indonesia Jamal Barafi , University of Sharjah, Sharjah, United Arab Emirates Comments on this article All Comments (0) Add a comment Sign up for content alerts Sign Up You are now signed up to receive this alert Browse by related subjects keyboard_arrow_left Back to all reports Reviewer Report 0 Views copyright © 2026 Barafi J. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. 24 Apr 2026 | for Version 1 Jamal Barafi , University of Sharjah, Sharjah, United Arab Emirates 0 Views copyright © 2026 Barafi J. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. format_quote Cite this report speaker_notes Responses (1) Approved info_outline Alongside their report, reviewers assign a status to the article: Approved The paper is scientifically sound in its current form and only minor, if any, improvements are suggested Approved with reservations A number of small changes, sometimes more significant revisions are required to address specific details and improve the papers academic merit. Not approved Fundamental flaws in the paper seriously undermine the findings and conclusions The manuscript addresses a timely and relevant legal issue concerning liability for artificial intelligence errors and hallucinations, with a particular focus on the UAE legal framework and comparative European approaches. The work is generally well-structured and adopts an appropriate doctrinal and analytical methodology; however, it is only partly clear and accurate in its presentation due to noticeable language weaknesses and grammatical errors. While the study design is appropriate and technically sound for a legal analysis, the explanation of the methodology remains insufficient. The paper does not rely on statistical analysis, which is not required for this type of research, and no underlying datasets are necessary. The conclusions are supported by the analysis. To strengthen the scientific quality of the article, several improvements are recommended: First, a thorough linguistic revision is necessary to ensure clarity and academic precision. Second, the paper would benefit from incorporating additional relevant legal cases & recent references to reinforce the analytical framework and support the arguments presented. Finally, the author should clearly outline the structure and division of the paper in the introduction to improve readability and logical flow. Addressing these points would significantly enhance the rigor, clarity, and applicability of the research. Is the work clearly and accurately presented and does it cite the current literature? Yes Is the study design appropriate and is the work technically sound? Yes Are sufficient details of methods and analysis provided to allow replication by others? Partly If applicable, is the statistical analysis and its interpretation appropriate? Not applicable Are all the source data underlying the results available to ensure full reproducibility? Yes Are the conclusions drawn adequately supported by the results? Yes References 1. The Legal Nature of Contracts Concluded by Artificial Intelligence According to The Uae Electronic Transactions and E-Commerce Law No. (46) of 2021 Al-Obeidi, A. , Hussein, S. 2023 24th International Arab Conference on Information Technology Acit 2023Open source preview, 2023. 2. Robotics and AI Systems: Legal Personality for AI System Under UAE Law and Islamic Jurisprudence Hussein, S. , Al-Obeidi, A. 2023 24th International Arab Conference on Information Technology Acit 2023Open source preview, 2023. Competing Interests No competing interests were disclosed. Reviewer Expertise International human rights law, international organizations law, environmental law, and cybercrime. I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard. reply Respond to this report Responses (1) Author Response 27 Apr 2026 Maya Khater, We sincerely thank the reviewer, Dr. Jamal Barafi, for the careful reading of our manuscript and for the constructive and insightful comments. We greatly appreciate the overall positive evaluation of our work. View more View less Competing Interests No competing interests were disclosed. reply Respond Report a concern Barafi J. Peer Review Report For: Towards Protecting the Injured Party from Errors and Hallucinations of Artificial Intelligence: A Contemporary Legal Perspective [version 1; peer review: 2 approved] . F1000Research 2026, 15 :569 ( https://doi.org/10.5256/f1000research.198134.r476859) NOTE: it is important to ensure the information in square brackets after the title is included in this citation. The direct URL for this report is: https://f1000research.com/articles/15-569/v1#referee-response-476859 keyboard_arrow_left Back to all reports Reviewer Report 0 Views copyright © 2026 Muhtar M. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. 22 Apr 2026 | for Version 1 Mohamad Hidayat Muhtar , Universitas Negeri Gorontalo, Gorontalo, Indonesia 0 Views copyright © 2026 Muhtar M. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. format_quote Cite this report speaker_notes Responses (1) Approved info_outline Alongside their report, reviewers assign a status to the article: Approved The paper is scientifically sound in its current form and only minor, if any, improvements are suggested Approved with reservations A number of small changes, sometimes more significant revisions are required to address specific details and improve the papers academic merit. Not approved Fundamental flaws in the paper seriously undermine the findings and conclusions The article adopts a comparative and analytical legal approach, focusing primarily on the UAE Civil Transactions Law and relevant European legal developments. Its central argument, that traditional civil liability rules are not fully adequate to address AI-related harms because of the difficulties of proving fault, causation, and identifying the responsible actor within complex AI ecosystems, is both relevant and persuasive. The paper also offers several forward-looking legal responses, including strict liability, transparency obligations, compulsory insurance, compensation funds, and a stronger judicial role in assessing technical fault. Overall, the manuscript is relevant, well structured in broad terms, and suitable for publication subject to minor revision. The work is generally clear and engages with recent literature, including current legal and policy materials. I answered “Partly” to the first question because the presentation is uneven in some sections, several passages are somewhat repetitive, and a few references appear only loosely connected to the specific issue of AI liability and hallucination-based harm. The paper would be strengthened if the authors relied more consistently on literature directly relevant to civil liability for AI systems, product and technology liability, algorithmic opacity, and evidentiary burdens in civil claims. I answered “Yes” to the question on study design because, for a doctrinal and comparative legal article, the overall design is appropriate and technically sound. The manuscript identifies a clear legal problem and advances a coherent normative discussion. I answered “Partly” to the question on methods and analysis because the methodology remains somewhat general. The manuscript states that it adopts a comparative and analytical legal approach, but it would benefit from a clearer explanation of how legal sources were selected, why the UAE and EU frameworks were chosen as the primary comparison, and how the comparative legal analysis was structured. I answered “Not applicable” to the statistical analysis question because no statistical analysis was undertaken, and none is necessary for this type of legal article. I answered “No source data required” because the article is based on publicly available legal materials and secondary sources rather than datasets. I also answered “Partly” to the question of whether the conclusions are adequately supported by the results. The article does support its core claim that conventional civil liability rules face difficulty when applied to AI-related harms. However, some of the proposed solutions, particularly compulsory insurance, compensation funds, and broader judicial presumptions, would benefit from being framed more explicitly as normative policy recommendations or supported through somewhat fuller comparative legal reasoning. These are relatively limited points and can be addressed through minor revision. In particular, the authors should clarify the methodology and comparative framework, strengthen the relevance of some cited literature, distinguish more carefully between different liability models such as fault-based liability, strict liability, contractual liability, product liability, and liability for things, and revise the language for greater clarity and academic precision. Subject to these small revisions, I consider the manuscript acceptable for indexing and believe it can make a useful contribution to the literature. Is the work clearly and accurately presented and does it cite the current literature? Partly Is the study design appropriate and is the work technically sound? Yes Are sufficient details of methods and analysis provided to allow replication by others? Yes If applicable, is the statistical analysis and its interpretation appropriate? Not applicable Are all the source data underlying the results available to ensure full reproducibility? No source data required Are the conclusions drawn adequately supported by the results? Yes Competing Interests No competing interests were disclosed. Reviewer Expertise Law I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard. reply Respond to this report Responses (1) Author Response 27 Apr 2026 Maya Khater, We sincerely thank the reviewer, Mohamad Hidayat Muhtar, for the careful reading of our manuscript and for the constructive and insightful comments. We greatly appreciate the overall positive evaluation of our work. View more View less Competing Interests No competing interests were disclosed. reply Respond Report a concern Muhtar MH. Peer Review Report For: Towards Protecting the Injured Party from Errors and Hallucinations of Artificial Intelligence: A Contemporary Legal Perspective [version 1; peer review: 2 approved] . F1000Research 2026, 15 :569 ( https://doi.org/10.5256/f1000research.198134.r476864) NOTE: it is important to ensure the information in square brackets after the title is included in this citation. The direct URL for this report is: https://f1000research.com/articles/15-569/v1#referee-response-476864 Alongside their report, reviewers assign a status to the article: Approved - the paper is scientifically sound in its current form and only minor, if any, improvements are suggested Approved with reservations - A number of small changes, sometimes more significant revisions are required to address specific details and improve the papers academic merit. Not approved - fundamental flaws in the paper seriously undermine the findings and conclusions Adjust parameters to alter display View on desktop for interactive features Includes Interactive Elements View on desktop for interactive features Competing Interests Policy Provide sufficient details of any financial or non-financial competing interests to enable users to assess whether your comments might lead a reasonable person to question your impartiality. Consider the following examples, but note that this is not an exhaustive list: Examples of 'Non-Financial Competing Interests' Within the past 4 years, you have held joint grants, published or collaborated with any of the authors of the selected paper. You have a close personal relationship (e.g. parent, spouse, sibling, or domestic partner) with any of the authors. You are a close professional associate of any of the authors (e.g. scientific mentor, recent student). You work at the same institute as any of the authors. You hope/expect to benefit (e.g. favour or employment) as a result of your submission. You are an Editor for the journal in which the article is published. Examples of 'Financial Competing Interests' You expect to receive, or in the past 4 years have received, any of the following from any commercial organisation that may gain financially from your submission: a salary, fees, funding, reimbursements. You expect to receive, or in the past 4 years have received, shared grant support or other funding with any of the authors. You hold, or are currently applying for, any patents or significant stocks/shares relating to the subject matter of the paper you are commenting on. Stay Updated Sign up for content alerts and receive a weekly or monthly email with all newly published articles Register with F1000Research Already registered? Sign in Not now, thanks close PLEASE NOTE If you are an AUTHOR of this article, please check that you signed in with the account associated with this article otherwise we cannot automatically identify your role as an author and your comment will be labelled as a “User Comment”. If you are a REVIEWER of this article, please check that you have signed in with the account associated with this article and then go to your account to submit your report, please do not post your review here. If you do not have access to your original account, please contact us . All commenters must hold a formal affiliation as per our Policies . The information that you give us will be displayed next to your comment. User comments must be in English, comprehensible and relevant to the article under discussion. We reserve the right to remove any comments that we consider to be inappropriate, offensive or otherwise in breach of the User Comment Terms and Conditions . Commenters must not use a comment for personal attacks. When criticisms of the article are based on unpublished data, the data should be made available. I accept the User Comment Terms and Conditions Please confirm that you accept the User Comment Terms and Conditions. Affiliation ✕ refresh Please enter your institution. Note: To add your institution or organisation, start typing the name and then select the correct name from the list. Where applicable, the name will appear in both the original language and in English. Do not paste in the name. If the name does not appear in the drop-down list, we will display the information you have entered. ✕ refresh Country/Region * USA UK Canada China France Germany Afghanistan Aland Islands Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia Bosnia and Herzegovina Botswana Bouvet Island Brazil British Indian Ocean Territory British Virgin Islands Brunei Bulgaria Burkina Faso Burundi Cambodia Cameroon Canada Cape Verde Cayman Islands Central African Republic Chad Chile China Christmas Island Cocos (Keeling) Islands Colombia Comoros Congo Cook Islands Costa Rica Cote d'Ivoire Croatia Cuba Cyprus Czech Republic Democratic Republic of the Congo Denmark Djibouti Dominica Dominican Republic Ecuador Egypt El Salvador Equatorial Guinea Eritrea Estonia Ethiopia Falkland Islands Faroe Islands Federated States of Micronesia Fiji Finland France French Guiana French Polynesia French Southern Territories Gabon Georgia Germany Ghana Gibraltar Greece Greenland Grenada Guadeloupe Guam Guatemala Guernsey Guinea Guinea-Bissau Guyana Haiti Heard Island and Mcdonald Islands Holy See (Vatican City State) Honduras Hong Kong Hungary Iceland India Indonesia Iran Iraq Ireland Israel Italy Jamaica Japan Jersey Jordan Kazakhstan Kenya Kiribati Kosovo (Serbia and Montenegro) Kuwait Kyrgyzstan Lao People's Democratic Republic Latvia Lebanon Lesotho Liberia Libya Liechtenstein Lithuania Luxembourg Macao Madagascar Malawi Malaysia Maldives Mali Malta Marshall Islands Martinique Mauritania Mauritius Mayotte Mexico Minor Outlying Islands of the United States Moldova Monaco Mongolia Montenegro Montserrat Morocco Mozambique Myanmar Namibia Nauru Nepal Netherlands Antilles New Caledonia New Zealand Nicaragua Niger Nigeria Niue Norfolk Island North Korea North Macedonia Northern Mariana Islands Norway Oman Pakistan Palau Palestinian Territory Panama Papua New Guinea Paraguay Peru Philippines Pitcairn Poland Portugal Puerto Rico Qatar Reunion Romania Russian Federation Rwanda Saint Helena Saint Kitts and Nevis Saint Lucia Saint Pierre and Miquelon Saint Vincent and the Grenadines Samoa San Marino Sao Tome and Principe Saudi Arabia Senegal Serbia Seychelles Sierra Leone Singapore Slovakia Slovenia Solomon Islands Somalia South Africa South Georgia and the South Sandwich Is South Korea South Sudan Spain Sri Lanka Sudan Suriname Svalbard and Jan Mayen Swaziland Sweden Switzerland Syria Taiwan Tajikistan Tanzania Thailand The Gambia The Netherlands Timor-Leste Togo Tokelau Tonga Trinidad and Tobago Tunisia Turkey Turkmenistan Turks and Caicos Islands Tuvalu UK USA Uganda Ukraine United Arab Emirates United States Virgin Islands Uruguay Uzbekistan Vanuatu Venezuela Vietnam Wallis and Futuna West Bank and Gaza Strip Western Sahara Yemen Zambia Zimbabwe Please select your country/region. You must enter a comment. Competing Interests Please disclose any competing interests that might be construed to influence your judgment of the article's or peer review report's validity or importance. Competing Interests Policy Provide sufficient details of any financial or non-financial competing interests to enable users to assess whether your comments might lead a reasonable person to question your impartiality. Consider the following examples, but note that this is not an exhaustive list: Examples of 'Non-Financial Competing Interests' Within the past 4 years, you have held joint grants, published or collaborated with any of the authors of the selected paper. You have a close personal relationship (e.g. parent, spouse, sibling, or domestic partner) with any of the authors. You are a close professional associate of any of the authors (e.g. scientific mentor, recent student). You work at the same institute as any of the authors. You hope/expect to benefit (e.g. favour or employment) as a result of your submission. You are an Editor for the journal in which the article is published. Examples of 'Financial Competing Interests' You expect to receive, or in the past 4 years have received, any of the following from any commercial organisation that may gain financially from your submission: a salary, fees, funding, reimbursements. You expect to receive, or in the past 4 years have received, shared grant support or other funding with any of the authors. You hold, or are currently applying for, any patents or significant stocks/shares relating to the subject matter of the paper you are commenting on. Please state your competing interests The comment has been saved. An error has occurred. Please try again. Cancel Post var lTitle = "Towards Protecting the Injured Party from...".replace("'", ''); var linkedInUrl = "http://www.linkedin.com/shareArticle?url=https://f1000research.com/articles/15-569/v1" + "&title=" + encodeURIComponent(lTitle) + "&summary=" + encodeURIComponent('Read the article by '); var deliciousUrl = "https://del.icio.us/post?url=https://f1000research.com/articles/15-569/v1&title=" + encodeURIComponent(lTitle); var redditUrl = "http://reddit.com/submit?url=https://f1000research.com/articles/15-569/v1" + "&title=" + encodeURIComponent(lTitle); linkedInUrl += encodeURIComponent('Abouhaiba N et al.'); var offsetTop = /chrome/i.test( navigator.userAgent ) ? 4 : -10; var addthis_config = { ui_offset_top: offsetTop, services_compact : "facebook,twitter,www.linkedin.com,www.mendeley.com,reddit.com", services_expanded : "facebook,twitter,www.linkedin.com,www.mendeley.com,reddit.com", services_custom : [ { name: "LinkedIn", url: linkedInUrl, icon:"/img/icon/at_linkedin.svg" }, { name: "Mendeley", url: "http://www.mendeley.com/import/?url=https://f1000research.com/articles/15-569/v1/mendeley", icon:"/img/icon/at_mendeley.svg" }, { name: "Reddit", url: redditUrl, icon:"/img/icon/at_reddit.svg" }, ] }; var addthis_share = { url: "https://f1000research.com/articles/15-569", templates : { twitter : "Towards Protecting the Injured Party from Errors and Hallucinations.... Abouhaiba N et al., published by " + "@F1000Research" + ", https://f1000research.com/articles/15-569/v1" } }; if (typeof(addthis) != "undefined"){ addthis.addEventListener('addthis.ready', checkCount); addthis.addEventListener('addthis.menu.share', checkCount); } $(".f1r-shares-twitter").attr("href", "https://twitter.com/intent/tweet?text=" + addthis_share.templates.twitter); $(".f1r-shares-facebook").attr("href", "https://www.facebook.com/sharer/sharer.php?u=" + addthis_share.url); $(".f1r-shares-linkedin").attr("href", addthis_config.services_custom[0].url); $(".f1r-shares-reddit").attr("href", addthis_config.services_custom[2].url); $(".f1r-shares-mendelay").attr("href", addthis_config.services_custom[1].url); function checkCount(){ setTimeout(function(){ $(".addthis_button_expanded").each(function(){ var count = $(this).text(); if (count !== "" && count != "0") $(this).removeClass("is-hidden"); else $(this).addClass("is-hidden"); }); }, 1000); } close How to cite this report {{reportCitation}} Cancel Copy Citation Details $(function(){R.ui.buttonDropdowns('.dropdown-for-downloads');}); $(function(){R.ui.toolbarDropdowns('.toolbar-dropdown-for-downloads');}); $.get("/articles/acj/179603/198134") new F1000.Clipboard(); new F1000.ThesaurusTermsDisplay("articles", "article", "198134"); $(document).ready(function() { $( "#frame1" ).on('load', function() { var mydiv = $(this).contents().find("div"); var h = mydiv.height(); console.log(h) }); var tooltipLivingFigure = jQuery(".interactive-living-figure-label .icon-more-info"), titleLivingFigure = tooltipLivingFigure.attr("title"); tooltipLivingFigure.simpletip({ fixed: true, position: ["-115", "30"], baseClass: 'small-tooltip', content:titleLivingFigure + " " }); tooltipLivingFigure.removeAttr("title"); $("body").on("click", ".cite-living-figure", function(e) { e.preventDefault(); var ref = $(this).attr("data-ref"); $(this).closest(".living-figure-list-container").find("#" + ref).fadeIn(200); }); $("body").on("click", ".close-cite-living-figure", function(e) { e.preventDefault(); $(this).closest(".popup-window-wrapper").fadeOut(200); }); $(document).on("mouseup", function(e) { var metricsContainer = $(".article-metrics-popover-wrapper"); if (!metricsContainer.is(e.target) && metricsContainer.has(e.target).length === 0) { $(".article-metrics-close-button").click(); } }); var articleId = $('#articleId').val(); if($("#main-article-count-box").attachArticleMetrics) { $("#main-article-count-box").attachArticleMetrics(articleId, { articleMetricsView: true }); } }); var figshareWidget = $(".new_figshare_widget"); if (figshareWidget.length > 0) { window.figshare.load("f1000", function(Widget) { // Select a tag/tags defined in your page. In this tag we will place the widget. _.map(figshareWidget, function(el){ var widget = new Widget({ articleId: $(el).attr("figshare_articleId") //height:300 // this is the height of the viewer part. [Default: 550] }); widget.initialize(); // initialize the widget widget.mount(el); // mount it in a tag that's on your page // this will save the widget on the global scope for later use from // your JS scripts. This line is optional. //window.widget = widget; }); }); } close Error Close Add Reset F1000.MICROSERVICES.AFFILIATION = ''; $(document).ready(function () { $('.js-affiliations-form').each((index, form) => { new AffiliationForm({ formId: form.id, institutionErrorSelector: '.comment-enter-institution', departmentErrorSelector: '.comment-enter-department', placeSelector: '.js-add-comment-place', stateSelector: '.js-add-comment-state', zipCodeSelector: '.js-add-comment-zipcode', countrySelector: '.js-add-comment-country', countryErrorSelector: '.comment-enter-country', }); }); }); $(document).ready(function () { var reportIds = { "476855": 0, "476864": 7, "476863": 0, "476862": 0, "476861": 0, "476860": 0, "476859": 6, "476858": 0, "476857": 0, "476856": 0, }; $(".referee-response-container,.js-referee-report").each(function(index, el) { var reportId = $(el).attr("data-reportid"), reportCount = reportIds[reportId] || 0; $(el).find(".comments-count-container,.js-referee-report-views").html(reportCount); }); var uuidInput = $("#article_uuid"), oldUUId = uuidInput.val(), newUUId = "756f3635-b0fa-4933-9c39-1e3fd2f857ff"; uuidInput.val(newUUId); $("a[href*='article_uuid=']").each(function(index, el) { var newHref = $(el).attr("href").replace(oldUUId, newUUId); $(el).attr("href", newHref); }); }); An innovative open access publishing platform offering rapid publication and open peer review, whilst supporting data deposition and sharing. Browse Gateways Collections How it Works Contact For Developers Cookie Notice Privacy Notice RSS Submit Your Research Follow us © 2012-2026 F1000 Research Ltd. ISSN 2046-1402 | Legal | Partner of Research4Life • CrossRef • ORCID • FAIRSharing R.templateTests.simpleTemplate = R.template(' $text $text $text $text $text '); R.templateTests.runTests(); var F1000platform = new F1000.Platform({ name: "f1000research", displayName: "F1000Research", hostName: "f1000research.com", id: "1", editorialEmail: "
[email protected]", infoEmail: "
[email protected]", usePmcStats: true }); $(function(){R.ui.dropdowns('.dropdown-for-authors, .dropdown-for-about, .dropdown-for-myresearch');}); // $(function(){R.ui.dropdowns('.dropdown-for-referees');}); $(document).ready(function () { if ($(".cookie-warning").is(":visible")) { $(".sticky").css("margin-bottom", "35px"); $(".devices").addClass("devices-and-cookie-warning"); } $(".cookie-warning .close-button").click(function (e) { $(".devices").removeClass("devices-and-cookie-warning"); $(".sticky").css("margin-bottom", "0"); }); $("#tweeter-feed .tweet-message").each(function (i, message) { var self = $(message); self.html(linkify(self.html())); }); $(".partner").on("mouseenter mouseleave", function() { $(this).find(".gray-scale, .colour").toggleClass("is-hidden"); }); }); Sign In Remember me Forgotten your password? Sign In Cancel Email or password not correct. Please try again Please wait... $(function(){ // Note: All the setup needs to run against a name attribute and *not* the id due the clonish // nature of facebox... $("a[id=googleSignInButton]").click(function(event){ event.preventDefault(); $("input[id=oAuthSystem]").val("GOOGLE"); $("form[id=oAuthForm]").submit(); }); $("a[id=facebookSignInButton]").click(function(event){ event.preventDefault(); $("input[id=oAuthSystem]").val("FACEBOOK"); $("form[id=oAuthForm]").submit(); }); $("a[id=orcidSignInButton]").click(function(event){ event.preventDefault(); $("input[id=oAuthSystem]").val("ORCID"); $("form[id=oAuthForm]").submit(); }); }); If you've forgotten your password, please enter your email address below and we'll send you instructions on how to reset your password. The email address should be the one you originally registered with F1000. Email address not valid, please try again You registered with F1000 via Google, so we cannot reset your password. To sign in, please click here . If you still need help with your Google account password, please click here . You registered with F1000 via Facebook, so we cannot reset your password. To sign in, please click here . If you still need help with your Facebook account password, please click here . Code not correct, please try again Reset password Cancel Email us for further assistance. Server error, please try again. If your email address is registered with us, we will email you instructions to reset your password. If you think you should have received this email but it has not arrived, please check your spam filters and/or contact for further assistance. Please wait... Register $(document).ready(function () { signIn.createSignInAsRow($("#sign-in-form-gfb-popup")); $(".target-field").each(function () { var uris = $(this).val().split("/"); if (uris.pop() === "login") { $(this).val(uris.toString().replace(",","/")); } }); });
Text is read by the "Ask this paper" AI Q&A widget below.
Extraction quality varies by source — PMC NXML preserves structure
cleanly, OA-HTML may include some navigation residue, and OA-PDF can
have broken hyphenation. The publisher copy
(via DOI)
is the canonical version.