Skip to main content

Clinical data warehouses: Sometimes it's worth being lazy


If you are a health organization you probably have or thinking of having a clinical data warehouse.

A Clinical Data Warehouse (CDW), sometimes called Clinical Data Repository (CDR), is a database that consolidates data from a variety of clinical sources to form a unified view of a the data for various purposes. Typical data types which are often found within a CDW include: clinical laboratory test results, vital signs, patient demographics, administered meds, hospital admissions, ICD-9 codes and more.

Developing and sustaining an effective CDW operations unit is a substantial effort and long-term commitment. The main challenge in designing a CDW is defining its scope and the use cases it should support. In theory a CDW can serve as a basis for reporting, studying and planning. The use case that is often mentioned in relate to CDW is supporting clinical trials. This would allow for researchers to have all the information from a study in one place as well as let other researchers benefit from the data to further innovation.

The challenge experienced by the stakeholders is that their needs vary depending on the clinical procedures and data formats. In order to please the fuzzy goals of the various stakeholders within the health organization IT teams spend most of their time gathering and modeling data instead of interpreting information and finding opportunities for cutting costs and improving patient care.

The two familiar design approaches are top–down and bottom–up. The top–down design approach provides the final shape of the system. This approach starts with defining an Enterprise Data Model (EDM) and constructing the pieces to reach the final goal. The bottom–up approach on the other hand starts with dividing the large problem into small pieces of obstacles and solving each obstacle individually.

A “by-the-book” development approach which most health organization adopt is top–down. It is a systematic approach which helps in decreasing integration obstacles and team collaboration. This approach is however time consuming and difficult to implement because concept consistency is difficult to achieve for all clinical organization data.
The bottom–up design approach is preferable for design, implementation and development of clinical data marts. This approach is characterized by flexibility and low implementation cost of CDW data marts, but it faces difficulty in integrating various data marts in the clinical enterprise of CDW.

In recent years No-SQL database engines have matured and so is their adoption rate. A No-SQL database supports schema-on-demand which is also referred to as Late binding. With late binding it is possible to execute complex queries on a large dataset in an effective manner without having to define first an EDM.
With late binding instead of spending months and even years to implement a data warehouse as in the case of the traditional early-binding approach, health systems can launch their CDW in weeks.
Late-binding data warehouses are also more scalable and adaptable to the industry-specific problems healthcare organizations are trying to solve.

Successful early EDW leaders ignored the Enterprise Data Model (EDM) in favor of late binding. In a fluid environment, an EDM is outdated as soon as it’s complete. Also, due to the nature of the EDM process (continuous modelling and mapping), data architects never finish mapping. Every time there’s a change in the environment, they have to go back and change the model, the ETL, and the downstream analytics. 

Healthcare is undergoing changes to business rules and vocabulary at an unprecedented rate. The Late-binding data warehouse provides not only faster time-to-value, it also enables the agility required for today’s healthcare analytics demands.
If your health organization hasn’t yet implemented a CDW, you may have profited from waiting that long. Using late binding and the growing echo system of No-SQL engines, you may be able to catch up with those organizations who started long time ago.


Comments

Popular posts from this blog

FHIR Status Check

 More than 2 years have past since I wrote my article  on the Fast Healthcare Interoperability Resources (FHIR®) standard and it’s time to do a quick status check and revisit the predictions I made back then. The FHIR standard continues the strong trajectory of adoption and is now used across the globe. The application programming interface (i.e. the FHIR API) is available in most major EHR systems today. According to the US Office of the National Coordinator Health Information Technology an estimated 85% of hospitals have FHIR in their systems. The NHS has been quick to adopt FHIR and the adoption curve in the UK is high. The NPfIT (NHS Care Record Service) HL7 V3 interfaces are being redeveloped in FHIR®, and new NHS specifications such as the CareConnect standard for secured Transfer of Care  are being specified in FHIR® by default. Despite the industry enthusiasm about the potential of FHIR still the old and faithful HL7 v2 remains the predominant interoperability sta...

Your Hospital on FHIR

As a technologist, I am always skeptical when hearing about a brand new technology that is going to solve all of our current problems. I feel it is my responsibility to warn people about these types of promises. Claims of “solving all healthcare information exchange (HIE) problems” are often being made about the emerging HL7 FHIR standard. According to Gartner’s hype cycle, the standard is at the “Peak of Inflated Expectations,” which I view as a stage where wishful thinking fills the gap created by a lack of knowledge and understanding. FHIR, which stands for Fast Healthcare Interoperability Resources, is a draft standard from HL7 International. This standard is designed to be easier to implement, more open and more extensible than its predecessors, V2 and V3 standards. So what’s the big deal here? Aren’t we simply replacing one transport protocol with another? FHIR claims to bring a change in paradigm to the way health information can be accessed and consumed. Since FHIR is ...

The case for PAA

PAA stands for Patient Admission App. In a nutshell it is a platform in which the hospital can communicate with its patients and their relatives before, during and after their stay in  the hospital. A patient's encounter with a hospital is often a traumatic event to both the patient and his family. A lack of  proper communication between the parties can have major implications on the hospital efficiency and the patient's experience which research shows has a critical impact on the quality of care. From red tape to red carpet  A PAA should accompany the patient throughout his journey by keeping him informed and engaged. This starts prior to the actual admission when the patient feels scared, anxious and confused. A PAA should provide the patient with all the information related to his upcoming treatment. This can include treatment reminders such as not to eat x hours before a planned anesthesia, orientation map, etc. It should also handle in...