Having a dynamic table that updates from different source messages, such as files, HL7, FHIR, and CCD, would be very useful. One important use case is linking records to FHIR store resource IDs—for example, linking a FHIR Observation ID to a unique HL7 identifier derived from an Epic encounter ID plus an LRR ID. This would support conditional updates to FHIR resources and also serve as a preprocessing layer for extracting refined data from the FHIR store for LLM AI need, analytics and dashboards. The idea aligns with FHIR resource identification and conditional update patterns, as well as C-CDA-to-FHIR mapping where repeated encounter references are consolidated into a single FHIR resource.