Note: The website is currently under development. We welcome contributions to verify and improve the product information accuracy.
- Admin Guide - User management, review assignment, security monitoring
- Reviewer Guide - Product review workflow and best practices
- Review Guide - How to review and update product information
- Field Reference - Definitions for every product field (useful when updating
lastUpdated/lastRevised) - Security Policy - Security features, GDPR compliance, and reporting vulnerabilities
- Manufacturer Templates - Communication templates
For complete documentation overview, see DOCUMENTATION_LINKS.md
Products in DLinRT.eu support:
- Multiple Categories: Products can belong to multiple categories using the
secondaryCategoriesfield - Multiple Versions: Different versions of the same product can be tracked with separate
versionandreleaseDatefields - Comprehensive Data: Each product includes regulatory, technical, market, and evidence information
-
Determine the Appropriate Category
- Products are organized by primary category in
src/data/products/directory - Use
secondaryCategoriesfield for products that span multiple categories - See the Review Guide for current categories
- Products are organized by primary category in
-
Create or Update the Company-Specific File
- Each company has its own file in the appropriate category directory
- If the company already exists, add your product to its file
- If it's a new company, create a new file named
company-name.ts - Example:
src/data/products/auto-contouring/varian.ts
-
Follow the Data Format
- See example templates for properly formatted data
- Include
secondaryCategoriesarray for multi-category products - Use separate entries for different product versions with distinct
versionandreleaseDatefields - Ensure all dates follow YYYY-MM-DD format
- Include regulatory information with proper structure
-
Multiple Versions Support
- Create separate product entries for major version releases
- Use consistent
idpatterns (e.g.,product-v1,product-v2) - Track evolution through
versionandreleaseDatefields - Maintain backward compatibility in data structure
-
Update the Category Index
- After adding the product, update the category index file to include your new products
-
Add the Company Logo
- Place the company logo in the
/public/logos/directory - Use a consistent naming scheme:
company-name.png
- Place the company logo in the
- Update
lastUpdatedevery time you edit any field in the product entry (structure, evidence, regulatory, etc.). - Refresh
lastRevisedonly after a reviewer-level QA pass—the value feeds the/reviewlisting table. - When in doubt, consult the Field Reference for per-field rules and allowed values.
For complete examples, refer to the example templates in src/data/products/examples/.
- Product Database: Comprehensive catalog of AI/ML products in radiotherapy
- Multi-Role System: User, Reviewer, Company Representative, Admin roles
- Company Certifications: Verified product certifications from manufacturers
- Review System: Structured product review with assignment workflows
- Compliance Resources: Regulatory information and compliance checklists
- Research Initiatives: Database of datasets, challenges, and model zoos
- User Tracking: Track products you use or are evaluating
- Community Experiences: Share and view product adoption experiences
- Healthcare Interoperability: FHIR R4 export for hospital system integration
- GDPR Compliance: Data export, anonymization, and consent management
This project uses Supabase for backend functionality:
- User authentication with role-based access control (RBAC)
- PostgreSQL database with Row Level Security (RLS)
- Edge functions for serverless logic
- Real-time notifications
- Secure file storage
User roles: User, Reviewer, Company Representative, Administrator
This project is built with:
- Vite
- TypeScript
- React
- Tailwind CSS
- Supabase (Database, Auth, Edge Functions)
- TanStack Query (React Query)
- Shadcn/ui Components
The only requirement is having Node.js & npm installed - install with nvm
# Clone the repository
git clone https://github.com/DLinRT-eu/dlinrteu-website.git
# Navigate to the project directory
cd dlinrteu-website
# Install dependencies
npm install
# Start the development server
npm run devYou can also use GitHub Codespaces for development:
- Navigate to the repository
- Click "Code" > "Codespaces"
- Create a new codespace to start developing
This project is licensed under the GNU AGPL-3.0 License - see the LICENSE file for details.
Matteo Maspero
Project Lead – Computational Imaging Group Utrecht
Feel free to contact the Project Lead in case you would like to be involved!
We welcome contributions to improve the accuracy of product information. If you notice any inaccuracies or have updates about the AI products listed, please:
- Open an issue describing the update needed.
- Submit a pull request with your changes.
- Ensure proper attribution and documentation.