Why am I receiving an authentication error?

An 'Authentication Failed' or 'Invalid API Key' error indicates that the key provided in the Flows360 connection settings is incorrect, has been revoked, or is for the wrong Allscripts environment (e.g., using a sandbox key for production).nn1. Verify the API key is copied correctly with no extra characters or spaces.n2. Confirm the key is still active in the Allscripts Developer Portal.n3. Ensure the correct environment (Sandbox/Production) is selected in the Flows360 connector configuration.

Data is not syncing for some patients or objects. What should I check?

If a flow is failing to retrieve or update data for certain records, it is likely a permissions issue. The API key inherits the permissions of the user it was created under in Allscripts.nn1. Log in to the Allscripts admin console and review the permissions for the user account associated with the API key.n2. Ensure the user has explicit read/write access to the specific data objects and patient records required by the integration.n3. After updating permissions in Allscripts, you may need to re-save the connection in Flows360.

There is a delay in trigger events, such as a new lab result. Why?

Triggers such as `new_lab_result_report` or `appointment_status_changed` depend on polling the Allscripts API for new information. The delay is determined by the polling interval configured in your flow (e.g., every 5 minutes). If the delay is longer than the configured interval, check the Allscripts API status page for reported incidents. Review the flow's execution history for any API-related error messages that may indicate rate limiting or other issues.

Allscripts Integration & Workflow Automation

Connector

Allscripts

Connect to Allscripts FHIR and Unity APIs to synchronize Electronic Health Records (EHR), patient data, appointments, and billing information. Automate clinical and administrative workflows between Allscripts and other business systems.

Get Started Talk to an Expert

CategoryHealthcare

Authenticationapi_key

Objects10 supported

Actions12 supported

Technical ReferenceView technical reference

Overview

What you can do with Allscripts.

Connected capability

Relevant workflows and teams

Customer 360
Data Warehousing
Finance & Billing
Revenue Operations

Technical Reference

Allscripts

View technical reference

Similar connectors

Continue exploring.

View all connectors

Cerner

Synchronize patient and clinical data between Cerner's electronic health record (EHR) system and other platforms. Automate workflows, reduce manual data entry, and connect patient information across your entire software stack using Cerner's SMART on FHIR APIs.View details

Epic

Connects to the Epic EHR system using the FHIR R4 API standard. It enables bidirectional data synchronization for core healthcare objects like Patients, Encounters, and Orders to automate clinical and administrative workflows.View details

MEDITECH

Integrate MEDITECH EHR for bidirectional data exchange. Automate clinical and administrative workflows by connecting patient records, scheduling, billing, and clinical data to other business systems.View details

NextGen Healthcare

Read and write patient and encounter data from NextGen Healthcare. This integration allows for syncing patient records, managing appointments, and creating medical referrals.View details

Next step

Connect Allscripts through Flows360.

Talk through the connector, the systems around it and the outcome you need.

Get Started Talk to an Expert

Find the right connection faster.

What you can do with Allscripts.

Connected capability

Relevant workflows and teams

Allscripts

Continue exploring.

Connect Allscripts through Flows360.