[Demo Video] Message Operational Data Store
#North American Demo Showcase entry.
>> Answer the question below to be entered in the raffle!
⏯️ Message Operational Data Store
Create an operational data store using the data flowing through your production. Create user-defined analytics tables based on fields and paths to their data from incoming documents with varying standards (FHIR, CDA, HL7v2, etc.).
Presenters:
🗣 @Kwabena Ayim-Aboagye, Sales Engineer at InterSystems
🗣 @Christopher Carmichael, Sales Engineer at InterSystems
🗣 @Jeff Semmens, Senior Sales Engineer at InterSystems
To enter the raffle, please answer the following question in the comments:
What is a collection table?
Each correct answer increases your chances! 💪
Comments
Thank you for this demo about aggregating different data: HL7, FHIR... in the same table.
For the raffle: A collection table is a user-defined data table that is dynamically populated with selected fields extracted from messages flowing through the integration engine (e.g., HL7, FHIR, CDA).
Imagine a busy airport where passengers arrive from all over the world, each speaking different languages and carrying different types of documents.
A collection table is like a smart customs desk that, in real time, picks out the same key details from every traveler: name, nationality, destination...; no matter what language their passport is in, and writes them neatly into a single standardized logbook.
This way, instead of dealing with hundreds of different document formats, the airport staff can instantly see clear, consistent information to monitor traffic, spot issues, or make decisions... without needing to archive and analyze every original document later!! ✈️
Thanks to @Kwabena Ayim-Aboagye, @Jeff Morgan Semmens and @Christopher Carmichael for this demo!
What is a collection table?
It’s a table dynamically populated with key fields extracted from incoming messages, used to aggregate and analyze data.
What is a collection table?
It is a data table that is dynamically populated through integration, in this example, with HL7.
What is a collection table?
A collection table is a data table dynamically populated with selected fields extracted from incoming messages.
What is a collection table?
a table of messages and the path to the data based on message type
What is a collection table?
It is a data table that is dynamically populated through integration, in this example, with HL7.
Hey Devs!
🙌6 members have already responded to the question and got into the raffle.
Join them for a chance to win a gift. Watch the video and reply:
What is a collection table?
🤩The more correct answers you give, the better your odds!
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.