# Title: Community Testing Needed—Expanded FHIR R4 Write Support

**URL:** <https://community.open-emr.org/t/title-community-testing-needed-expanded-fhir-r4-write-support/27040>\
**Category:** OpenEMR Development\
**Created:** [September 8, 2026, 11:49pm UTC](https://community.open-emr.org/t/title-community-testing-needed-expanded-fhir-r4-write-support/27040 "2026-09-08T23:49:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sjpadgett](https://community.open-emr.org/user_avatar/community.open-emr.org/sjpadgett/32/21623_2.png) [@sjpadgett](https://community.open-emr.org/u/sjpadgett)\
**Post date:** [September 8, 2026, 11:49pm UTC](https://community.open-emr.org/t/title-community-testing-needed-expanded-fhir-r4-write-support/27040/1 "2026-09-08T23:49:03Z")

</div>

Hi all,

I’m getting [PR #13281](https://github.com/openemr/openemr/pull/13281) ready for broader testing. This expands OpenEMR’s FHIR API with create and update support for 16 resources, including AllergyIntolerance, Condition, Encounter, CarePlan, CareTeam, Goal, Immunization, MedicationRequest, ServiceRequest, Coverage and others.

This work was originally started by Chris (`@rollingventures`) in [PR #11507](https://github.com/openemr/openemr/pull/11507). Chris built the original write framework and most of the resource mappings. When his availability became limited, he graciously allowed me to take over. The original commits and authorship have been preserved, and he deserves considerable credit for getting this project underway.

Once the PR is ready, I’ll install it on my demo server and post the FHIR base URL, access instructions, test patients and sample payloads. A basic test would be:

1. Obtain a token with the required FHIR create/update scopes.

2. POST a resource and confirm it can be read back.

3. PUT an update and verify the change through both FHIR and the OpenEMR UI.

4. Report the resource, request, response, scopes used and expected versus actual result.

Testing invalid data, permissions, references and normal FHIR reads for regressions will also be helpful. Please use demo data only—no real patient information.

If you use FHIR or develop integrations, I’d appreciate your help putting these new write paths through some real-world testing.

Please ping me here or a PM if questions or letting me know how you plan to test.  
I have an app oeApiExplorer that handles all endpoints and all supported grants. I’m adding the 16 write endpoints now and will make available for any whom may want.

 ![image](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/3X/3/6/3645a03f829a33820b9783285fb1e5967ca2e4bd.png)

---

<div class="post-metadata">

**Author:** ![sjpadgett](https://community.open-emr.org/user_avatar/community.open-emr.org/sjpadgett/32/21623_2.png) [@sjpadgett](https://community.open-emr.org/u/sjpadgett)\
**Post date:** [September 10, 2026, 5:27am UTC](https://community.open-emr.org/t/title-community-testing-needed-expanded-fhir-r4-write-support/27040/2 "2026-09-10T05:27:34Z")

</div>

Getting there. Modified my ApiExplorer to test all write endpoints.

 ![image](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/3X/d/7/d7a7ecf463dfbb6bbc3e89f68738eab50026ce82.png)

---

<div class="post-metadata">

**Author:** ![sjpadgett](https://community.open-emr.org/user_avatar/community.open-emr.org/sjpadgett/32/21623_2.png) [@sjpadgett](https://community.open-emr.org/u/sjpadgett)\
**Post date:** [October 5, 2026, 8:23pm UTC](https://community.open-emr.org/t/title-community-testing-needed-expanded-fhir-r4-write-support/27040/3 "2026-10-05T20:23:05Z")

</div>

My FHIR write project is now in master and for sure part of next release 8.5.0  
Also Observation vitals category as separate PR will be in that release. I’m working Observation labs category now and hope will be ready.

Check out