I may be wrong but that line does not look like it changes at all. I looked up str_pad and all it does is add padding to the 000000001 that never changes.
public static function ediSenquence()
{
//Query the edi_sequence number and return that value
$sql = "select id from edi_sequence";
return QueryUtils::fetchRecords($sql);
}
$control = self::eidSequence();
$ISA[13] = str_pad($control['id'], 9, " "); // INTERCHANGE CONTROL NUMBER
Question, does the sequence number have to be nine digits?
I believe it’s the GS segment that has the control number that should be tracked. Say your submission fails and you have to find out what batch it was with the returned transaction set, like a 999.
Okay but believe that’s in the response. I thought the problem is that they use the ISA13 control id within the batch request to delimit a new request so must be unique within the session. Simply increment in the generator.
Anyway, I can’t read Sherwin screenshot of spec. If I could I’d have a better understanding of issue plus, while fixing this we should add to the eligibility tab in demographics to allow a single request to update patients eligibility status or user can view the status.
They suggested that there be one entry for claims and one entry in the x12 partners’ settings for eligibility. We should not be using the one entry for both types of requests.
Okay looks like you guys have the solution. Still don’t understand why the need for a new table to create ids to track throughput of workflow. Should be part of the response and openemr parsed record.
Okay sure maybe as I haven’t looked at that possibility however, IMO, we should do it then and not have the table hanging around until then.
For this issue, I’d assume you can create the ISA13 in generator as an incremented PHP var based on the request session iteration.
If I remember right, it’s done in code but doesn’t populate the ISA13.
@juggernautsei You’ll have to develop/modify the current workflow for Availity in batch to send a single request with all the 270 patient segments.
Are you currently trying to enable OA with an Availity x-12 partner to send an electronic batch request or downloading the batch file and sending the batch to FTP or such?
At any rate, you’ll need to set up the workflow. I can explain in a call if you need.