medplum VS cpl

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...).

I am testing a solution to the problem of funding open source through a custom license based off the AGPL, the Candid Public License: https://github.com/candiddev/cpl

The goal is to be ridiculously FOSS and require companies to do the same in order to use your project. If they don't want to embrace the copyleft aspect, they can purchase an exemption from it (see https://yaml8n.dev/pricing/ for an example).

In this model, the FOSS ecosystem can still thrive and build off of each other, and projects can negotiate license exemption to help sustain themselves.

I made an open source license that you may be interested in. It's basically the AGPL + copyleft for _servives_ that are dependent on your service, as well as build tools. You can check it out here: https://github.com/candiddev/cpl.