-
Notifications
You must be signed in to change notification settings - Fork 2
Troubleshooting Guide
Andre Mfune edited this page Feb 28, 2022
·
7 revisions
Use this guide to identify and resolve common issues in HIS-Core New Architecture.
| Issue | Possible causes | Solution |
|---|---|---|
| White screen on initial page load | - Outdated browser - Corrupted system files |
- Update and use the latest firefox version the device supports - Re-clone the application to restore corrupted files |
| Unable to connect to API | - Config.json file is missing - API not running - Misconfigured API settings in config.json |
- Rename config.json.example to config.json/ re-clone the repository - Ensure that the API is running using the configured port and host - Ensure API configuration used matches target API environment |
| Blank encounter page with Cancel button | - Api Error most likely using outdated tags - Programming error on the frontend |
- Update API tags or HIS-Core tags to their latest versions |
| Saving but unable to go to next task after saving an Encounter | When a Save notification appears and you cant proceed, just cancel to the patient dashboard and click on the next task | |
| Unable to search existing patients in the system | - DDE is enabled as system preference but it's not running - DDE is enabled but selected Application is not registered for DDE - NPID does not exist/ is voided - Using an outdated Tag that does not support DDE in API |
- Ensure that DDE API is running without errors - DDE requires apps such as ART, OPD or LOS to be registered with it. Contact your DDE administrator on your facility to register Apps to use DDE - Update API and His-Core to the latest tags that support DDE feature |
| Unable to print label | - Firefox is not setup to print via print.rb script - Malfunctioning label printer/ out of stickers to print - Record to print is corrupted or invalid |
- Configure Firefox to handle label files when downloading - Ensure the label printer has stickers |
| Unknown Errors | - Likely a programming error or oversight - Corrupted record / missing identifiers |
|
| System version not appearing | - HEAD file is missing in the system directory or HEAD file is empty | Create a HEAD file in the directory and write and save version string |
| Applications not appearing | - Application is not configured in config.json - application is configured to false |
Check if application is configured in config.json is "available" is set to true |
| New updates/fixes not taking effect on the system | - Web browser might be caching the old version of the system | - Clear your browser's cache or disable caching all together - Refresh your browser window for changes to take effect |
| System updated but version number hasnt changed | - Logout and login into the system and refresh your browser window | |
When reporting issues, Please indicate:
- system version number as appearing on the system
- detailed description including actions that the user took to create the issue
- Expected outcome and action from the system
Sometimes when errors occur in the system, they may appear vague or not show up at all. In such scenario, you can use your browser's debugging tools for more details. You can check the console tab or network for errors or warnings