OpenEMR Project Wiki - Recent changes [en]

QA and Release Process

Bradymiller — Thu, 17 Sep 2026 07:08:31 GMT

Documentation

← Older revision		Revision as of 07:08, 17 September 2026
Line 32:		Line 32:
	:**After release, redirect [[OpenEMR 8 API]] to [[OpenEMR 8.X.X API]] ('''8.3.0''')('''8.4.0''')		:**After release, redirect [[OpenEMR 8 API]] to [[OpenEMR 8.X.X API]] ('''8.3.0''')('''8.4.0''')
	:*onc b10 docs		:*onc b10 docs
	:**[[OpenEMR 8.X.X B10]] ('''8.3.0''')('''8.4.0''')		:**[[OpenEMR 8.X.X B10]] ('''8.3.0''')('''8.4.0''')('''8.4.1''')
	:**Rebuild EHI documentation and publish on website ('''AUTOMATED ON RELEASE''')		:**Rebuild EHI documentation and publish on website ('''AUTOMATED ON RELEASE''')
	:**After release, redirect [[OpenEMR 8 B10]] to [[OpenEMR 8.X.X B10]] ('''8.3.0''')('''8.4.0''')		:**After release, redirect [[OpenEMR 8 B10]] to [[OpenEMR 8.X.X B10]] ('''8.3.0''')('''8.4.0''')

OpenEMR 8.4.1 B10

Bradymiller — Thu, 17 Sep 2026 07:08:06 GMT

Created page with "=OpenEMR 8.4.1 B10 Electronic health information (EHI) export= ==Public EHI Export Format Documentation== : Online ONC Certification public URL documentation for this export can be found at: :*https://www.open-emr.org/documentation/8.4.1/b10/ {{ehi_export_instructions}}"

New page

=OpenEMR 8.4.1 B10 Electronic health information (EHI) export=
 
==Public EHI Export Format Documentation==
: Online ONC Certification public URL documentation for this export can be found at:
:*https://www.open-emr.org/documentation/8.4.1/b10/

 

{{ehi_export_instructions}}

QA and Release Process

Bradymiller — Thu, 17 Sep 2026 07:07:06 GMT

Documentation

← Older revision		Revision as of 07:07, 17 September 2026
(3 intermediate revisions by the same user not shown)
Line 5:		Line 5:

	===Testing vehicle===		===Testing vehicle===
	:*[[8.X.~~0_Demo~~\|8.X.~~0_Demo~~]] ('''8.3.0''')('''8.4.0''')('''8.4.1''')		:*[[8.X.X_Demo\|8.X.X_Demo]] ('''8.3.0''')('''8.4.0''')('''8.4.1''')

	===Code===		===Code===
	:*Create 8.X.0(rel-8X0) branch or start new minor release process on same branch ('''8.3.0''')('''8.4.0''')('''8.4.1''')		:*Create 8.X.X(rel-8X0) branch or start new minor release process on same branch ('''8.3.0''')('''8.4.0''')('''8.4.1''')
	:**to master branch, add new sql upgrade script ('''AUTOMATED ON CUT''')		:**to master branch, add new sql upgrade script ('''AUTOMATED ON CUT''')
	:**to master branch, increment version.php ('''AUTOMATED ON CUT''')		:**to master branch, increment version.php ('''AUTOMATED ON CUT''')
Line 19:		Line 19:

	===Documentation===		===Documentation===
	:*USER MANUAL at [[OpenEMR 8.X.0 Users Guide]] ('''8.3.0''')('''8.4.0''')('''8.4.1''')		:*USER MANUAL at [[OpenEMR 8.X.X Users Guide]] ('''8.3.0''')('''8.4.0''')('''8.4.1''')
	:** Redirect [[OpenEMR 8.X.0 Users Guide]] to [[OpenEMR 8.X-1.0 Users Guide]] ('''8.3.0''')('''8.4.0''')('''8.4.1''')		:** Redirect [[OpenEMR 8.X.X Users Guide]] to [[OpenEMR 8.X-1.X-1 Users Guide]] ('''8.3.0''')('''8.4.0''')('''8.4.1''')
	:*feature list will be at [[Release Features#Version 8.3.0\|Release Features]] ('''AUTOMATED ON RELEASE''')		:*feature list will be at [[Release Features#Version 8.3.0\|Release Features]] ('''AUTOMATED ON RELEASE''')
	:*install docs		:*install docs
Line 29:		Line 29:
	:**[[OpenEMR Windows Upgrade]] ('''COMPLETED; OPENEMR VERSION AGNOSTIC, SO NO MORE UPDATES NEEDED''')		:**[[OpenEMR Windows Upgrade]] ('''COMPLETED; OPENEMR VERSION AGNOSTIC, SO NO MORE UPDATES NEEDED''')
	:*onc api docs		:*onc api docs
	:**[[OpenEMR 8.X.0 API]] ('''8.3.0''')('''8.4.0''')		:**[[OpenEMR 8.X.X API]] ('''8.3.0''')('''8.4.0''')('''8.4.1''')
	:**After release, redirect [[OpenEMR 8 API]] to [[OpenEMR 8.X.0 API]] ('''8.3.0''')('''8.4.0''')		:**After release, redirect [[OpenEMR 8 API]] to [[OpenEMR 8.X.X API]] ('''8.3.0''')('''8.4.0''')
	:*onc b10 docs		:*onc b10 docs
	:**[[OpenEMR 8.X.0 B10]] ('''8.3.0''')('''8.4.0''')		:**[[OpenEMR 8.X.X B10]] ('''8.3.0''')('''8.4.0''')
	:**Rebuild EHI documentation and publish on website ('''AUTOMATED ON RELEASE''')		:**Rebuild EHI documentation and publish on website ('''AUTOMATED ON RELEASE''')
	:**After release, redirect [[OpenEMR 8 B10]] to [[OpenEMR 8.X.0 B10]] ('''8.3.0''')('''8.4.0''')		:**After release, redirect [[OpenEMR 8 B10]] to [[OpenEMR 8.X.X B10]] ('''8.3.0''')('''8.4.0''')
	:*onc main doc		:*onc main doc
	:**[[OpenEMR ONC Ambulatory EHR Certification Requirements]] ('''COMPLETED; OPENEMR VERSION AGNOSTIC, SO NO MORE UPDATES NEEDED''')		:**[[OpenEMR ONC Ambulatory EHR Certification Requirements]] ('''COMPLETED; OPENEMR VERSION AGNOSTIC, SO NO MORE UPDATES NEEDED''')

OpenEMR 8.4.1 API

Bradymiller — Thu, 17 Sep 2026 07:04:39 GMT

Created page with "= Overview = :OpenEMR API documentation for both FHIR API and Standard API. = FHIR API = :*[https://github.com/openemr/openemr/blob/rel-840/FHIR_README.md FHIR API Documentation for 8.4.1] :*[https://github.com/openemr/openemr/blob/rel-840/FHIR_README.md#fhir-api-documentation Click Here] for instructions on using Swagger, which is included in OpenEMR, to see full documentation of endpoints and testing support. :*Online links to Swagger based documentation can be f..."

New page

= Overview =
:OpenEMR API documentation for both FHIR API and Standard API.
 

= FHIR API =
:*[https://github.com/openemr/openemr/blob/rel-840/FHIR_README.md FHIR API Documentation for 8.4.1]
:*[https://github.com/openemr/openemr/blob/rel-840/FHIR_README.md#fhir-api-documentation Click Here] for instructions on using Swagger, which is included in OpenEMR, to see full documentation of endpoints and testing support.
:*Online links to Swagger based documentation can be found at [[8.4.1 Demo|8.4.1 Demo]].
:*Videos that overview OpenEMR's FHIR API:
::*[https://youtu.be/LQHNRBgg6Q8 OpenEMR FHIR Lecture Series: Lecture 1 - Overview and Use of FHIR in OpenEMR]
::*[https://youtu.be/2qr0IV9Kulg OpenEMR FHIR Lecture Series: Lecture 2 - FHIR Bulk Data in OpenEMR]
:*Specific instructions for a Clinical Summary of Care Document (CCD) request:
::*[https://github.com/openemr/openemr/blob/rel-840/FHIR_README.md#carecoordination-summary-of-care-docref-operation Instructions in API Documentation]
::*[https://github.com/openemr/openemr/issues/5284#issuecomment-1155678620 Tutorial to Generate CCDA (With Screenshots)]
 

= Standard API =
:*[https://github.com/openemr/openemr/blob/rel-840/API_README.md Standard API Documentation for 8.4.1]
:*[https://github.com/openemr/openemr/blob/rel-840/API_README.md#standard-api-documentation Click Here] for instructions on using Swagger, which is included in OpenEMR, to see full documentation of endpoints and testing support.
:*Online links to Swagger based documentation can be found at [[8.4.1_Demo|8.4.1 Demo]].
 

= Terms of use =
:*This section is required for ONC certification. OpenEMR and the API is open source and licensed under the [https://www.gnu.org/licenses/gpl-3.0.en.html GNU General Public License 3].
 

= Service Base URLs =
{{ServiceBaseURLs}}

QA and Release Process

Bradymiller — Thu, 17 Sep 2026 07:02:31 GMT

Documentation

← Older revision		Revision as of 07:02, 17 September 2026
Line 19:		Line 19:

	===Documentation===		===Documentation===
	:*USER MANUAL at [[OpenEMR 8.X.0 Users Guide]] ('''8.3.0''')('''8.4.0''')		:*USER MANUAL at [[OpenEMR 8.X.0 Users Guide]] ('''8.3.0''')('''8.4.0''')('''8.4.1''')
	:** Redirect [[OpenEMR 8.X.0 Users Guide]] to [[OpenEMR 8.X-1.0 Users Guide]] ('''8.3.0''')('''8.4.0''')		:** Redirect [[OpenEMR 8.X.0 Users Guide]] to [[OpenEMR 8.X-1.0 Users Guide]] ('''8.3.0''')('''8.4.0''')('''8.4.1''')
	:*feature list will be at [[Release Features#Version 8.3.0\|Release Features]] ('''AUTOMATED ON RELEASE''')		:*feature list will be at [[Release Features#Version 8.3.0\|Release Features]] ('''AUTOMATED ON RELEASE''')
	:*install docs		:*install docs

OpenEMR 8.5.0 Users Guide

Bradymiller — Thu, 17 Sep 2026 07:01:47 GMT

Changed redirect target from OpenEMR 8.4.0 Users Guide to OpenEMR 8.4.1 Users Guide

← Older revision		Revision as of 07:01, 17 September 2026
Line 1:		Line 1:
	#REDIRECT [[OpenEMR_8.4.~~0_Users_Guide~~]]		#REDIRECT [[OpenEMR_8.4.1_Users_Guide]]

OpenEMR 8.4.1 Users Guide

Bradymiller — Thu, 17 Sep 2026 07:01:27 GMT

Created page with "{{Languages|OpenEMR 8.4.1 Users Guide}} __TOC__ ==Users Guide== ===Main Topics=== ====Wiki Format==== :* '''OpenEMR 7.0 Users Guide''' - including multiple old feature docs upgraded for OpenEMR v 7.0x ::*HOWTO: Create a New Patient Record - OpenEMR v7 - The Patient Dashboard :::*HOWTO: Create a New Patient Record v7 - New - Search :::*HOWTO: Create a New Patient Record v7- Dashboard Links ::*OpenEMR 7..."

New page

{{Languages|OpenEMR 8.4.1 Users Guide}}
 
__TOC__
==Users Guide==

===Main Topics===
====Wiki Format====
:* '''OpenEMR 7.0 Users Guide''' - including multiple old feature docs upgraded for OpenEMR v 7.0x
::*[[HOWTO: Create a New Patient Record - OpenEMR v7|HOWTO: Create a New Patient Record - OpenEMR v7 - The Patient Dashboard]]
:::*[[HOWTO: Create a New Patient Record v7 - New - Search]]
:::*[[HOWTO: Create a New Patient Record v7- Dashboard Links]]
::*[[OpenEMR 7 New Clinic Setup|OpenEMR v7 New Clinic Essentials Setup]] - v7 pictured, most items apply since v5
::*[[HOWTO: Create and Delete Recurring Calendar Events]] shows OpenEMR v7 but good back to v5
::*[[TheCalendarNotes-v7|The OpenEMR v7 Calendar]] - updated showing v7 interface; most items apply since v6
:::*[[AllCalendarGlobals-v7]]
:::*[[AppointmentStatuses-v7]]
:::*[[Calendar_CategoriesV7]]
:::*[[Holidays_v7]]
:::*[[FlowboardV7]]
::*[[HOWTO: Apply Billing Adjustments to a Patient Account]] - v7
:* '''OpenEMR 6.0 Users Guide'''
::[[OpenEMR_v6+_Walkthrough|OpenEMR v6+ Walkthrough and New User Intro]]
::*[[A Generic Medical Encounter Workflow in OpenEMR 6.1|A Generic Medical Encounter Workflow in OpenEMR 6.x]]
::*[[The OpenEMR 6.0+ Patient Portal|The OpenEMR 6.0+ Patient Portal Overview]]
:::*[[The_Portal_Dashboard|The Portal Dashboard]]
:::*[[HOWTO: Activate the Patient Portal v6.0+]]
:::*[[HOWTO Activate a Patient's portal access - v6.0|HOWTO: Activate a Patient's portal access - v6.0+]]
:::*[[HOWTO: Patient self-registration in the Native Patient Portal v6.1|HOWTO: Patient self-registration in the Patient Portal, OpenEMR v6.1]].
:::*[[Patient Use of the Patient Portal in OpenEMR v6+|Patient Use of the Patient Portal in OpenEMR v6.0+]]
:::*[[HOWTO: Send Files To A Patient Portal Account]] in OpenEMR v6+
::*'''Billing'''
:::*[[HOWTO: Add Or Edit A Billing Code In OpenEMR]] -- for v7 but applies to 4.x+
:::*[[HOWTO:_Create_A_Claim-_Ready_Encounter|HOWTO: Create A Claim- Ready Encounter]]
:::*[[List of OpenEMR Data Fields Required For Insurance Claims]] OpenEMR v4.x +
:::*[[OpenEMR 6.x Billing - Claims Workflows]] OpenEMR v4.x +
:::*[[OpenEMR 6.x Billing - Process Payments]] OpenEMR v4.x +
:* '''OpenEMR 5.0x Workflows''':
::* [[Quick Reference Handout 4.2|Quick Reference Handout - v4.2]]
::* [[Getting Started 4.1.3|Getting Started - v4.1.3]]
::* [[Main Screen & Navigation 4.1.3|Main Screen & Navigation - v4.1.3]]
::* [[New Clinic OpenEMR Setup 4.1.3|New Clinic OpenEMR Setup - v4.1.3]]
::* [[Patient_Portal_Document_Templates|OpenEMR and the Patient Portal Document Templates v5.0+]]
::* [[HOWTO:_Create_Custom_Document_Template_Categories]] OpenEMR v5+

:* '''OpenEMR 4.2x Workflows''':
::* [[Adding a New Patient 4.1|Adding a New Patient]]
:::*[[Quickie External ID Mask Tutorial|Quickie External ID Mask Tutorial v4.x +]]
:::*[[HOWTO: Customize A Demographics User Defined Field|HOWTO: Customize A Demographics User Defined Field v4.x +]]
::* [[Using the Calendar 4.1|Using the Calendar]]
::* [[New Encounters & Coding 4.1|New Encounters & Coding]]
::* [[Issues & Immunizations 4.1|Issues & Immunizations]]
::* [[Patient Notes & Transactions 4.1|Patient Notes & Transactions]]
::* [[Basic Billing 4.1|Basic Billing]]
::* [[Sample: Applying Adjustment to Pt Account|Sample: Applying Adjustment to Pt Account]]
::* [[Accounting & Receivables 4.1|Accounting & Receivables]]
::* [[Reporting 4.1|Reporting]]

===Supplementary Topics===
:*ACL
::*[[Basic User ACLs In OpenEMR And How To Customize Them]]
::*[[Access_Controls_Listing|Access Control List]]
::*[[Adding_and_Removing_User_Permissions|Changing Permissions]]
::*[[ACL_Fine_Granular_Control|ACL Fine Granular Control]]
:*Apps
::*[[Apps]]
:* Backup
::Lest you rue the day.
::*[[OpenEMR_Backup_Tools#Linux|Linux]].
::*[[OpenEMR_Backup_Tools#Windows|Windows]].
:::Take note of this [http://sourceforge.net/p/openemr/discussion/202505/thread/2a87885a/?page=0 Forum thread].
::*[[Macrium_Reflect_Backup_and_Recovery|System Image]]: Creation and recovery in 32/64 bit devices.
:*Billing
::*837P
:::*[[X12_837p_Reference|X12 837p Reference]], Version 4010.
:::*[https://apps.availity.com/availity/AvHelp/Glossary/Loops_and_Segments_in_EDI_Claims_X12_837_Files.htm Version 5010].
::*[[Charges Panel]].
::*[[Credit_Card_Processing_Inside_OpenEMR|Credit Card Processing]].
::*[[Review_EDI_History_Module|Review EDI History Module]].
::*[[Credit_Card_Processing_Inside_OpenEMR|Credit Card Processing]].
::*[[HOWTO: Add Custom Service Codes To The Fee Sheet - Updated]] - applies to all versions > 4.0 but written for v7
::*[[OpenEMR_4.2.1_Fee_Sheet Review Button_and_CPT4_Link |Fee Sheet Review Button and CPT4 Link]]
::*[[Add Red Notification to Patient Billing Widget|Red Notification, Patient Billing Widget]].
::*[[Media:Patient_ledger.odt|Patient Ledger]]
::*Patient Statement with [[Media:Setting_up_the_statements_dunning_for_OpenEmr.pdf|Dunning Messages]].
::*[[HOWTO: Locate A Specific Insurance Claim’s Batch File]] for all versions since 4.0
::*[[Superbills in OpenEMR]] - shows OpenEMR v7 but applies to all vers
:*Brute Force Login Prevention
::*[[Brute Force Login Prevention]]
:*Clinical Decision Rules - Different interface versions are shown but controls work the same since OpenEMR v4.x
::*[[CDR in OpenEMR 5 - Survey of CDRs]].
::*[[CDR in OpenEMR 5 - Create a CDR]].
::*[[CDR in OpenEMR 5 - Using a CDR]].
::*[[CDR in OpenEMR 5 - Administering CDRs]]
::*[[CDR User Manual]]
::*[[Media:Clinical_Decision_Rules_Manual.pdf|CDR Guide]]: How to add rules for Clinical Quality Measures.
:*Coding
::*[[Configure OpenEMR for ICD-10]].
:*Communication
::*[[HOWTO: Use OpenEMR's Dated Reminder|Dated Reminders]].
::*[[Direct]]: Direct Project guide.
::*[[Mercury Mail Configuration in Windows]].
::*[[Patient Portal|Patient Portal in OpenEMR pre- v6.0]].
::*[[Short Message Service]].
::*[[Sms_and_Email_Notification_Howtos|SMS & Email]].
::*Comlink Telehealth Module Documentation OpenEMR v 7.0.1
:::*[[Comlink Telehealth Module Providers Instructions]]
:::*[[Comlink Telehealth Module Patient Instructions]]
:*Data Import
::*[[Import_Standard_Tables|Standard Tables]]: An ICD9, ICD10, SNOMED & RxNorm import guide.
::*[[Import_RxNorm_and_SNOMED_Tables|RxNorm and SNOMED]].
::*[[Code_Types|Other Data Sets - Other Methods]].
:*Diagnostic Studies
::* [[How to Add Covid-19 or any other single test to OpenEMR Procedures|How to Add Covid-19 or any other single test to OpenEMR Procedures]].
::* [[Procedure configuration & order process]].
::: Step wise explanation of how to configure '''Procedures''':
:::* [[Media:Process+4-5-0+Diagnostic+Laboratories+Orders+Ver+4-0.pdf|Diagnostic Laboratories Orders]].
:::* [[Media:Process+4-5-1+Laboratory+Catalogue+Configuration+Ver+4-0.pdf|Laboratory Catalogue Configuration]].
:::* [[Media:Process+4-5-2+Laboratory+Orders+and+Results+Ver+4-0.pdf|Laboratory Orders & Results]].
:::* [[Procedures_Module_Configuration_for_Manual_Result_Entry|Procedures Module Configuration for Manual Result Entry]]: A pictorial guide.
:::* [[Media:LEN_User_Documentation_v1.0.pdf‎|Laboratory Exchange User Documentation]]: Communication with external laboratory facility.
::*[[Sample Create and Use Procedure Orders 4.1-4.2|Sample: Create and Use Procedure Orders 4.1-4.2]]
:*Documents
::*[[HOWTO: Use the OpenEMR DICOM Web Viewer]] – v7 Update
::*[[Faxing & Scanning]].
::*[[Templates for Patient Documents|Templates for Patient Documents OpenEMR v4.2]]: How to download, modify & upload templates.
::*[[Patient Education]]: Providing preprinted materials to patients.
::*[[Document Categories]]: Customizing document categories.
::*[[HOWTO:Associate A Document Attachment To An Encounter]]: good from OpenEMR v6? OpenEMR v7 shown
:*Efficiency Tools
::*[[Patient_Flow_Board|Patient Flow Board]].
::*[[Recall_Board|Recall Board]].
::*[[Random_Drug_Screening|Random Drug Screening]].
::*[[Review_EDI_History_Module|Review: EDI History Module]].
:*Forms
::*[[HOWTO: Customize The Issue Types List]]
::*[[OpenEMR_Contributed_Forms|Contributed Forms]]: 60 forms.
::*[[Social Screening Tool]]: Form that measures Social Determinants of Health (SDOH). This form and the documentation are a good example and tutorial for building a form.
::*[[HOWTO_Register_OpenEMR_Contributed_Forms|HOWTO Register OpenEMR Contributed Forms]] OpenEMR 5.0.x
:::*[[CAMOS module]]: An intuitive interface for text organization and insertion in a patient's chart.
:::*[[Eye_Exam|Eye Exam]]: The Comprehensive Ophthalmic Exam.
:::*[[Graphic_pain_map|Graphic Pain Map]]: Image uploading & annotations guide.
:::*[[Previews of Forms Distributed with OpenEMR|Form Previews]].
:::*[[Track Anything Form|Track Anything]]: A graph generating form for any data.
::*Layout Based Visit Forms.
:::*[[LBV Forms]].
:::*[[Sample Layout Based Visit Form]].
:::*[[LBV FORMS FOR OPHTHALMOLOGY]]: A pictorial tutorial.
:::*[[Layout Based Validation]].
::*[[Nation Notes]]: LBV Form with a WYSIWYG editor.
:::*[[Sample NationNotes Form]].
::*[[Simple Note Templates|Simple Note Templates]].
:*Illustration
::*[[Videos and Animations]].
:*Meaningful Use
::*[[OpenEMR 4.2.0 AMC Reports]].
:*Multi-factor Authentication
::*[[Multi-factor Authentication]]
:*Navigation
::*[[Cross Reference Views]].
::*[[OpenEMR Search| Find - Search HowTos]]: Finding things in OpenEMR - various search methods used.
::*[[Patient Note and Form Searching]].
::*[[HOWTO: Change Search Columns in Patient Finder|HOWTO: Change Search Columns in Patient Finder]].
:*Practice Setup
::*[[Facility Specific User Information]].
::*[[User Settings]]
::*[[Role Based Menus]]
:*Prescription
::*[[OpenEMR_ePrescribe|ePrescribing]].
::*[[Pharmacy Dispensary Module]].
::*[[Using OpenEMR Inventory-Dispensary Module for Non- Pharmaceutical Products]].
:*Reports
::*[[End of Day Report]].
:*Scheduling
::*[[Calendar_Categories|Calendar Categories]]: Guide to change name, color & interval of appointments.
::*[[Calendar_Holidays|Holidays]]: How to set up holidays for the clinic.

=== Configuration Topics ===
==== General ====
:* [[Access Controls Listing|Description of Access Controls]]: Documentation of the settings in Administration->ACL.
:* [[ACL_Fine_Granular_Control|ACL Fine Granular Control]]: A guide with examples and screenshots.
:* [[Client Sided Validation]]
:* [[HOWTO: Create And Use Database Views|HOWTO: Create And Use Database Views]].
:* [[HOWTO: Edit a List in OpenEMR]].
:* [[OpenEMR Backup Tools| Backup - Backup Tools]]: Backup Methods and Scripts in OpenEMR - Protecting Your Data.
:* [[OpenEMR Database Conversion Tools| Database - Database Conversion Tools]]: Changing Data For Use in OpenEMR.
:* [[Obliteration_of_OpenEMR|OpenEMR Deletion]].
:* [[OpenEMR Form Creation Tools| Forms - Form Creation Tools]]: Tools for editing existing forms and creating new forms in OpenEMR.
:* [[DIY_IMPLEMENTATION_OF_OPENEMR|DIY Implementation of OpenEMR]]: A do-it-yourself guide with encouragements.
:* [[Hosted_OpenEMR|Installation in a hosted environment]].
:* [[OpenEMR Layout Selection| Layout Selection]]: Configuration and selection of three visual layouts with comparison screenshots.
:* [[OpenEMR Internationalization Configuration| Language Translation Configuration]]: Translation of OpenEMR into your native language.
:* [[OpenEMR Multiple Sites Module|Multiple Sites Module]]: Configuration and maintenance of multiple sites from one OpenEMR instance.
:* [[Operating Systems]].
:* [[Securing OpenEMR]]: Advice from the community on how to secure an OpenEMR instance.
:* [[settings_lists|Description of Settings]]: Documentation of the settings in Administration->Globals and Administration->Lists.
:* [[OpenEMR Patient Statement Printing and Configuration Howtos| Patient Statement Printing/Configuration Howtos]].
:* [[MySQL/MariaDB SSL Support Howto]]
:* [[SSL Installation Howtos|SSL Install Howtos]].
:* [[OpenEMR UTF-8 Upgrade Howto|UTF-8 Upgrade Howto]]: Configuration of non-Latin scripts.
:* [[Dual_Upgrade_of_OpenEMR_and_XAMPP_in_Windows|Windows Package Dual Upgrade]]: Simultaneous upgrades of XAMPP and OpenEMR.

==== Modules ====
:* [[OpenEMR Billing Setup Howtos| Billing - Billing Setup Howtos]]: How To Configure and Use OpenEMR For Billing.
:* [[OpenEMR Calendar| Calendar - Using The Calendar As A Tool]]: Using The Calendar As A Tool in OpenEMR.
:* [[CouchDB Documents Module]] - Using CouchDB to store patient documents.
:* [[Mercury Mail Configuration in Windows|Mercury Mail Configuration in Windows XAMPP]].
:* [[Pharmacy Dispensary Module Configuration|Pharmacy Dispensary Module Configuration]].
:* [[Sms and Email Notification Howtos|Sms/Email Notification Howtos]].
:* [[Z&H's CCDA Module]]: Setup and Configuration of Z&H's Carecoordination module.
:* [[HOWTO Setup and Use OpenEMR Groups Module|HOWTO Setup and Use OpenEMR Groups Module]].
:* [[Patient Privacy Module]] - Setup and use of MI-Squared's Patient Privacy Module
:* [[Custom Modules for OpenEMR|Custom Modules for OpenEMR]]: Modules not in the released codebase but available for installation. Preview here and contact the dev.

 

==Video Tutorials==
===Choosing a User Interface - OpenEMR 5.0.0===
{{#ev:youtube|-XtYLXFPo8g|300||'''Choosing a User Interface - OpenEMR 5.0.0'''}}
===Adding a New Patient - OpenEMR 5.0.0===
{{#ev:youtube|q_yXYgg7EdE|300||'''Adding a New Patient - OpenEMR 5.0.0'''}}

===OpenEMR 5.0.x - Intro 1 Walkthrough===
{{#ev:youtube|TRb3jBBlPgQ|300||'''MI2-OpenEMR 5 - Intro 1 Walkthrough'''}}
===OpenEMR 5.0.x - CDR Survey===
{{#ev:youtube|zpG3PlnnEPY|300||'''MI2 OpenEMR5 CDR Survey'''}}
===OpenEMR 5.0.x - Create a CDR===
{{#ev:youtube|Y3f5PaI_gJw|300||'''MI2 OpenEMR5 Create a CDR'''}}
===OpenEMR 5.0.x - Use a CDR===
{{#ev:youtube|7ztgKk3_Vew|300||'''MI2 OpenEMR5 Use a CDR'''}}

===OpenEMR 5.0.x - Getting Around===
{{#ev:youtube|CdSZzau2Pvw|300||'''Getting Around 4.2.x'''}}
===OpenEMR 5.0.x - New Clinic: Facility Settings===
{{#ev:youtube|667NXhWlLpA|300||'''Facility Settings'''}}
===OpenEMR 5.0.x - New Clinic: User Accounts===
{{#ev:youtube|-s8dYXEsaVQ|300||'''User Accounts'''}}
===OpenEMR 5.0.x - New Clinic: Create Patient Record===
{{#ev:youtube|QVirVE8idF8|300||'''Create Patient Record'''}}
===OpenEMR 5.0.x - Data Forms===
{{#ev:youtube|Q3gO_uHuKj0|300||'''Data Forms 4.2.x'''}}

===Getting Started===
{{#ev:youtube|QUCkplnEhcc|300||'''OpenEMR Tutorial - Getting Started'''}}

===Setting up your clinic===
{{#ev:youtube|gocY0-vgeTI|300||'''OpenEMR Tutorial - Setting up your clinic (part 1)'''}}
{{#ev:youtube|kD9LGIou0ug|300||'''OpenEMR Tutorial - Setting up your clinic (part 2)'''}}

===Adding a new patient===
{{#ev:youtube|q_yXYgg7EdE|300||'''Adding a New Patient - OpenEMR 5.0.0'''}}

===Using your calendar===
{{#ev:youtube|gocY0-vgeTI|300||'''OpenEMR Tutorial - Using your calendar'''}}

===Documenting a visit/encounter===
{{#ev:youtube|39GvnyPn6d4|300||'''OpenEMR Tutorial - Documenting a visit/encounter'''}}

===Issues, Problems & Immunizations===
{{#ev:youtube|AGN6Ivrv_rI|300||'''Openemr Tutorial - Issues, Problems & Immunizations'''}}

===Billing and Claim Generation===
{{#ev:youtube|bVizIGgC1Ts|300||'''OpenEMR Tutorial - Billing and Claim Generation'''}}

===EOBs, Payments & Accounts Receivables===
{{#ev:youtube|fjmyLg6hGgI|300||'''Openemr Tutorial - EOBs, Payments & Accounts Receivables'''}}

==Frequently Asked Questions (FAQ)==
:Plan to post questions here that are frequently asked on the forums for OpenEMR version 7.0.1.

==Acknowledgments==
:*[[OpenEMR_Acknowledgments|OpenEMR Acknowledgments Page]]
 

[[Category:User Guide]][[Category:Video Tutorial]][[Category:Frequently Asked Questions]]

QA and Release Process

Bradymiller — Thu, 17 Sep 2026 07:00:17 GMT

Code

← Older revision		Revision as of 07:00, 17 September 2026
Line 8:		Line 8:

	===Code===		===Code===
	:*Create 8.X.0(rel-8X0) branch ('''8.3.0''')('''8.4.0''')		:*Create 8.X.0(rel-8X0) branch or start new minor release process on same branch ('''8.3.0''')('''8.4.0''')('''8.4.1''')
	:**to master branch, add new sql upgrade script ('''AUTOMATED ON CUT''')		:**to master branch, add new sql upgrade script ('''AUTOMATED ON CUT''')
	:**to master branch, increment version.php ('''AUTOMATED ON CUT''')		:**to master branch, increment version.php ('''AUTOMATED ON CUT''')

OpenEMR Wiki Home Page

Bradymiller — Thu, 17 Sep 2026 06:58:53 GMT

Newest Developments

← Older revision		Revision as of 06:58, 17 September 2026
(One intermediate revision by the same user not shown)
Line 51:		Line 51:
	* '''[https://www.open-emr.org/demo/ 8.4.0]''' — Current stable release <span style="color:green">● stable</span>		* '''[https://www.open-emr.org/demo/ 8.4.0]''' — Current stable release <span style="color:green">● stable</span>
	===== Prior Versions =====		===== Prior Versions =====
			<!--* [[8.4.1 Demo\|8.4.1]]-->
	<!--* [[8.4.0 Demo\|8.4.0]]-->		<!--* [[8.4.0 Demo\|8.4.0]]-->
	* [[8.3.0 Demo\|8.3.0]]		* [[8.3.0 Demo\|8.3.0]]
Line 60:		Line 61:
	''These demos may contain features known not to work yet.''		''These demos may contain features known not to work yet.''
	* [[Development Demo\|8.5.0]] <span style="color:red">● development</span>		* [[Development Demo\|8.5.0]] <span style="color:red">● development</span>
			* [[8.4.1 Demo\|8.4.1]] <span style="color:red">● development</span>
	* [[Development Demo#UP FOR GRABS Development Demos\|Up For Grabs]] — git branches		* [[Development Demo#UP FOR GRABS Development Demos\|Up For Grabs]] — git branches

QA and Release Process

Bradymiller — Thu, 17 Sep 2026 06:57:23 GMT

Testing vehicle

← Older revision		Revision as of 06:57, 17 September 2026
Line 5:		Line 5:

	===Testing vehicle===		===Testing vehicle===
	:*[[8.X.0_Demo\|8.X.0_Demo]] ('''8.3.0''')('''8.4.0''')		:*[[8.X.0_Demo\|8.X.0_Demo]] ('''8.3.0''')('''8.4.0''')('''8.4.1''')

	===Code===		===Code===

8.4.1 Demo

Bradymiller — Thu, 17 Sep 2026 06:56:54 GMT

Created page with "==Overview== OpenEMR 8.4.1 demo includes daily build of the OpenEMR 8.4.1 codebase. (Daily at 8:30 am UTC time these demos reset.) The API (Swagger) links contain FHIR and API documentation, which allow testing. ==Demo Credentials== ===Standard Demo Credentials in ALL Demos=== * OpenEMR - user:admin pass:pass ===Special Demo Credentials in Demos WITH Demo Data=== :'''OpenEMR''' ::{| border="1" cellspacing="1" cellpadding="5" |- | '''Username''' | '''Password'''..."

New page

==Overview==
OpenEMR 8.4.1 demo includes daily build of the OpenEMR 8.4.1 codebase. (Daily at 8:30 am UTC time these demos reset.)

The API (Swagger) links contain FHIR and API documentation, which allow testing.

 

==Demo Credentials==
===Standard Demo Credentials in ALL Demos===
* OpenEMR - user:admin pass:pass

===Special Demo Credentials in Demos WITH Demo Data===
:'''OpenEMR'''
::{| border="1" cellspacing="1" cellpadding="5"
|-
| '''Username'''
| '''Password'''
| '''Description'''
|-
| admin
| pass
| Administrator
|-
| physician
| physician
| Physician(more access than clinician)
|-
| clinician
| clinician
| Clinician(less access than physician)
|-
| accountant
| accountant
| Accountant
|-
| receptionist
| receptionist
| Front desk receptionist
|}
:'''Patient Portal'''
::{| border="1" cellspacing="0" cellpadding="5"
|-
| '''Patient Username'''
| '''Password'''
| '''Email'''
|-
| Phil1
| phil
| heya@invalid.email.com
|-
| Susan2
| susan
| nana@invalid.email.com
|}
 

==Demo==
===Without demo data===
* OpenEMR: [https://nine.openemr.io/openemr/index.php https://nine.openemr.io/openemr] 
* Onsite Patient Portal: [https://nine.openemr.io/openemr/portal/index.php https://nine.openemr.io/openemr/portal] 
* API (Swagger) User Interface: [https://nine.openemr.io/openemr/swagger/index.html https://nine.openemr.io/openemr/swagger] 

===With demo data===
* OpenEMR: [https://nine.openemr.io/a/openemr/index.php https://nine.openemr.io/a/openemr] 
* Onsite Patient Portal: [https://nine.openemr.io/a/openemr/portal/index.php https://nine.openemr.io/a/openemr/portal] 
* API (Swagger) User Interface: [https://nine.openemr.io/a/openemr/swagger/index.html https://nine.openemr.io/c/openemr/swagger] 

===Logs===
* PHP log file: https://nine.openemr.io/log/logPhp.txt 
* Setup log file: https://nine.openemr.io/log/logSetup.txt

Weekly Meetings:2026-09-15

David Eschelbacher — Wed, 16 Sep 2026 09:57:37 GMT

← Older revision		Revision as of 09:57, 16 September 2026
Line 3:		Line 3:
	'''Attendees:''' Brady Miller, Stephen Nielson, Stephen Waite, Eric Stern (OCE), Sherwin Gaddis, Simon Quigley (new), David Eschelbacher.		'''Attendees:''' Brady Miller, Stephen Nielson, Stephen Waite, Eric Stern (OCE), Sherwin Gaddis, Simon Quigley (new), David Eschelbacher.

	'''PDF version:''' [https://www.open-emr.org/wiki/images/x/xx/OpenEMR_Weekly_Meeting_Detailed_Summary_2026-09-15.pdf 📄 OpenEMR Weekly Meeting Detailed Summary 2026-09-15.pdf]		'''PDF version:''' [https://www.open-emr.org/wiki/images/f/f1/OpenEMR_Weekly_Meeting_Detailed_Summary_2026-09-15.pdf 📄 OpenEMR Weekly Meeting Detailed Summary 2026-09-15.pdf]

	== New Participant: Simon Quigley ==		== New Participant: Simon Quigley ==

File:OpenEMR Weekly Meeting Detailed Summary 2026-09-15.pdf

David Eschelbacher — Wed, 16 Sep 2026 09:56:36 GMT

David Eschelbacher uploaded File:OpenEMR Weekly Meeting Detailed Summary 2026-09-15.pdf

New page

Weekly Meetings:2026-09-15

David Eschelbacher — Wed, 16 Sep 2026 09:53:01 GMT

Created page with "''← All meeting summaries'' | Join the call '''Attendees:''' Brady Miller, Stephen Nielson, Stephen Waite, Eric Stern (OCE), Sherwin Gaddis, Simon Quigley (new), David Eschelbacher. '''PDF version:''' [https://www.open-emr.org/wiki/images/x/xx/OpenEMR_Weekly_Meeting_Detailed_Summary_2026-09-15.pdf 📄 OpenEMR Weekly Meeting Detailed Summary 2026-09-15.pdf] == New Part..."

New page

''← [[OpenEMR Weekly Conference Call Meeting Notes|All meeting summaries]]'' | [[OpenEMR Once Weekly Conference Call Details|Join the call]]

'''Attendees:''' Brady Miller, Stephen Nielson, Stephen Waite, Eric Stern (OCE), Sherwin Gaddis, Simon Quigley (new), David Eschelbacher.

'''PDF version:''' [https://www.open-emr.org/wiki/images/x/xx/OpenEMR_Weekly_Meeting_Detailed_Summary_2026-09-15.pdf 📄 OpenEMR Weekly Meeting Detailed Summary 2026-09-15.pdf]

== New Participant: Simon Quigley ==
* '''Returning contributor.''' Was involved with OpenEMR as a developer previously and is coming back to it for a specific project. GitHub: tsimonq2. Works at Altispeed Technologies.
* '''Deploys OpenEMR via Ansible rather than Docker,''' on a yearly upgrade cycle. Stated goal: upstream as much as possible rather than carry a fork.
* '''Has two open pull requests,''' both driven by requests from a client practice.

:''Simon Quigley is a Debian Developer and long-time Ubuntu contributor — relevant context for how he framed his questions about project policy, since Debian has formal governance procedures for exactly the kind of question he raised about AI usage.''

=== PR 13795 — LBF Statements Module ===
Pull request: https://github.com/openemr/openemr/pull/13795
* '''What it does:''' adds a module ("Form statements" in the interface, "LBF statements" internally) that generates prose sentences from numeric values already recorded on a layout-based form, and writes the resulting paragraph into a textarea on that same form.
* '''The worked example from the PR:''' a value between 0.0000 and 1.0000 produces "This value is mildly recorded"; 1.0001 to 2.0000 produces the moderate sentence; above that, the severe one. An administrator defines those bands once, and the sentence is then generated consistently rather than a clinician remembering which template matches which cutoff.
* '''Rule types supported:''' numeric bands, ratios between two numeric fields, and list or text tokens. Overlapping bands on the same field are rejected at save time, with database-level locking so two administrators cannot create a conflict concurrently.
* '''Why not Nation Notes or Text Notes,''' addressed directly in the PR: both are template-insertion tools where a person reads the chart, picks a template, and writes. Neither reads the other fields on the form instance, so neither can act on the recorded value. Switching the destination field to Nation Notes would also change its data type and discard existing form data.
* '''Design consequence:''' the measurements stay ordinary LBF fields, so graphing, printing, and export continue to work, and the generated paragraph is written as ordinary form data — meaning stock LBF printing picks it up with no changes.
* '''Scope:''' roughly 5,000 lines across 33 files, entirely self-contained within the module directory with no touch points into core. Includes isolated unit tests; patch coverage reported around 67%. CodeRabbit rated it complex, roughly an hour of review.
* '''Rules require the admin/super ACL; generation requires encounters/notes.'''

:''Correction to the meeting notes: this PR is not an autocomplete feature and does not involve Nation Notes. The PR text explicitly argues against the Nation Notes approach. The autocomplete framing appears to have arisen during the call as participants worked out what the module did — the discussion moved from "is the main feature autocomplete?" to a narrower understanding by the end.''

=== PR 13852 — Window Envelope Statements ===
Pull request: https://github.com/openemr/openemr/pull/13852
* '''What it does:''' adds a Billing global, "Statement envelope," that repositions the clinic return address and patient address on printed statements so they line up with the windows of a double-window envelope.
* '''The problem:''' stock OpenEMR statements print addresses where they do not align with envelope windows, so a folded statement shows neither sender nor recipient through the glass.
* '''Options provided:''' None (unchanged), US #9 double-window, US #10 double-window, or Custom — which accepts the measurements printed on the envelope carton in inches or centimeters, including fractions such as 3/8 and 1-3/16.
* '''Also included:''' payments are directed to the facility mailing address rather than the physical clinic address when a mailing address is present, with fallback to the physical address so the window is never blank.
* '''Implementation note:''' geometry and address fitting live in a single StatementEnvelope class shared by the statement template and the EOB PDF path. Long addresses wrap and shrink to fit. HTML, plain text, and portal statements all honor the setting.
* '''Stephen Waite posted a review on this PR the same day as the meeting,''' asking that the render callback be moved out of globals.inc.php into a class under src/ rendering a Twig template, following the existing telehealth config pattern, with JavaScript as a separate asset rather than inline.

:''This one is a straightforward core change rather than a module, and it is the kind of small, self-contained contribution that fits the "bring in straightforward PRs" position expressed later in the meeting.''

=== An Unanswered Question ===
* '''Both PR descriptions ask whether AI assistance is welcome in OpenEMR contributions,''' noting that Simon did not use it and that Debian recently passed a general resolution on the subject. The question does not appear to have been answered on either PR or during the meeting.

:''Worth answering, given how central AI-assisted development has become to the project's own workflow — a contributor asking in good faith whether it is acceptable, and receiving no reply, is a poor signal. A short written position would settle it for everyone.''

== Module Policy — What Belongs in Core ==

=== The Concern Raised ===
* '''If new modules are directed to Packagist and no new modules are accepted into core, features arrive unreviewed.''' Nobody knows their quality, nobody knows how they are built, and module authors get no feedback. As the project upgrades, it will not know which modules it has broken.
* '''The worry stated plainly:''' a parallel ecosystem of important features develops that the admins are too busy to look at, making it hard for OpenEMR to progress as a product.

=== The Clarification ===
* '''Being a module does not mean being outside the code base.''' Core modules exist and are not leaving. The test is applicability, not packaging.
* '''The working rule offered:''' if a feature is needed by a large share of users, it belongs in core. If it talks to a third-party service, that is a clear line against — OpenEMR should not be opinionated about which vendors a practice plugs into.
* '''Applied to the case at hand:''' if the same feature had been submitted embedded rather than as a module, it would have been considered for inclusion on its merits. Doing it properly as a module should not count against it.
* '''Conversely,''' the fax module is unlikely to be removed because clinics need it, whereas a vendor could equally build their own fax integration and distribute it independently.
* '''The design intent behind the module work, restated:''' the goal is to address upgradability and ease of installation — a packaging problem more than a distribution problem. Anything included by default would still get the same review as a direct contribution.
* '''The resource constraint stated honestly:''' not a refusal to accept features, but limited capacity. Where long-term contributors actively maintain an area, bringing code in is fine. Where something will generate ongoing development and concerns, active maintainers need to be identified first.

=== Bundling Third-Party Code ===
* '''Strong position against the transitional middle ground''' — extracting a module from core but continuing to ship it in the official package. For security purposes that is equivalent to including it: if a vulnerability is reported and the author is not fixing it, the project is still answerable.
* '''Counter-position:''' this is the same as any other Composer dependency, and the project already declines to depend on anything without an active maintainer.
* '''Rejoinder:''' an actively maintained package is not necessarily an actively secured one, and the exposure here is a logged-in user inside OpenEMR.
* '''Resolution reached:''' modules packaged with core should live under the OpenEMR organization, so the project retains the ability to fix them. A contributed module could change ownership to OpenEMR if the author wishes.
* '''A fairness consideration raised:''' where a contributor has volunteered to take a module out of core on the understanding it would still be distributed, changing that expectation later would reduce its reach. Not a reason to avoid the change, but a reason to provide a good installation path first.
* '''The unblocking idea:''' a module registry — a list of modules certified to work well with OpenEMR. With that in place, extracted modules could be removed from the package without stranding anyone, and the contributor would be comfortable.

=== How Hard Is Installing a Module? ===
* '''Essentially a single Composer install command.''' Anyone who has worked out the OpenEMR upgrade process can manage it, and AI assistance makes it easier still.
* '''The nuance is immutable Docker images:''' for those, you would build your own image on top of the OpenEMR image with the module installed at build time. Most users do not work that way.
* '''The envisioned shape:''' the official Docker image as a base containing core OpenEMR, with deployments layering their chosen modules on top — the base stays immutable and each site's distribution is that base plus its own additions.

== The Decision on PR 13795 ==
* '''Reviewed live on the call.''' Assessment: cleanly structured as a module with no touch points into core; queries reasonable in number; no major problems visible. One file flagged — dynamic JavaScript generation in the encounter toolbar, which should be a separate JavaScript file with variables injected.
* '''The feature was judged a genuine value add.''' Nothing else in OpenEMR does this across all layout-based forms.
* '''Why LBF specifically:''' layout-based forms are standardized, so one implementation reaches every LBF form in existence. Custom forms are all different, and many already do their own totalling and range logic. Simon confirmed the approach could extend to other form types but has not been generalized.
* '''Suggestion raised:''' abstract the logic into a library that other areas of the application could call, rather than keeping it available only within the module.
* '''Argument that the module form is an advantage:''' embedding it would add to the existing tangle, whereas an isolated module is easier to separate later and may provide a model for eventually extracting all the LBF machinery into a core module of its own.
* '''The case for waiting:''' let it run on Packagist, see whether there is demand, then bring it into core — at which point inclusion is a single line in composer.json. Hesitancy about adding new surface area while the security workload is heavy.
* '''The case against waiting:''' community feedback will not arrive. Experience is that forum posts get no responses; the only feedback that comes back is when something is broken. The decision has to be made on the merits by the people making it.
* '''The countervailing point on review capacity, stated candidly:''' review has been triaged to bug fixes and broken behavior, with feature PRs left sitting. The suggestion made was to branch out — have someone take on straightforward feature PRs, since a clean, simple PR is much easier to bring in than one doing unusual things.
* '''Position on messaging:''' rather than telling contributors the project is not accepting features, say that capacity is limited, the intent is to get to it, and to keep pinging.
* '''Deferred to next week''' given the disagreement, and because the release discussion needed the remaining time.

== Doctrine, Schema Drift, and Static Analysis ==
* '''Hesitation expressed — not specific to this PR but to all current code:''' queries and column references are plain strings, so static analysis has no visibility into them.
* '''The concrete failure mode described:''' a deployment where schema changes were not applied somewhere, and nothing caught it because nothing could. Code that is correct today can drift out of sync as the schema evolves, and that is a risk for the project as a whole.
* '''With Doctrine, the mapping is structured and the tooling understands the real schema,''' so that class of problem disappears. Hand-constructed SQL goes away, and handling of new columns and schema changes becomes largely automatic.
* '''What is blocking adoption:''' the core foundation is in place; what remains is the front controller and some routing work so that modules reliably use it.
* '''Counter-argument on sequencing:''' the harder problem is the legacy code that follows none of the current conventions, not newly written code that already follows most of them. Converting a well-structured module to Doctrine later should be largely mechanical.

:''Doctrine is the standard PHP object-relational mapper; DBAL is its database abstraction layer. The practical benefit in this context is that table and column names become part of typed, analyzable code rather than strings assembled at runtime — which is what makes both schema drift and injection-class problems visible to tooling rather than only to a human reader.''

* '''Recognition of what the existing tooling has already achieved:''' contributors are now producing markedly more structured PRs because PHPStan, CodeRabbit, and the enforced conventions catch problems before a human looks.

== Layout-Based Forms ==

:''Layout-based forms (LBF) are OpenEMR's mechanism for building custom clinical forms through the administration interface rather than by writing code. An administrator defines fields, data types, and list options, and the resulting form is stored in the database and rendered generically. Values are stored as rows in a shared data table keyed by form instance and field, which is why a single implementation can reach every LBF form at once.''

* '''Widely regarded as both a major strength and a maintenance burden.''' Described as an awesome feature at one end and a pain source at the other.
* '''Evidence of demand:''' a lecture on layout-based forms given roughly four years ago remains by a wide margin the most-viewed video the project has ever published.
* '''The associated technical debt:''' the options file behind the layout machinery runs to around 4,000 lines and is acknowledged as needing substantial refactoring. A candidate for eventual extraction into a core module.
* '''Telemetry gap:''' the project does not currently know how widely layout-based forms are used, because telemetry covers menu usage rather than encounter activity.

== Telemetry ==
* '''Proposal: record which modules are installed on an instance.''' That would answer adoption questions directly — publish a module, then see who installed it — rather than relying on forum feedback that does not arrive.
* '''Broader point:''' there is a lot that could be added to telemetry, and the current coverage is not well documented. Suggestion made that the simplest way to find out what is currently collected is to ask AI to read the code base and report.

:''This connects directly to decisions taken in earlier meetings. The fax/SMS core-versus-module question on 8/11 also stalled on the absence of usage data, and the backup.php removal on 8/18 turned on a telemetry figure of roughly 10% adoption. Module and feature telemetry would make several recurring arguments resolvable with evidence.''

== Release Status ==
* '''Two bugs under discussion for a point release.''' First, the refined patient search — the field-by-field narrowing search, not the main patient finder — is broken. Confirmed as not the main finder, which reduced the severity considerably.
* '''Second, the encounter form is broken,''' traced to a change in how the patient identifier parameter is passed. Considered significant enough to justify a release.
* '''Also outstanding:''' portal fixes from Jerry restoring auditing, and a long-standing data issue where male and female values are transposed in a FHIR context. The latter has apparently existed for a very long time without anyone noticing, and Inferno does not catch it because the test suite has no way to know which patients are which.
* '''Argument for doing the point release:''' the release mechanism has only recently been straightened out, so exercising it on a low-stakes release is worthwhile — breakage is likely, and better to discover it now than during a genuinely critical issue.
* '''Mechanics noted:''' a database change requires manual handling around the dev release tag, since tagging generates a further upgrade file in master that has to be moved back. Not painful, but manual.
* '''An unrelated observation on release friction:''' the most tedious remaining step is manually removing unsubscribed addresses from the mailing database. Automating it was raised as worth asking about.
* '''Tentative plan:''' gather the available fixes and do the release over the weekend.

== Vendor Upgrade Experience ==

=== The General Problem ===
* '''Discussion of how vendors keep large deployments current.''' The recurring difficulty is that customizations made directly to core code must be rebased onto each new version, and each release starts a clock.
* '''Speaking generally rather than about any specific deployment:''' the motivation behind simplifying module development and making things easier to disentangle is precisely so that deployments can pull in patches without rewriting half their code.
* '''Performance work has been contributed upstream''' where it was not specific to any one installation. A synthetic test with roughly 100,000 calendar events across a year rendered the calendar page with about 15,000 queries; after the fixes it ran about eight. That class of problem surfaces only at scale.
* '''On the proposed module system:''' real-world deployment experience is largely aligned with the design. The base — roughly three hooks covering command line, database, and API registration — remains a good starting point, with further layers to be added as modules become more sophisticated.
* '''Repeated request for feedback:''' the module design is currently informed by three or four people's views, which is a limited view of how OpenEMR is actually used. More real-world input would make the design more comprehensive.

=== Event Listeners vs. Bootstrap Registration ===
* '''Two different approaches were described.''' The existing custom modules use event listeners. The newer approach uses a low-level bootstrap — a three-line change in the file every request passes through, which registers the modules.
* '''Why this requires the front controller:''' a single registration point is needed for modules to function reliably. Every request must run the modules it is supposed to run, and without one entry point there is no way to guarantee that.
* '''The two are orthogonal rather than competing.''' Single-point registration is a requirement for any reasonable approach; whether customization happens through events or through a defined API is a separate, more philosophical question.
* '''That deeper question framed:''' OpenEMR today can be customized so extensively that a heavily modified installation is nearly a different piece of software. That is powerful, but it makes it hard for core to offer any guarantees to modules. The alternative — defined, largely additive extension points — trades flexibility for predictability. There is no technically correct answer; it is a decision about what OpenEMR should be.

:''This is the same tension the project has returned to repeatedly: the fax/SMS extraction, the backup.php removal, and the module registry all turn on how much the project is willing to own and guarantee. The front controller keeps appearing as the prerequisite because it is what makes any guarantee enforceable.''

=== Sherwin Gaddis on Real-World Upgrades ===
* '''Test run completed upgrading 8.3 to 8.4''' with core modifications in place, working toward a documented playbook. The challenge is rebasing existing modifications onto the new code base.
* '''Key caution:''' you cannot fall far behind. Too many versions back and rebasing stops working — files change completely or disappear, and modifications may no longer apply at all. A five-to-eight jump was called too much.
* '''Longest migration performed:''' version 3 to version 7, successfully, though complicated by a site that had installed version 3 twice and copied patients between the two instances. Almost nightmarish to unpick, with essentially no documentation of why anything was done as it was. The client was happy with the result.
* '''Current plan:''' move every client to 8.4 before the end of the year, starting with unmodified installations where the upgrade is just the SQL step. Holiday season provides the window. Motivation is not falling behind on security and features.
* '''On modules and upgrades:''' everything was moved into modules roughly four years ago, and anything needed in core gets pushed upstream so it is available to everyone. This helps, but modules still misbehave between versions — they have to be installed rather than simply moved, and quirky issues occur even when the database records them as installed.
* '''Refactoring a module between major versions is described as mild,''' mostly globals and session handling — bring in the global bag, fix the sessions, and it works. Written to standard, going from 7 to 8 should not be a large problem. Their published module list states which versions each module supports.

== Payment Processors ==
* '''Question raised about supporting additional payment processors,''' prompted by interest in lower-cost alternatives to the processors currently supported.
* '''Advice given:''' do not follow the pattern of the processors currently in the code base. Build a module that ties into what exists rather than baking another integration into core.
* '''The gap identified:''' there is no generalized payment interface in core that individual processor modules could hook into. Agreement that one is needed — a generic mechanism in core, with per-processor modules.
* '''Prior art recalled:''' a package existed that built a gateway abstraction across credit card processors, so integrating code only had to speak to that gateway and the gateway negotiated each processor's differing API. Believed to have been looked at years ago.

:''This is almost certainly Omnipay, a long-established PHP payment abstraction library that provides a consistent interface across a large number of gateway drivers. It remains actively maintained and is the closest existing match to what was described.''

* '''Current state:''' a recent processor addition sits alongside the older integration in the same connections area, which was noted as the current project norm but also as accumulating duplicate code. The suggestion was that the connections section will need to be broken out into its own tab as vendors keep being added.
* '''Also noted:''' the card reader supported by the older integration is outdated and possibly no longer compliant.
* '''A prior conversation with a major processor did not progress''' because the arrangement proposed did not fit how the foundation and independent clinics relate to one another. Worth revisiting.

== Security Workload — Context Given to the New Contributor ==
* '''Asked how long the current security situation would last,''' the answer given was that it is an industry-wide phenomenon affecting essentially all projects, not something specific to OpenEMR.
* '''An infrastructure indicator:''' CVE identifiers that were once issued within a day or two are now taking considerably longer across the board, pointing to a backlog in the underlying process rather than anything specific to this project. Releases go out ahead of identifier assignment, with identifiers attached afterward.
* '''Reason for cautious optimism:''' there is now noticeable duplication in reports — different people using automated tooling find and report the same issues. That implies a finite set rather than an endless stream. Rough estimate offered: perhaps a year, with the rate levelling off and beginning to decline in three to six months.
* '''The realistic counterweight:''' OpenEMR is a high-value, source-available target. It will attract more scrutiny than a hobby utility because the payoff is higher. The volume should become much smaller, but it will not stop.
* '''The compensating benefit:''' the pressure has driven real infrastructure improvement — the release mechanism, the demo farm, and much that previously required manual work are now automated, which puts the project in a position to focus on the backlog rather than the pipeline.
* '''Refactoring work has second-order security benefits,''' not just maintainability ones: understanding what data is where is what makes it possible to verify that data is safe in a given context. As that improves across the system, the report volume should fall.
* '''Centralization compounds:''' as logic is consolidated, one fix replaces what would previously have been many.

== Housekeeping ==
* '''Last week's forum post implied the meeting time change applied to the weekly call.''' It applies to the monthly Foundation board meeting, which moves to 10am Pacific / 1pm Eastern next month. The weekly call is unchanged. The forum post was corrected during the meeting, and the minutes already had it right.
* Noted that the forum software records and displays edits, so corrections are visible rather than silent.

== Items Discussed and Proposed ==
''Recorded as topics raised and directions favored, not as assigned work or commitments.''

{| class="wikitable" style="width:100%;"
! style="width:18%; padding:10px 0;" | Area !! style="padding:10px 0;" | Discussed / Proposed
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''PR 13795''' || style="padding:10px 0;" | Decision on whether the LBF statements module warrants inclusion in core deferred to next week. Disagreement acknowledged; no objection to the code quality itself.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Module policy''' || style="padding:10px 0;" | Clarified: the test is applicability, not packaging. A module that delivers a broadly useful feature can still live in the code base. Third-party and vendor-specific modules go to Packagist.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Bundled modules''' || style="padding:10px 0;" | Position taken that modules shipped in the official package should live under the OpenEMR organization, so the project can fix security issues in anything it distributes.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Transitional packaging''' || style="padding:10px 0;" | Consensus against a long-term middle ground where a module is extracted from core but still bundled. Preference is for a proper post-install path.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Module registry''' || style="padding:10px 0;" | Revisited — a list of modules known to work well with OpenEMR, which would let extracted modules be removed from the package without stranding their users.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Telemetry''' || style="padding:10px 0;" | Proposal to record which modules are installed on an instance, so adoption questions can be answered with data rather than guesswork.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Release''' || style="padding:10px 0;" | Patient search (refined search, not the main finder) and the encounter form are both broken. A point release was discussed for the weekend, partly as a rehearsal of the process.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Front controller''' || style="padding:10px 0;" | Still the blocker for the module system. An up-for-grabs demo remains outstanding.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Payment processors''' || style="padding:10px 0;" | No generalized gateway abstraction exists in core. Suggestion that core define a generic interface with per-processor modules.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Forum correction''' || style="padding:10px 0;" | Last week's post implied the time change applied to the weekly call; it applies to the monthly Foundation meeting. Corrected.
|}

== Notes ==
* '''The central tension of the meeting, stated cleanly by one participant:''' the project is telling contributors to build modules, and then declining to review modules. Whether or not that is the intent, it is how the policy reads from outside, and the clarification reached — that applicability rather than packaging decides inclusion — is worth stating publicly.
* Recurring theme: several threads ended at the same place — telemetry would answer the question. Module adoption, LBF usage, and feature demand were all discussed without data, and in each case someone observed that community feedback rarely arrives on request. Community members who do have views on these questions would be unusually useful right now, precisely because so little feedback comes in unprompted.

[[Category:Developer Guide]]

OpenEMR Weekly Conference Call Meeting Notes

David Eschelbacher — Wed, 16 Sep 2026 09:46:16 GMT

2026

@@ Line 26: / Line 26: @@
 == '''2026''' ==
 ===== '''September 8, 2026''' =====
 :*Topics:

OpenEMR Wiki Home Page

Bradymiller — Wed, 16 Sep 2026 05:57:28 GMT

Main

← Older revision		Revision as of 05:57, 16 September 2026
Line 102:		Line 102:
	User manuals are available for:		User manuals are available for:

	* '''[[OpenEMR 8.3.0 Users Guide\|Current stable release]]''' '''[<nowiki/>[[OpenEMR 8.3.0 Users Guide\|8.3.0]]]''' <span style="color: green">(current)</span>		* '''[[OpenEMR 8.4.0 Users Guide\|Current stable release]]''' '''[<nowiki/>[[OpenEMR 8.4.0 Users Guide\|8.4.0]]]''' <span style="color: green">(current)</span>
	* Previous releases [<nowiki/>[[OpenEMR 8.2.0 Users Guide\|8.2.0]]], [<nowiki/>[[OpenEMR 8.0.0 Users Guide\|8.0.0]]], [<nowiki/>[[OpenEMR 7.0.4 Users Guide\|7.0.4]]], [<nowiki/>[[OpenEMR 7.0.3 Users Guide\|7.0.3]]], [<nowiki/>[[OpenEMR 7.0.2 Users Guide\|7.0.2]]],<nowiki/> [<nowiki/>[[OpenEMR 7.0.1 Users Guide\|7.0.1]]<nowiki/>[[OpenEMR 7.0.1 Users Guide\|<nowiki>]</nowiki>]], [<nowiki/>[[OpenEMR 7.0.0 Users Guide\|7.0.]]<nowiki/>[[OpenEMR 7.0.0 Users Guide\|0]]] / [<nowiki/>[[OpenEMR 6.1.0 Users Guide\|6]]<nowiki/>[[OpenEMR 6.1.0 Users Guide\|.1.0]]], [<nowiki/>[[OpenEMR 6.0.0 Users Guide\|6]]<nowiki/>[[OpenEMR 6.0.0 Users Guide\|.0.0]]] /<nowiki/> [<nowiki/>[[OpenEMR 5.0.2 Users Guide\|5.0.2]]],[<nowiki/>[[OpenEMR 5.0.1 Users Guide\|5.0.1]]], <nowiki/>[ [[OpenEMR 5.0.0 Users Guide\|5.0.0]]<nowiki/>] / [<nowiki/>[[OpenEMR 4.2.2 Users Guide\|4.]]<nowiki/>[[OpenEMR 4.2.2 Users Guide\|2.2]]], [<nowiki/>[[OpenEMR 4.2.1 Users Guide\|4.2.1]]],<nowiki/> [<nowiki/>[[OpenEMR 4.2.0 Users Guide\|4.2.0]]<nowiki/>], [<nowiki/>[[OpenEMR 4.1.2 Users Guide\|4]][[OpenEMR 4.1.2 Users Guide\|.1.]]<nowiki/>[[OpenEMR 4.1.2 Users Guide\|2]]], [<nowiki/>[[OpenEMR 4.1.1 Users Guide\|4.]][[OpenEMR 4.1.1 Users Guide\|1.1]]], [<nowiki/>[[OpenEMR 4.1 Users Guide\|4.1]][[OpenEMR 4.1 Users Guide\|.0]] ], [<nowiki/>[[OpenEMR 4.0 Users Guide\|4.0]]]		* Previous releases [<nowiki/>[[OpenEMR 8.3.0 Users Guide\|8.3.0]]], [<nowiki/>[[OpenEMR 8.2.0 Users Guide\|8.2.0]]], [<nowiki/>[[OpenEMR 8.0.0 Users Guide\|8.0.0]]], [<nowiki/>[[OpenEMR 7.0.4 Users Guide\|7.0.4]]], [<nowiki/>[[OpenEMR 7.0.3 Users Guide\|7.0.3]]], [<nowiki/>[[OpenEMR 7.0.2 Users Guide\|7.0.2]]],<nowiki/> [<nowiki/>[[OpenEMR 7.0.1 Users Guide\|7.0.1]]<nowiki/>[[OpenEMR 7.0.1 Users Guide\|<nowiki>]</nowiki>]], [<nowiki/>[[OpenEMR 7.0.0 Users Guide\|7.0.]]<nowiki/>[[OpenEMR 7.0.0 Users Guide\|0]]] / [<nowiki/>[[OpenEMR 6.1.0 Users Guide\|6]]<nowiki/>[[OpenEMR 6.1.0 Users Guide\|.1.0]]], [<nowiki/>[[OpenEMR 6.0.0 Users Guide\|6]]<nowiki/>[[OpenEMR 6.0.0 Users Guide\|.0.0]]] /<nowiki/> [<nowiki/>[[OpenEMR 5.0.2 Users Guide\|5.0.2]]],[<nowiki/>[[OpenEMR 5.0.1 Users Guide\|5.0.1]]], <nowiki/>[ [[OpenEMR 5.0.0 Users Guide\|5.0.0]]<nowiki/>] / [<nowiki/>[[OpenEMR 4.2.2 Users Guide\|4.]]<nowiki/>[[OpenEMR 4.2.2 Users Guide\|2.2]]], [<nowiki/>[[OpenEMR 4.2.1 Users Guide\|4.2.1]]],<nowiki/> [<nowiki/>[[OpenEMR 4.2.0 Users Guide\|4.2.0]]<nowiki/>], [<nowiki/>[[OpenEMR 4.1.2 Users Guide\|4]][[OpenEMR 4.1.2 Users Guide\|.1.]]<nowiki/>[[OpenEMR 4.1.2 Users Guide\|2]]], [<nowiki/>[[OpenEMR 4.1.1 Users Guide\|4.]][[OpenEMR 4.1.1 Users Guide\|1.1]]], [<nowiki/>[[OpenEMR 4.1 Users Guide\|4.1]][[OpenEMR 4.1 Users Guide\|.0]] ], [<nowiki/>[[OpenEMR 4.0 Users Guide\|4.0]]]
	* Older releases (PDF only) [[http://www.open-emr.org/files/OpenEMR_3.2_Users_Guide.pdf 3.2]], [[http://www.open-emr.org/files/OpenEMR_3.1_Users_Guide.pdf 3.1]], [[http://www.open-emr.org/files/OpenEMR_3.0_Users_Guide.pdf 3.0]]		* Older releases (PDF only) [[http://www.open-emr.org/files/OpenEMR_3.2_Users_Guide.pdf 3.2]], [[http://www.open-emr.org/files/OpenEMR_3.1_Users_Guide.pdf 3.1]], [[http://www.open-emr.org/files/OpenEMR_3.0_Users_Guide.pdf 3.0]]

OpenEMR Foundation Monthly Conference Call Details

Stephen waite — Tue, 15 Sep 2026 19:19:27 GMT

Meeting Date/Time

← Older revision		Revision as of 19:19, 15 September 2026
Line 4:		Line 4:
	=='''Meeting Date/Time'''==		=='''Meeting Date/Time'''==
	:*The meeting is once monthly and on:		:*The meeting is once monthly and on:
	::* Second Wednesday of the month at 6:00 PM PST (Pacific Standard Time).		::* Second Wednesday of the month at 10:00 AM PST (Pacific Standard Time).

	:*This call may be recorded — see [[#Recording and Meeting Notes\|Recording and Meeting Notes]] below.		:*This call may be recorded — see [[#Recording and Meeting Notes\|Recording and Meeting Notes]] below.

OpenEMR ePrescribe

Harley Tuck — Mon, 14 Sep 2026 17:04:14 GMT

deleted item not affiliated with ensora eRx

← Older revision		Revision as of 17:04, 14 September 2026
Line 36:		Line 36:
	''' NOTE: The video shows Ensora Health v1, which has been superseded by v2, which contains major interface changes and does not visually resemble v1 at all.		''' NOTE: The video shows Ensora Health v1, which has been superseded by v2, which contains major interface changes and does not visually resemble v1 at all.
	:: If you are interested in seeing a demo of the current Ensora Health contact		:: If you are interested in seeing a demo of the current Ensora Health contact
	:: helpdesk@mi-squared.com or		:: helpdesk@mi-squared.com
	~~:: support@ehrcommunityhelpdesk.com~~


	{{#ev:youtube\|5Lxs1nAvEZU\|275\|\|'''OpenEMR/ Ensora Health eRx walkthrough for G3 Usability testing by MI-Squared''' [[file:MI2Bug40.png]]}}		{{#ev:youtube\|5Lxs1nAvEZU\|275\|\|'''OpenEMR/ Ensora Health eRx walkthrough for G3 Usability testing by MI-Squared''' [[file:MI2Bug40.png]]}}

QA and Release Process

Bradymiller — Mon, 14 Sep 2026 00:58:41 GMT

Packages

← Older revision		Revision as of 00:58, 14 September 2026
Line 95:		Line 95:
	:*** Ensure auto upgrade works ('''AUTOMATED ON ACCEPT TESTING''')		:*** Ensure auto upgrade works ('''AUTOMATED ON ACCEPT TESTING''')
	:*Kubernetes		:*Kubernetes
	:** Update script to use the new docker ('''8.3.0''')		:** Update script to use the new docker ('''8.3.0''')('''8.4.0''')
	:*AWS Cloud packages (PENDING)		:*AWS Cloud packages (PENDING)
	:** Include the Fargate option in listings (PENDING)		:** Include the Fargate option in listings (PENDING)

OpenEMR Wiki Home Page

Bradymiller — Sun, 13 Sep 2026 09:50:57 GMT

Release History

← Older revision		Revision as of 09:50, 13 September 2026
Line 265:		Line 265:
	! scope="col" \| Milestones		! scope="col" \| Milestones
	\|-		\|-
	\| '''8.4.0''' \|\| September 13, 2026 \|\| ([https://community.open-emr.org/t/openemr-8-3-0-has-just-been-released/~~26982~~ See full summary of changes])		\| '''8.4.0''' \|\| September 13, 2026 \|\| ([https://community.open-emr.org/t/openemr-8-4-0-has-just-been-released/27050 See full summary of changes])
	\|-		\|-
	\| '''8.3.0''' \|\| August 18, 2026 \|\| ([https://community.open-emr.org/t/openemr-8-3-0-has-just-been-released/26982 See full summary of changes])		\| '''8.3.0''' \|\| August 18, 2026 \|\| ([https://community.open-emr.org/t/openemr-8-3-0-has-just-been-released/26982 See full summary of changes])

QA and Release Process

Bradymiller — Sun, 13 Sep 2026 09:35:17 GMT

Documentation

← Older revision		Revision as of 09:35, 13 September 2026
Line 38:		Line 38:
	:**[[OpenEMR ONC Ambulatory EHR Certification Requirements]] ('''COMPLETED; OPENEMR VERSION AGNOSTIC, SO NO MORE UPDATES NEEDED''')		:**[[OpenEMR ONC Ambulatory EHR Certification Requirements]] ('''COMPLETED; OPENEMR VERSION AGNOSTIC, SO NO MORE UPDATES NEEDED''')
	:*official demo ('''AUTOMATED ON RELEASE''')		:*official demo ('''AUTOMATED ON RELEASE''')
	:* update after release [[OpenEMR_Wiki_Home_Page#Release_History]] ('''8.3.0''')		:* update after release [[OpenEMR_Wiki_Home_Page#Release_History]] ('''8.3.0''')('''8.4.0''')
	:* after release ensure the development documentation linked to from download page has correct demo to download the master package from. (not related to release, but a good time to check on it)		:* after release ensure the development documentation linked to from download page has correct demo to download the master package from. (not related to release, but a good time to check on it)

OpenEMR Wiki Home Page

Bradymiller — Sun, 13 Sep 2026 09:34:55 GMT

Release History

← Older revision		Revision as of 09:34, 13 September 2026
(3 intermediate revisions by the same user not shown)
Line 49:		Line 49:

	=== Official Demos ===		=== Official Demos ===
	* '''[https://www.open-emr.org/demo/ 8.3.0]''' — Current stable release <span style="color:green">● stable</span>		* '''[https://www.open-emr.org/demo/ 8.4.0]''' — Current stable release <span style="color:green">● stable</span>
	===== Prior Versions =====		===== Prior Versions =====
	<!--* [[8.4.0 Demo\|8.4.0]]-->		<!--* [[8.4.0 Demo\|8.4.0]]-->
	~~<!--~~* [[8.3.0 Demo\|8.3.0]]~~-->~~		* [[8.3.0 Demo\|8.3.0]]
	* [[8.2.0 Demo\|8.2.0]]		* [[8.2.0 Demo\|8.2.0]]
	* [[8.0.0 Demo\|8.0.0]]		* [[8.0.0 Demo\|8.0.0]]
Line 60:		Line 60:
	''These demos may contain features known not to work yet.''		''These demos may contain features known not to work yet.''
	* [[Development Demo\|8.5.0]] <span style="color:red">● development</span>		* [[Development Demo\|8.5.0]] <span style="color:red">● development</span>
	* [[8.4.0 Demo\|8.4.0]] <span style="color:red">● development</span>
	* [[Development Demo#UP FOR GRABS Development Demos\|Up For Grabs]] — git branches		* [[Development Demo#UP FOR GRABS Development Demos\|Up For Grabs]] — git branches

Line 109:		Line 108:
	===API===		===API===
	API documentation is available for:		API documentation is available for:
	* '''[[OpenEMR 8 API\|Current stable release]]''' '''[<nowiki/>[[OpenEMR 8.3.0 API\|8.3.0]]]''' <span style="color: green">(current)</span>		* '''[[OpenEMR 8 API\|Current stable release]]''' '''[<nowiki/>[[OpenEMR 8.4.0 API\|8.4.0]]]''' <span style="color: green">(current)</span>
	* Previous releases [<nowiki/>[[OpenEMR 8.2.0 API\|8.2.0]]], [<nowiki/>[[OpenEMR 8.0.0 API\|8.0.0]]]		* Previous releases [<nowiki/>[[OpenEMR 8.3.0 API\|8.3.0]]], [<nowiki/>[[OpenEMR 8.2.0 API\|8.2.0]]], [<nowiki/>[[OpenEMR 8.0.0 API\|8.0.0]]]

	===B10===		===B10===
	The B10 Electronic health information (EHI) export is available for:		The B10 Electronic health information (EHI) export is available for:
	* '''[[OpenEMR 8 B10\|Current stable release]]''' '''[<nowiki/>[[OpenEMR 8.3.0 B10\|8.3.0]]]''' <span style="color: green">(current)'''</span>		* '''[[OpenEMR 8 B10\|Current stable release]]''' '''[<nowiki/>[[OpenEMR 8.4.0 B10\|8.4.0]]]''' <span style="color: green">(current)'''</span>
	* Previous releases [<nowiki/>[[OpenEMR 8.2.0 B10\|8.2.0]]], [<nowiki/>[[OpenEMR 8.0.0 B10\|8.0.0]]]		* Previous releases [<nowiki/>[[OpenEMR 8.3.0 B10\|8.3.0]]], [<nowiki/>[[OpenEMR 8.2.0 B10\|8.2.0]]], [<nowiki/>[[OpenEMR 8.0.0 B10\|8.0.0]]]

	===Real World Testing===		===Real World Testing===
Line 265:		Line 264:
	! scope="col" style="width:15%" \| Release Date		! scope="col" style="width:15%" \| Release Date
	! scope="col" \| Milestones		! scope="col" \| Milestones
			\|-
			\| '''8.4.0''' \|\| September 13, 2026 \|\| ([https://community.open-emr.org/t/openemr-8-3-0-has-just-been-released/26982 See full summary of changes])
	\|-		\|-
	\| '''8.3.0''' \|\| August 18, 2026 \|\| ([https://community.open-emr.org/t/openemr-8-3-0-has-just-been-released/26982 See full summary of changes])		\| '''8.3.0''' \|\| August 18, 2026 \|\| ([https://community.open-emr.org/t/openemr-8-3-0-has-just-been-released/26982 See full summary of changes])

QA and Release Process

Bradymiller — Sun, 13 Sep 2026 09:07:06 GMT

Documentation

← Older revision		Revision as of 09:07, 13 September 2026
Line 30:		Line 30:
	:*onc api docs		:*onc api docs
	:**[[OpenEMR 8.X.0 API]] ('''8.3.0''')('''8.4.0''')		:**[[OpenEMR 8.X.0 API]] ('''8.3.0''')('''8.4.0''')
	:**After release, redirect [[OpenEMR 8 API]] to [[OpenEMR 8.X.0 API]] ('''8.3.0''')		:**After release, redirect [[OpenEMR 8 API]] to [[OpenEMR 8.X.0 API]] ('''8.3.0''')('''8.4.0''')
	:*onc b10 docs		:*onc b10 docs
	:**[[OpenEMR 8.X.0 B10]] ('''8.3.0''')('''8.4.0''')		:**[[OpenEMR 8.X.0 B10]] ('''8.3.0''')('''8.4.0''')
	:**Rebuild EHI documentation and publish on website ('''AUTOMATED ON RELEASE''')		:**Rebuild EHI documentation and publish on website ('''AUTOMATED ON RELEASE''')
	:**After release, redirect [[OpenEMR 8 B10]] to [[OpenEMR 8.X.0 B10]] ('''8.3.0''')		:**After release, redirect [[OpenEMR 8 B10]] to [[OpenEMR 8.X.0 B10]] ('''8.3.0''')('''8.4.0''')
	:*onc main doc		:*onc main doc
	:**[[OpenEMR ONC Ambulatory EHR Certification Requirements]] ('''COMPLETED; OPENEMR VERSION AGNOSTIC, SO NO MORE UPDATES NEEDED''')		:**[[OpenEMR ONC Ambulatory EHR Certification Requirements]] ('''COMPLETED; OPENEMR VERSION AGNOSTIC, SO NO MORE UPDATES NEEDED''')

OpenEMR 8 B10

Bradymiller — Sun, 13 Sep 2026 09:06:52 GMT

Changed redirect target from OpenEMR 8.3.0 B10 to OpenEMR 8.4.0 B10

← Older revision		Revision as of 09:06, 13 September 2026
Line 1:		Line 1:
	#REDIRECT [[OpenEMR 8.3.0 B10]]		#REDIRECT [[OpenEMR 8.4.0 B10]]

OpenEMR 8 API

Bradymiller — Sun, 13 Sep 2026 09:06:33 GMT

Changed redirect target from OpenEMR 8.3.0 API to OpenEMR 8.4.0 API

← Older revision		Revision as of 09:06, 13 September 2026
Line 1:		Line 1:
	#REDIRECT [[OpenEMR 8.3.0 API]]		#REDIRECT [[OpenEMR 8.4.0 API]]

OpenEMR Modules

SherwinGaddis — Sat, 12 Sep 2026 15:03:41 GMT

Chart Summary

← Older revision		Revision as of 15:03, 12 September 2026
Line 42:		Line 42:
	This module represents a sophisticated integration between OpenEMR's comprehensive medical data and modern AI capabilities, providing clinicians with intelligent, context-aware patient summaries that adapt to medical specialty and clinical workflow requirements.		This module represents a sophisticated integration between OpenEMR's comprehensive medical data and modern AI capabilities, providing clinicians with intelligent, context-aware patient summaries that adapt to medical specialty and clinical workflow requirements.

	: ~~Request~~ module ~~by sending a request to support@ehrcommunityhelpdesk~~.~~com~~		[https://github.com/juggernautsei/oe-module-chart-summary Download Module] Or install using Composer.

	===Voice To Text===		===Voice To Text===

Repository work flow structure

Bradymiller — Sat, 12 Sep 2026 04:14:50 GMT

Associate Administrators

← Older revision		Revision as of 04:14, 12 September 2026
(One intermediate revision by the same user not shown)
Line 46:		Line 46:
	:[https://github.com/jesdynf Asher Densmore-Lynn] (2024 - current)		:[https://github.com/jesdynf Asher Densmore-Lynn] (2024 - current)
	:[https://github.com/kojiromike Michael Smith] (2026 - current)		:[https://github.com/kojiromike Michael Smith] (2026 - current)
			:[https://github.com/Firehed Eric Stern] (2026 - current)

	===Associate Administrators===		===Associate Administrators===
	:~~[https://github~~.~~com/Firehed Eric Stern] (2026 - current)~~		:None at this time.

	===Integration Developers===		===Integration Developers===

OpenEMR ePrescribe

Ken Chapple — Sat, 12 Sep 2026 00:52:34 GMT

Ensora Health

← Older revision		Revision as of 00:52, 12 September 2026
(3 intermediate revisions by the same user not shown)
Line 3:		Line 3:

	'''Ensora''', a subscription service, is well integrated into OpenEMR.		'''Ensora''', a subscription service, is well integrated into OpenEMR.

	* ''' $38.45/mo/prescriber ''' [https://buy.stripe.com/eVq00j9d85V13HC5ef3F60k Buy Standalone e-Prescribing] We will open a ticket to configure your system.

	* ''' $119/yr/prescriber ''' [https://buy.stripe.com/28EeVd3SO839fqkbCD3F60j Buy ECPS service] Setup completed in minutes.


	'''Weno Exchange''' with 3 integration options, including a no-code solution well integrated for OEMR v7.02 and above.		'''Weno Exchange''' with 3 integration options, including a no-code solution well integrated for OEMR v7.02 and above.
Line 15:		Line 10:
	=='''Ensora Health'''==		=='''Ensora Health'''==
	Ensora Health (formerly NewCrop) eRx is a robust e-prescribing solution provided by Ensora Health LLC/ Scriptx and supported in OpenEMR.		Ensora Health (formerly NewCrop) eRx is a robust e-prescribing solution provided by Ensora Health LLC/ Scriptx and supported in OpenEMR.

			[https://mi-squared.com MI-Squared] is the primary vendor for OpenEMR for the Ensora integration. [https://mi-squared.com MI-Squared] developed the integration and has maintained the integration since its initial development in 2016. MI-Squared has maintained its DEA certificate for electronic prescribing with each iteration of OpenEMR (not valid for other vendors.) [https://mi-squared.com MI-Squared] offers premium support for Ensora. You can reach out for pricing at [mailto:helpdesk@mi-squared.com helpdesk@mi-squared.com]

	In addition to basic e-prescribing of all medications to any registered pharmacy in the USA, Ensora Health also supports (list from their website):		In addition to basic e-prescribing of all medications to any registered pharmacy in the USA, Ensora Health also supports (list from their website):
	:*Scalable, dynamic display responsive to all screen and window sizes, including mobile.		:*Scalable, dynamic display responsive to all screen and window sizes, including mobile.

QA and Release Process

Bradymiller — Fri, 11 Sep 2026 07:21:27 GMT

Documentation

← Older revision		Revision as of 07:21, 11 September 2026
Line 32:		Line 32:
	:**After release, redirect [[OpenEMR 8 API]] to [[OpenEMR 8.X.0 API]] ('''8.3.0''')		:**After release, redirect [[OpenEMR 8 API]] to [[OpenEMR 8.X.0 API]] ('''8.3.0''')
	:*onc b10 docs		:*onc b10 docs
	:**[[OpenEMR 8.X.0 B10]] ('''8.3.0''')		:**[[OpenEMR 8.X.0 B10]] ('''8.3.0''')('''8.4.0''')
	:**Rebuild EHI documentation and publish on website ('''AUTOMATED ON RELEASE''')		:**Rebuild EHI documentation and publish on website ('''AUTOMATED ON RELEASE''')
	:**After release, redirect [[OpenEMR 8 B10]] to [[OpenEMR 8.X.0 B10]] ('''8.3.0''')		:**After release, redirect [[OpenEMR 8 B10]] to [[OpenEMR 8.X.0 B10]] ('''8.3.0''')

OpenEMR 8.4.0 B10

Bradymiller — Fri, 11 Sep 2026 07:20:51 GMT

Created page with "=OpenEMR 8.4.0 B10 Electronic health information (EHI) export= ==Public EHI Export Format Documentation== : Online ONC Certification public URL documentation for this export can be found at: :*https://www.open-emr.org/documentation/8.4.0/b10/ {{ehi_export_instructions}}"

New page

=OpenEMR 8.4.0 B10 Electronic health information (EHI) export=
 
==Public EHI Export Format Documentation==
: Online ONC Certification public URL documentation for this export can be found at:
:*https://www.open-emr.org/documentation/8.4.0/b10/

 

{{ehi_export_instructions}}

QA and Release Process

Bradymiller — Fri, 11 Sep 2026 07:20:06 GMT

Documentation

← Older revision		Revision as of 07:20, 11 September 2026
Line 29:		Line 29:
	:**[[OpenEMR Windows Upgrade]] ('''COMPLETED; OPENEMR VERSION AGNOSTIC, SO NO MORE UPDATES NEEDED''')		:**[[OpenEMR Windows Upgrade]] ('''COMPLETED; OPENEMR VERSION AGNOSTIC, SO NO MORE UPDATES NEEDED''')
	:*onc api docs		:*onc api docs
	:**[[OpenEMR 8.X.0 API]] ('''8.3.0''')		:**[[OpenEMR 8.X.0 API]] ('''8.3.0''')('''8.4.0''')
	:**After release, redirect [[OpenEMR 8 API]] to [[OpenEMR 8.X.0 API]] ('''8.3.0''')		:**After release, redirect [[OpenEMR 8 API]] to [[OpenEMR 8.X.0 API]] ('''8.3.0''')
	:*onc b10 docs		:*onc b10 docs

OpenEMR 8.4.0 API

Bradymiller — Fri, 11 Sep 2026 07:18:56 GMT

Created page with "= Overview = :OpenEMR API documentation for both FHIR API and Standard API. = FHIR API = :*[https://github.com/openemr/openemr/blob/rel-840/FHIR_README.md FHIR API Documentation for 8.4.0] :*[https://github.com/openemr/openemr/blob/rel-840/FHIR_README.md#fhir-api-documentation Click Here] for instructions on using Swagger, which is included in OpenEMR, to see full documentation of endpoints and testing support. :*Online links to Swagger based documentation can be f..."

New page

= Overview =
:OpenEMR API documentation for both FHIR API and Standard API.
 

= FHIR API =
:*[https://github.com/openemr/openemr/blob/rel-840/FHIR_README.md FHIR API Documentation for 8.4.0]
:*[https://github.com/openemr/openemr/blob/rel-840/FHIR_README.md#fhir-api-documentation Click Here] for instructions on using Swagger, which is included in OpenEMR, to see full documentation of endpoints and testing support.
:*Online links to Swagger based documentation can be found at [[8.4.0 Demo|8.4.0 Demo]].
:*Videos that overview OpenEMR's FHIR API:
::*[https://youtu.be/LQHNRBgg6Q8 OpenEMR FHIR Lecture Series: Lecture 1 - Overview and Use of FHIR in OpenEMR]
::*[https://youtu.be/2qr0IV9Kulg OpenEMR FHIR Lecture Series: Lecture 2 - FHIR Bulk Data in OpenEMR]
:*Specific instructions for a Clinical Summary of Care Document (CCD) request:
::*[https://github.com/openemr/openemr/blob/rel-840/FHIR_README.md#carecoordination-summary-of-care-docref-operation Instructions in API Documentation]
::*[https://github.com/openemr/openemr/issues/5284#issuecomment-1155678620 Tutorial to Generate CCDA (With Screenshots)]
 

= Standard API =
:*[https://github.com/openemr/openemr/blob/rel-840/API_README.md Standard API Documentation for 8.4.0]
:*[https://github.com/openemr/openemr/blob/rel-840/API_README.md#standard-api-documentation Click Here] for instructions on using Swagger, which is included in OpenEMR, to see full documentation of endpoints and testing support.
:*Online links to Swagger based documentation can be found at [[8.4.0_Demo|8.4.0 Demo]].
 

= Terms of use =
:*This section is required for ONC certification. OpenEMR and the API is open source and licensed under the [https://www.gnu.org/licenses/gpl-3.0.en.html GNU General Public License 3].
 

= Service Base URLs =
{{ServiceBaseURLs}}

QA and Release Process

Bradymiller — Fri, 11 Sep 2026 07:17:11 GMT

Documentation

← Older revision		Revision as of 07:17, 11 September 2026
Line 19:		Line 19:

	===Documentation===		===Documentation===
	:*USER MANUAL at [[OpenEMR 8.X.0 Users Guide]] ('''8.3.0''')		:*USER MANUAL at [[OpenEMR 8.X.0 Users Guide]] ('''8.3.0''')('''8.4.0''')
	:** Redirect [[OpenEMR 8.X.0 Users Guide]] to [[OpenEMR 8.X-1.0 Users Guide]] ('''8.3.0''')		:** Redirect [[OpenEMR 8.X.0 Users Guide]] to [[OpenEMR 8.X-1.0 Users Guide]] ('''8.3.0''')('''8.4.0''')
	:*feature list will be at [[Release Features#Version 8.3.0\|Release Features]] ('''AUTOMATED ON RELEASE''')		:*feature list will be at [[Release Features#Version 8.3.0\|Release Features]] ('''AUTOMATED ON RELEASE''')
	:*install docs		:*install docs

OpenEMR 8.5.0 Users Guide

Bradymiller — Fri, 11 Sep 2026 07:16:34 GMT

Redirected page to OpenEMR 8.4.0 Users Guide

New page

#REDIRECT [[OpenEMR_8.4.0_Users_Guide]]

OpenEMR 8.4.0 Users Guide

Bradymiller — Fri, 11 Sep 2026 07:16:17 GMT

Removed redirect to OpenEMR 8.3.0 Users Guide

Show changes

QA and Release Process

Bradymiller — Fri, 11 Sep 2026 07:14:44 GMT

Testing vehicle

← Older revision		Revision as of 07:14, 11 September 2026
Line 5:		Line 5:

	===Testing vehicle===		===Testing vehicle===
	:*[[8.X.0_Demo\|8.X.0_Demo]] ('''8.3.0''')		:*[[8.X.0_Demo\|8.X.0_Demo]] ('''8.3.0''')('''8.4.0''')

	===Code===		===Code===

OpenEMR Wiki Home Page

Bradymiller — Fri, 11 Sep 2026 07:13:57 GMT

Newest Developments

← Older revision		Revision as of 07:13, 11 September 2026
(One intermediate revision by the same user not shown)
Line 51:		Line 51:
	* '''[https://www.open-emr.org/demo/ 8.3.0]''' — Current stable release <span style="color:green">● stable</span>		* '''[https://www.open-emr.org/demo/ 8.3.0]''' — Current stable release <span style="color:green">● stable</span>
	===== Prior Versions =====		===== Prior Versions =====
			<!--* [[8.4.0 Demo\|8.4.0]]-->
	<!--* [[8.3.0 Demo\|8.3.0]]-->		<!--* [[8.3.0 Demo\|8.3.0]]-->
	* [[8.2.0 Demo\|8.2.0]]		* [[8.2.0 Demo\|8.2.0]]
Line 58:		Line 59:
	==== Newest Developments ====		==== Newest Developments ====
	''These demos may contain features known not to work yet.''		''These demos may contain features known not to work yet.''
	* [[Development Demo\|8.4.0]] <span style="color:red">● development</span>		* [[Development Demo\|8.5.0]] <span style="color:red">● development</span>
			* [[8.4.0 Demo\|8.4.0]] <span style="color:red">● development</span>
	* [[Development Demo#UP FOR GRABS Development Demos\|Up For Grabs]] — git branches		* [[Development Demo#UP FOR GRABS Development Demos\|Up For Grabs]] — git branches

8.4.0 Demo

Bradymiller — Fri, 11 Sep 2026 07:10:57 GMT

Created page with "==Overview== OpenEMR 8.4.0 demo includes daily build of the OpenEMR 8.4.0 codebase. (Daily at 8:30 am UTC time these demos reset.) The API (Swagger) links contain FHIR and API documentation, which allow testing. ==Demo Credentials== ===Standard Demo Credentials in ALL Demos=== * OpenEMR - user:admin pass:pass ===Special Demo Credentials in Demos WITH Demo Data=== :'''OpenEMR''' ::{| border="1" cellspacing="1" cellpadding="5" |- | '''Username''' | '''Password'''..."

New page

==Overview==
OpenEMR 8.4.0 demo includes daily build of the OpenEMR 8.4.0 codebase. (Daily at 8:30 am UTC time these demos reset.)

The API (Swagger) links contain FHIR and API documentation, which allow testing.

 

==Demo Credentials==
===Standard Demo Credentials in ALL Demos===
* OpenEMR - user:admin pass:pass

===Special Demo Credentials in Demos WITH Demo Data===
:'''OpenEMR'''
::{| border="1" cellspacing="1" cellpadding="5"
|-
| '''Username'''
| '''Password'''
| '''Description'''
|-
| admin
| pass
| Administrator
|-
| physician
| physician
| Physician(more access than clinician)
|-
| clinician
| clinician
| Clinician(less access than physician)
|-
| accountant
| accountant
| Accountant
|-
| receptionist
| receptionist
| Front desk receptionist
|}
:'''Patient Portal'''
::{| border="1" cellspacing="0" cellpadding="5"
|-
| '''Patient Username'''
| '''Password'''
| '''Email'''
|-
| Phil1
| phil
| heya@invalid.email.com
|-
| Susan2
| susan
| nana@invalid.email.com
|}
 

==Demo==
===Without demo data===
* OpenEMR: [https://six.openemr.io/openemr/index.php https://six.openemr.io/openemr] 
* Onsite Patient Portal: [https://six.openemr.io/openemr/portal/index.php https://six.openemr.io/openemr/portal] 
* API (Swagger) User Interface: [https://six.openemr.io/openemr/swagger/index.html https://six.openemr.io/openemr/swagger] 

===With demo data===
* OpenEMR: [https://six.openemr.io/a/openemr/index.php https://six.openemr.io/a/openemr] 
* Onsite Patient Portal: [https://six.openemr.io/a/openemr/portal/index.php https://six.openemr.io/a/openemr/portal] 
* API (Swagger) User Interface: [https://six.openemr.io/a/openemr/swagger/index.html https://six.openemr.io/c/openemr/swagger] 

===Logs===
* PHP log file: https://six.openemr.io/log/logPhp.txt 
* Setup log file: https://six.openemr.io/log/logSetup.txt