SAP Clinical Data
Category: EHR & Practice Mgmt
Node id: sap-clinical-data
Standards: SOC2
Integrates with SAP IS-H/MED for clinical data management including diagnoses, procedures, orders, and observations
What it does
- SAP IS-H/MED diagnosis data retrieval
- Procedure and intervention queries
- Clinical order management
- Observation and result data access
- OData-based SAP IS-H/MED integration
Use cases
- Extract patient diagnoses from SAP clinical systems
- Retrieve surgical procedure records for reporting
- Query clinical orders and results for care coordination
- Clinical data integration from SAP to FHIR-based systems
Runtime
- Performance tier:
variable
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
case_id | text | No | Case ID for get_diagnoses, get_procedures, and get_orders operations |
diagnosis_data | json | No | Diagnosis data for add_diagnosis operation |
order_data | json | No | Order data for create_order operation |
patient_id | text | No | Patient ID for get_observations operation |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
diagnoses | json | No | List of diagnoses for a case |
diagnosis | json | No | Created diagnosis record |
procedures | json | No | List of procedures for a case |
orders | json | No | List of orders for a case |
order | json | No | Created order record |
observations | json | No | List of patient observations |
http_status | number | No | HTTP status code from SAP |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| SAP URL | sap_url | string | Yes | Base URL of the SAP IS-H/MED instance | ||
| Operation | operation | enum | No | get_diagnoses | get_diagnoses, add_diagnosis, get_procedures, get_orders, create_order, get_observations | Clinical data operation to perform |
Auth
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Auth Token | auth_token | secret | No | Bearer token for SAP authentication | ||
| API Key | api_key | secret | No | SAP API key |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| SAP Client | sap_client | string | No | 100 | SAP client number |
Errors
| Code | Description |
|---|---|
SAP_URL_REQUIRED | SAP system URL must be configured |
PATIENT_ID_REQUIRED | Patient ID required for clinical data queries |
SAP_REQUEST_FAILED | HTTP request to SAP system failed |
UNSUPPORTED_OPERATION | Operation not recognized |
Runtime notes
- Only one output key is populated per execution depending on the operation
- case_id is required for get_diagnoses, get_procedures, and get_orders; patient_id for get_observations
- Output shape comes directly from SAP OData response; structure varies by IS-H/MED version
- http_status is always present alongside the data output
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
Something unclear? Send documentation feedback by email.