Regarding the office ally eligibility check bad request when click on the update status button

OpenEMR Development
#1

Hi All,

For OpenEMR Office ally eligibility check I have I have fixed code of two place now my request get hit to the office ally server but I am getting the bad request from the office ally server below is 270 I am sending to office allay is there any issue with my 270 please let me know
ISA000000000 000000000000ZZ ZZ 2310161302*^005010000000010T*:~GSHS202310161302572X005010X279A1~ST270000000003005010X279A1~BHT002213PROVTest600202310161302~HL1**201~NM1PR2Test company name*****PIHCSVC~HL21211~NM11P2Workflow Clinic*****XX72347653~HL32220~NM1IL1TestLTestFTestMMI723648623486~REFEJ1~DMGD819940719F~DTP291D820231016~EQ30~SE13000000003~GE12~IEA1000000001~**

eligiblityCheck
eligiblityCheck1600×728 108 KB

#2

the ~** at the end is wrong. If it really is there, and not the message board doing a weird format.

#3

I just went through this same thing with WayStar. Have you checked with Office Ally to see if they have changed their request format? Bad data may not be in the file you are sending. For me, it ended up being the request header. After I had fixed the message to match exactly what their tech support sent to me. I had followed their guide but the guide was out of date. We know how that goes.

#4

@juggernautsei there existing functionality is not working I have writing new code for getting the eligibility response.

1 Like
#5

@Nilesh_Hake do you plan to share with the updated code? I have been studying the whole eligibility process. The implementation or the real time eligibility needs to be converted to an interface so that different providers can be implemented without having to rewrite/overwrite the existing code. I am still mapping out the calls to before embarking on the journey. Do you want to talk it over together?

#6

Yes I will share the code with community but I am still pending some part of code writing for the same.

1 Like
#7

Is the service still free? If not can you share how much it cost for the service?

#8

@juggernautsei My client had given me access I do not know if that service is free or not but I will check with my client and update you.
Below is response I got from office allay

–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“PayloadType”

X12_271_Request_005010X279A1
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“ProcessingMode”

RealTime
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“PayloadID”

e51bfb51-e69a-4c5a-ac95-b74a003d9eb4
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“TimeStamp”

2023-12-01T07:22:09Z
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“SenderID”

1006419
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“ReceiverID”

OFFALLY
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“CORERuleVersion”

2.2.0
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“Payload”

ISA000000000 000000000000ZZOFFALLY ZZ1006419 2312131838*^005012392987680T*>~GSHBOFFALLY1006419202312131838239298768X005010X279A1~ST271239298768005010X279A1
ALL SEGEMENT of 271
~SE219239298768~GE1239298768~IEA1*239298768~
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“ErrorCode”

Success
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“ErrorMessage”

None
–7ee164f1-c212-415f-b88b-45d2db030224–

#9

I recommend change from using our internal HTTP client over to Symfony client if you don’t understand how to use oeHttp client.
When this was developed Office Ally did not support batching requests via API so batching is emulated in code by sending as single request of each in batch. If OA does now support batching then this should be an easy change.

This was implement at least 3 years ago if not more.

#10

Hi @sjpadgett office allay now support the API I working on response handling part for the API that have the 271. What my plan is with above above response I will extract the 271 data and return from the requestEligibility. And then I will verify you written remaining cod. I think you had handled all response 271 correct ?

#11

@sjpadgett and @juggernautsei if you have time can we connect I want to finish this functionality today

#12

hi, I suggest to take advantage of the recent refactor also have had success using the guzzle client.

2 Likes
#13

Yes but let’s be clear; You say Office Ally now supports a batch request from a single API request?
I can not find my original forum thread from the development and testing conversation. I know there is a pretty extensive conversation with how to and logging feature.

1 Like
#14

@stephenwaite I did got successfully response from the guzzle client therefore I had move with API.

1 Like
#15

@sjpadgett
Below are the request they are accepting now I got successful response from the sample data

curl --location ‘https://wsd.officeally.com/TransactionSite/realtime-request/MIME’ \ --form ‘PayloadType=“X12_276_Request_005010X212”’ \ --form ‘PayloadId=“2457fe0c-568c-4769-9d76-b481804253ec”’ \ --form ‘ReceiverId=“OFFALLY”’ \ --form ‘Payload=" ISA00 **
**00 **
ZZ…IEA1000000001~"’ \ --form ‘SenderId=“SENDERID”’ \ --form ‘TimeStamp=“CCYY-MM-DDTHH:MM:SSZ”’ \ --form ‘UserName=“USERNAME”’ \ --form ‘ProcessingMode=“RealTime”’ \ --form ‘Password=“PASSWORD”’ \ --form ‘CoreRuleVersion=“2.2.0”’

#16

I’d leave alone if the oeHttp client is not throwing any errors as I wrote that client mainly for FHIR client and was working very well with easy options/oauth/restful.
Still if replacing we have another client for symfony available. oeHttp also has security and again if api request are working then leave be.

1 Like
#17

If you can send me test credentials I’ll test it…

#18

I have mixed feelings using Guzzle. Always something with it. I rather use cURL than it and I think I moved to cURL for fax module. Still if works then really doesn’t matter and I can remove the oeHttp client from core with just a couple refactors if a PR is put up with this change.

#19

@sjpadgett I cant share the test credential with you because credential is from the client but I have tested with test patient and credential when I hit above curl I am getting below response

–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“PayloadType”

X12_271_Request_005010X279A1
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“ProcessingMode”

RealTime
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“PayloadID”

e51bfb51-e69a-4c5a-ac95-b74a003d9eb4
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“TimeStamp”

2023-12-01T07:22:09Z
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“SenderID”

1006419
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“ReceiverID”

OFFALLY
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“CORERuleVersion”

2.2.0
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“Payload”

ISA000000000 000000000000ZZOFFALLY ZZ1006419 2312131838*^005012392987680T*>~GSHBOFFALLY1006419202312131838239298768X005010X279A1~ST271239298768005010X279A1
ALL SEGEMENT of 271
~SE219239298768~GE1239298768~IEA1*239298768~
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“ErrorCode”

Success
–7ee164f1-c212-415f-b88b-45d2db030224
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=“ErrorMessage”

None
–7ee164f1-c212-415f-b88b-45d2db030224–

IF YOU LOOK THE ST segment its 271 as response

#20

As long as response body hasn’t changed then feature should fly.
I still don’t understand why anything needs to be done unless the request form data has changed. With @stephenwaite refactor and I assume he tested, the current client should work that is if we aren’t getting any errors due to recent php version changes.

2 Likes