Mobile Patient Data Systems: query-based vs. event-driven
Yesterday, I spoke with Michael Murphy of MercuryMD to get some background on this company and to find about their current focus. One of the questions I asked was the time required for syncing the pertinent patient data. Michael gave me a thorough answer on their solution to this problem and he sent me their latest technical brief, Designed for Performance. (Again, in the ever-so-popular PDF format that I continue to rail against.)
The publication provides a comparison between query-based systems which must search through the hospital's main database to find updates relevant to the person initiating the sync, versus their event-driven model which uses a staging database to duplicate data that will be required for sync'ing the device. In essence, it is a data cache meant to spare the main database the competition for processing time required for culling delta data required for each sync. Michael claims that this model allows a memory requirement of only 2-3 MB for most users without need to store any data on an expansion card.
I'm just beginning to compare vendors and their strategies as well as case studies to come to a conclusion about the best solution at this time. As my research progresses, I'll try to survey as many vendors as possible before I can come to any conclusions.
8:10:17 AM 
|
