appliesResult to StratifierResult in detailed results output

[elsaperelli]

Summary

This PR adds an optional attribute to the StratifierResult interface so that we can report the result of a stratifier that includes an appliesTo extension for Patient-based Measures only.

New behavior

The appliesTo extension indicates which population a stratifier should apply to. If it is included on a Measure.group.stratifier, we now report the result of the stratifier AND the result of the population it applies to on the appliesResult attribute on the StratifierResult. The previous result attribute remains as it was: simply the result of the stratifier. The DetailedResults now contain the raw stratifier result in result (like before) as well as the result of the stratifier with the population result it applies to taken into consideration in appliesResult.

Code changes

• src/calculation/DetailedResultsBuilder.ts - add AND logic of population result and stratifier result to appliesResult attribute of StratifierResults for patient based measures
• src/types/Calculator.ts - add optional appliesResult attribute to StratifierResult interface
• test/unit/DetailedResultsBuilder.test.ts - unit tests for described changes

Testing guidance

• Run detailed results with the measure and patient bundles provided in Calculation for Stratification does not consider associated population #306 . This can be done in a variety of ways but I personally just the cli: npm run cli -- detailed -m <path to mb> --p <path to patient bundle (I think the file they provide is in an array so just make sure to get rid of that)> -s 2025-01-01 -e 2025-12-31 --trust-meta-profile true -o --debug
• Inspect the detailedResults.json. Make sure the stratifierResults.result are the same as before and the stratifierResults.appliesResult are correct based on the population result that stratifier applies to.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟢	Statements	85.35% (+0.09% 🔼)	2423/2839
🟡	Branches	72.89% (+0.09% 🔼)	2269/3113
🟢	Functions	87.47% (+0.1% 🔼)	433/495
🟢	Lines	85.65% (+0.09% 🔼)	2340/2732

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟡	... / MeasureReportBuilder.ts	73.26% (-0.67% 🔻)	54.77% (-1.21% 🔻)	66.67% (-0.98% 🔻)	76.02% (-0.57% 🔻)

Test suite run success

456 tests passing in 31 suites.

Report generated by 🧪jest coverage report action from 8fd71a3

[lmd59]

Looks good to me!

[hossenlopp]

The place where the appliedResult is created needs to be moved to have accurate results.

[hossenlopp]

This isn't the right place to get the results for population as the patientResults is the raw data from the engine. The define statement that provides the results might not match the code. Should look back at the populationResults that have already been collected and find by populationType.

[hossenlopp]

Additionally the populationResults will not be accurate at this point and should happen after the call to handlePoulationValues on line 35.

[hossenlopp]

This call to isStatementValueTruthy shouldn't be needed as the && should be done on the result and the boolean result found in the populationResults.

[hossenlopp]

A handful of things in the new function.

It should also be run on the individual episode results after handlePopulationValues at https://github.com/projecttacoma/fqm-execution/blob/master/src/calculation/DetailedResultsBuilder.ts#L439.

The code in the measure report builder that does appliesTo logic could be removed and the appliedResult could be used instead of the result.

[hossenlopp]

Looks good to me.

[hossenlopp]

I like the Stratification addition to the README. This looks ready to go!

[lmd59]

Made one optional test description clarification