-
Notifications
You must be signed in to change notification settings - Fork 341
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guide as how to enable ABDM and hcx plug apps in care #2779
Comments
We recently had an architecture change in the backend and the ABDM plugins are being rewritten for the same, you can integrate with the old plugin but that would likely change in the next two weeks. |
We check after 2 weeks, but architecture change means getting ABDM compliance certificate again? I was intending to use ABDM compliant HMIS to accelerate our hospital certification efforts |
The ABDM architecture remains the same, its maintained and built in a separate repo as a plugin, the core care architecture is changing and that might cause some changes in ABDM plugin as well. mostly in hooks that connect ABDM plugin to care. |
Ok
…On Mon, 27 Jan 2025, 15:09 Vignesh Hari, ***@***.***> wrote:
The ABDM architecture remains the same, its maintained and built in a
separate repo as a plugin, the core care architecture is changing and that
might cause some changes in ABDM plugin as well. mostly in hooks that
connect ABDM plugin to care.
—
Reply to this email directly, view it on GitHub
<#2779 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHH34WMWAEJT4OATCHR6WOT2MX5GNAVCNFSM6AAAAABV3WFRQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJVGI3DENRRHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Is your feature request related to a problem? Please describe.
Steps to include ABDM and hcx plug apps in care, I have tried it by modifying plug_config.py file but built error is...no module ABDM. This is going help those who have ABDM credentials available.
The text was updated successfully, but these errors were encountered: