1. I can’t open the v2022 classifications. What should I do?
Uninstall the product and carefully follow the instructions to reinstall it.
2. Where can I get help?
Send an email to help@cihi.ca.
3. Do I need to download the licences separately like I did for previous versions?
No, the licences are embedded within the classifications.
4. What should I do if I need additional licences?
Send an email to help@cihi.ca.
5. Why do I have to open the Folio classification in a shadow file (.SDW) and not an infobase (.NFO)?
These shadow files have functionality embedded in them that allows you to readily merge your v2018 shadow files with the v2022 classifications.
If you don’t have a v2018 shadow file, the v2022.SDW file will allow you to add notes, highlights and bookmarks directly into it without having to create a new shadow file.
6. What should I do if the Upgrade Shadow option in the Tools menu is greyed out?
In the classification, when you click the Tools button, the Upgrade Shadow option in the drop‐down menu should be active (i.e., not greyed out). If it is greyed out, you will need to modify the shadow file’s permissions to allow read/write permission. To check whether the installation is read/write:
- Go to your C:\ drive (or the drive where you installed the v2022 classifications).
- Right‐click on the CIHI folder (or the folder where you installed the v2022 classifications).
- Click Properties.
- Go to the Security tab and make sure you have Modify permissions. If you do not, check the Modify box and click Apply.
7. What rights do I need on the files to be able to upgrade the shadow file?
You need to have read/write permission in the v2022 shadow file (.SDW).
8. What do I do when the shadow file (.SDW) or the classification (.NFO) is a read‐only file?
Make sure that the file is read/write:
- Go to your C:\ drive (or the drive where you installed the v2022 classifications).
- Right‐click on the CIHI folder (or the folder where you installed the v2022 classifications) and click Properties.
- Go to the Security tab and make sure you have Modify permissions. If you do not, check the Modify box and click Apply.
9. Who should use the Upgrade Shadow functionality?
You should use the Upgrade Shadow functionality only if you have a v2018 shadow file and want to integrate it with the v2022 classification.
10. What if I don’t have a v2018 shadow file?
If you don’t have a v2018 shadow file, you won’t need to carry out the Upgrade Shadow process.
11. If I don’t have a v2018 shadow file, how do I create a new shadow file?
You don’t need to create a new shadow file if you don’t have a v2018 shadow file. The v2022.SDW file is a shadow file. You can add notes, highlights and bookmarks directly to the v2022.SDW file.
12. How do I know I am in a shadow file?
The title bar at the top of the screen of the classification will have the word “Shadow” in brackets.
13. How do I know whether my v2018 shadow file was successfully merged with v2022 ICD‐10‐CA/CCI?
A log file will pop up as soon as the upgrade process has been completed. Look for one of the notes that you had in your v2018 shadow file:
- Open the Advanced Query binoculars.
- Enter an open square bracket ([), type “note” and click the double arrows at the bottom of the screen to advance through the notes to confirm they were imported from your v2018 shadow file.
14. What happens if I merge the wrong classifications (e.g., CCI to ICD‐10‐CA)? How do I fix it?
The log file will display a message such as “NOTE NOT IMPORTED: couldn’t find destination note location for note(s), heading: ‘1.AC.59.^^.’” Delete any log files that you may have saved and redo the Upgrade Shadow process for each classification. Ensure that the v2018 shadow file classification is the same as the v2022 classification.
15. I forgot to keep a copy of the log file. How can I get a list of all the notes that did not come across into my v2022.SDW file?
You can redo the Upgrade Shadow process and save the log file to a desired location. For each v2018 entry that did not come across to v2022, the log file will display a message such as “Import Summary‐NOTES: Total # Notes: 6, # Notes Imported: 3 (50.0%).” You can also compare the v2018.SDW file notes with notes that you have in the v2022.SDW file. Review each unsuccessful entry in the log file; then, in the v2018 shadow file, locate each entry that did not import successfully into the v2022 shadow file using the Folio search functionality. Search on the text included with the log entry.
16. How can I get a list of the notes that I have created in my shadow files?
To export your personal notes into an html document:
- Close any versions of Folio that may be open.
- From the Start menu, open the v2022 ICD-10-CA – Shadow – English or v2022 CCI – Shadow – English.
- Click the Export Notes icon . If the Export Notes icon does not appear in the toolbar, go to Tools, Customize, and select Export Notes. Drag the icon to the toolbar.
- Create a unique name for this file when the dialogue box appears, then select where you want to save your personal notes log file (e.g., your desktop).
- Click Save. You can also find the instructions on our website: v2022 Shadow File Upgrade Export Notes
17. Can I delete notes from the shadow file?
To delete a note, go to the Tools menu and click Remove Note.
18. Who do I contact if I have problems with the shadow file?
Send an email to help@cihi.ca.
19. Where do I find a list of the new and deactivated codes?
In any version, new and deactivated codes are found in the appendices of both ICD‐10‐CA (Appendix A and Appendix B) and CCI (Appendix E and Appendix F).
20. Are CDs still available?
CDs were not produced for v2022.
21. Does Folio have Log4j vulnerability?
Folio does not use any Java libraries. Folio is a native C++ Windows application, so there is no Log4j vulnerability risk for the Folio product suite.
22. I’m getting the error message “Unable to open Infobase. The licence user limit has been exceeded.” What can I do?
Close the application and then right-click the Windows Start icon and select Task Manager. Then click More Details and look for Folio Views (32bit). Select it and click End Task, then try to launch Folio again.