OP number not to be unique if readmitted to same facility

[rithviknishad]

Is your feature request related to a problem? Please describe. When a patient is readmitted to the same facility and both the consultation (new and previous) are Out-patient consultations (decision after consultation), the OP number may be the same as the last consultation's OP number. However, currently it throws an error

Describe the solution you'd like

• [ ] Need not perform a unique validation check for OP consultations if the previous consultation's facility is the same as the new consultation's facility.
• [ ] If the previous consultation's facility is the same as the new consultation's facility, maybe we could auto-fill the OP Number field with the last consultation's OP No.? (To be discussed and finalized and NOT a priority, can be done separately)

Additional context

cc: @nihal467 @aparnacoronasafe

[github-actions[bot]]

:warning: Refrain from assigning this issue to yourself if you have another P1 issue assigned that is not yet closed.

[aparnacoronasafe]

The requirement here is to remove any type of Data validation on the OP No. field. Irrespective of the facility the patient is admitted to.

Discussed with @gigincg

CC: @rithviknishad @skks1212 @nihal467

REASON: The issue is, some hospitals are utilising this field to add their Patient ID (MRD No) for the patient, which may be consistent across all encounters for the patient in the facility. This is an acceptable behaviour. In order to allow this, remove all data validation from the field

[sainak]

The requirement here is to remove any type of Data validation on the OP No. field. Irrespective of the facility the patient is admitted to.

Discussed with @gigincg

CC: @rithviknishad @skks1212 @nihal467

REASON: The issue is, some hospitals are utilising this field to add their Patient ID (MRD No) for the patient, which may be consistent across all encounters for the patient in the facility. This is an acceptable behaviour. In order to allow this, remove all data validation from the field

@aparnacoronasafe the field is handling many responsibilities, should we consider splitting it up?

cc: @gigincg

[gigincg]

The requirement here is to remove any type of Data validation on the OP No. field. Irrespective of the facility the patient is admitted to.

Discussed with @gigincg

CC: @rithviknishad @skks1212 @nihal467

REASON: The issue is, some hospitals are utilising this field to add their Patient ID (MRD No) for the patient, which may be consistent across all encounters for the patient in the facility. This is an acceptable behaviour. In order to allow this, remove all data validation from the field

@aparnacoronasafe I thought we finalized on dropping Validations for Both OP and IP Numbers.

[rithviknishad]

https://github.com/coronasafe/care_fe/issues/7798

[aparnacoronasafe]

please proceed with removing all validations for both IP and OP field