Docs Alternatives

Similar projects and alternatives to docs

fasten-sources

9 15 9.4 Go docs VS fasten-sources

The Fasten Sources is a library that defines medical provider metadata (definitions - OpenID Metadata documents) and http clients (OAuth2/Smart-on-FHIR clients) which can be used to retrieve data from various Medical Providers (clients).
dwv

3 1,596 9.7 JavaScript docs VS dwv

DICOM Web Viewer: open source zero footprint medical image library.
SurveyJS

surveyjs.io sponsored

Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better docs alternative or higher similarity.

Suggest an alternative to docs

docs reviews and mentions

Posts with mentions or reviews of docs. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-25.

Fasten Health - Open Source Self-hosted Personal Health Record
6 projects | /r/selfhosted | 25 Jan 2023

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
Fasten Open Sourced - BETA - A Self-hosted Personal Electronic Medical Record system
1 project | /r/selfhosted | 13 Oct 2022

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.