HMIS Integration20 min read1 July 2025
Share:

Afyalink Integration Guide: HMIS to HIE Implementation

Complete implementation guide for Health Management Information System (HMIS) teams integrating with the Health Information Exchange (HIE). Covers Client Registry, Facility Registry, Health Worker Registry, and Claims systems.

Afya Stack Kenya

Healthcare Technology Experts

HMIS | HIE Integration Guide

HIE Implementation Guide for HMIS Integration

This implementation guide assists Health Management Information System (HMIS) integration teams in connecting with the Health Information Exchange (HIE). Following these guidelines ensures proper interfacing with the HIE's critical components: Client Registry, Facility Registry, Health Worker Registry, and Claims systems.

Priority Levels

IconLevelDescription
๐Ÿ”ดCriticalEssential functionality โ€” must be implemented
๐ŸŸ StandardExpected functionality โ€” should be implemented
๐ŸŸขAdvancedEnhanced functionality โ€” optional features

๐Ÿ”ง Core Requirements

Use Official APIs

Priority: ๐Ÿ”ด Critical

RequirementDetails
API SourceUse only APIs provided through the official portal
No Third-PartyAvoid unofficial interfaces or middleware
Data ExchangeAll communication through official channels only

Best Practices:

  • Maintain up-to-date API documentation
  • Implement proper authentication and security
  • Monitor API usage and performance

Direct HMIS Integration

Priority: ๐Ÿ”ด Critical

RequirementDetails
ImplementationDirect integration within HMIS itself
No MiddlewareNo external components or third-party systems
Native FunctionalityAll features built into the HMIS

๐Ÿ‘ค Client Registry Integration

1. Patient Registration

Priority: ๐ŸŸ  Standard

FeatureImplementation Details
Registration FormImplement patient registration functionality
ID SearchSearch by ID number capability
PIN ManagementSet default PIN, enable PIN changes
User AwarenessInform patients about PIN for Afyayangu login

2. Patient Search

Priority: ๐Ÿ”ด Critical

Search Parameters:

ParameterRequiredDescription
ID NumberYesNational identification number
Full NameYesComplete patient name
Date of BirthYesPatient's date of birth
Phone NumberNoContact phone number
Other IdentifiersNoAs per API documentation

Implementation:

  • Enable comprehensive search functionality
  • Display accurate results
  • Implement error handling for failed searches

3. Patient Data Decryption

Priority: ๐Ÿ”ด Critical

ComponentRequirement
Decryption KeysUse Afyalink-provided keys
Data SecurityEncrypt all sensitive information
Key ManagementSecure storage with access controls
Audit LoggingLog all decryption activities

4. Patient Data Mapping & Storage

Priority: ๐ŸŸ  Standard

Mandatory Fields:

FieldTypeDescription
CR IDStringClient Registry identifier
ID NumberStringNational ID
Full NamesStringComplete patient name
Date of BirthDatePatient DOB
GenderEnumPatient gender
Phone NumberStringContact number

Implementation:

  • Store patient details locally after successful search
  • Eliminate repeated API calls through local storage
  • Map all required fields accurately

5. Update Patient

Priority: ๐ŸŸ  Standard

FeatureDetails
Update FunctionalityEnable information updates
EncryptionSend updates with encrypted PIN
ValidationValidate all update requests
Change TrackingTrack all patient modifications

6. Dependents Handling

Priority: ๐ŸŸ  Standard

Dependent TypeAction
SpouseStore and display as next of kin
ChildrenRegister as dependents
RelationshipsMap family connections clearly

7. Consent Workflow

Priority: ๐ŸŸข Advanced

  • Capture patient consent before processing requests
  • Store consent linked to patient records
  • Comply with privacy laws and regulations
  • Implement age-appropriate consent mechanisms

๐Ÿ” Eligibility Check

1. Search Patient Eligibility

Priority: ๐Ÿ”ด Critical

FeatureImplementation
Eligibility SearchImplement search functionality
Status DisplayClear visual indicators
Ineligibility HandlingShow reasons and solutions

2. SHA Patient Visit

Priority: ๐Ÿ”ด Critical

Process Flow:

  1. Verify eligibility
  2. Initialize SHA visit
  3. Capture required parameters
  4. Confirm visit creation

3. Display SHA Scheme Eligibility

Priority: ๐ŸŸ  Standard

SHA Schemes:

SchemeDisplay Requirements
SHIFStatus, coverage period, benefit limits
ECCIF & PCIFActive periods, waiting periods
POMFEligibility status, coverage details
ECDFActive coverage, benefit information

Visual Design:

  • Color-coded eligibility status
  • Easy-to-read benefit displays
  • Detailed information on hover/click

๐Ÿฅ Facility Registry Integration

1. Search Facility

Priority: ๐Ÿ”ด Critical

Search Parameters:

ParameterDescription
Facility CodeUnique facility identifier
Facility NameOfficial facility name
LocationGeographic location
LevelFacility level (primary, secondary, tertiary)

2. Save Facility Details

Priority: ๐ŸŸ  Standard

Required Data:

Data FieldPurpose
Facility NameIdentification
Facility LevelService scope
Facility CodesSystem identifiers
Location InfoGeographic data
Contact DetailsCommunication

Implementation:

  • Store locally in HMIS database
  • Implement caching to reduce API calls
  • Ensure proper data mapping

3. Use Facility Details

Priority: ๐ŸŸ  Standard

  • Populate organization resource in claims
  • Ensure consistent facility information
  • Implement data validation and fallback mechanisms

๐Ÿ‘จโ€โš•๏ธ Health Worker Registry Integration

1. Search Practitioner

Priority: ๐Ÿ”ด Critical

Search Parameters:

ParameterDescription
ID NumberNational identification
Registration NumberProfessional registration ID
NamePractitioner name

2. Save Practitioner Details

Priority: ๐ŸŸ  Standard

Required Data:

FieldDescription
Full NamesComplete practitioner name
License NumbersProfessional licenses
Registration NumberOfficial registration ID
ID NumberNational ID
SpecializationMedical specialty

3. Use Practitioner Details

Priority: ๐ŸŸ  Standard

  • Populate practitioner resource in claims
  • Ensure consistent information across claims
  • Handle updates and missing data appropriately

๐Ÿ’ผ Claims Integration

1. SHA Codes Mapping

Priority: ๐Ÿ”ด Critical

TaskImplementation
Code AdditionMap SHA codes to local database
ConsistencyEnsure uniform coding for SHA visits
ValidationValidate codes before submission
UpdatesHandle code version changes

2. Map Preauth Services

Priority: ๐Ÿ”ด Critical

Service Handling:

  • Flag services requiring preauthorization
  • Visual indicators in service selection
  • Block service until preauth confirmed

3. Send PreAuth Check

Priority: ๐Ÿ”ด Critical

Process Flow:

StepAction
1Identify service requiring preauth
2Collect required information
3Submit preauth request
4Process and store response
5Proceed based on authorization status

4. SHA Intervention Amounts

Priority: ๐ŸŸ  Standard

  • Display SHA payable amount per intervention
  • Use locally stored data
  • Update amounts regularly
  • Indicate patient vs. SHA responsibility

5. ICD-11 Search

Priority: ๐Ÿ”ด Critical

Implementation Options:

ApproachBenefits
API-based with cachingAlways current, minimal storage
Local databaseFast, offline capability
HybridOptimal performance and accuracy

6. Build Claim Bundle (Registries)

Priority: ๐ŸŸ  Standard

Bundle Components:

ComponentSource
Patient InformationLocal storage
Facility DetailsLocal storage
Practitioner InformationLocal storage
Visit DetailsCurrent encounter
Claim MetadataSystem-generated

7. Build Claim Bundle (SHR, Services & Diagnosis)

Priority: ๐Ÿ”ด Critical

Data Requirements:

CategoryDetails
DiagnosesPrimary and secondary (ICD-11)
ProceduresAll services rendered
MedicationsPrescribed medications
Clinical InfoAdditional required data

8. Claim Submission

Priority: ๐ŸŸ  Standard

Submission Process:

  1. Validate claim data completeness
  2. Submit claim to HIE
  3. Receive and process response
  4. Store claim ID for tracking
  5. Provide status feedback

9. Poll Claim Status

Priority: ๐Ÿ”ด Critical

FeatureImplementation
Status PollingRegular status checks using claim ID
Status CodesHandle all status codes appropriately
Visual IndicatorsClear display of claim status
ActionsEnable resubmission for rejections

๐Ÿš€ Advanced Features

Facility Level Context

Priority: ๐ŸŸข Advanced

  • Customize workflows based on facility capabilities
  • Display appropriate options by facility level
  • Hide unavailable features
  • Provide facility-specific guidance

Service Filtering By Facility Level

Priority: ๐ŸŸข Advanced

  • Filter services by facility level
  • Show only relevant services
  • Prevent selection of unavailable services
  • Implement referral workflows

โœ… Production Readiness Requirements

To be eligible for production deployment, you must complete 100% of all Critical (๐Ÿ”ด) and Standard (๐ŸŸ ) components.

Advanced features (๐ŸŸข) are optional enhancements that improve functionality but are not required for production.

Core Requirements

ComponentPriority
Use Official APIs๐Ÿ”ด Critical
Direct HMIS Integration๐Ÿ”ด Critical

Required for Production: 2/2 components

Client Registry Integration

ComponentPriority
Patient Registration๐ŸŸ  Standard
Patient Search๐Ÿ”ด Critical
Patient Data Decryption๐Ÿ”ด Critical
Patient Data Mapping & Storage๐ŸŸ  Standard
Update Patient๐ŸŸ  Standard
Dependents Handling๐ŸŸ  Standard
Consent Workflow๐ŸŸข Advanced

Required for Production: 6/6 Critical & Standard components

Eligibility Check Integration

ComponentPriority
Search Patient Eligibility๐Ÿ”ด Critical
SHA Patient Visit๐Ÿ”ด Critical
Display SHA Scheme Eligibility๐ŸŸ  Standard

Required for Production: 3/3 Critical & Standard components

Facility Registry Integration

ComponentPriority
Search Facility๐Ÿ”ด Critical
Save Facility Details๐ŸŸ  Standard
Use Facility Details๐ŸŸ  Standard

Required for Production: 3/3 Critical & Standard components

Health Worker Registry Integration

ComponentPriority
Search Practitioner๐Ÿ”ด Critical
Save Practitioner Details๐ŸŸ  Standard
Use Practitioner Details๐ŸŸ  Standard

Required for Production: 3/3 Critical & Standard components

Claims Integration

ComponentPriority
SHA Codes Mapping๐Ÿ”ด Critical
Map Preauth Services๐Ÿ”ด Critical
Send PreAuth Check๐Ÿ”ด Critical
SHA Intervention Amounts๐ŸŸ  Standard
ICD-11 Search๐Ÿ”ด Critical
Build Claim Bundle (Registries)๐ŸŸ  Standard
Build Claim Bundle (SHR, Services & Diagnosis)๐Ÿ”ด Critical
Claim Submission๐ŸŸ  Standard
Poll Claim Status๐Ÿ”ด Critical

Required for Production: 9/9 Critical & Standard components

Advanced Features (Optional)

ComponentPriority
Facility Level Context๐ŸŸข Advanced
Service Filtering By Facility Level๐ŸŸข Advanced

Required for Production: 0/2 (Optional enhancements)


๐Ÿ“Š Production Readiness Summary

Integration AreaRequired ComponentsStatus
Core Requirements2โ˜
Client Registry6โ˜
Eligibility Check3โ˜
Facility Registry3โ˜
Health Worker Registry3โ˜
Claims Integration9โ˜
TOTAL REQUIRED26โ˜

Production Eligibility Criteria

  • โœ… Ready for Production: All 26 Critical and Standard components completed
  • โš ๏ธ Not Ready for Production: Any Critical or Standard component incomplete

Note: Advanced features are optional and do not affect production eligibility.

Share:

Need Help with SHA Compliance?

Our experts have helped 50+ healthcare providers across Kenya achieve SHA compliance. Schedule a free assessment today.