Hospitals, clinics, health insurers and telemedicine services use RDCPASS to confirm who a patient is against the national register. Records, claims and prescriptions then sit under the person they belong to. RDCPASS verifies identity only and never holds or shares medical records.
Example journey
Kabeya M. Tshisekedi
COD-2103-0214-4937
Gives their RDCPASS ID at reception and looks into the tablet camera
A name spelled two ways or a missing document is enough to open a second file for the same patient. Their history ends up split across records, and care suffers for it.
If presenting a card is all it takes, people who are not the insured member use the cover. Claims made that way are hard to challenge afterwards.
A telemedicine consultation or an online prescription is only safe when the provider is sure of the patient’s identity.
Register each patient against their certified identity. When they come back, the front desk finds the same record instead of opening a new one.
Before care is authorised or a claim goes in, a selfie confirms that the person at reception is the insured member.
Patients sign in with RDCPASS, confirm with a face check on their phone and decide which details your service receives.
Link each prescription and claim to a verified person. Where you suspect identity fraud, you can escalate it to the national fraud desk.
Your app, website, branches and back office call RDCPASS through a single integration. The services you choose send back verified answers your staff can act on.
Your channels
Your outcomes
Every organization goes through the same three steps.
Build in the sandbox
Free and available immediately, with synthetic identities, businesses and faces.
Pass due diligence
We review your business (governance) and your application (security, scopes, testing).
Go live
Set up production keys and an mTLS certificate, and choose the billing model that suits you.
No. RDCPASS confirms who the patient is and returns only the identity details your application is approved for. Medical records, diagnoses and prescriptions stay in your own systems.
No, cover stays in your insurance system. What RDCPASS confirms is that the person presenting is the insured member, so your own eligibility check is applied to the right individual.
Yes. Submit patient identifiers in batches of up to 10,000 records. Each one is confirmed against the national identity, and duplicate files can then be merged under one verified person.
Building and testing in the sandbox is free. Production access follows due diligence on your organisation and your application. After that, you pay from a prepaid wallet or on a monthly Enterprise invoice in USD or CDF.
Verify policyholders and beneficiaries, and catch identity fraud in claims.
Learn moreRegister each beneficiary once and make sure the aid reaches that person.
Learn moreOffer public services online using the national identity citizens already hold.
Learn moreThe sandbox is free and open now. If you would rather discuss your sector, expected volumes and billing model first, our team can take you through it.