SHA Claims prepares eligibility checks, pre-authorisations and claims for Kenya’s Social Health Authority as FHIR R4 messages from your claims. It is built and sends once your facility’s SHA account is entered.
What happens through Social Health Authority (SHA), Kenya
Builds each message from the claim in Insurance Claims, with the patient’s national ID, the coded diagnosis and your facility’s SHA code.
Maps your service codes to SHA’s where you have mapped them.
Asks a person to record how the patient agreed to the claim before it can be marked ready.
Keeps SHA’s answer exactly as it came. A cover that is not in force is recorded, never a reason to turn a patient away.
Switching it on
What it takes
1Step 1Get your facility contracted with SHA and its system accepted.
2Step 2An administrator enters the SHA account in SHA Claims. It is sealed and never shown again.
3Step 3Enter the profiles and codes from your SHA onboarding pack.
4Step 4Until then, file on SHA’s portal and record its answer in SHA Claims.
What it does not do yet
The connector is written to SHA’s published specification and has not yet exchanged a live message with SHA; the first one is checked against your onboarding pack.
In the store
The apps that use Social Health Authority (SHA), Kenya
Does MedAppz connect to Social Health Authority (SHA), Kenya?
It is built, and it connects once your clinic adds its own keys. SHA Claims prepares eligibility checks, pre-authorisations and claims for Kenya’s Social Health Authority as FHIR R4 messages from your claims. It is built and sends once your facility’s SHA account is entered.
How do I switch on Social Health Authority (SHA), Kenya?
Get your facility contracted with SHA and its system accepted. An administrator enters the SHA account in SHA Claims. It is sealed and never shown again. Enter the profiles and codes from your SHA onboarding pack. Until then, file on SHA’s portal and record its answer in SHA Claims.
What does the Social Health Authority (SHA), Kenya connection not do yet?
The connector is written to SHA’s published specification and has not yet exchanged a live message with SHA; the first one is checked against your onboarding pack.