Configure OpenEMR for ICD-10 is a hot off the press compilation of things to know in preparation for the transition.
Very well done, Harley.
I would like to make 3 suggestions.
In the section about ICD-9 to ICD-10 crosswalk,
Make a list of the desired ICD-9 codes and go to one of the websites where you can look up their ICD-10 equivalents; a few links are provided in References and Resources below.
it may be easier for the reader to have the link to the little converter or any other converter in the above sentence rather in the last section because most users are not acquainted with running a SQL query. A query is a bit more laborious if the user only needs a cheat sheet.
This is a more direct link to the AAPC converter. Had to hunt around for a few seconds to get to it with the other link.
A number of users submit multiple diagnoses, therefore the reader should be alerted to the fact that they must add qualifiers as noted in this post.
Suggestion # 4
Occasionally when e-claims fail & paper need to be submitted, the gen_hcfa_1500_02_12.inc.php must be tweaked to have enough space for 8 characters. See attachment.
There is a code submission for gen_1500_02_12.inc.php in the queue …
not sure if it’s been pulled in yet.
Tony McCormick, CTO
Support: 866-735-0897, Direct: 713-574-6709
My Calendar: http://bit.ly/XznvDo
“It makes me feel young again to be wrong so often now.” - paraphrased from
Greg Bear
Suggestion # 4
Occasionally when e-claims fail & paper need to be submitted, the
gen_1500_02_12.inc.php must be tweaked to have enough space for 8
characters. See attachment.
–
Please be aware that e-mail communication can be intercepted in
transmission or misdirected. Please consider communicating any sensitive
information by telephone. The information contained in this message may be
privileged and confidential. If you are NOT the intended recipient, please
notify the sender immediately with a copy to hipaa-security@mrsb-ltd.com and
destroy this message.
Regarding the gen_hcfa_1500_02_12.inc.php length issue, the author closed the github item, so unclear whether should be reviewed (I requested a clarification). This fix looks like it’s ICD10 specific and should also get into the next patch before ICD10 becomes official (by 10/1/15). Also, will this fix break ICD9 or will it also work with ICD9?
As far as User Docs go, seems safest to just remind everybody to patch after the end of August. Especially if one more ICD-10 oriented patch is coming for the many 4.1.2 users?