Increase clinical_event.EVENT_TYPE size from 20 to 50 characters to a…

[PRASHANTS19]

Title: Increase clinical_event.EVENT_TYPE column size to 50 characters to support longer event names (#11512)

Description:
This PR addresses the limitation of the EVENT_TYPE field in the clinical_event table being restricted to 20 characters. Users reported that this limits their ability to use descriptive event types like "Progressive Brain Metastasis".

The change increases the column size to VARCHAR(50) in the database schema to accommodate longer event names. This improves flexibility for clinical event data capture without affecting existing data constraints.

Details of changes:

Modified clinical_event table schema to change EVENT_TYPE from VARCHAR(20) to VARCHAR(50).

Ensured the change is backward-compatible and does not affect other components of the system.

For existing databases:
We need to create a new migration file or alter script that runs an ALTER TABLE statement like:
ALTER TABLE clinical_event MODIFY COLUMN EVENT_TYPE VARCHAR(50) NOT NULL;

Impact:
This change allows users to store more descriptive clinical event types and improves usability in clinical timelines or reports that use this data.

[PRASHANTS19]

Hi Team,can any one look into this PR.
Thanks!

[dippindots]

Hi @PRASHANTS19, I think this change makes sense and we can increase the EVENT_TYPE size to a larger value.

I’ve included an example PR
that shows a similar change, including the required database scheme changes. You can use it as a reference and make updates accordingly. Just a reminder: whenever we modify the database schema, we also need to update the database version.

Please let me know if you’d like me to help with this.

[dippindots]

Hi @PRASHANTS19, thanks for working on this ticket! We’ll need to close this PR since it’s missing the necessary database schema updates. I’ve opened another PR to address the same ticket: #11752