applaud
← Check another system

Nextech

Can applaud connect to Nextech Select and NexCloud?

YesReady: automatic connection

How it connects

Best way

Connects automatically

Nextech Select and NexCloud sends each visit to applaud as it happens. Nothing for your team to do day to day.

Certified FHIR R4 API (ONC (g)(10)): backend app polls Encounter + Patient, or bulk Group export

Connects automatically: Nextech Select and NexCloud

  1. applaud submits Nextech's connection request form from the developers portal for a backend (system) app; Nextech screens the app for security before a connection is made. (Not submitted by us: it needs applaud's company details.)
  2. The practice confirms its FHIR services are activated (its organization appears in Nextech's published Select / NexCloud base-URL bundle) and authorises applaud's app.
  3. applaud authenticates with SMART backend services: client_credentials plus a private_key_jwt assertion, against https://select.nextech-api.com/api/r4.
  4. Each day applaud searches Encounter by date or _lastUpdated, reads each Patient (given name + phone) and posts first name + mobile to applaud's intake API. If the server insists on a patient parameter for Encounter, use the Group $export instead.
  5. Keep only name, phone and visit date; drop every clinical resource the export returns.

Resources

Other ways, in order

Option 2

Connects through a script on your server

We install a small script on the computer that runs Nextech Select and NexCloud. It sends each visit to applaud automatically.

Read-only SQL Server reader on a client-server Select data server (not NexCloud)

Connects through a script on your server: Nextech Select and NexCloud

  1. Only for practices that run Select themselves (client-server model with their own SQL Server data server); NexCloud practices have no server of their own.
  2. Ask Nextech for written agreement first; the schema is unpublished and a contract or upgrade could change what is allowed.
  3. The practice's IT creates a read-only SQL login and applaud installs a small Windows service that reads each day's completed appointments and the matching patients' first name and mobile.
  4. The service posts them to https://applaud.you/api/v1/contacts. Unconfirmed: table and column names and how Select marks a completed visit.

Resources

Option 3

Connects by export

Recent patients are exported from Nextech Select and NexCloud and uploaded to applaud. A couple of minutes, and we can set it up with you.

Per-patient EHI export (Appointments.csv + Patient demographics.csv); a bulk visit report is not publicly documented

Connects by export: Nextech Select and NexCloud

  1. A practice user exports a patient's EHI ZIP from Select; the CSV folder holds Appointments.csv and Patient demographics.csv.
  2. The same ZIP holds EMN note PDFs and a CCDA, so this is not a minimum-necessary feed; use only if no API route is available.
  3. Select's own report writer and export screens are described in the Nextech Community Portal, which needs a Nextech login, so a bulk 'completed visits with first name + mobile' report could not be verified.

Resources

Option 4

Connects through a partner tool

A connector tool links Nextech Select and NexCloud to applaud.

Keragon: Nextech 'Appointment updated' -> HTTP POST to applaud

Connects through a partner tool: Nextech Select and NexCloud

  1. The practice opens a Keragon account (BAA included) and connects Nextech with its Nextech API credentials (see the API routes above: Nextech still has to issue them).
  2. Trigger: Appointment updated, filtered to completed visits; add a patient lookup if the payload lacks the phone.
  3. Action: HTTP POST to https://applaud.you/api/v1/contacts with the practice's applaud API key (first name + mobile).

Resources

Questions about connecting Nextech Select and NexCloud? We set it up with every new practice.

Ask us about your system

Tell us where to reach you and we'll come back with how applaud connects.

Book a demo