Get Help

Where to ask for help with OpenELIS Global — for users, implementers, developers, and operators.

Search before you ask. Most questions have been asked before. Try the search box at the top of this Confluence space first, then search OpenMRS Talk, then look at GitHub issues. Reposting a known issue or question slows everyone down — including the next person who searches for the same thing.

By what you need

"How do I…" usage questions

You're trying to do a thing in OpenELIS and you need to know which buttons to click.

Look in the section that matches your role: For Lab Staff, For Implementers, For Operators, For Developers.
If it's a specific feature, check Modules & Features.
If you can't find it, post on OpenMRS Talk with a clear subject line ("How do I configure X for Y?") and tag your version (v3.1, v3.2, etc.).

"It's broken" bug reports

Something that worked yesterday doesn't work today, or the system is behaving in a way that contradicts the documentation.

Reproduce the bug fresh — clear browser cache, try a different browser, log out and back in.
Gather: OpenELIS version (look at the footer or Site Information), browser version, exact steps to reproduce, what you expected, what happened, screenshots if visual.
Search GitHub Issues for similar reports. If found, add a comment with your reproduction details.
If new, file a new issue with the gathered details. Use clear titles like "Validation page: results disappear after clicking Save" not "validation broken".

"I want a new feature" enhancement requests

The system doesn't do something you need.

Search GitHub Issues and OpenMRS Talk to see if it's been proposed before.
Read the Releases roadmap to see if it's already on the plan.
If new, file an enhancement issue on GitHub with the "enhancement" label. Describe the user problem first, then propose a solution. Implementers and the OE team triage these regularly.

"The docs are wrong / out of date"

You found a Confluence page that doesn't match what the system actually does.

Quickest: add an inline comment on the specific page (highlight the wrong text and click the comment bubble in Confluence). Be specific about what you observed in the live system and what version you're on.
If you can edit: edit the page directly. Add a version stamp at the bottom ("Verified against v3.2.1.x — YYYY-MM-DD by your-name"). Save with a meaningful version message.
If you can't edit but want to flag broadly: post in OpenMRS Talk with a link to the page and what's wrong.

"I'm an implementer and I need help during a deployment"

Your installation isn't going well and you're under time pressure.

Read the relevant page in For Implementers first — installation order matters and skipping steps causes 80% of issues.
Check the Troubleshooting page for common failures.
Post on OpenMRS Talk with subject like "[Implementation] OpenMRS integration not receiving orders — v3.1, fresh install" and include: exact error messages, what step you're on, what you've tried.
For urgent production-blocking issues that affect a deployment, reach out directly to the OpenELIS team via Talk (mention @OpenELIS_Team) or by emailing the team contact listed in the project README.

"I'm a developer and I want to contribute"

See the For Developers section for the onboarding path. Coordinate with the team in Talk before starting substantial work.

By channel

Channel	Best for	Response time

Channel	Best for	Response time
OpenMRS Talk — OpenELIS Global	Usage questions, integration questions, design discussions, broad announcements	Hours to days; volunteer community
GitHub Issues	Bugs with reproductions, feature requests, code-level questions	Days; maintainers triage on a cadence
Confluence inline comments	Documentation fixes, version mismatches, "this page is wrong" feedback	Days; the doc team reads regularly
Confluence page mentions	Tagging specific contributors for follow-up	Days; depends on the person
Direct email to project lead	Sensitive issues (security, governance), implementation escalations	Reserve for things the public channels can't address

Etiquette

Be specific. "It doesn't work" is unhelpful. "When I click Save on the validation page in v3.1, I get a 500 error and the browser console shows…" gives someone a starting point.
Include your version. Always. The system behaves differently across versions.
Show what you tried. "I read the install guide and tried steps A, B, C; X happened" is much faster to help with than "doesn't work".
Update threads when you find the answer. Post the resolution so the next person who hits it has a path forward.
The community is volunteer. Maintainers and contributors help on their own time. Be kind, patient, and respectful.

Reporting a security issue

If you've found a security vulnerability in OpenELIS Global, do not file a public GitHub issue. Email the project security contact (see the project README) with details and reproduction steps. The team will work with you on responsible disclosure.

🆘 Get Help