Hello @dkayiwa and the OpenMRS Community,
My name is Kanishka Bhati, and I am a B.Tech Computer Science student. I am writing to express my strong interest in the “Archiving voided data” project for GSoC 2026.
I have a solid foundation in Core Java and have already achieved my /dev/1 (Smart Developer) status within the community. I’ve also successfully submitted my first documentation PR to the Developer Manual.
I am particularly drawn to this project because it focuses on backend data management and logic, which aligns well with my academic background and my previous project work on virtual file systems. I have already begun reviewing the project description and the OpenMRS data model to understand how voided observations and encounters are currently handled.
A few initial questions to help me prepare my proposal:
-
Are there any specific “warm-up” tickets or related modules I should look at to better understand the current “soft-delete” implementation?
-
Is there a preferred archival strategy (e.g., moving to separate shadow tables vs. a dedicated archive database) that the community is currently leaning toward?
I am eager to contribute to OpenMRS and look forward to your guidance!
Best regards,
Kanishka Bhati
OpenMRS ID: bhatikanishka9