System Configuration Guide - hmislk/hmis GitHub Wiki
The HMIS system provides extensive configuration options that allow administrators to customize system behavior according to organizational needs. This guide explains how to access and manage configuration settings effectively.
System-wide settings that affect all users and departments
Settings specific to your hospital or healthcare institution
Settings that apply only to specific departments
Personal preferences that individual users can customize
Navigation Path: Administration โ Manage Institutions โ [Configuration Type]
How to Access: Administration โ Manage Institutions โ Application Options
Purpose: System-wide settings affecting all users
Examples: Billing behavior, security settings, global display options
How to Access: Administration โ Manage Institutions โ Institution Options
Purpose: Settings specific to your healthcare facility
Examples: Institution-specific workflows, branding, policies
How to Access: Administration โ Manage Institutions โ Department Options
Purpose: Department-specific customizations
Examples: Department billing rules, workflow variations
How to Access: Administration โ Manage Institutions โ User Options
Purpose: User-level preferences and personalization
Examples: Interface preferences, default values, personal settings
Configuration Keys:
applicationPreference.opdBillingAftershiftStart
applicationPreference.pharmacyBillingAfterShiftStart
Impact:
- When enabled, users must start a cashier shift before processing bills
- Affects OPD billing, pharmacy billing, and channelling operations
- Enables Financial Transaction Manager features
How to Configure:
- Access Application Options
- Search for "shift" or "billing"
- Enable/disable shift requirements as needed
Configuration Keys:
OPD Bill Item Search By Autocomplete
- Various display preference settings
Impact:
- Changes how users search for items during billing
- Affects interface appearance and workflow speed
Configuration Keys:
The system uses the Laboratory Dashboard as its default interface
Lab Daily Summary Report - Legacy Method
Lab Daily Summary Report - Optimized Method
Impact:
- Changes laboratory user interface layout
- Affects report generation performance
- Determines available menu options
Configuration Keys:
Display Colours for Stock Autocomplete Items
Pharmacy Analytics - Show Department Stock By Batch
- Various pharmacy transfer settings
Impact:
- Visual aids for stock management
- Report display options
- Transfer workflow behavior
Configuration Keys:
Recording Shift End Cash is Required Before Viewing Shift Reports
Shift Shortage Bills are enabled
Shift Excess Bills are enabled
Impact:
- Enforces cash reconciliation procedures
- Controls financial accountability features
- Affects end-of-shift workflows
- Document Current Settings: Export or record existing configurations before changes
- Test Environment: Always test configuration changes in a non-production environment first
- User Impact Assessment: Consider how changes will affect daily workflows
- Training Requirements: Plan user training for significant interface changes
- Staged Rollout: Implement changes in phases, starting with less critical departments
- Communication: Inform affected users about upcoming changes
- Support Preparation: Ensure help desk staff understand new configurations
- Rollback Planning: Have a plan to revert changes if issues arise
- Performance Monitoring: Watch for performance impacts after configuration changes
- User Feedback: Regularly collect feedback on system usability
- Error Monitoring: Check system logs for configuration-related errors
- Regular Reviews: Periodically review configurations to ensure they still meet organizational needs
Objective: Require cashier shifts for financial accountability
Steps:
- Access Application Options
- Enable
applicationPreference.opdBillingAftershiftStart
- Enable
applicationPreference.pharmacyBillingAfterShiftStart
if applicable - Train users on shift start/end procedures
- Update Financial Transaction Manager access
Impact:
- Users must start shifts before billing
- Financial Transaction Manager becomes available in menus
- Enhanced financial tracking and accountability
Objective: Optimize laboratory workflow with dashboard interface
Steps:
- Access Application Options
- Enable
The system uses the Laboratory Dashboard as its default interface
- Train laboratory staff on new interface layout
- Update laboratory procedures and documentation
Impact:
- Laboratory Dashboard becomes primary interface
- Sample Management may be hidden from main menu
- Centralized laboratory operations management
Objective: Improve stock management with visual indicators
Steps:
- Access Application Options
- Enable
Display Colours for Stock Autocomplete Items
- Configure color coding rules for stock status
- Train pharmacy staff on color meanings
Impact:
- Color-coded stock items based on expiry dates
- Improved visual identification of stock status
- Reduced dispensing errors
Symptoms: Changes made but users don't see them
Solutions:
- Clear browser cache and refresh
- Restart application server if needed
- Verify configuration was saved correctly
- Check user permissions for affected features
Symptoms: System slowdown after enabling new features
Solutions:
- Review enabled display options (disable unnecessary ones)
- Check system resource usage
- Consider optimized versions of features where available
- Monitor database query performance
Symptoms: Users cannot access features after configuration changes
Solutions:
- Verify user has required privileges
- Check if shift requirements are enabled and met
- Review department-specific settings
- Confirm user is in correct user role
Symptoms: Unexpected system behavior or errors
Solutions:
- Review related configuration settings for conflicts
- Ensure only one option is enabled for mutually exclusive settings
- Check institution vs department vs application option priorities
- Verify configuration key spelling and values
- Limit Configuration Access: Only authorized administrators should modify system configurations
- User Role Management: Ensure proper role-based access to configuration features
- Audit Logging: Monitor who makes configuration changes and when
- Approval Process: Implement approval workflows for significant configuration changes
- Documentation: Maintain records of all configuration modifications
- Testing Requirements: Mandatory testing before production implementation
- Sensitive Settings: Pay special attention to configurations affecting data visibility
- Privacy Compliance: Ensure configurations align with healthcare privacy requirements
- Backup Procedures: Regular backups of configuration settings
- System Administrator: First point of contact for configuration questions
- Department Heads: For department-specific configuration needs
- User Training Materials: Updated documentation reflecting current configurations
- Help Desk: For user-level configuration support
- Configuration Documentation: Refer to this guide and related documentation
- System Logs: Check logs for configuration-related error messages
- Test Environment: Use test systems to experiment with configurations
- Vendor Support: Contact HMIS support for complex configuration issues
- Pharmacy Issue Configuration - Detailed pharmacy-specific settings
- Administration Navigation Guide - How to access administrative functions
- User Privileges Guide - Understanding system permissions
- Application Options Reference - Comprehensive configuration options list
Important Notes:
- Always test configuration changes in a non-production environment first
- Document all changes and their business justification
- Train users before implementing significant configuration changes
- Monitor system performance after making configuration modifications