Documentation of the FAIR-BioRS guidelines and all things related to them
The FAIR Biomedical Research Software (FAIR-BioRS) guidelines are a set of minimal and actionable step-by-step instructions for making biomedical research software FAIR (Findable, Accessible, Interoperable, Reusable), i.e., optimizing their reusability. You can find everything about the guidelines in the documentation at fair-biors.org
The FAIR-BioRS guidelines were developed for software "that were created during the research process or for a research purpose" as per the definition established in "Defining Research Software: a controversial discussion". Such research software can come in many formats such as Python scripts, R code, or Jupyter notebooks and can be developed for various applications such as AI/ML models, computational models, or data visualization.
If you are developing such a software for biomedical research, head to the documentation to learn how you can make your software compliant with the FAIR Principles for Research Software (FAI4RS Principles). This will allow you to get proper recognition (e.g., citation) for your software development effort, enhance the impact of your software (e.g., by being reused in other projects), and increase collaboration opportunities. As funding agencies are pushing for all research outcomes to be FAIR, following the FAIR-BioRS guidelines will also allow you to start complying with those requirements.
If you are working with or developing biomedical research software and are interested in joining the FAIR-BioRS Working Group, please open a GitHub issue or email bpatel@calmi2.org.
Have feedback, suggestions, or questions related to the FAIR-BioRS guidelines? Submit them by opening a GitHub issue. If you want to suggest changes to this docs, you can also submit a PR by following the instructions in the developer instructions (see next section).
Instructions for making changes to the documentation, submitting a PR, and publishing a new version of the documentation and guidelines are available here.
A special thank you to Vercel for hosting this documentation.
