# Officeally integration **URL:** \ **Category:** Management and Administration\ **Created:** [March 17, 2020, 3:26am UTC](https://community.open-emr.org/t/officeally-integration/13970 "2020-03-17T03:26:00Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![visolveemr](https://community.open-emr.org/user_avatar/community.open-emr.org/visolveemr/32/10974_2.png) [@visolveemr](https://community.open-emr.org/u/visolveemr)\ **Post date:** [March 17, 2020, 3:26am UTC](https://community.open-emr.org/t/officeally-integration/13970/1 "2020-03-17T03:26:00Z")
We have been told by officeally one can not verify “Eligibility” verification online with officeally. However, claim verification can be done online. Does anyone have any experience integration “Eligibility” verification of OpenEMR with officeally? -Visolve-899 ---
**Author:** ![stephenwaite](https://community.open-emr.org/user_avatar/community.open-emr.org/stephenwaite/32/15754_2.png) [@stephenwaite](https://community.open-emr.org/u/stephenwaite)\ **Post date:** [March 17, 2020, 6:39pm UTC](https://community.open-emr.org/t/officeally-integration/13970/2 "2020-03-17T18:39:33Z")
hi @visolveemr , @sjpadgett [built realtime with oa last year](https://community.open-emr.org/t/eligibility-checks-clearinghouses/9742/101) ---
**Author:** ![visolveemr](https://community.open-emr.org/user_avatar/community.open-emr.org/visolveemr/32/10974_2.png) [@visolveemr](https://community.open-emr.org/u/visolveemr)\ **Post date:** [March 18, 2020, 3:37am UTC](https://community.open-emr.org/t/officeally-integration/13970/3 "2020-03-18T03:37:05Z")
@stephen Thank you. When you say real time - is this for claim verification or for “Eligibility” verification? ViSolve have integrated with OA on Claim verification but there is no simple online mechanism to validate “Eligibility” verification unless you go to OA web site! -[Visolve-899](http://www.visolve.com/hc) ---
**Author:** ![stephenwaite](https://community.open-emr.org/user_avatar/community.open-emr.org/stephenwaite/32/15754_2.png) [@stephenwaite](https://community.open-emr.org/u/stephenwaite)\ **Post date:** [March 18, 2020, 10:34am UTC](https://community.open-emr.org/t/officeally-integration/13970/4 "2020-03-18T10:34:43Z")
it’s eligibility verification ---
**Author:** ![visolveemr](https://community.open-emr.org/user_avatar/community.open-emr.org/visolveemr/32/10974_2.png) [@visolveemr](https://community.open-emr.org/u/visolveemr)\ **Post date:** [March 18, 2020, 1:48pm UTC](https://community.open-emr.org/t/officeally-integration/13970/5 "2020-03-18T13:48:15Z")
@stephen Thank you! This helps. But the OA support guy clearly told me that they don’t support 3rd party integration of online “Eligibility” verification. My gut told me he may not be correct! That is why we posted the question here. We will do some more analysis including getting views from sjpadgett. -Visolve-899 ---
**Author:** ![stephenwaite](https://community.open-emr.org/user_avatar/community.open-emr.org/stephenwaite/32/15754_2.png) [@stephenwaite](https://community.open-emr.org/u/stephenwaite)\ **Post date:** [March 18, 2020, 2:02pm UTC](https://community.open-emr.org/t/officeally-integration/13970/6 "2020-03-18T14:02:50Z")
hi @visolveemr, that is probably true because you’re entering the provider’s credentials on the X12 partner page please see: > [@Eligibility Checks & Clearinghouses](https://community.open-emr.org/t/eligibility-checks-clearinghouses/9742/133): > > hi @sjpadgett, does this look like an ok setup with the username/password for OA? ---
**Author:** ![Mark\_Sarnov](https://community.open-emr.org/user_avatar/community.open-emr.org/mark_sarnov/32/15607_2.png) [@Mark\_Sarnov](https://community.open-emr.org/u/Mark_Sarnov)\ **Post date:** [July 12, 2021, 3:49am UTC](https://community.open-emr.org/t/officeally-integration/13970/7 "2021-07-12T03:49:08Z")
There is another glitch as well. My username with OA was longer than the 10 characters that openemr allows in the database… Therefore it was being truncated and I was getting the error listed above with a truncated username. Therefore, OA would not provide me with the updated eligibility when I requested it with the “Update” button. The fix: used phpmyadmin to change the length of the ISA\_02 character string to 13 characters to accommodate my username, which is 13 characters. Once I did that and reentered my full username, the eligibility worked as it should. Not sure how this would be coded, except to expand the default character length SPECIFICALLY for OA as the X12 EDI 270 submission for eligibility is supposed to be maxed out at 10 characters. OA was suggesting I resubmit an application to get a shorter username… (??) Anywho… Hope this helps someone! Mark L. Sarnov, MD ---
**Author:** ![stephenwaite](https://community.open-emr.org/user_avatar/community.open-emr.org/stephenwaite/32/15754_2.png) [@stephenwaite](https://community.open-emr.org/u/stephenwaite)\ **Post date:** [July 12, 2021, 12:57pm UTC](https://community.open-emr.org/t/officeally-integration/13970/8 "2021-07-12T12:57:46Z")
hi @Mark_Sarnov, the ISA record has to be a fixed length record with `ISA02` set to length 10 so guessing that your change might impact your claims and other transactions. Probably best to get a shorter username 🙂 ---
**Author:** ![Mark\_Sarnov](https://community.open-emr.org/user_avatar/community.open-emr.org/mark_sarnov/32/15607_2.png) [@Mark\_Sarnov](https://community.open-emr.org/u/Mark_Sarnov)\ **Post date:** [July 12, 2021, 2:26pm UTC](https://community.open-emr.org/t/officeally-integration/13970/9 "2021-07-12T14:26:38Z")
Ya, I know… but I may kludge the php file to TRIM the extra characters for Change Healthcare to format the 835/837 as I use a separate X12 partner for submissions than OA for eligibility.