Team may look into adding new sections in documentation to cover following points
HRP are software service providers who offer ABDM compliant software and long term record storage to different HIPs. The documentation should have a new section to define the responsibilities of HRP as data fiduciary to store long term records. The section should provide the guidelines on the format of data for long term storage (assume it would be FHIR repository), technical and operational guidelines to manage cybersecurity of health data stored in HRP repository and technical measures to be implemented by HRP to manage long term data retention as per NHA Data retention policy.
A new section in documentation may be added on defining the different technical approaches for software integrators to connect their different tenant HIP databases with a cloud based HRP repository (in case HIP has a on-premises database) . The HIP can push data to HRP repository whenever the visit is closed or HRP can pull on demand the health records from HIP databases .The documentation may provide reference examples for integrators to define the process of sending and retrieving data between HIP or HIU database and HRP Repository.
3 A new section should be added in documentation to cover the networking configuration to be done by integrators to connect on premises HIP/HIU with cloud HRP bridge (in hybrid cloud model) as cloud HRP bridge will have public apis exposed to ABDM ecosystem and the on premises HIP systems will be behind firewalls.
These detailed sections in documentation will help software integrators in ABDM integration and implementations with different HIP/HIUs.
Team may look into adding new sections in documentation to cover following points
HRP are software service providers who offer ABDM compliant software and long term record storage to different HIPs. The documentation should have a new section to define the responsibilities of HRP as data fiduciary to store long term records. The section should provide the guidelines on the format of data for long term storage (assume it would be FHIR repository), technical and operational guidelines to manage cybersecurity of health data stored in HRP repository and technical measures to be implemented by HRP to manage long term data retention as per NHA Data retention policy.
A new section in documentation may be added on defining the different technical approaches for software integrators to connect their different tenant HIP databases with a cloud based HRP repository (in case HIP has a on-premises database) . The HIP can push data to HRP repository whenever the visit is closed or HRP can pull on demand the health records from HIP databases .The documentation may provide reference examples for integrators to define the process of sending and retrieving data between HIP or HIU database and HRP Repository.
3 A new section should be added in documentation to cover the networking configuration to be done by integrators to connect on premises HIP/HIU with cloud HRP bridge (in hybrid cloud model) as cloud HRP bridge will have public apis exposed to ABDM ecosystem and the on premises HIP systems will be behind firewalls.
These detailed sections in documentation will help software integrators in ABDM integration and implementations with different HIP/HIUs.