Skip to content

Stacksync × Supabase Miami: AI-Native OperationsOct 13Reserve your spot

New

Stacksync MCP is here. Give Claude, Cursor, and any MCP client governed access to your syncs, workflows, and connections.

Set up MCP
Business productivity / Accounting and finance · Two-way sync platform

NextGen Healthcare and Rillet integration

Plan how NextGen Healthcare and Rillet should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

Set this up from Claude or ChatGPT
  • Scope your workflow with an integration engineer
  • Review the systems, records, and updates you need
Integration planning
stacksync.com
NextGen Healthcare
Rillet
Review the integration scope

Built for teams where self-serve, reliability and scale matter

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo

Proposed workflow

Reconcile Rillet business records with NextGen Healthcare

This is an evaluation scenario; connector and operation support require confirmation.

Starting eventA finance-owned record in Rillet needs operational visibility through Clinical Documents.

  1. Select Customer or Vendor with the correct legal entity, period, and currency.

  2. Define a reporting relationship in NextGen Healthcare; do not equate customer records, ledger accounts, and posted transactions.

  3. Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.

What to verifyTotals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.

Review records and field ownership

AI assistant

Set up NextGen Healthcare and Rillet from Claude or ChatGPT

Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.

1. Add the Stacksync MCP server

Server URL

https://mcp.stacksync.com/mcp

In Claude

  1. Open Customize → Connectors, select + Add, then Add custom connector.
  2. Name it Stacksync and enter https://mcp.stacksync.com/mcp.
  3. Select Connect, sign in to Stacksync and choose your workspace.

In ChatGPT

  1. Open Settings → Apps → Advanced settings and turn on Developer mode.
  2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
  3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat.
Set up Codex or Claude Code

Codex

codex mcp add stacksync --url https://mcp.stacksync.com/mcp
codex mcp login stacksync

Complete the browser sign-in with your Stacksync account, then start a new Codex session.

Claude Code

claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp

Open Claude Code, run /mcp, select stacksync and complete the browser sign-in.

Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet.

Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: setup steps in the docs.

2. Ask your assistant

Create a sync between my NextGen Healthcare and Rillet.

Also from the same chat

You can also ask for workflows and AI agents (Genies) that use NextGen Healthcare and Rillet. The assistant checks what each app supports, for example:

  • “Build a workflow that messages our team in Slack when a NextGen Healthcare record changes.”
  • “Create a Genie that answers questions about our Rillet data in Slack.”

What happens next

  • Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat.
  • Gives you a secure sign-in link for each app it connects; you open it and sign in to that app.
  • Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first.

New to Stacksync? Create an account first, then sign in from your assistant.

Proposed record relationships

Records to connect

Use these examples to define record matching and field ownership for your technical review.

Download the mapping worksheet

CSV · No email required

Start with one NextGen Healthcare record and the result you want in Rillet: a report, a linked record, or an approved action. The listed record types do not identify a direct match, so define that relationship with your integration team before mapping fields.

Record coverage to review

Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.

NextGen Healthcare

Connection and object support require review

Record types to review with Stacksync

Record typesCoverage and requirements
  • Patients
  • Appointments
  • Encounters
  • Providers
  • Clinical Documents
  • Medications & Allergies
Confirm support for this record type and the direction you need.

Discuss NextGen Healthcare requirements

Rillet

Read and write support varies by record

Record types covered in the setup guide

Record typesCoverage and requirements
  • Customer
  • Invoice
  • Vendor
  • Credit Memo
  • Bill
  • Journal Entry
  • Invoice Payment
  • Charge
  • Reimbursement
  • Custom Field
Incremental: Yes; historical: Yes; delete detection: Yes. Confirm field permissions and sync direction.
  • Account
Incremental: Yes; historical: Yes; delete detection: Yes, every 1h. Confirm field permissions and sync direction.
  • Subsidiary
  • Tax Rate
  • Product
  • Contract
  • Bank Account
Incremental: No; historical: Yes; delete detection: Yes, every 1h. Confirm field permissions and sync direction.
  • Bank Transaction
Incremental: No; historical: Yes; delete detection: Yes, every 4h. Confirm field permissions and sync direction.

Read the Rillet connector guide

Connection essentials

Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.

View setup requirements and limits
Connection requirementNextGen HealthcareRillet
Integration interfaceREST API, including FHIR-based endpoints published through NextGen's developer API programREST API (OpenAPI-specified, with production and sandbox environments)
AuthenticationConfirm the credentials, API plan, and permissions required for NextGen Healthcare.API key generated in Rillet
Change detectionConfirm how Stacksync detects changes for this connector and the objects you need.Historical and incremental syncs are documented by object.
Read accessConfirm with StacksyncAvailable for supported records
Write accessConfirm with StacksyncAvailable for supported records

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

  • SOC 2 Type II
  • ISO 27001
  • HIPAA BAA
  • GDPR
  • CCPA
  • DPF US-EU-UK-CH

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

NextGen Healthcare
Integration interface
REST API, including FHIR-based endpoints published through NextGen's developer API program
Authentication
Confirm the credentials, API plan, and permissions required for NextGen Healthcare.
Change detection
Confirm how Stacksync detects changes for this connector and the objects you need.
Read access
Confirm with Stacksync
Write access
Confirm with Stacksync
Setup requirements
  • Identify the NextGen Healthcare account, edition, environment, and business objects the integration must access.
  • Confirm a Stacksync connector or implementation path for NextGen Healthcare, including read/write support, authentication, and initial-load limits.
Limitations to check
  • Confirm Stacksync support for NextGen Healthcare and the record types your workflow needs.
  • Review write-back, deletion handling, update timing, and account limits with the integration team.
Rillet
Integration interface
REST API (OpenAPI-specified, with production and sandbox environments)
Authentication
API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only to enable writes for two-way sync; check Read Only to prevent write-back
Change detection
Historical and incremental syncs are documented by object. Some objects have only historical sync; delete detection intervals vary.
Read access
Available for supported records
Write access
Available for supported records
Setup requirements
  • Generate an API key in Rillet Organization Setting > API Access.
  • For two-way sync, clear the Read Only setting; use a read-only key when the integration only needs outbound data.
Limitations to check
  • Some objects have historical sync only; deletion checks for supported objects can run at different intervals.
Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

Rillet setup guide

Prepare NextGen Healthcare and Rillet access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

NextGen Healthcare setup checklist
  • Identify the NextGen Healthcare account, edition, environment, and business objects the integration must access.
  • Confirm a Stacksync connector or implementation path for NextGen Healthcare, including read/write support, authentication, and initial-load limits.
Rillet setup checklist
  • Generate an API key in Rillet Organization Setting > API Access.
  • For two-way sync, clear the Read Only setting; use a read-only key when the integration only needs outbound data.

Setup guides: Authorize Rillet Connection

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the NextGen Healthcare and Rillet planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet · CSV, no email required

Start with one NextGen Healthcare record and the result you want in Rillet: a report, a linked record, or an approved action. The listed record types do not identify a direct match, so define that relationship with your integration team before mapping fields.

Compare integration approaches

Choose a method around one example record and the update your business needs. Define how the NextGen Healthcare source record should appear or trigger work in Rillet. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit
Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility
Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose
Provide your table or object schemas and one example update; confirm the supported keys, fields, and direction.

Native vendor integration

Best fit
A vendor-built integration may fit if it supports your NextGen Healthcare and Rillet record types.
Operating responsibility
Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose
First check whether either vendor offers this integration. If available, verify your record types, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit
Consider when NextGen Healthcare and Rillet need a transformation, approval, or action outside a direct record sync.
Operating responsibility
Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose
Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.

File or scheduled snapshot

Best fit
Consider for a one-time NextGen Healthcare / Rillet migration or a reporting need with an explicit freshness window.
Operating responsibility
Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose
Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Reconcile Rillet business records with NextGen Healthcare

This is an evaluation scenario; connector and operation support require confirmation.

Starting event: A finance-owned record in Rillet needs operational visibility through Clinical Documents.

  1. Select Customer or Vendor with the correct legal entity, period, and currency.
  2. Define a reporting relationship in NextGen Healthcare; do not equate customer records, ledger accounts, and posted transactions.
  3. Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.

Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.

If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.

Initial load and acceptance testing

Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.

Direction and permissions

Test case

Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.

Expected result

Only an approved, supported direction and permitted fields are written.

Freshness and reconciliation

Test case

Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.

Expected result

The process meets its agreed freshness target and reconciliation has no unexplained differences.

Failed updates, retries and recovery

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

A record type or update is unavailable

Investigate

Check the NextGen Healthcare and Rillet connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between NextGen Healthcare and Rillet

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

NextGen Healthcare Rillet Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in Rillet.

Rillet NextGen Healthcare Direction requires confirmation

Detect changesHistorical and incremental syncs are documented by object. Some objects have only historical sync; delete detection intervals vary.

Apply updatesConfirm that Stacksync can create or update the records you need in NextGen Healthcare.

Update timing and record limits
  • Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
  • Review write-back, deletion handling, update timing, and account limits with the integration team.
  • Some objects have historical sync only; deletion checks for supported objects can run at different intervals.
FAQ

NextGen Healthcare and Rillet integration FAQ

Further reading

Resources for your technical review

Next step

Plan your integration with an engineer

Walk through your NextGen Healthcare and Rillet records, field mappings, and requirements with an integration engineer.

Talk to an engineer Explore plans and pricing