User Story: Truenat Test Result-Based Workflow

Epic: Truenat Testing and Result-Based Case Management

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.

  1. Preconditions
  1. The beneficiary is registered in the application.
  2. TB Symptoms Screening based on verbal questions has been completed.
  3. A Visit ID has been generated against the beneficiary.
  4. The beneficiary has been referred for a Truenat test.
  5. For automated result capture, the Truenat testing device is integrated with the application through the approved integration mechanism.
  1. Functional User Story

US-TRUENAT-001: Create Visit and Truenat Test Order

As a system,
I want to create a Visit ID after completion of TB Symptoms Screening and create a Test Order ID whenever a new Truenat referral is generated,
so that every Truenat test can be uniquely identified and tracked against the beneficiary's visit.

Acceptance Criteria

AC-01: Visit ID Creation

  • Given TB Symptoms Screening is completed,
  • When the screening is submitted successfully,
  • Then the system shall create a unique Visit ID against the beneficiary.

AC-02: New Truenat Referral

  • Given a valid Visit ID exists,
  • When a new Truenat test referral is generated,
  • Then the system shall automatically create a unique Test Order ID under the Visit ID.

AC-03: Multiple Orders

  • The system shall allow multiple Test Order IDs to be created against the same Visit ID on the same date.
  • Each Test Order ID shall have its own status, result, timestamps and audit trail.
  • A closed Test Order ID shall not be overwritten or reused.

AC-04: Order Validity

  • Each Test Order ID shall be valid for one day only.
  • Any open/pending order remaining at the end of the day shall be automatically closed.
  1. Test Order Status

The system shall support the following Test Order statuses:

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 Rule

BR-01: An order shall be marked Completed only when a valid test result is captured.

BR-02: An Invalid/Error result shall not make the order Completed. The current order shall be closed and a new order shall be created for repeat testing.

  1. User Story: Capture Truenat Result

US-TRUENAT-002: Capture Test Result Through Automated or Manual Mode

As a Lab Technician / Nurse / Counsellor,
I want to capture Truenat test results either automatically from an integrated Truenat device or manually,
so that the application can support both integrated and field-operational testing scenarios.

Acceptance Criteria

AC-05: Automated Result Capture

When the Truenat testing device is integrated:

  1. The test result shall be received automatically from the Truenat device.
  2. The result shall be associated with the correct:
    • Beneficiary ID
    • Visit ID
    • Test Order ID
    • Test Type
  3. The system shall validate the received result before updating the order.
  4. A valid result shall update the Test Order ID to Completed.
  5. An Invalid/Error result shall trigger the repeat-test workflow.

AC-06: Manual Result Capture

When automated integration is unavailable:

  1. Authorized users shall have the option to manually enter the result.
  2. Authorized users shall include:
    • Lab Technician
    • Nurse
    • Counsellor
  3. The user shall select the applicable Test Order ID and Test Type.
  4. The user shall select one of the predefined result values.
  5. The system shall apply the same result-based business rules used for automated results.
  6. The system shall record the result source as Manual.

Important: Automated and Manual result capture shall use the same downstream business rules. The difference is only the source of the result.

  1. Truenat MTB Test User Story

US-TRUENAT-003: Process Truenat MTB Result

As a system,
I want to process the Truenat MTB result according to predefined result rules,
so that the beneficiary is automatically routed to the appropriate next step.

MTB Result Options

  1. TB Positive (Detected)
  2. TB Negative (Not Detected)
  3. Invalid / Error

Acceptance Criteria

MTB Result

System Action

Order Status

TB Positive (Detected)

Complete MTB order and create Truenat RIF Test Order ID

Completed

TB Negative + X-Ray Normal

No further action required

Completed

TB Negative + X-Ray Abnormal but not TB Presumptive

Refer for Clinical Assessment & Diagnosis

Completed

TB Negative + X-Ray TB Presumptive

Refer for Clinical Assessment & Diagnosis

Completed

Invalid / Error

Save result, close current order and create new MTB order for repeat test

Closed

AC-07: MTB Positive

When MTB result is TB Positive (Detected):

  1. The system shall save the result.
  2. The MTB Test Order ID shall be marked Completed.
  3. The system shall automatically create a new Truenat RIF Test Order ID under the same Visit ID.
  4. The new RIF order shall have status Pending.
  5. The RIF order shall maintain a reference to the MTB order that triggered it.

AC-08: MTB Negative + Normal Chest X-Ray

When:

  • MTB = TB Negative (Not Detected), and
  • Chest X-Ray = Normal

Then:

  1. MTB order shall be marked Completed.
  2. No additional diagnostic referral shall be generated.
  3. The beneficiary shall not be referred to RIF testing based on this result combination.

AC-09: MTB Negative + Abnormal Chest X-Ray

When:

  • MTB = TB Negative, and
  • Chest X-Ray = Abnormal but not TB Presumptive

OR

  • MTB = TB Negative, and
  • Chest X-Ray = TB Presumptive

Then:

  1. MTB order shall be marked Completed.
  2. The system shall generate a referral for Further Clinical Assessment & Diagnosis.
  3. The referral shall be recorded against the beneficiary/Visit ID.

AC-10: MTB Invalid/Error

When MTB result is Invalid / Error:

  1. The system shall save the Invalid/Error result.
  2. The current MTB Test Order ID shall be changed to Closed.
  3. The system shall automatically create a new MTB Test Order ID under the same Visit ID.
  4. The new order shall have status Pending.
  5. The new order shall be identified as a repeat test.
  6. The previous order shall remain available in the beneficiary's test history.
  1. Truenat RIF Test User Story

US-TRUENAT-004: Process Truenat RIF Result

As a system,
I want to process the Truenat RIF result and trigger the appropriate TB treatment or clinical assessment workflow,
so that confirmed TB/DR-TB cases can be appropriately flagged and referred.

RIF Result Options

  1. DR TB (Rif Resistance Detected)
  2. Non-DR TB (Rif Resistance Not Detected)
  3. Indeterminate
  4. Invalid / Error

Acceptance Criteria

RIF Result

System Action

Order Status

DR TB

Flag confirmed DR-TB case and refer for DOTS/appropriate DR-TB treatment

Completed

Non-DR TB

Flag confirmed TB case and refer for DOTS/appropriate TB treatment

Completed

Indeterminate

Refer for further Clinical Assessment & Diagnosis

Completed

Invalid / Error

Save result, close current order and create new RIF order for repeat test

Closed

AC-11: RIF DR-TB

When RIF result is DR TB (Rif Resistance Detected):

  1. Save the result.
  2. Mark the RIF Test Order ID as Completed.
  3. Flag the beneficiary as a Confirmed DR-TB Case.
  4. Generate a referral for DOTS/appropriate DR-TB treatment as per program protocol.
  5. Record the referral against the beneficiary/Visit ID.

AC-12: RIF Non-DR TB

When RIF result is Non-DR TB (Rif Resistance Not Detected):

  1. Save the result.
  2. Mark the RIF Test Order ID as Completed.
  3. Flag the beneficiary as a Confirmed TB Case.
  4. Generate a referral for DOTS/appropriate TB treatment as per program protocol.

AC-13: RIF Indeterminate

When RIF result is Indeterminate:

  1. Save the result.
  2. Mark the RIF order as Completed.
  3. Generate a referral for Further Clinical Assessment & Diagnosis.

AC-14: RIF Invalid/Error

When RIF result is Invalid / Error:

  1. Save the result.
  2. Close the current RIF Test Order ID.
  3. Automatically create a new RIF Test Order ID under the same Visit ID.
  4. Set the new order to Pending.
  5. Mark the new order as a repeat test.
  6. Preserve the previous Invalid/Error order in the test history.
  1. User Story: Test Not Conducted

US-TRUENAT-005: Close Test Order When Test Is Not Conducted

As a Lab Technician / Nurse / Counsellor,
I want to close a Test Order when the test is not conducted and capture the reason,
so that every Test Order has a clear and auditable outcome.

Acceptance Criteria

AC-15: MTB Test Not Conducted

If the MTB test is not conducted:

  1. User shall select Test Not Conducted.
  2. The system shall make Reason mandatory.
  3. The user shall enter/select the reason.
  4. The MTB Test Order ID shall be changed to Closed.
  5. The closure date/time and user shall be recorded.

AC-16: RIF Test Not Conducted

The same rule shall apply to RIF:

  1. Test Not Conducted shall be selected.
  2. Reason shall be mandatory.
  3. RIF Test Order ID shall be marked Closed.
  4. Closure details shall be recorded.
  1. User Story: End-of-Day Order Closure

US-TRUENAT-006: Automatically Close Open Orders at EoD

As a system,
I want to automatically close all applicable open/pending Truenat Test Orders at the end of the day,
so that no Test Order remains active beyond its one-day validity.

Acceptance Criteria

At EoD, the system shall identify Truenat Test Orders with status Pending where:

  • Test was not conducted; or
  • Result has not been entered/received; or
  • The order has reached the end of its one-day validity.

The system shall:

  1. Change the order status to Closed.
  2. Record EoD as the closure reason.
  3. Record closure date/time.
  4. Maintain the complete order history.
  5. Ensure that a new Test Order can subsequently be created from the beneficiary record when required.

Important Rule

A Completed order shall not be closed by the EoD process because it already represents a successfully completed test.

An Invalid/Error attempt is closed as soon as the result is recorded, and a new repeat order is created. If the repeat order remains Pending at EoD, that repeat order shall subsequently be closed by EoD.

  1. User Story: Create New Test Order for Closed Order

US-TRUENAT-007: Re-Order Truenat Test

As a Lab Technician / Nurse / Counsellor / authorized user,
I want to create a new Test Order ID for a beneficiary whose previous order is closed,
so that the test can be performed again when required.

Acceptance Criteria

  1. The beneficiary record/card shall display the previous Test Order status.
  2. If the order is Closed, the system shall provide a Create New Test Order option, subject to applicable referral/business rules.
  3. The new order shall:
    • Have a unique Test Order ID.
    • Be linked to the same Visit ID where applicable.
    • Have status Pending.
    • Record the previous order as the Parent/Previous Order ID where applicable.
  4. The previous closed order shall remain unchanged.
  5. The new order shall appear as a separate test attempt in the test history.
  1. End-to-End Business Workflow

TB Symptoms Screening Completed

              ↓

        Create Visit ID

              ↓

     New Truenat Referral

              ↓

      Create Test Order ID

              ↓

          Status: Pending

              ↓

     ┌────────┴─────────┐

     ↓                  ↓

Automated Result    Manual Result

(Device)            (User Entry)

     └────────┬─────────┘

              ↓

       Result Captured

              ↓

       ┌──────┴───────┐

       ↓              ↓

   MTB Test        RIF Test

       ↓              ↓

   MTB Result      RIF Result

       ↓              ↓

 ┌─────┼──────┐   ┌───┼──────────────┐

 ↓     ↓      ↓   ↓   ↓       ↓      ↓

Pos.  Neg.  Invalid DR  Non-DR  Indeterminate Invalid

 ↓     ↓      ↓   ↓     ↓          ↓       ↓

RIF   X-Ray   Repeat  Confirmed  Confirmed Clinical Repeat

 ↓    Check    MTB     DR-TB       TB      Assessment RIF

 ↓      ↓                         ↓          ↓

RIF   Normal                    DOTS/      Clinical

Order   ↓                       TB Tx      Assessment

 ↓    No Action

 ↓

 └──────────────────────────────────────────

                    ↓

          Pending Orders at EoD

                    ↓

              Status = Closed


  1. 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.

  1. 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

Example of Repeat Test History

Visit ID: V10001


MTB Order M10001

Result: Invalid/Error

Status: Closed

        ↓

MTB Order M10002

Result: Invalid/Error

Status: Closed

        ↓

MTB Order M10003

Result: TB Positive

Status: Completed

        ↓

RIF Order R10001

Result: Non-DR TB

Status: Completed

        ↓

Flag: Confirmed TB Case

        ↓

Refer for DOTS / TB Treatment

This design ensures that every Truenat test attempt is independently traceable, while the Visit ID provides the overall clinical journey for the beneficiary.


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


17. Complete Functional Workflow

                 


  • No labels

1 Comment

  1. Shivani Garg

    Hey Madhava Ramu N

    • What happens to a patient sent for "Clinical Assessment & Diagnosis"?
      Does our system track what happens after that, or does it just end there for us?
    • Does the RIF test have to happen right after MTB comes back positive, or can there be a delay?
      And if RIF never gets done for that patient, does anyone follow up?
    • If RIF testing gets skipped for someone who's already MTB Positive, is that a bigger deal than a normal skipped test?
      Should there be extra follow-up since this decides their treatment path?
    • How many times can we retry a test that keeps coming back "Invalid/Error"?
      Is there a limit, or can staff keep trying all day until it auto-closes?
    • When someone is flagged as "Confirmed DR TB" or "Confirmed TB Case," does our system need to actually notify the treatment program, or just save the flag?
    • Should "Invalid/Error" be a manual option too, or should staff use a different label when it's a human decision instead of a device error?
    • Can a lab tech fix a mistake after a result is already saved?
      For example, if they picked the wrong result and it already created a RIF order or a DR TB flag — can that be corrected?
    • Is "end of day" the same exact time/cutoff as the X-ray workflow, since both are on the same patient visit?
    • If the Truenat device sends a result but we can't tell which patient it belongs to, what should happen?
    • Are the X-ray result names ("Normal," "Abnormal but not TB Presumptive," "TB Presumptive") written exactly the same way in both systems?
      Want to make sure they match so the two workflows connect properly.