This article was originally published by the e-Health magazine in its June '15 issue.
These are interesting times for India’s e-Governance in general and the country’s eHealth, in particular. Over the last couple of years, we have witnessed the government’s concerted effort to standardise data, metadata, communication protocols and processes in the health sector.
Interesting times indeed! While EHR adoption in India is still catching up, we have several international national eHealth system use-case scenarios to learn from. We are perfectly poised to take stock, clarify our direction and start building the right information systems for the India of tomorrow.
This is where we have to remember that the end state we hope to achieve is Utopian and the ask is Herculean.
With EHRs installed at every point of care and exchanging data via Health Information Exchanges, the benefit to stakeholders is huge.
Medical records are not lost. They are no longer in silos, each with a different healthcare provider. Doctors have a better insight into the patient’s history. This helps the former take better decisions. Test results are not misplaced.
The implementation of universal coverage becomes much easier. Public health programs are better focused and more effective with the availability of rich and more accurate data. The list could go on. For all these benefits to see the light of day, there are challenges to be met and compromises to be made.
Apart from the usual technical laundry list of challenges like handling de-duplication, legacy data, security, scale, usability and more , there are perhaps a few just as if not more important factors to deal with.
A successful national eHealth system needs sufficient electricity and network connectivity which means it has to be much better than it is now.
We plan to use Aadhar cards to identify people in the proposed new national eHealth system. However, around 27% of the country still need to get their Aadhar cards done.
The current concept note to create NeHA mentions interagency cooperation; how well cooperation is achieved will decide the success of the program.
One of the biggest compromises would be eating into doctors’ time. In a country where the doctor to patient ratio is already skewed, providing additional responsibilities to doctors will definitely affect the care provided.
However, as it is imperative that solutions like the Electronic Health Record (EHR) not affect patient care, the EHR systems need to be more robust, tactical remedies like implementing transcription could help. Apart from this, judicious consideration of how much data is collected might be required. Add to this a long term vision of increasing the number of practicing doctors (by building more medical colleges), and we have the makings of a solution.
This is no easy task, especially when stakeholder requirements are in conflict.
Here is an example - today, most health data collection happens at the aggregate level - this makes it easier to collect and maintain. Most policy decisions are based on such data. However, while tactical decisions can maximise the system's’ utility, unless detailed patient records are collected, the system is in fact ignoring patients.
What would help, here is making the complex decision of how much data is enough for a clinician to capture. And this is a hard decision - what is better for patient care, is it more data at the cost of a doctor’s time or an incomplete patient record. Here, answers are not simple to find and such decisions are taken based on experience. Keeping the program’s end goal; bringing a smile to the patient’s face, in mind ensures the right decisions are taken.
What makes these tough decisions worth it? That, in these times of data driven decisions, relevant data analyses performed for public policy be part of the public domain as open data. Taking the right steps to ensure an excellent healthcare system for our and future generations also means taking bold, confident and careful steps towards that future.
To view the published article, click here.
Disclaimer: The statements and opinions expressed in this article are those of the author(s) and do not necessarily reflect the positions of Thoughtworks.