# Looking for help on two new OpenELIS features

**URL:** <https://talk.openelis-global.org/t/looking-for-help-on-two-new-openelis-features/2319>\
**Category:** Development\
**Created:** [April 23, 2026, 5:09am UTC](https://talk.openelis-global.org/t/looking-for-help-on-two-new-openelis-features/2319 "2026-04-23T05:09:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![caseyi](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/caseyi/32/65_2.png) [@caseyi](https://talk.openelis-global.org/u/caseyi)\
**Post date:** [April 23, 2026, 5:09am UTC](https://talk.openelis-global.org/t/looking-for-help-on-two-new-openelis-features/2319/1 "2026-04-23T05:09:35Z")

</div>

**Looking for help on two new OpenELIS features**

Hi folks — our team at DIGI-UW has been working with a few labs running OpenELIS Global and we keep hearing about two small-but-real gaps we’d love community help closing. We’ve put together full designs, interactive mockups, and acceptance criteria for both. If you’ve been looking for a way to contribute that has a clear spec and visible mockup, we’d really appreciate the help!

**[Help wanted: Analyzer Manual QC Recording](https://github.com/DIGI-UW/OpenELIS-Global-2/issues/3490)** — Right now, techs running manual QC on bench analyzers either log it on paper or in a separate module, disconnected from the patient results they’re about to process. This feature adds a small QC status strip on the analyzer import page with one-click inline QC entry — no screen switching. Smaller of the two, good first project for someone new to the codebase. [Live mockup here.](https://digi-uw.github.io/openelis-work/#/quality/analyzer-manual-qc)

**[Help wanted: Batch Workplan with Reagent QC Integration](https://github.com/DIGI-UW/OpenELIS-Global-2/issues/3491)** — Replaces the four current workplan screens (By Test / By Panel / By Lab Unit / By Priority) with one unified page, with reagent-lot QC status visible at the moment you pick a lot for your batch. If QC is overdue you can enter it inline, or proceed with an auto-generated Non-Conforming Event so nothing slips through. Bigger project — could be split between frontend and backend. [Live mockup here.](https://digi-uw.github.io/openelis-work/#/quality/batch-workplan-reagent-qc)

Both features close gaps where patient samples can end up run against instruments or reagent lots that weren’t QC’d today — a real patient-safety issue and a common ISO 15189 audit finding.

If anyone’s interested in picking one (or part of one) up, comment on the issue or drop a note here. Happy to help you get oriented and answer questions. Thanks for reading!

---

<div class="post-metadata">

**Author:** ![nigar08](https://avatars.discourse-cdn.com/v4/letter/n/e9bcb4/32.png) [@nigar08](https://talk.openelis-global.org/u/nigar08)\
**Post date:** [April 23, 2026, 1:05pm UTC](https://talk.openelis-global.org/t/looking-for-help-on-two-new-openelis-features/2319/2 "2026-04-23T13:05:48Z")

</div>

Hi @caseyi , thanks for the detailed spec and mockup. I went through the Analyzer Manual QC flow and also looked at how it relates to the Batch Workplan QC work. My understanding is that the main backend piece here is a shared QcRun history/status flow, where analyzer level QC uses analyzerId and leaves reagentLotId null, while the Batch Workplan can later reuse the same model for reagent-lot QC.

I’d be happy to help with the backend/API side for Analyzer Manual QC and coordinate around the shared QcRun foundation so it lines up cleanly with the Batch Workplan work.

---

<div class="post-metadata">

**Author:** ![priyanshu56](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/priyanshu56/32/1148_2.png) [@priyanshu56](https://talk.openelis-global.org/u/priyanshu56)\
**Post date:** [April 23, 2026, 3:52pm UTC](https://talk.openelis-global.org/t/looking-for-help-on-two-new-openelis-features/2319/3 "2026-04-23T15:52:05Z")

</div>

Hi! I’d love to work on this feature. I have experience with React, Node.js, and backend APIs, and this seems like a great contribution opportunity. Could you guide me on the initial setup and relevant parts of the codebase?

---

<div class="post-metadata">

**Author:** ![Agaba\_Derrick\_Junior](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/agaba_derrick_junior/32/503_2.png) [@Agaba\_Derrick\_Junior](https://talk.openelis-global.org/u/Agaba_Derrick_Junior)\
**Post date:** [April 26, 2026, 7:02am UTC](https://talk.openelis-global.org/t/looking-for-help-on-two-new-openelis-features/2319/4 "2026-04-26T07:02:24Z")

</div>


