@NNSiri the "Feed" tab/button is hidden for any of the following reasons as of today:

• No bed assigned to the patient
• No camera is attached/configured to the patient's bed.
• The consultation has ended (discharged).
• User is not one of the following: "District Admin", "State Admin", "Doctor"

@NNSiri could you also specify which user type this bug is present for? The screenshots attached above does not confirm if both are same users.

@gigincg read-only users of the above mentioned users also does not have access to the camera feed from consultation dashboard. Should we allow for read only user types?

@rithviknishad

• Bed is assigned to the patient
• Camera was configured to the patient (later we found that the presets were getting deleted) this is observed in many hospitals . So may be we should restrict who deletes the Camera Presets.
• The consultation was not ended. Patient is not yet discharged
• User : State Admin

@rithviknishad We understood, that the issue is observed when the presets are deleted. but we do not know who deleted the presets. can we restrict the delete option, and keep only edit preset option. ?

@NNSiri The presets being deleted seems is being repeatedly reported from the field now. We can work on improving the audit trail for Preset Deletions to track this better.

@rithviknishad Can you update the issue to improve the AssetBed through table as well as add audit-trail for soft deleted presets

Updated the issue body with the following:

Currently, each camera bed preset is stored as an individual AssetBed record (1 preset => 1 AssetBed record; 10 presets => 10 AssetBed records). This is not very efficient. Instead a camera (asset) can be linked to a bed (which represents an AssetBed record), and multiple presets can be added for this AssetBed record.

Action Items

• Create a new model CameraPreset (having many-to-one relation with AssetBed model).
• Add fields for tracking modifications made to the CameraPreset records (created_by and modified_by along with created and updated at datetime fields)
• Necessary changes in FE to reflect these.

Any update on this feature ?

@NNSiri We have discussed the issue and I am currently in the process of implementing those changes.

@aeswibon unassigning you from this issue due to inactivity ,