Skip to main content

Data explosion and aging population meet in the hospital

It is breathtaking to read the statistics highlighting the sheer growth of data that is being captured globally. For example, every two days we create as much information as we did from the beginning of time until 2003; over 90% of all the data in the world was created over the past two years; if we burn all the data created in just one day onto CD-ROMs we could stack them on top of each other and reach the moon twice.
Although traditionally the healthcare industry has lagged behind other industries in implementing technology, there is no reason to think that it will not embrace this trend of data explosion. We are seeing new medical devices collecting high-resolution data being introduced to the market and wearable devices promising disruptive breakthroughs. This year there will be over 1.2 billon smartphones in the world which are stuffed full of sensors and data collection features.
Another trend that has been already discussed at length is that of the ageing population. The world is getting older, especially in developed countries. Within 20 years, many countries in Europe will count citizens over 65 as their largest population cohort. By contrast, the number of hospital beds is increasing at a very slow rate. In fact, according to the NHS, over the past three decades, the number of hospital beds has been steadily declining.
The net result of these two trends converging is that hospitals in the future will have to operate like intensive care units operate today. Patients who will be admitted to general and acute wards are likely to be sicker than in the past and will require constant monitoring. The type of decision support tools that are being used in critical care, like smart alerts, automatic scores and fluid balance calculation, will have to find their way to the general wards.
Hospitals need to prepare for what is coming: high-resolution data being captured and analysed on a near real-time basis, from numerous and diverse data sources.
There is also going to be a push to tap into data collected outside the hospital from community and personal data repositories, as the information that can be extracted from these sources can be critical to the care of the patient. This information is valuable for a variety of purposes including predictive analysis, research, preventive medicine, continuum of care from community and more.
Here are a few things that hospital chief information officers should be thinking of today in order to prepare their organisation for this inevitable future:
  1. Ensure that your electronic patient record has the ability to deal with high-resolution data, both in terms of storage and compute. If this functionality doesn’t exist today, it should at least be on the vendor roadmap
  2. Address device connectivity as a strategy – it shouldn’t be an isolated solution for a particular ward or specific device
  3. Separate between clinical data repositories (CDRs) and applications. This approach will help provide accessibility to the data necessary for various utilities (e.g. predictive algorithms, evidence-based medicine and research). A CDR must provide a common and secure interface for accessing its data (e.g. FHIR). It is OK for a system to provide both CDR and end user functionality, as long as its primary role is that of master of the data
There is no question that grappling with the plethora of data out there today presents some short-term pain. I firmly believe, however, that with the right approach, hospitals can capitalise on the advances in clinical information management in order to realise high-impact clinical, financial and operational results.

Comments

Popular posts from this blog

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

The big battle: Best of breed vs One stop shop

The world of economics has decided on this debate a long time ago: monopolies are bad, diversity is good. No matter what a monopoly promises, you can rest assure that over time the lack of competition will cause prices to go up and quality to go down. When it comes to healthcare IT, however, there is one unique factor that flips the coin – interoperability. Despite various attempts the healthcare industry has yet to solve the interoperability challenge in a satisfactory manner which will enable a full continuum of care across different health information systems within a health delivery organization. Taking a common scenario of prescribing a medication order in theatres using a surgical system to be later administered in a ward requires significant investment to achieve, even using the modern Fast Health Interoperability Resource (FHIR) protocol. The investment required to streamline the data flow across systems raise in an exponential order with every new system that is thrown to t

Are we ready for a Cloud First hospital?

I will start this article by defining what I mean by the term a Cloud First hospital. The term cloud has been a buzz word in the past decade which led many organizations to declare their support for the cloud, sometime without understanding its true meaning. For the purpose of this article I am proposing a simple test to decide whether an organization is a cloud first or not. If you are software vendor you must have an IT department which directly in charge of the system up-time at your clients sites. If you are a health organization then you should never have visited the data center where your data resides. A Cloud First hospital is one which more than 50% of its systems reside in data center that none of its staff members ever visited or not even sure where they are. According to a recent survey by Datica, in the US only 17.7 percent of the respondents say they work with healthcare organizations that have more than 50% of the existing software infrastructure remotely hosted or