Thank you for using GenPRES! This document provides guidance on how to get help and support. The current document is a first draft and will be expanded over time to include more details on support processes, contact points, and best practices.
Important: Before using GenPRES in any context, please review the canonical clinical use and support disclaimer in the Medical Advice Disclaimer section below.
-
Check the documentation
- README.md - Getting started and overview
- User Guide - Application usage, testing workflows, and URL reference
- ARCHITECTURE.md - System architecture
- CONTRIBUTING.md - Contribution guidelines
docs/- Detailed documentation
-
Search existing resources
- GitHub Issues - Known bugs and feature requests
- GitHub Discussions - Past questions and discussions
- Closed Issues - Previously resolved problems
-
Verify your setup
- Ensure you have the correct .NET version (see
global.json) - Check that all dependencies are installed
- Review error messages carefully
- Ensure you have the correct .NET version (see
Use GitHub Discussions for:
- General questions about using GenPRES
- Design discussions and architectural questions
- Feature ideas and brainstorming
- Clinical use cases and scenarios
- Best practices and implementation advice
Create a new discussion in the appropriate category:
- Q&A: Questions about using or developing GenPRES
- Ideas: Feature requests and suggestions
- Show and Tell: Share your implementations or extensions
- General: Other discussions
Include in your question:
- Clear, descriptive title
- What you're trying to accomplish
- What you've tried so far
- Relevant code snippets or configuration
- Error messages (if applicable)
- Environment details (OS, .NET version, browser)
Use GitHub Issues only for:
- Bug reports - Something is broken or incorrect
- Feature requests - Specific, well-defined new functionality
- Documentation improvements - Errors or gaps in documentation
Do NOT use issues for:
- General questions (use Discussions instead)
- Support requests (use Discussions instead)
- Debugging help (use Discussions first)
When creating an issue, use the appropriate template and provide:
- Clear reproduction steps for bugs
- Expected vs actual behavior
- Environment information
- Screenshots or error messages
- Relevant code snippets
For questions related to:
- Clinical accuracy of dosing calculations
- Safety concerns with medication recommendations
- Medical literature references or validation
- Regulatory compliance questions
Please:
- Review existing clinical documentation in
docs/scenarios/anddocs/mdr/ - Search for related issues with
safetyorclinicallabels - Create a discussion in the Q&A category with
[Clinical]prefix - Be prepared to provide clinical context and references
For urgent safety concerns, see SECURITY.md for responsible disclosure process.
If you've solved a problem or learned something useful:
- Answer questions in Discussions
- Improve documentation via pull request
- Share your experience in Show and Tell
- Report bugs you discover
- Contribute code following CONTRIBUTING.md
- GitHub Discussions for questions
- GitHub Issues for bugs and features
- Community-driven responses
- Best-effort support from maintainers and community
Response time: Variable, typically 1-7 days depending on complexity and community activity
For organizations requiring:
- SLA-based support
- Priority bug fixes
- Custom feature development
- Regulatory consulting
- Integration assistance
- Training and onboarding
Contact: [INSERT PROFESSIONAL SUPPORT CONTACT]
## What I'm trying to do
[Clear description of your goal]
## What I've tried
[Steps you've already taken]
## Environment
- OS: [macOS/Windows/Linux]
- .NET version: [output of `dotnet --version`]
- GenPRES version: [version or commit hash]
- Browser: [if UI-related]
## Additional context
[Any other relevant information]
## Description
[What's wrong]
## Steps to Reproduce
1. [First step]
2. [Second step]
3. [...]
## Expected Behavior
[What should happen]
## Actual Behavior
[What actually happens]
## Error Messages
[Full error messages or stack traces]
## Environment
- OS: [macOS/Windows/Linux]
- .NET version: [output of `dotnet --version`]
- GenPRES version: [version or commit hash]
- Browser: [if UI-related]
## Screenshots
[If applicable]
## Problem Statement
[What problem does this solve?]
## Proposed Solution
[How should it work?]
## Alternatives Considered
[What else could solve this problem?]
## Clinical/Safety Implications
[Any patient safety considerations?]
## Additional Context
[Links to literature, guidelines, or examples]
- Simple questions: Often answered within 1-3 days
- Complex questions: May take 1-2 weeks
- No guarantee of response time
- Community members and maintainers respond when available
- Critical safety bugs: Within 24-48 hours
- Major bugs: Within 1 week
- Minor bugs: As time permits
- Priority based on severity and impact
- Initial response: Within 1-2 weeks
- Implementation: Based on roadmap and priorities
- May be marked as "help wanted" for community contribution
All interactions must follow our Code of Conduct. We expect:
- Respectful communication
- Professional behavior
- Patience with volunteers and community members
- Clear, constructive feedback
Primary language for support is English. This ensures:
- Broader community participation
- Better searchability of past discussions
- Consistency in documentation
Canonical disclaimer: This repository contains the source code and documentation for GenPRES. It does not include professional support services, and it is not intended for direct clinical use without appropriate validation and regulatory approval.
- Do not use GitHub for urgent clinical questions
- Do not rely solely on software for patient care decisions
- Always verify calculations and recommendations with appropriate clinical expertise
- Follow your institution's policies and protocols
For medical emergencies or urgent clinical questions, contact appropriate medical professionals.
When asking questions:
- Never share actual patient data
- Never include PHI (Protected Health Information)
- Use anonymized or synthetic examples
- Respect patient privacy and GDPR/HIPAA requirements
Violations will be removed and may result in access restrictions.
- README.md - Project overview
- ARCHITECTURE.md - System architecture
- CONTRIBUTING.md - How to contribute
docs/mdr/- Medical device regulatory documentationdocs/scenarios/- Clinical scenario examples
We welcome feedback on how to improve our support process:
- Open a discussion in the General category
- Suggest documentation improvements
- Share what worked well or could be better
Last updated: 2025-12-09
Thank you for being part of the GenPRES community! 🚀