You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now, the LLM is only able to access health data resources via function calling that are available upon initialization of the LLM, as can be seen here:
The code line above results in the fact that FHIRStore updates won't propagate to the LLM function, meaning the most up-to-date health data that becomes available during the application lifecycle won't be accessible to the LLM.
Solution
An example solution would be to use the Observable conformance of FHIRStore and utilize this to get informed about updates, re-assign the parameter property wrapper with new values, and then re-register for observation changes.
Additional context
No response
Code of Conduct
I agree to follow this project's Code of Conduct and Contributing Guidelines
The text was updated successfully, but these errors were encountered:
Problem
As of now, the LLM is only able to access health data resources via function calling that are available upon initialization of the LLM, as can be seen here:
SpeziFHIR/Sources/SpeziFHIRLLM/FHIRInterpretation/MultipleResources/FHIRGetResourceLLMFunction.swift
Line 37 in 9a171a2
The code line above results in the fact that
FHIRStore
updates won't propagate to the LLM function, meaning the most up-to-date health data that becomes available during the application lifecycle won't be accessible to the LLM.Solution
An example solution would be to use the
Observable
conformance ofFHIRStore
and utilize this to get informed about updates, re-assign the parameter property wrapper with new values, and then re-register for observation changes.Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: