Health
PlatformDomainAcademyDesign SystemFeedback
v1.7
v1.7
  • πŸ‘‹Introducing Health
    • Release Notes
      • HCM v1.7 Release Notes
        • Release Checklist
        • Eligibility Checklist
        • Service Build Updates
      • HCM v1.6 Release Notes
        • Service Build Updates
        • Release Checklist
        • Migration from v1.5 to v1.6
      • HCM v1.5 Release Notes
        • Migration from v1.4 to v1.5
        • Service Build Updates
        • Release Checklist
      • HCM v1.4 Release Notes
        • Migration from v1.3 to v1.4
        • Service Build Updates
        • Release Checklist
      • v1.3 Release Notes
      • v1.3 Tech Release Summary
        • Master Data Management Service (MDMS) & Configuration Updates
        • Test Cases
        • Service Build Updates
      • v1.2 Release Notes
      • v1.0 Release Notes
  • Product Roadmap
  • πŸ’™HEALTH CAMPAIGN MANAGEMENT
    • Understanding Health Campaign Management (HCM)
    • Value Proposition
  • 🎯HCM PRODUCT SUITE
    • Functional Specifications
      • Campaign Type Setup
      • Campaign Setup
      • Inventory
      • Boundary Hierarchy
      • Beneficiary
      • Boundary Data Specs
      • Draft System User Setup
      • Role Action Mapping
    • Building Blocks & Services
    • Health Products
      • HCM App
        • User Manual
          • Single Round Campaigns
            • Registration & Delivery
              • Registration & Delivery: IRS
          • Multi-Round Campaigns
            • Registration & Delivery
            • Download Beneficiary Data
          • Common Functions
            • User Management
            • 2D Voucher Scanning
            • Proximity-Based Search
            • Voucher-Based Registration and Distribution
            • Tracking Beneficiary Referrals
            • Tracking Side-Effects for Beneficiaries
            • Tracking Adverse Events
            • Health Facility Referral
            • Raising Complaints
            • Resolving Complaints
            • Inventory Management
              • User Manual
                • Stock Management
                • Stock Reconciliation
                • View Reports
                • Bale Scanning
            • Attendance Management
            • Payments
              • Guide to HCM Payments
            • Community Living Facilities
              • Product Requirement Document
          • Support Functions
            • Language Selection
            • Login
            • Forgot Password
            • Project Selection
            • Hamburger Menu
            • Help
            • Sync
            • Checklist
      • Campaign Management Dashboard
        • User Manual
        • Configurations
          • MDMS Configurations and s3 assets
          • IRS Dashboard Chart Configurations
        • Kibana Dashboard Integration With DSS Module
          • Auth Proxy Setup and Configuration for Kibana
        • SMC Dashboard
      • Microplanning
      • HCM Console
      • Health Payments
        • MDMS Configurations
        • Attendance Update and Approval Process
          • Project Selection
          • Register Inbox
          • View Attendance:Edit And Approve
        • Bill Generation Process
          • Project And Bill Aggregation
          • Bill Generation
          • My Bills
  • πŸš€REFERENCE IMPLEMENTATIONs
    • Mozambique
      • LLIN Overview
      • Customisation
      • Rollout
  • 🧰TECHNOLOGY
    • Architecture
      • High Level Design
        • Health Campaign System High Level Design
        • Design Decision Log
      • Low Level Design
        • Registries
          • Individual
          • Household
          • Product
          • Facility
          • Attendance
          • Expense
        • Services
          • Project
          • Stock
          • Referral
          • Muster Roll
          • Expense Calculator
      • Field App Architecture
        • UI Packages
          • Closed HouseHold package
          • Registration & Delivery Package
            • Eligibility Checklist
            • Communal Living Facilities
          • Referral Reconciliation Package
          • Inventory Management Package
          • Attendance Management Package
          • DIGIT Scanner Package
          • Digit Showcase Package
          • Digit Data Model Package
          • DIGIT DSS Package
          • Complaints Package
          • Survey Form Package
          • Sync Service Package
    • Standards
    • Security
    • Interoperability
  • πŸͺSETUP
    • Planning an HCM Implementation
    • Establish Project & Team
    • Gathering Requirements
    • Installation
      • Install Using GitHub Actions in AWS
      • System Data Setup
      • Project Data Setup
      • Setup Mobile App
      • Setup Kibana Dashboard
        • Create or Edit Existing Dashboards
      • Server Cleanup
    • Configuration
      • Configuring HCM to Campaign and Country Needs
      • Service Configuration
        • Individual Registry
        • Household Registry
        • Product Registry
        • Facility Registry
        • Stock & Inventory
        • Project Services
        • Referral Management
        • Attendance
        • Complaints
          • QA Sign-Off
            • Test Cases
        • User Management
          • QA Sign-Off
        • Muster Roll
        • Expense Service
        • Expense calculator
      • UI Configuration
        • Stock Management
        • Language Selection
        • Login
        • Forgot Password
        • Project Selection
        • Dashboard Configuration
          • Dashboard UI Enhancements
          • HCM Dashboard Master Promotion Guide
        • Attendance Management
          • Attendance Package Extraction and Interaction with HCM Application
    • Quality Assurance Testing
      • Regression Test cases
        • HCM Product
        • HCM Console
        • Microplanning
      • Eligibility and CLF Test cases
      • Console v0.3.1
      • Micro planning v0.2
      • HCM Payments v0.1
  • πŸ”΅COMMUNITY
    • Source Code
    • Committee
      • Digital Product Advisory Committee Charter
      • Idea Management Process
      • Sessions
        • November 2023 Session
        • August 2024 Session
          • Minutes of the Meeting
        • December 2024 Session
    • HCM Declarative Statements & FAQs
Powered by GitBook

https://creativecommons.org/licenses/by/4.0/

On this page
  • Overview
  • Steps for configuring HCM to campaign and country needs

Was this helpful?

Export as PDF
  1. SETUP
  2. Configuration

Configuring HCM to Campaign and Country Needs

PreviousConfigurationNextService Configuration

Was this helpful?

Overview

This document will cover the steps to configure HCM for a campaign. Every new campaign in a country or province will ideally require a few configurations to be done on the basic HCM application to cater to the exact needs of the campaign.

Steps for configuring HCM to campaign and country needs

First, the application must be installed using the procedure mentioned . For easy installation, you may refer to video. Once the application is installed, you will have access to the admin console and workbench using which a campaign can be configured to the needs of the country and campaign.

  1. Loading of new boundary hierarchy/boundary

a. Each country will have its boundary hierarchy, which must be configured using the console/workbench feature. Refer to the for doing this. The login URL will be the <domain configured during the installation>/workbench-ui/employee/user/language-selection

b. After the hierarchy has been configured, the boundary master data will be uploaded.

  1. Setting up a campaign and related master data using the HCM Console

a. Refer to document for using the console for campaign setup

b. Set up users for various roles

c. Set up all other masters for HCM

  1. Setting up the configuration parameters for the HCM app

a. Using the workbench link, configure the parameters per the .

  1. Changing the labels and messages as per the campaign needs

a. Login to the workbench URL, select the localisation option and appropriately change the values for the keys. Refer to document for instructions.

b. These localisation changes will apply to both the web and the mobile application.

  1. Making the APK as per the new configuration

a. Once the master data and language configuration, including loading of values are done, you are ready to make an APK.

  1. Installing the APK on a device and making it ready for use

a. Once the APK is made, it can be downloaded and installed on the device.

b. Enable the permissions to run background services.

c. Enable the permission to access the camera.

d. Enable location permissions.

e. Check for the other recommended prerequisites mentioned below

i. ​​RAM: Recommended is 6GB and minimum is 4GB.

ii. Processor: Octa-core processors.

iii. Battery: Minimum 5000 mAh. The higher the mAh, the better it is. Battery consumption is heavily dependent upon phone searching, network searching, and GPS usage.

iv. Screen: Generally the bigger the better for the field teams, but a minimum 6.5-inch screen size is recommended.

v. Storage: Minimum 32 GB. Typically 4 GB or 6GB RAM phones are available with more than 32 GB storage.

  1. Login to the new application on the device

b. Login using the user credentials created using the console.

  1. Login to the web application

log in a. Using the domain URL configured while installing, you should be able to log in to the web application.

b. Select the language of your choice.

c. You can use the user credentials configured using the console.

d. Once logged in you can see the menu options are per the roles assigned to this user.

  1. Configuring Dashboard

b. Follow the Kibana help documents for adding new charts and graphs.

c. You should be able to log in to the web application using the dashboard role the user created as part of Step 1.

b. Follow the steps mentioned to make the APK which can then be installed on your Android device.

a. Click on the icon with the name HCM to open the application.

a. Kibana will be installed as part of the installation. Visualisations relevant to the campaign can be added to the dashboard by following the steps mentioned .

πŸͺ
here
this
documentation
this
instructions
this
here
here