# Unexpected behavior

**URL:** <https://community.open-emr.org/t/unexpected-behavior/6335>\
**Category:** OpenEMR Development\
**Created:** [July 15, 2011, 5:34am UTC](https://community.open-emr.org/t/unexpected-behavior/6335 "2011-07-15T05:34:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [July 15, 2011, 5:34am UTC](https://community.open-emr.org/t/unexpected-behavior/6335/1 "2011-07-15T05:34:41Z")

</div>

**[aethelwulffe](https://sourceforge.net/u/aethelwulffe/)** wrote on [Friday, July 15, 2011](https://sourceforge.net/p/openemr/discussion/202506/thread/8582fe63/#daae):

A sleep clinic (version 4.1dev…not sure what date right now) with a pretty standard set-up, normal table fields (pid auto-increment, no mask, etc…) had an issue and called me for some advice.&nbsp; When they created a new patient, some other patient’s insurance info was already filled out in the record!&nbsp; Came to find that there was a PID value in the insurance data of “000”.&nbsp; We got rid of that and everything was fine.&nbsp; Possibly that happened when someone entered 000 as a new patient ID, and perhaps deleted the patient, and the insurance data did not get deleted as well due to the number being a slab of zeros.&nbsp; After that, the 000 table apparently matched the undefined PID for a new unsaved patient etc…  
&nbsp; I don’t have a db that I am ready to trash to try this out (very wrapped up in my project) but is it possible that a bit of a check needs to be made in the new patient entry form to avoid allowing a PID of that sort of value to be entered?
