Overview
The Flows360 Allscripts connector uses the Allscripts FHIR and Unity APIs to enable secure, automated data synchronization between the Allscripts Electronic Health Record (EHR) platform and other applications. This integration facilitates the movement of key healthcare data objects, eliminating manual data entry, reducing administrative overhead, and ensuring data consistency across systems.
Automate the transfer of patient demographics, appointments, prescriptions, clinical notes, lab results, and insurance data to systems such as CRMs, billing platforms, and data analytics tools. This direct API connection provides a reliable method for creating a unified view of patient information and streamlining clinical and administrative workflows. Use this connector to build a more connected and efficient healthcare data ecosystem.
Capability summary
Authentication
Auth method: api_key
Required scopes
patient.read
patient.write
appointment.read
appointment.write
prescription.read
prescription.write
clinical_note.read
clinical_note.write
allergy.read
allergy.write
lab_result.read
lab_result.write
insurance_claim.read
insurance_claim.write
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Patients | Yes | Yes | |
| Appointments | Yes | Yes | |
| Prescriptions | Yes | Yes | |
| Clinical Notes | Yes | Yes | |
| Allergies | Yes | Yes | |
| Vital Signs | Yes | Yes | |
| Lab Results | Yes | Yes | |
| Insurance Claims | Yes | Yes | |
| Providers | Yes | No | Provider data is available for reading as part of other data objects. |
| Medications | Yes | No | Medication data is available for reading as part of other data objects. |
Supported actions
| Action | Description |
|---|---|
| fetch_patient_demographics | Retrieves the complete demographic and profile information for a specified patient. |
| create_new_appointment | Schedules a new patient appointment in the Allscripts calendar. |
| update_prescription | Modifies the details of an existing medication prescription. |
| new_clinical_note_added | Triggers when a new clinical note is saved for a patient record. |
| add_allergy | Adds a new allergy record to a patient's chart. |
| record_vital_signs | Records new vital sign measurements for a patient. |
| add_lab_result | Adds a new laboratory result to a patient's record. |
| submit_insurance_claim | Submits a new insurance claim for a patient encounter or procedure. |
| update_patient_status | Updates the administrative status of a patient (e.g., active, inactive). |
| new_lab_result_report | Triggers when a new lab result report becomes available. |
| appointment_status_changed | Triggers when an existing appointment's status is changed (e.g., confirmed, cancelled). |
| patient_checked_in | Triggers when a patient's appointment status is updated to 'checked-in'. |
Setup steps
1. Access the Allscripts Developer Portal
Log in to your organization's Allscripts Developer Portal or administrative console.
2. Create or Select an Application
Navigate to the API integration or application management section. You may need to register a new application to represent Flows360.
3. Generate API Credentials
Generate a new API key for the application. Ensure that the key is granted the necessary permissions (scopes) to read and write the objects you intend to manage (e.g., Patient, Appointment, Prescription).
4. Copy the API Key
Securely copy the generated API key. This value is required to establish the connection in Flows360.
5. Configure the Connector in Flows360
In the Flows360 connection settings for Allscripts, paste the API key into the designated field. Select the appropriate environment (e.g., Sandbox or Production) if applicable. Save the configuration to activate the connection.
Limitations
- The connector's performance is subject to the rate limits and availability of the Allscripts API.
- Data access is contingent on the permissions assigned to the API key user within Allscripts. If certain data types (e.g., specific lab results, financial data) are not visible, verify the user's permissions in the Allscripts administrative console.
- This connector supports the latest version of the Allscripts FHIR API. Compatibility with older or custom instances may vary.
- The
patient_checked_inaction relies on the timely update of appointment statuses within the Allscripts system. Delays in the source system will result in delayed trigger events.
Troubleshooting
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.