Allscripts FHIR
Category: EHR & Practice Mgmt
Node id: allscripts-fhir
Standards: HIPAA, GDPR, SOC2
Integrates with Allscripts EHR via FHIR R4 API for searching, reading, and patient lookup operations
What it does
- OAuth2 client credentials authentication for Allscripts
- FHIR R4 search and read operations
- Patient-specific search by demographics and identifier
- Application name header support (X-Allscripts-App-Name)
Use cases
- Query patient records from Allscripts EHR for data integration
- Search Allscripts for patients by name or identifier
- Feed Allscripts clinical data into downstream FHIR transformation pipelines
Runtime
- Performance tier:
variable
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
search_params | json | No | Search parameters as key-value pairs |
resource_id | text | No | Resource ID for read operations |
family_name | text | No | Patient family name for patient_search |
given_name | text | No | Patient given name for patient_search |
birthdate | text | No | Patient birth date for patient_search |
identifier | text | No | Patient identifier for patient_search |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Main result data from the Allscripts FHIR operation |
metadata | json | No | Response metadata including resource type, counts, and operation details |
success | boolean | No | Whether the operation succeeded |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Allscripts Base URL | allscripts_base_url | string | Yes | Base URL of the Allscripts EHR instance | ||
| Operation | operation | enum | Yes | search | search, read, patient_search | FHIR operation to perform |
| Resource Type | resource_type | string | No | Patient | FHIR resource type to operate on |
Auth
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Client ID | client_id | secret | Yes | OAuth2 client ID for Allscripts authentication | ||
| Client Secret | client_secret | secret | Yes | OAuth2 client secret for Allscripts authentication | ||
| Application Name | app_name | string | No | Allscripts application name (sent as X-Allscripts-App-Name header) |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Search Parameters | search_params | json | No | Default search parameters as key-value pairs | ||
| Resource ID | resource_id | string | No | Resource ID for read operations (can also come from input) |
Errors
| Code | Description |
|---|---|
ALLSCRIPTS_AUTH_FAILED | Failed to obtain OAuth2 token from Allscripts |
ALLSCRIPTS_SEARCH_FAILED | Allscripts FHIR search returned an error |
ALLSCRIPTS_READ_FAILED | Allscripts FHIR read returned an error |
RESOURCE_ID_REQUIRED | resource_id is required for read operation |
Runtime notes
- patient_search returns both a FHIR bundle and a flat patients array for convenience — downstream nodes can use either
- search_params from the input port are merged with (and override) search_params from config
- OAuth2 token is fetched automatically via client_credentials grant on every execution
- The result shape varies by operation: search returns bundle, read returns resource, patient_search returns bundle+patients
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
¿Algo no está claro? Envíe sus comentarios sobre la documentación por correo electrónico..