Skip to content

AMM-2128 new table for tb confirmed cases #82

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.

Sign up for GitHub

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

Open
SauravBizbRolly wants to merge 1 commit into
base: main
Choose a base branch
from
Open

AMM-2128 new table for tb confirmed cases #82

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 34 additions & 0 deletions src/main/resources/db/migration/dbiemr/V41__TB_conformed_cases_DB_IEMR.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
USE db_iemr;

CREATE TABLE IF NOT EXISTS `tb_confirmed_cases` (

@coderabbitai coderabbitai Bot Jan 21, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ 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).

`id` INT NOT NULL AUTO_INCREMENT,
`ben_id` BIGINT NOT NULL,
`regimen_type` VARCHAR(100) DEFAULT NULL,
`treatment_start_date` DATE NOT NULL,
`expected_treatment_completion_date` DATE DEFAULT NULL,
`follow_up_date` DATE DEFAULT NULL,
`monthly_follow_up_done` VARCHAR(20) DEFAULT NULL,
`adherence_to_medicines` VARCHAR(20) DEFAULT NULL,
`any_discomfort` TINYINT(1) DEFAULT NULL,
`treatment_completed` TINYINT(1) DEFAULT NULL,
`actual_treatment_completion_date` DATE DEFAULT NULL,
`treatment_outcome` VARCHAR(100) DEFAULT NULL,
`date_of_death` DATE DEFAULT NULL,
`place_of_death` VARCHAR(100) DEFAULT NULL,
`reason_for_death` VARCHAR(100) DEFAULT NULL,
`reason_for_not_completing` VARCHAR(255) DEFAULT NULL,
`created_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
`updated_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
`user_id` INT DEFAULT NULL,

PRIMARY KEY (`id`),
INDEX `idx_ben_id` (`ben_id`),
INDEX `idx_treatment_start_date` (`treatment_start_date`),
INDEX `idx_follow_up_date` (`follow_up_date`),
INDEX `idx_user_id` (`user_id`)

) ENGINE=InnoDB
AUTO_INCREMENT=1
DEFAULT CHARSET=utf8mb4
COLLATE=utf8mb4_unicode_ci
COMMENT='TB Confirmed Cases Treatment Tracking';
Loading