Differences

This shows you the differences between two versions of the page.

--- openemr_manual [2026/08/25 21:49] – brad.sharp
+++ openemr_manual [2026/08/26 21:25] (current) – [Module Version Compatibility] brad.sharp
@@ Line 684: / Line 684: @@
 ==== Module Version Compatibility ====
-Use this table to pick the right module version for your OpenEMR install. **If you are on any OpenEMR 8.x release, use v2.1.7 or later** — earlier versions have known faults on the 8.0.x patch line.
+**Always run the current release.** A single build covers every supported OpenEMR version — the ''src/Compat/'' shim layer adapts to the host core at runtime, so there is no version-specific build to choose.
-^ Module version ^ OpenEMR 7.0.4 ^ OpenEMR 8.0.x ^ OpenEMR 8.2 / 8.3 ^ Notes ^
+^ Module version ^ OpenEMR 7.0.2 ^ OpenEMR 7.0.4 ^ OpenEMR 8.0.x ^ OpenEMR 8.2 ^ OpenEMR 8.3 ^
-| **v2.1.7** (current) | Yes | Yes | Yes | Recommended for every supported core. Verified on 7.0.4, 8.0.0.3, 8.2.0 and 8.3.0. |
+| **v2.1.9** (current) | Yes | Yes | Yes | Yes | Yes |
-| v2.1.6 and earlier | **No** | **No** | Yes | Module pages fail with //Call to undefined method OEGlobalsBag::getKernel()//. Confirmed on 7.0.4 and on the 8.0.x line. |
-| v2.1.3 only | **No — do not install** | **No — do not install** | Yes | In addition to the above, causes an HTTP 500 during login bootstrap, taking the whole site down. |
-Earlier OpenEMR 7.0.x releases (7.0.2 and below) may work on older module versions, because those cores ship no ''OEGlobalsBag'' at all and the module's shim engages. This has not been re-verified — if you are on 7.0.x, v2.1.7 is the safe choice.
-All versions require **PHP 8.2 or later**.
+Requires **PHP 8.2 or later** on any core. v2.1.8 verified live against the ClaimRev API on 8.3.0, 7.0.4 and 7.0.2, including 837P claim submission.
-=== Why older module versions fail ===
+=== Running an older module version? ===
-OpenEMR 7.0.4 and the 8.0.x patch releases ship an ''OEGlobalsBag'' //without// the ''getKernel()'' method that the flex/master line provides. Because the real class //is// present on 8.0.x, the module's compatibility shim never activates there, so any direct call to ''getKernel()'' fails with "Call to undefined method".
+**v2.1.6 and earlier fail on OpenEMR 7.0.4 and on the 8.0.x patch line.** Module pages die with:
-  * **v2.1.3** called it during login bootstrap — the entire site returned HTTP 500.
+<code>Call to undefined method OpenEMR\Core\OEGlobalsBag::getKernel()</code>
-  * **v2.1.4** routed the service layer through ''Compat\KernelCompat::resolve()'', which fixed login, but eleven call sites in the module's own pages and templates were missed.
-  * **v2.1.7** completed that migration. One of the missed call sites rendered inside the patient dashboard, so on 8.0.x it aborted the page render and made the adjacent **Patient Portal / API** panel disappear — a symptom that did not obviously point at this module.
-If you are running OpenEMR 7.0.4 or 8.0.x on v2.1.6 or earlier and see blank module pages or a missing Patient Portal / API panel, upgrading to v2.1.7 resolves it.
+Those cores ship an ''OEGlobalsBag'' //without// ''getKernel()''. Because the class itself is present, the module's shim does not engage, and the direct call fails. Symptoms are blank module pages, or the **Patient Portal / API** panel vanishing from the patient dashboard. v2.1.3 is worse still — it fails during login bootstrap and returns HTTP 500 for the entire site.
+Upgrading to v2.1.7 or later resolves all of it.
 === Pinning a specific version ===
@@ Line 709: / Line 706: @@
 Every release stays available on Packagist. To hold a particular version:
-<code>composer require claimrevolution/oe-module-claimrev-connect:2.1.7</code>
+<code>composer require claimrevolution/oe-module-claimrev-connect:2.1.8</code>
 There is no separate branch per OpenEMR version. A single build covers both 7.x and 8.x, and older cores are supported by pinning the last release that supported them.