R-Cloud 

UAE payers do not accept free-form invoices. Every claim and every remittance has to travel through a regulator-operated transaction bus in a strict XML schema, and a provider that submits a dirty claim — or misses a resubmission window — simply does not get paid. elicoRCM is the platform that keeps that from happening: it ingests claims, scrubs them, generates eClaim XML for Shafafiya, Riayati and DHPO, submits, ingests the remittance advice that comes back, and turns denials into a worklist someone can actually finish.

The scrubbing engine is the part I care most about. Rules are configuration rather than code — regex, code-list membership, conditional, lookup-table and custom-expression rules — so an analyst can encode a payer quirk on a Tuesday afternoon instead of waiting for a release. On the other side of the cycle, MNEC denials get AI-generated medical-necessity justifications behind explicit guardrails, rate limiting, retry handling and a mandatory human review step before anything is resubmitted; PRCE pricing rejections use deterministic templates instead, because there is no judgement call worth an LLM there. Both run as tracked batch jobs that recover on startup, so a restart mid-batch resumes rather than restarts.

Multi-tenancy is enforced by collection prefixing per client code, with identity kept in a separate database from operational claim data. Alongside the platform work I rebuilt the legacy Angular 4 / PrimeNG frontend as an Angular 21 application — standalone components, Signals, zoneless change detection and a Tailwind design system — and made the heavy claim worklists usable at real volume with virtual scrolling over server-side paged loads.