Skip to content

Latest commit

 

History

History
48 lines (32 loc) · 1.65 KB

File metadata and controls

48 lines (32 loc) · 1.65 KB

Contributing to Upstream Intelligence

Thanks for your interest. Open contributions help every operator on the network.

This file is the org wide fallback. Each repository may have its own CONTRIBUTING.md with repo specific guidance. When the repo has its own, that one wins.

Quick start

  1. Find an issue labeled good first issue or help wanted
  2. Comment on the issue to claim it (avoids duplicate work)
  3. Fork the repository
  4. Create a feature branch from main
  5. Make your changes with tests
  6. Submit a pull request linking the original issue

What we welcome

  • Bug fixes with tests that prove the fix
  • Documentation improvements that make a concept clearer
  • Reference data coverage (CARC/RARC codes, payer registries — submit in upstream-community)
  • Specialty-specific enhancements across the eight verticals we cover
  • Performance improvements with before and after measurements
  • Better example queries
  • Notebooks demonstrating real workflows

What is out of scope

  • Anything requiring proprietary payer data
  • Anything requiring production Upstream internals
  • Vendor specific integrations without community demand
  • Cosmetic refactors without functional improvement
  • AI generated PRs without a human review of the diff

Code style

Follow the existing style in each repo. We do not enforce a global standard.

Healthcare data

This is healthcare software. Never include PHI in any contribution. Tests use synthetic data only. If you need data, use CMS public datasets and document the source.

License

By contributing, you agree your contributions are licensed under the same MIT license as the repository.

Questions

hello@upstream.cx