Notifications
Clear all
Topic starter
We have an issue where 2 patient records were merged together. We've had this happen before but don't have a good solution for it.
Obviously, preventing it is the best solution (using application Security, procedures, etc).
Here is the process we are thinking of:
- Identify which patient of the 2 we'd rather not have to recreate data for, then designate the single remaining chart as that patient (Patient A).
- Update the registration as necessary for Patient A, including Guarantor. (making note of any reg data that will be needed for the other patient – Patient B).
- Create new patient record for Patient B
- Identify all PM data that does not belong in Patient A's record.
- Recreate the PM data in new record for Patient B and inactivate or remove that PM data for Patient A.
- Identify all EMR data that does not belong in Patient A's record.
- Recreate the EMR data in new record for Patient B and inactivate or remove that EMR data for Patient A.
Unfortunately we can't think of any good way to move observations.
Has anyone developed scripts or an automated tool to unmerge patient records? Or even have documentation of what would need changed in the database (we have some in-house SQL experience).
Does anyone have a recommended method of dealing with these?
Any other thoughts or recommendations?
Thanks, Matthew | IS Analyst
Posted : January 23, 2014 11:32 pm
CPS or Oracle?
Posted : January 26, 2014 10:05 pm
Topic starter
CPS
Posted : January 26, 2014 10:11 pm
