This reference guide provides a comprehensive list of application configuration options available in the HMIS system. These settings allow administrators to customize system behavior according to organizational needs.

Navigation: Administration → Manage Institutions → Application Options

Once in the Application Options interface:

1. Use the search function to find specific configuration keys
2. Browse through categories to find related settings
3. Click on any configuration key to modify its value
4. Save changes to apply them system-wide

These options control what information is visible during pharmacy transfer and issue operations:

Control how pharmacy transfer bills appear and print:

Important: Only ONE of these should be set to true at any time:

Control how transfer bill numbers are generated:

Customize what appears in pharmacy disbursement reports:

Customize bill appearance:

Impact of Enabling Shift-Based Operations:

• Users must start a cashier shift before billing
• Financial Transaction Manager becomes available in relevant menus
• Enhanced financial accountability and tracking
• End-of-shift reconciliation procedures become mandatory

• Current State Analysis: Document existing configuration before changes
• User Impact Review: Assess how changes will affect daily workflows
• Training Requirements: Plan user education for interface changes
• Performance Considerations: Evaluate potential system performance impacts

• Test Environment: Always test configuration changes in non-production environment first
• User Acceptance Testing: Get feedback from key users before full implementation
• Integration Testing: Verify configurations work correctly with existing workflows
• Performance Testing: Monitor system performance with new configurations

• Staged Rollout: Implement changes gradually, starting with less critical departments
• Communication Plan: Inform all affected users about upcoming changes
• Support Preparation: Ensure help desk staff understand new configurations
• Documentation Updates: Update user guides and training materials

• Performance Metrics: Monitor system performance after configuration changes
• User Feedback: Collect feedback on usability and workflow impacts
• Error Monitoring: Watch system logs for configuration-related issues
• Usage Analytics: Track adoption and usage patterns of new features

• Regular Reviews: Periodically assess if configurations still meet organizational needs
• Optimization Opportunities: Look for ways to improve system performance through configuration
• User Training Updates: Provide refresher training on configuration-dependent features
• Documentation Maintenance: Keep configuration documentation current

Objective: Reduce complexity for basic pharmacy operations

Recommended Settings:

Stock Transaction - Show Rate and Value = false
Pharmacy Transfer Issue - Show Rate and Value = false
Pharmacy Disbursement Reports - Display Purchase Rate = false
Pharmacy Disbursement Reports - Display Purchase Value = false
Pharmacy Disbursement Reports - Display Retail Sale Rate = false
Pharmacy Disbursement Reports - Display Retail Sale Value = false

Result: Simplified interface with minimal financial information

Objective: Implement comprehensive financial controls

Recommended Settings:

applicationPreference.opdBillingAftershiftStart = true
applicationPreference.pharmacyBillingAfterShiftStart = true
Recording Shift End Cash is Required Before Viewing Shift Reports = true
Shift Shortage Bills are enabled = true
Shift Excess Bills are enabled = true

Result: Mandatory shift procedures with full accountability

Objective: Streamline laboratory workflow

Recommended Settings:

The system uses the Laboratory Dashboard as its default interface = true
Lab Daily Summary Report - Optimized Method = true
Lab Daily Summary Report - Legacy Method = false

Result: Modern laboratory interface with improved performance

Problem: Configuration changes made but not visible to users
Solutions:

• Clear browser cache and refresh pages
• Restart application server if changes affect system-level behavior
• Verify configuration was actually saved in the system
• Check if user has appropriate permissions to see affected features

Problem: System becomes slower after configuration changes
Solutions:

• Review enabled display options and disable unnecessary ones
• Use optimized versions of features where available (e.g., DTO reports)
• Monitor database query performance for complex configurations
• Consider staged implementation of performance-heavy features

Problem: Unexpected behavior or system errors
Solutions:

• Ensure mutually exclusive options are properly configured (only one enabled)
• Review related settings that might interact with changed configurations
• Check configuration hierarchy (application vs institution vs department)
• Verify configuration key names are spelled correctly

• Administrative Privileges: Only users with appropriate administrative rights should modify application options
• Change Documentation: Maintain audit trail of who made configuration changes and when
• Testing Requirements: Always test configuration changes before implementing in production

• Data Visibility: Consider privacy implications of configuration changes that affect data display
• Workflow Changes: Assess how configuration changes might impact existing procedures
• Training Requirements: Plan user education for significant configuration modifications

1. System Administrator: Primary contact for configuration questions and issues
2. Department Heads: For understanding business requirements behind configuration needs
3. Power Users: Experienced users who can provide feedback on configuration impacts
4. Documentation: This guide and related configuration documentation

1. HMIS Technical Support: For complex configuration issues or system-level problems
2. User Community: Other HMIS users who may have similar configuration needs
3. Training Resources: Additional documentation and training materials

Related Resources:

• System Configuration Guide - General configuration concepts and procedures
• Pharmacy Issue Configuration - Detailed pharmacy-specific configuration guide
• User Privileges Guide - Understanding system permissions and access control

Important Reminders:

• Always test configuration changes in a non-production environment first
• Document the business justification for all configuration changes
• Consider the impact on user training and support when making changes
• Monitor system performance after implementing new configurations