RDCPASSBusiness
Health & medical· Public sector & social impact

Certified patient identity for hospitals, clinics and insurers

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.

  • One verified identity per patient
  • Face match at admission and when a claim is made
  • Telemedicine sign-in with RDCPASS

Example journey

Admitting an insured patient at a clinic

9:41
RDCPASSCustomer
KT

Kabeya M. Tshisekedi

COD-2103-0214-4937

Gives their RDCPASS ID at reception and looks into the tablet camera

Continue

The challenges

Duplicate and mismatched patient records

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.

Borrowed insurance cards and false claims

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.

Remote care depends on knowing who is on the call

A telemedicine consultation or an online prescription is only safe when the provider is sure of the patient’s identity.

How RDCPASS helps

01

Patient registration

Register each patient against their certified identity. When they come back, the front desk finds the same record instead of opening a new one.

02

Insurance eligibility at the point of care

Before care is authorised or a claim goes in, a selfie confirms that the person at reception is the insured member.

03

Telemedicine and patient portals

Patients sign in with RDCPASS, confirm with a face check on their phone and decide which details your service receives.

04

Claims and prescription fraud

Link each prescription and claim to a verified person. Where you suspect identity fraud, you can escalate it to the national fraud desk.

Connects to the channels you already run

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

  • Mobile app
  • Website
  • Branches & agents
  • Back office

Your outcomes

  • One verified identity per patient
  • Face match at admission and when a claim is made
  • Telemedicine sign-in with RDCPASS

Regulation & compliance

  • RDCPASS verifies identity only. It does not store, receive or share medical records, diagnoses or prescriptions.
  • Each application receives only the data scopes it is approved for, which supports your data-protection obligations for health information.
  • Every face check declares its purpose and is logged, so auditors can see why each patient was verified.
  • With Login with RDCPASS, patients confirm on their own phone and decide which details your service receives.

From first test to production

Every organization goes through the same three steps.

  1. 1

    Build in the sandbox

    Free and available immediately, with synthetic identities, businesses and faces.

  2. 2

    Pass due diligence

    We review your business (governance) and your application (security, scopes, testing).

  3. 3

    Go live

    Set up production keys and an mTLS certificate, and choose the billing model that suits you.

Frequently asked questions

Does RDCPASS see our patients’ medical data?+

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.

Can RDCPASS tell us whether a patient is insured?+

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.

Can we clean up our existing patient register?+

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.

How do we get started?+

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.

Start in the sandbox or talk to our team

The 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.