The underlying issue you are likely seeing is due to how the Sidexis4 database checks for and handles duplicate record scenarios if the issue does NOT occur when you take images on a new patient who has never been in the office before.
This issue exhibits itself when you try and take an image on a patient in XVCapture but there is already an existing patient record in the Sidexis4 database that was preexisting or created apart from using XVCapture.
** The Sidiin_out.ini error occurs when there is an existing non XVCapture created patient in the Sidexis4 database that has the same first name, last name, and/or DOB, but that existing patient record has a different GUID (Globally Unique Identifier) assigned in the Sidexis database, which is different than the GUID being used/created by the Apteryx integration when you try and capture through XVCapture. Every patient created in the Sidexis database is assigned a unique ID# (GUID) that you never really see, but this is a unique identifier used by the Sidexis database for record keeping purposes.
Sidexis and Sidiin (Sidiin is a Sirona service used by XVCapture to take images with Sirona devices) have a “patient check” process. If during that check Sidexis/Sidiin sees what it calls ambiguous patient information (i.e., same first name, last name, and/or DOB but a different GUID is being used) the patient creation process for XVCapture fails, and you get the SIDIIN_out.ini error because the Sidexis database isn’t allowing a duplicate patient record to be created.
** In the left pic below, I have included the error you see in XVCapture overlayed on top of the actual Sirona SidiinServer.log file showing the patient creation process failure occur (because Sidexis sees an existing record with a different GUID). This “patient check” occurs in the background outside of XVCapture, so you don’t see it occur, but this is how the Sidexis database checks for and keeps duplicate patients from being created and there is no way to bypass this check on our end. There is no way to bypass this check on our end.
** You see the error occur in XVCapture, but the underlying issue is Sidexis not allowing what they see as a duplicate patient record to be created in their SQL Database because a patient with the same first name/last name and/or DOB already exists but with a varying GUID than what XVCapture is using for its capture process.
You should not see this error with any patients that are new and/or do not have an existing patient record in the S4 database.
We have reached out and provided this information to Sirona to see if there is any way to get around these issues, but as of now, there is not a solution outside of using a workaround.
** Option1: Manually open Sidexis4 and take an image then export/import that image into the patient record in Fuse/Apteryx.
** Option2: Open Sidexis4, find and edit the existing patient record in Sidexis4 (if that record can be edited which should be possible in most cases).
*** We have found adding a 1 to the end of the existing record’s first name field will allow a new patient to be created by XVCapture and 2D acquisition can occur, but this would be a manual edit/change that has to be made in Sidexis4 prior to trying to take an image in XVCapture, which we understand is not ideal by any means."
2D/3D Combo Units : Sidexis Holds onto the driver
Make certain offices are closing Sidexis if they capture CBCT / 3D in Sidexis. Before they attempt to capture 2D Pano in XV Capture. Or else Sidexis will hold onto the driver and produce this error as well.