openemr VS medplum

It’s total shit.

I’m rooting for something like this in the long term: https://github.com/openemr/openemr

Here is OpenEMRs github page. The project is coded predominantly in PHP and the project seems to be very active when you look at the rate of code merges.

Looks like you'd be better suited to just following the projects current pipeline strategy (https://github.com/openemr/openemr/actions). Looks like they use GitHub actions.

Thought this was great - especially being so up front about the value of distribution.

I wrote a post about the very same meetup, but note distribution is not one of our "why open source" answers https://www.medplum.com/blog/yc-oss-faq - perhaps we are alone in this regard

https://github.com/medplum/medplum

Good question. Custom data is tricky. The first thing we always try to do is dig deep into the FHIR spec to see if the data is truly custom, or if there is an existing FHIR representation that will actually work. In many cases, there are good options, and it's nice to work within the spec.

If not, then falling back to extensions is the next logical step. FHIR extensions can be clunky to work with. Our client libraries provide a bunch of helper utilities to make it easier.

In extreme cases, we have created custom FHIR resources via custom StructureDefinition and SearchParameter resources to represent completely unique data elements (examples: https://github.com/medplum/medplum/blob/main/packages/defini...).