We've expanded the flowsheet functionality so that when loading encounters for a flowsheet, one can specify a "byConcept" parameter and then the flowsheet will fetch all encounters that contain an obs with that concept, not just those of a certain encounter type.
However, this can lead to problems... for instance, if the flowsheet finds a ART_FOLLOWUP encounter with viral load information, generally we wouldn't want the end user to delete the form or edit the visit date from the viral load view...
A simple first pass to handle is would be to disable the edit link for all encounters where the encounter does not match the form encounter type.
Hopefully this can be handled by some tweaks to the the flowsheet controller, flowsheet.gsp and flowsheet.js: we should compare the encounter type associated with the HTML Form with the encounter type associated with the current encounter and hide/show the "#delete-button" for this row accordingly.
Mark Goodrich: I just added here a corresponding ticket for PIH IS-373 issue.