· Jul 13, 2018

HealthShare Patient Index - Extracting Data from Cache

Is Cache the preferred database source for extracting data elements for use in Health Share Patient Index or is there a significant benefit in sourcing data from a warehouse, data mart, or MV? I realize that could be a loaded question with 100 other questions that may follow, however, if there is a known advantage to extracting data from a particular data storage type, the answer may highlight that point. 

Our team is in the inception and elaboration phase of using the Health Share Patient Index solution. Our road map has checkpoints to integrate data storage within a Cache DB as well as into a warehouse and/or data mart(s). Essentially, what I want to know is there a significant advantage to sourcing data from Cache vs a warehouse or data mart so that we may elaborate the idea further and plan accordingly. 

Discussion (1)1
Log in or sign up to continue

Late in replying but the differences between sourcing data from Cache vs a warehouse/data mart is that Cache will be able to provide you real-time information vs a warehouse/data mart which can have some degree of staleness, but that's likely obvious.  The advantage with a warehouse/datamart is that you could bring in other data and join with that data.  At the same time, there would be nothing to exclude you from bringing in external data in the HSPI namespace.   We at Ready Computing have extensive experience with reporting of the HSPI data.  This includes several ZEN reports, although note that the ZEN reports are just calling SQL Stored Procedures we wrote.  We also have DeepSee cubes defined that provide analysis on both the Patient table as well as the Classified pairs data.  It should be noted that the Classified pairs table has a number of indices defined to support most use cases for SQL queries.  Lastly, we've not found issues with the definition of the Patient table as far as performance goes.