-
Type:
Epic
-
Resolution: Unresolved
-
Priority:
High
-
Affects Version/s: None
-
None
-
Truenat Testing and Result-Based Case Management
-
STOP TB Sprint 8
As a Lab Technician / Nurse / Counsellor / authorized Camp User, I want the application to automatically create and manage Truenat test orders under the beneficiary's Visit ID, capture MTB/RIF test results through either automated device integration or manual entry, and trigger the appropriate next action based on the test result, so that Truenat testing, repeat testing, clinical referral, TB treatment referral, and end-of-day order closure can be managed systematically with complete traceability.
Source: Confluence AMRIT space — "Truenat Test Workflow Epic" (page 171737114) - Truenat Test Workflow Epic - AMRIT - Confluence
Preconditions
- The beneficiary is registered in the application.
- TB Symptoms Screening based on verbal questions has been completed.
- A Visit ID has been generated against the beneficiary.
- The beneficiary has been referred for a Truenat test.
- For automated result capture, the Truenat testing device is integrated with the application through the approved integration mechanism.
Test Order Status
| Status | Definition |
|---|---|
| Pending | Test Order ID created, but test is not yet completed with a valid result |
| Completed | Test conducted and a valid result other than Invalid/Error has been captured |
| Closed | Order is no longer active, including EoD closure, not conducted, invalid/error attempt, or other applicable closure |
Business Rules
| ID | Business Rule |
|---|---|
| BR-01 | Visit ID shall be created after completion of TB Symptoms Screening. |
| BR-02 | Every new Truenat referral shall generate a unique Test Order ID. |
| BR-03 | Multiple Test Order IDs can exist under one Visit ID on the same date. |
| BR-04 | Every Test Order ID is valid for one day. |
| BR-05 | Valid result → Order Status = Completed. |
| BR-06 | Invalid/Error result → Current Order Status = Closed and repeat order is created. |
| BR-07 | Test Not Conducted → Reason is mandatory and Order Status = Closed. |
| BR-08 | Pending order with no valid result at EoD → Order Status = Closed. |
| BR-09 | Closed orders shall not be overwritten or reused. |
| BR-10 | A new order may be created against the beneficiary after an order is closed, subject to applicable workflow. |
| BR-11 | Automated and Manual result capture shall follow the same result-processing rules. |
| BR-12 | All test attempts and results shall remain available in the beneficiary's test history. |
Audit & Traceability Requirements — for every Test Order ID, the system should maintain: Beneficiary ID, Visit ID, Test Order ID, Test Type (MTB/RIF), Parent/Previous Test Order ID, Attempt Number, Order Date & Time, Test Date & Time, Order Status, Test Result, Result Source (Automated/Manual), Result Entered By, Result Received Date & Time, Closure Reason, Closure Date & Time, Created By/Updated By, Referral/Next Action, Device/Integration reference (where automated).
Status Matrix
| Scenario | Status |
|---|---|
| New MTB Order | Pending |
| MTB Positive | Completed |
| MTB Negative | Completed |
| MTB Invalid – repeat required with new test order id | Closed |
| MTB Invalid after final repeat at EoD | Closed |
| MTB not conducted | Closed |
| MTB result not entered at EoD | Closed |
| New RIF Order | Pending |
| RIF DR TB | Completed |
| RIF Non-DR TB | Completed |
| RIF Indeterminate | Completed |
| RIF Invalid – repeat required with new test order id | Closed |
| RIF Invalid after final repeat at EoD | Closed |
| RIF not conducted | Closed |
| RIF result not entered at EoD | Closed |
