phongtrang wrote on Friday, August 21, 2015:
Hello,
I had switch to ICD10 and doing a test billing X12 transfer to clearing house. We use ICD10 code when doing the billing. The test came back fail due to the following reason:
ICD9 qualifier is BK
ICD10 qualifier is ABK
But I look into the X12 ascii file and the ICD10 code is in the file but the qualifier remain at BK
Do you know if I’m missing some settings somewhere that I can change in openemr to make it work
Thanks.
teryhill wrote on Friday, August 21, 2015:
I commited tose changes a few months back if you are able to edit the files and make changes this is what is needed
MAKE A BACKUP OF THE FILE BEFORE YOU BEGIN
/library/gen_x12_837.inc.php
About line 668 add this
$da = $claim->diagArray();
if ($claim->diagtype == “ICD9”) {
$diag_type_code = ‘BK’;
}
ELSE
{
$diag_type_code = ‘ABK’;
}
and at about line 684 add this
if ($claim->diagtype == “ICD9”) {
$diag_type_code = ‘BF’;
}
ELSE
{
$diag_type_code = ‘ABF’;
}
++$tmp;
bradymiller wrote on Friday, August 21, 2015:
Hi,
To help clarify, here is Terry’s commit to fix this:
Terry, are there any other fixes needed for ICD10 that are not yet in the codebase? Considering there have been 3 requests for this in 2 days (2 on the forum and I just received an email from another), I am thinking of releasing a 4.2.0 patch for ICD10 related fixes.
-brady
OpenEMR
teryhill wrote on Friday, August 21, 2015:
That was the only change that I needed to pass the test with the clearing house. Unless there is something I am missing it should pass ICD10 with the above change. I do have a commit for expanding the ref number on paper resubmission and some changes to the misc billing form.
Terry
phongtrang wrote on Friday, August 21, 2015:
Thank you for your help. I’m testing right now.
Another question:
I tried to download the latest ICD10 code and place it into contrib/icd10 but I have unsupported message from openemr. How do I update the code?
Thanks.
fsgl wrote on Friday, August 21, 2015:
Try downloading these files. See attachment 1.
Assume you’ve seen instructions as depicted in 2 & 3.
If “unsupported” error message persists, External Data Load may need tweaking; therefore nothing for a user to do, unless he wishes to volunteer to fix codebase.
Highly likely that 2015 data set is sufficient for reimbursement. Commonly used diagnoses are not likely to change from year to year.
phongtrang wrote on Friday, August 21, 2015:
Dear fsgl,
Thanks. It looks like openemr is not supporting those 2016 files I downloaded from the same website. As you said, it is not important since the original descriptions and code still applied today, so I will just keep the original files from the release.
Thanks for your help.
fsgl wrote on Friday, August 21, 2015:
You’re welcome.
To keep the billing clerk from being driven insane during the transition, you may wish to use this little converter & give her a cheat sheet of your 20 most commonly used diagnosis codes (your personalized GEM).
Not likely that you will need the code for Schistosomiasis.
phongtrang wrote on Friday, August 21, 2015:
Brady/Terry –
Just to update: The x12 upload to clearing house pass the ICD10 test.
Thanks again for prompt help
PhongT
phongtrang wrote on Friday, August 21, 2015:
fsgl,
That website is extremely useful. Thank you.
PhongT
fsgl wrote on Saturday, August 22, 2015:
It was my pleasure.
We got the transition done in 20 minutes, despite being confronted with laterality (right eye, left eye, both eyes).
Also used “indeterminate stage” to avoid the severity hassle.
I understand the need to indicate laterality when billing for surgery, but they don’t pay us more for treating both eyes with severe glaucoma in a medical setting.
harleytuck wrote on Thursday, August 27, 2015:
Hi Brady-
Any chance there’ll be a patch coming with Terry’s commit for those still using 4.1.2?
fsgl wrote on Thursday, August 27, 2015:
See his post.
tmccormi wrote on Thursday, August 27, 2015:
Patches for 4.1 are unlikely except perhaps security. 4.2 is the official release that a patch would apply too.
fsgl wrote on Friday, August 28, 2015:
Besides getting the patch for Terry’s fix & a more direct way of installing 2015 version of ICD-10 via External Data Loads, more reasons for upgrading.
CMS Portal, E-sign, Templates & End of Day Report are very helpful to a practice.
bradymiller wrote on Monday, August 31, 2015:
To confirm, no resources to support 4.1 with patches. Only supporting 4.2 with patches at this time.
-brady
OpenEMR
fsgl wrote on Monday, August 31, 2015:
Now it’s official & tomorrow is September, the time to upgrade is the present.
Upgrading is not difficult, but users have reported hiccups. Don’t want upgrade glitches to complicate the transition.
Our local Blue Shield has insisted upon Sept. 24th as the start date for ICD-10.
cverk wrote on Saturday, September 19, 2015:
I thought I would chime in that I ran an ICD-10 - X12 test file just now using Windows 10 and firefox to OfficeAlly with the new patches installed and it went through just fine.