docs VS fasten-sources

If you really want to get your hands dirty and add a new platform vendor (Epic, Cerner, etc) You can figure out which EMR platform your medical providers use and then create a development app with them, create a Fasten Source definition, and then open a pull request. Here's a non-comprehensive list of vendors - https://github.com/fastenhealth/docs/blob/main/PATIENT_PORTAL_AND_SOURCES_TESTING.md

regarding the license choice - My goal was always to eventually open source fasten, but I was hoping to give myself time breathing room to monetize it first -- see if I could create a viable company around it. I had a couple of discussions with lawyers regarding various noncommercial source-available licenses, and the feedback there was unanimously negative lol. The other reason I decided to just straight open-source it is that I wanted to decrease the barriers to entry -- the overarching goal with Fasten is to support every single healthcare provider, and I wouldn't be able to do that myself. Any friction stopping a developer from contributing their healthcare provider means the application is less useful. Some of the feedback from my licensing discussions is available here - https://github.com/fastenhealth/docs/blob/main/legal/LICENSE.md though its a bit out of date.

Just added a page listing all the sources available in Fasten - https://github.com/fastenhealth/fasten-sources/blob/main/SOURCE_LIST.md