I'm not sure if this is just something that I noticing now or it's new but I am getting spouses overwritten :(
Here is the situation
I import a gift from John & Jane Doe
First Name: John
Last Name: Doe
Spouse First Name: Jane
Spouse Last Name: Doe
In RE I have a record with Jane Doe as the primary and John Doe as a non-constituent spouse
When I import the file IOM pops up a choice of matching to John Doe/Jane Doe (with little rings) or Jane Doe/John Doe so I pick the one with rings since it lines up correctly.
But now when I open up the record it now says John Doe & John Doe :(
Also, it doesn't give me the pop-up about changing the bio fields on the spouse record. Maybe I am missing something?
Posted By Sue Edward on 24 Mar 2015 11:34 AM
Do you still prefer an option when matching to a non-constituent spouse record that it only write bio/address info the the non-constituent spouse and write all other data to the full constituent?
In the organization I'm with, wives DO NOT get constituent records (unless there is no knowledge of the husband).
Any gifts, from the spouse, are attached to the main constituent's record.
I would be interested in having this, as an option.
We are in the process of adding patient data into our database, and there will be many that match to non-constituent spouses. I'm testing the file right now, and while the profile is identifying the non-constituent spouse, it is not promoting them, even though I have that option selected in the profile.
Am I correct in understanding that having certain criteria in the import file will trigger the promotion of the non-constituent spouse? Currently, we are only adding bio/address information and constituent attributes. It sounds like we do not have the data trigger in the file to make the promotion happen.
I'm thinking our only other options are to treat them as exceptions and do them manually in the future (not ideal), or to attempt to promote all of our living non-constituent spouses using the elevator before embarking on this import. Our initial import file will be over 100K records and then will be maintained weekly at about 100-200 records.
What version of IOM are you using? We found an issue where importing attributes to the non-constituent spouse was not promoting the record when it should. That was fixed in 126.96.36.199 so if you are on an older version, updating to the latest should fix this for you. Please let us know if that solves your issue.
I've been running into the same problem with our patient file, that we import into List Management. We are running 3.2 and in re-reading the documentation to see if I had a setting wrong that was preventing the non-constituent spouse from getting promoted to a full constituent, I came across this: "If you have the List Management module and are importing Wendy into a LM list, any non-bio/address information is written to Robert regardless of these settings. Wendy will still be added to the list."
This is exactly our problem and sounds like it is by design. I've had to manually promote those constituents, so the non-bio information was on their record.
Omatic is there any plans to provide the same functionality in List Management to promote the non-constituent to Full Constituent?
Foundation Application Systems Analyst
OSF Healthcare Foundation
I'm thinking yes, but maybe I'm missing something.
I'm importing weekly patient files using List Management and often times it's a non-constituent spouse that was the patient. When I go to add an Action that contains all the relevant information about that particular discharge, if I don't promote the non-constituent spouse to a full constituent, the action ends up on the full constituent spouse who wasn't a patient.
This affects who gets pulled into our biweekly meetings then. I don't necessarily need all of these non-constituent spouses promoted, but I do need the Action to reside on the non-constituent spouse.