Connect Allscripts to your entire application stack.
The Flows360 Allscripts integration provides a secure and reliable way to connect your Allscripts electronic health record platform with other software, including CRMs, billing systems, patient engagement platforms, and data analytics tools. By automating data synchronization, healthcare providers can eliminate information silos, improve operational efficiency, and ensure data consistency across the patient journey. Move patient demographics, appointments, lab results, and financial data to where it's needed most, without manual intervention or complex custom development. This enables a more connected, efficient, and data-driven healthcare operation.
Common use cases
- Create a 360-degree patient view by syncing Allscripts data with a CRM.
- Automate billing workflows by connecting Allscripts to accounting software.
- Enable patient self-service portals with real-time appointment and record data.
- Feed clinical data into analytics platforms for population health management.
- Streamline patient intake by synchronizing registration forms with Allscripts records.
Sync scenarios
- Patient Demographics
- Appointments & Scheduling
- Clinical Summaries (CCDA)
- Billing & Financial Records
- Lab Results & Orders
- Prescriptions
Objects supported
- Patients
- Appointments
- Prescriptions
- Clinical Notes
- Allergies
- Vital Signs
- Lab Results
- Insurance Claims
- Providers
- Medications
Actions
- fetch_patient_demographics
- create_new_appointment
- update_prescription
- new_clinical_note_added
- add_allergy
- record_vital_signs
- add_lab_result
- submit_insurance_claim
- update_patient_status
- new_lab_result_report
- appointment_status_changed
- patient_checked_in
Frequently asked questions
What kinds of systems can I connect Allscripts to?
You can connect Allscripts to hundreds of applications, including CRMs, ERPs, marketing automation platforms, patient communication tools, and data warehouses. The platform is designed for flexible, system-agnostic integration.
How does this integration improve operational efficiency?
By automating data transfer between Allscripts and other systems, you eliminate manual data entry, reduce the risk of human error, and ensure that your teams are always working with the most up-to-date information, saving time and resources.
Is the Allscripts integration compliant with HIPAA?
Yes. Flows360 is built with security and compliance at its core. We operate within a HIPAA-compliant framework to ensure all Protected Health Information (PHI) is handled securely.
- Auth method: api_key
- Required scopes: 14
- Supported objects: 10
- Supported actions: 12
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.
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.
Required scopes
patient.readpatient.writeappointment.readappointment.writeprescription.readprescription.writeclinical_note.readclinical_note.writeallergy.readallergy.writelab_result.readlab_result.writeinsurance_claim.readinsurance_claim.write
Supported objects
- Patients
- Appointments
- Prescriptions
- Clinical Notes
- Allergies
- Vital Signs
- Lab Results
- Insurance Claims
- Providers
- Medications
Supported actions
- 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'.
Use cases
- Revenue Operations
- Customer 360
- Data Warehousing
- Finance & Billing
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_in` action relies on the timely update of appointment statuses within the Allscripts system. Delays in the source system will result in delayed trigger events.
