Apologies first up, I was little lazy of creating separate issues (or grouped appropriately together). I will try to be more organized in future :) .. nevertheless
Setup an end point URL for your health repository or consumer health application
setup access URL for your HRP or HIU or Health Locker applications
Link health facilities with your health repository
Link a health facility (HIP) with your health repository (HRP)
need to explain role of HRP - either as a hosted SaaS, or just acting as a bridge. Also even a HIP needs to implement the APIs meant for HRP. In a way, everyone must abide by the HRP specs
Should we calling it PHR framework - or FHR framework?
PHR is an application, FHR allows PHR and Lockers to be created
Add to HIP example
any entity which creates medical data pertaining to a patient.
any entity that creates Health Information for a patient.
also include wearable like Fitbit sort of devices
Such an instance of an ABDM certified software is a HRP.
HIUs will be able to request for health records of a user, and upon obtaining the user’s digital consent, access a copy of the patients records and use them for the time period consented by the user.
also add : HIUs can also request for subscriptions for health information whenever new care context is linked or has additional data
What is HIE-CM
HIE-CM is primarily responsible for maintaining linkage of patient records at HIPs, suspension and deletion of such linkages
Managing patient approvals for "authentication" for specific purpose like linking, consent request and grant management, and also approvals for subscriptions
HIE-CM is responsible for managing the life cycle of consent - grants and revocation
ABHA Address
ABHA address can be created using mobile number, email id or ABHA number
Every ABHA number also automatically acts as a ABHA address on the HIE-CM and looks like <14digitabha>@abdm
does this automatically create the PHR address in HIE-CM? Not sure ...
How HIE CM works
When a new record is generated by health facility it adds a link called a care context ... rephrase: when new record is generated by the health facility, it creates a link with a "care context". Explain care context better with examples
Sharing Health Records With Consent
need better image - lines are not visible
If the user grants the consent, the HIE-CM shares a signed consent artificat with the the requesting HIU
HIE-CM generates two copies of consent artefact. One copy is shared with HIU and the other with HIP
Health Locker - does not need to provide a PHR app (consent management process). Its also a HIU + HIP
Should we specifically list out capabilities of Health Locker
PHR app capabilities
--- allow see consented requested, allow revocation of consent,
--- delink, suspend linkages with PHR
--- approve requests for authentication for HIP initiated linking
--- manage subscriptions
--- 12. Act as a HRP for users health records and share it on demand - is not mandatory!
Apologies first up, I was little lazy of creating separate issues (or grouped appropriately together). I will try to be more organized in future :) .. nevertheless
link: https://kiranma72.github.io/abdm-docs/1-basics/index.html
link: https://kiranma72.github.io/abdm-docs/1-basics/about_abdm_sandbox/index.html
Image
link: https://kiranma72.github.io/abdm-docs/1-basics/the_phr_framework/index.html
Link: https://kiranma72.github.io/abdm-docs/1-basics/postman_setup/index.html
Link: https://kiranma72.github.io/abdm-docs/1-basics/making_your_app_abdm_compliant/index.html