Connect Your EHR

TietAI connects to Electronic Health Record systems via FHIR R4, native EHR APIs, and HL7 v2 MLLP. Once a connector is configured and tested by an administrator, it is available to every workflow in your organization.

remarque

Connector configuration requires the Admin role. Clinicians and Viewers can use existing connectors in workflows but cannot create or edit them.

---

Supported systems

EHR / Clinical systems

System	Connection type	Auth method	Notes
Epic	FHIR R4 + Epic API	OAuth 2.0 (JWT)	Requires App Orchard / MyApps registration
Cerner (Oracle Health)	FHIR R4	OAuth 2.0	Standard SMART on FHIR
athenahealth	FHIR R4	OAuth 2.0	Requires athenahealth developer account
Allscripts	FHIR R4	OAuth 2.0 + API key	Unity API and TouchWorks
Dedalus	FHIR R4	Bearer token	European healthcare systems; ENS/IHE/GDPR compliant
Generic FHIR R4	FHIR R4	Bearer, Basic, or none	Any FHIR R4 server (Azure, AWS, GCP, internal)
HL7 v2 sources	HL7 MLLP	None (network-level)	Via TietAI Connect service

SAP Healthcare systems

System	Module	Auth method	Use for
SAP S/4HANA for Healthcare	S/4HANA Health	OAuth 2.0 (OData v4)	Real-time analytics, FHIR bridge, Patient 360
SAP Patient Management	SAP IS-H	RFC / SAP Logon	Admissions, discharges, transfers (ADT), bed management
SAP Clinical Data	SAP IS-H*MED	RFC / SAP Logon	Clinical documentation, CPOE, lab results, nursing notes
SAP Healthcare Billing	SAP IS-H FI	RFC / SAP Logon	Claims, DRG, X12 837/835, revenue cycle
SAP Integration Suite	SAP CPI / BTP	OAuth 2.0	Message routing, HL7↔FHIR↔IDoc transformation

---

Connecting Epic

Before you start: MyApps registration

Epic requires all third-party applications to be registered in the Epic MyApps marketplace before API access is granted. If your Epic administrator has not already registered TietAI:

1. Log in to Epic's App Orchard at https://appmarket.epic.com
2. Search for TietAI and request access for your organization
3. Epic will issue an App Name, App Key (Client ID), and a private key (downloaded as a .pem file)
4. Share these credentials with your TietAI administrator

This process can take 1–5 business days. Your Epic integration team can expedite it if you have an existing relationship with Epic.

Steps to connect

1. Go to Settings → Connectors → Add Connector
2. Select Epic from the connector type list
3. Fill in the connection details:

Field	What to enter	Example
Connector name	A display name for this connection	Epic Production
Base URL	Your Epic FHIR endpoint	https://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/R4
App Name	From your MyApps registration	TietAI_Platform
Client ID (App Key)	From your MyApps registration	a1b2c3d4-e5f6-...
Private key	Upload the .pem file from Epic	—
Environment	Select Production or Sandbox	—

4. Click Test Connection

A successful test shows a green checkmark and displays the server's capability statement — confirming TietAI can authenticate and reach your Epic server.

5. Click Save

The connector now appears in the Connectors list with status Active. It is immediately available to all workflow nodes that accept an Epic connection.

attention

Never share your Epic private key via email or Slack. Upload it directly through the TietAI connector form. TietAI encrypts and stores it at rest using AES-256.

---

Connecting a generic FHIR R4 server

Use this connector for any server that speaks standard FHIR R4 — including internal FHIR servers, Azure Health Data Services, AWS HealthLake, and Google Cloud Healthcare API.

Steps

1. Go to Settings → Connectors → Add Connector
2. Select FHIR R4 from the connector type list
3. Fill in the connection details:

Field	What to enter
Connector name	A display name (e.g., Internal FHIR Server)
Base URL	FHIR server base URL (no trailing slash) — e.g., https://fhir.yourhospital.org/r4
Authentication	Select the appropriate method (see below)

Authentication options

Method	When to use
Bearer token	The server requires a static API token or a JWT you generate externally. Paste the token into the field. Note: static tokens do not auto-refresh — you must update the connector when the token expires.
Basic auth	The server requires a username and password. Enter credentials in the respective fields. Used for internal servers with simple HTTP auth.
None	The server is accessible without authentication (internal networks only). Do not use this for any server reachable from the internet.

4. Click Test Connection, then Save

---

Connecting via HL7 v2 (MLLP)

HL7 v2 integration uses the TietAI Connect service, which listens for inbound MLLP connections and routes messages into your workflows.

What is MLLP?

MLLP (Minimum Lower Layer Protocol) is the standard transport protocol for HL7 v2 messages. It is a TCP-based protocol that adds start-of-block and end-of-block framing to HL7 message bytes. Most HIS, lab, and radiology systems that generate HL7 messages support MLLP natively.

Steps

1. Go to Settings → Connectors → Add Connector
2. Select HL7 v2 / MLLP
3. Configure the listener:

Field	What to enter
Connector name	e.g., Lab HL7 v2 Listener
Listen port	The TCP port TietAI Connect will open (e.g., 2575)
Message types	Select which message types to accept (ADT, ORU, ORM, SIU)
Encoding	ER7 (pipe-delimited) or XML

4. Click Save. TietAI Connect opens the listener port.
5. Configure your source system (HIS, lab system, etc.) to send HL7 messages to <TietAI Connect IP>:<port>

Contact your TietAI administrator for the Connect service IP address.

---

Connecting Dedalus

Dedalus is widely used in European healthcare systems, particularly in Spain, Italy, and Germany. TietAI's Dedalus connector is GDPR, ENS, and IHE compliant.

Steps

1. Go to Settings → Connectors → Add Connector
2. Select Dedalus FHIR
3. Fill in the connection details:

Field	What to enter
Connector name	e.g., Dedalus Production
Base URL	Your Dedalus FHIR R4 endpoint
Authentication	Bearer token (provided by your Dedalus administrator)
Language	Interface language (e.g., es, it, de)
ENS settings	Esquema Nacional de Seguridad settings (Spain only)

4. Click Test Connection, then Save

remarque

ENS (Esquema Nacional de Seguridad) configuration is required for deployments in Spain. Contact your Dedalus representative for the correct ENS profile settings.

---

Connecting SAP Healthcare systems

TietAI supports multiple SAP IS-H modules. Choose the right connector for your use case:

• SAP Patient Management — for ADT workflows (admissions, discharges, transfers)
• SAP Clinical Data — for orders, results, clinical documentation
• SAP Healthcare Billing — for claims and revenue cycle
• SAP S/4HANA for Healthcare — for analytics, reporting, and FHIR integration
• SAP Integration Suite — for routing and transforming messages between systems

Connecting SAP Patient Management (IS-H)

Used for admissions, discharge, transfer (ADT) workflows and bed management.

1. Go to Settings → Connectors → Add Connector
2. Select SAP Patient Management
3. Fill in the connection details:

Field	What to enter
Connector name	e.g., SAP IS-H Production
SAP Host	SAP application server hostname or IP
SAP Client	SAP client number (e.g., 100)
Institution	IS-H institution code (e.g., 0001)
Ward/Unit	Default ward unit code (optional)
ADT Mapping	HL7 ADT to IS-H field mapping profile
Insurance check	Enable automatic insurance verification on admission

4. Click Test Connection, then Save

Connecting SAP Clinical Data (IS-H*MED)

Used for querying clinical documentation, creating orders (CPOE), and retrieving lab/radiology results.

1. Go to Settings → Connectors → Add Connector
2. Select SAP Clinical Data
3. Fill in the connection details:

Field	What to enter
SAP Host	SAP application server hostname
Clinical module	IS-H*MED or the specific module identifier
Order types	Order categories to expose (e.g., LAB, RAD, MED)
Result categories	Result types to retrieve (e.g., LAB_RESULT, RAD_REPORT)
Document types	Clinical document types to query (e.g., DISCHARGE_LETTER)

4. Click Test Connection, then Save

Connecting SAP Healthcare Billing (IS-H FI)

Used for submitting claims, processing X12 835 remittance, DRG calculation, and revenue cycle workflows.

1. Go to Settings → Connectors → Add Connector
2. Select SAP Healthcare Billing
3. Fill in the connection details:

Field	What to enter
SAP Host	SAP application server hostname
Billing organisation	IS-H FI billing organization code
Claim format	X12_837P (professional), X12_837I (institutional), or HL7
DRG engine	DRG grouper version (e.g., GRD_2024)
Clearinghouse	Clearinghouse ID for claim routing (optional)

4. Click Test Connection, then Save

Connecting SAP S/4HANA for Healthcare

Used for real-time analytics, Patient 360 views, FHIR data bridging, and financial reporting.

1. Go to Settings → Connectors → Add Connector
2. Select SAP S/4HANA for Healthcare
3. Fill in the connection details:

Field	What to enter
S/4HANA URL	Your S/4HANA system URL
Client ID	OAuth 2.0 client ID from SAP BTP
Client Secret	OAuth 2.0 client secret from SAP BTP
Tenant	SAP BTP tenant/subaccount ID
OAuth URL	SAP BTP token endpoint URL
Scope	OAuth scopes required (e.g., patient.read analytics.read)
FHIR Mapping	FHIR-to-SAP field mapping profile (leave empty for defaults)

4. Click Test Connection, then Save

Connecting SAP Integration Suite (CPI)

Used for routing, transforming, and orchestrating messages between TietAI and SAP systems — especially for HL7↔FHIR↔IDoc translation.

1. Go to Settings → Connectors → Add Connector
2. Select SAP Integration Suite
3. Fill in the connection details:

Field	What to enter
CPI URL	Your SAP Integration Suite tenant URL
Client ID	OAuth client ID from SAP BTP cockpit
Client Secret	OAuth client secret
iFlow ID	The CPI integration flow to invoke
Adapter	Message adapter: HL7, FHIR, X12, or IDoc
Message protocol	Protocol expected by the iFlow

4. Click Test Connection, then Save

astuce

SAP Integration Suite is the recommended connector when you need to route messages through existing SAP CPI iFlows or when your SAP landscape uses B2B/EDI message exchange.

---

Testing your connection

After saving any connector, you can re-test it at any time from the Connectors list:

1. Go to Settings → Connectors
2. Find the connector in the list
3. Click the ... menu → Test Connection

Result	What it means
Green checkmark — "Connection successful"	The server is reachable and credentials are valid
Yellow warning — "Partial connection"	The server responded but returned unexpected data (check the FHIR version or endpoint path)
Red X — "Connection timeout"	The server did not respond within 10 seconds. Check the URL and network firewall rules.
Red X — "Authentication failed (401)"	Credentials are invalid or expired. Re-enter them.
Red X — "Forbidden (403)"	Credentials are valid but the account lacks the required permissions. Contact your EHR administrator.

---

Troubleshooting

Error: "SSL certificate verification failed" The FHIR server's TLS certificate is self-signed or from an untrusted CA. Contact TietAI support to add a custom CA certificate to your deployment.

Error: "Unable to resolve hostname" The URL is incorrect or the hostname does not resolve from TietAI's servers. Verify the URL by opening it in your browser from the same network. If the server is internal, you may need a VPN or private link configuration — contact TietAI support.

Test passes but workflow fails with connector error Connector tests use a lightweight capability request. The workflow may be requesting resources that your Epic account does not have permission to access. Review the Epic user account associated with the connector and ensure it has access to Patient, Condition, Medication, and other resource types your workflows need.

Epic connection works in Sandbox but fails in Production Production and Sandbox are separate Epic environments with separate credentials. Confirm you have a MyApps registration for the Production environment, not just Sandbox, and that you have entered the correct Production base URL.