Skip to main content

Patient Matching & Mapping to EHR Accounts (Cliniko/Nookal/Meddbase)

Written by Dr. Harvinder Power

OS migration note: no Cliniko or Nookal patients recognised

If you use Cliniko or Nookal and Motics recognises no patients after the Motics OS migration, treat this as a likely integration/API-key reconnection issue first. This is expected for some users during the migration.

Go to Settings > Integrations, open Cliniko or Nookal, re-enter or verify the API key, save the connection, then retry the patient search. Do not create duplicate patients unless the integration is connected and only one specific patient is missing.

Cliniko patient search

  • Search by the patient's legal or primary first and last name in Cliniko.

  • Confirm DOB or another identifier before linking.

  • If the patient has a preferred name in Cliniko, Motics may still need the legal/primary name for search and matching.

  • If several similar results appear, open the patient card in Cliniko to verify identifiers.

  • If one specific patient is not found after the integration is connected, create or update the patient in Cliniko first, then link in Motics.

Preferred names in Cliniko

If a patient uses a preferred name, Cliniko may show that preferred name in some areas while Motics search relies on the primary name fields. For example, if the preferred name is John but the legal/primary name is Alan, search for Alan when linking the patient.

This is a known patient-matching limitation. It does not mean the note has linked to the wrong person, but you should always confirm DOB or another identifier before pushing.

Nookal patient search

  • Use the patient search box and confirm DOB or another identifier.

  • If results seem incomplete, check Settings > Integrations > Nookal and confirm the API key and region.

  • Confirm the mapped patient before pushing a note.

Meddbase

  • Ensure the session has the right patient context before pushing documents.

  • For referrer letters, confirm the contact has an address and the right department/key person.

Avoid duplicates

  • Do not create duplicate patients just because search is failing after the OS migration. Check the integration/API key first.

  • Always compare DOB, postcode, or another identifier where available before linking.

  • If a wrong link was made, remove and relink before pushing.

Did this answer your question?