Sekar/pc poc

[vvenglaturmsft]

Purpose

• ...

Does this introduce a breaking change?

[ ] Yes
[ X] No

Pull Request Type

What kind of change does this Pull Request introduce?
This is a draft PR for patient context management to ensure patient context is determined and maintained

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information

[matthiasblondeel]

I think my main question is why do we need the PATIENT_CONTEXT_JSON to be sent to the agents

The snapshot is programmatically generated, and agents don't need this information. Could we not get rid of it?

[matthiasblondeel]

Are these facts still used?

[vvenglaturmsft]

Right now it is empty {} but the infrastructure is in place for when we add patient specific metadata if required so the agents do not have to re-parse the history. If we dont need we can remove this. I will ask lukas to d othat

[matthiasblondeel]

Why do we still need this ephemeral/patient context for the agents?

[vvenglaturmsft]

This is primarily being used for agent grounding. while agents might be able to infer the patient identity through history the ephemeral snapshot ensures immediate and more accurate patient context. It also maintaints the session patients so that multiple use cases can be addressed. I will ask lukas to try without it but i think it might fail a few use cases. But we can definitely check it out