SPIKE: Pulling relevant encounters to the Reportable Conditions Summary

What needs to be done

Determine if we can modify the TCR service to stamp Encounter resources and pull this information to the Reportable Conditions summary.

Although we do not currently pull relevant encounter information to the Conditions Summary, this could potentially be useful information for epis and case investigators, especially since we've encountered RCKMS Rules based on encounter information.

Example eCR: Link

Why it needs to be done

The Relevant lab & clinical info sections in the eCR Summary help epis and case investigators get a sense of what exactly in the whole eCR document caused the eCR to be sent to them. Pulling up these most relevant bits of information to the top can help them to make a decision more quickly about what to do with the document and what data to look for in more detail in the whole eCR. If we don't display the right information there, we may not actually save any time, so we want to make sure that we have a good sense of how this functionality is working for a few eCRs so we can make sure one of the big value propositions of the eCR Viewer is going to work when pilots are in full gear.

Timebox

How much time should be dedicated to this spike?

To-do list

[ ] Check if there are other examples of eCRS with encounters in their triggerable RCKMS rule summary.
[ ] Are there codes associated with the encounter RCKMS rule? Are there codes associated with the Encounter that could be stamped? Would it be possible to stamp these encounters in the TCR service and bubble this information to the Condition Summary?

Additional context

Relevant files:

TCR Service: containers/trigger-code-reference/app/main.py

CDCgov / phdi