Your new post is loading...
NDHM Architecture
NDHM is employing a federated architecture for its ecosystem. That means that management and data access occurs in a federated manner where different entities or systems will manage the health data.
There is no central data storage controlling and storing data.
Using the Federated Health Records Framework (FHR), patients can access and view their health records, and provide consent to any HIPs and HIUs to access their data.
To ensure smooth consented data sharing and time-bound data access, it is necessary to make the data traceable and auditable. Therefore the FHR Framework architecture leverages MeitY's Data Empowerment and Protection Architecture (DEPA) electronic consent framework, which is already being used in the financial sector.
Here are some interesting technical features of the NDHM ecosystem
FHIR for all Medical Data
Asynchronous APIs
Patient Privacy & Security Features of NDHM
- HIPs can only create data if authorized by the Patient:
- An HIU(Health Information User) can only get past health records of other HIPs if consented by Patient
- Peer to Peer Data Transfer Between HIP & HIU
Final Thoughts
It is one thing to have a concept and another thing to implement and execute it. So far NDHM seems to be going in the right direction. And there is hope that it will continue to do so.
Technology is being given equal importance to gain the trust of all players involved in this industry.
Privacy and Security have been a prime priority in the project as you can see from the above article, this is an oft-ignored aspect in old projects. Hope it continues to stay this way.
read the whole article at http://technology4doctors.blogspot.com/2021/05/an-overview-of-ndhms-technology.html
