3.6 Report Testing Notes

FHIR integration

Measures

In the `Insert List of Measures` (ReplaceText) processor inside the `Check for Measures` Processor group, there is a list of measures to be generated and their descriptions.

After files have run through the flow and through the final InvokeHTTP processor named `Post Measure Resources to server` there will be a number of flowfiles that passes through the response relationship.

So, if the number of measures in the list and the number of flow files at the end is the same, then the test was a success, otherwise, the test has failed.

MeasureReports

• For each requisition check that the total number or reports generates is the same as the total number of measures

• Check that the values in the measure reports for the measures such as beginning_balance and stock_on_hand, match the values in the requisition

• Check that the reference to the Measure resource is as expected

• Check that the reference to the Location resource is as expected

Reports

Below are the scenarios we are going to test around the indicator queries. Successes will be highlighted green and failures will be highlighted red.

Reporting Rate and Timeliness

1. Requisition A is AUTHORIZED 4 days after the end of the processing period

   1. Facility should be counted as reporting “on time”

2. Requisition B is AUTHORIZED 12 days after the end of the processing period

   1. Facility should be counted as reporting “late”

3. Requisition C is AUTHORIZED 24 days after the end of the processing period

   1. Facility should be counted as reporting “unscheduled”

4. Requisition D never reaches the status of AUTHORIZED

   1. Facility should be counted as “did not report”

Stock Status

1. Requisition A (can use the same one as above) has stock on hand = 0 for a product

   1. This should give a stock status of “stock out”

2. Requisition B (ditto) has months of stock = 0 for a different product

   1. This should give a stock status of “stock out” and the Periods of Stock column in the Stock Status Table should read 0

3. Requisition C has has months of stock between 3 and 6 of a product

   1. This should give a stock status of “adequately stocked”

4. Requisition A has months of stock between 0 and 3 of a product

   1. This should give a stock status of “understocked”

5. Requisition B has months of stock greater than 6 for a product

   1. This should give a stock status of “overstocked”

Stockouts

1. Use 1a) above also to test stockouts

2. I think you can use one of the scenarios above where MOS > 0 to test that those facilities are NOT being counted as stocked out for those products

Consumption

1. Create a requisition, fill in all of the fields shown in the screenshot below, and confirm they are displayed accurately

2. Confirm that the line chart accurately displays adjusted consumption for that facility. Note that you need to apply a filter for a single product, otherwise the chart aggregates consumption for all products

Orders

1. Complete a requisition with these fields populated and confirm that they display correctly

2. Create an emergency order and confirm that the pie chart displays an emergency order

Adjustments

1. Create an adjustment and confirm the data displays in the table correctly