AMM-2128 new table for tb confirmed cases

[SauravBizbRolly]

📋 Description

JIRA ID: AMM-2128

new table for tb confirmed cases

✅ Type of Change

• 🐞 Bug fix (non-breaking change which resolves an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 🔥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 🛠 Refactor (change that is neither a fix nor a new feature)
• ⚙️ Config change (configuration file or build script updates)
• 📚 Documentation (updates to docs or readme)
• 🧪 Tests (adding new or updating existing tests)
• 🎨 UI/UX (changes that affect the user interface)
• 🚀 Performance (improves performance)
• 🧹 Chore (miscellaneous changes that don't modify src or test files)

---

ℹ️ Additional Information

Please describe how the changes were tested, and include any relevant screenshots, logs, or other information that provides additional context.

Summary by CodeRabbit

• New Features
  • Added database support for TB confirmed cases management, enabling comprehensive tracking of patient information and treatment progress for clinical oversight.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

A new SQL migration file is added that creates the tb_confirmed_cases table for tracking tuberculosis patient cases and treatment information, including fields for patient identification, treatment dates, follow-up dates, and auditing timestamps with appropriate indexes.

Changes

Cohort / File(s)	Summary
Database Migration - TB Case Tracking src/main/resources/db/migration/dbiemr/V41__TB_conformed_cases_DB_IEMR.sql	Creates tb_confirmed_cases table with patient/treatment tracking fields, composite indexes on ben_id, treatment_start_date, follow_up_date, and user_id, standard audit timestamps, InnoDB engine, and UTF-8 character encoding.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 A hop and a skip through the migration stream,
New tables arise like a database dream,
TB cases tracked with indices so bright,
Patient records shining, everything right!
The carrot-shaped path to health data true,
Version forty-one hops through the queue! 🥕

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'AMM-2128 new table for tb confirmed cases' is directly related to the changeset, which adds a new SQL migration creating the tb_confirmed_cases table.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@src/main/resources/db/migration/dbiemr/V41__TB_conformed_cases_DB_IEMR.sql`:
- Line 3: The migration filename contains a misspelling ("conformed") that
doesn't match the created table `tb_confirmed_cases`; rename the migration file
V41__TB_conformed_cases_DB_IEMR.sql to V41__TB_confirmed_cases_DB_IEMR.sql so it
accurately reflects the table name, and update any references to the old
filename in your migration tooling or documentation (and re-run checks or adjust
any stored checksums if your migration system tracks filenames).

🧹 Nitpick comments (2)

src/main/resources/db/migration/dbiemr/V41__TB_conformed_cases_DB_IEMR.sql (2)

1-1: Avoid hard‑coding the schema in migrations.

Using USE db_iemr; can break deployments where the migration runner sets the schema or where the DB user lacks USE privileges. Prefer relying on the configured schema unless this is a repo-wide convention.

✅ Suggested change

-USE db_iemr;
-

---

5-22: Confirm referential integrity strategy for ben_id and user_id.

If these columns reference parent tables, consider adding FK constraints (or explicitly documenting that integrity is enforced at the application layer) to avoid orphaned records.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Align migration filename spelling with the table name.

The migration file says “conformed” while the table is “confirmed.” Consider renaming the migration to match for clarity and future traceability.

🤖 Prompt for AI Agents

In `@src/main/resources/db/migration/dbiemr/V41__TB_conformed_cases_DB_IEMR.sql`
at line 3, The migration filename contains a misspelling ("conformed") that
doesn't match the created table `tb_confirmed_cases`; rename the migration file
V41__TB_conformed_cases_DB_IEMR.sql to V41__TB_confirmed_cases_DB_IEMR.sql so it
accurately reflects the table name, and update any references to the old
filename in your migration tooling or documentation (and re-run checks or adjust
any stored checksums if your migration system tracks filenames).