Differences

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

--- openemr_manual [2026/08/25 22:01] – brad.sharp
+++ openemr_manual [2026/08/26 21:25] (current) – [Module Version Compatibility] brad.sharp
@@ Line 686: / Line 686: @@
 **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 ^ OpenEMR 8.3 ^
+^ 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 | Yes |
+| **v2.1.9** (current) | Yes | Yes | Yes | Yes | Yes |
-| v2.1.8 //(in testing, not yet released)// | Yes | Yes | Yes | Yes |
-Requires **PHP 8.2 or later** on any core.
+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.
 === Running an older module version? ===
@@ Line 700: / Line 700: @@
 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 resolves all of it.
+Upgrading to v2.1.7 or later resolves all of it.
 === Pinning a specific version ===
@@ Line 706: / 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.