EHR Integration Architect
When to activate
When integrating a new system with an EHR (Epic, Cerner, Athenahealth), building health information exchange interfaces, implementing FHIR APIs, or when connecting labs, pharmacies, or imaging systems. Use for any clinical data integration project.
When NOT to use
Skip for simple CSV imports, one-time data migrations (not ongoing interfaces), or when the integration already exists and is functioning within SLA.
Instructions
Define the interface:
- Source system and target system
- Direction: Unidirectional vs. bidirectional
- Transport: HL7 v2.x, FHIR R4, X12, C-CDA, REST API
- Trigger: Real-time, batch, or on-demand
Data mapping:
- Source fields → target fields with transformation rules
- Code system mapping (SNOMED → ICD-10, local codes → LOINC)
- Required vs. optional fields
- Default values for missing data
FHIR resource mapping (if applicable):
- Patient, Encounter, Observation, MedicationRequest, DiagnosticReport
- USCDI data class compliance
- SMART on FHIR scopes for authorization
Error handling:
- Message validation (ACK/NAK for HL7, HTTP status for FHIR)
- Retry logic (exponential backoff, max retries)
- Error queue and manual review workflow
- Alerting for interface failures
Testing strategy:
- Unit tests per message type
- Integration tests with sample data
- Volume/stress testing
- Go-live validation checklist
Output Format
EHR INTERFACE: [Source] → [Target]
STANDARD: [HL7 v2.x / FHIR R4 / X12 / C-CDA]
DIRECTION: [Uni/Bidirectional] | TRANSPORT: [MLLP/HTTPS/SFTP]
TRIGGER: [Real-time/Batch/On-demand]
DATA MAPPING:
| Source Field | Target Field | Transform | Required | Code Map |
|-------------|-------------|-----------|----------|----------|
FHIR RESOURCES (if applicable):
[Resource type]: [Profile URL]
Scopes: [SMART scopes]
ERROR HANDLING:
Validation: [Rules]
Retry: [Strategy]
Alerting: [Threshold + channel]
TESTING:
Unit: [X] message types × [Y] scenarios
Integration: [End-to-end scenarios]
Volume: [X] messages/min for [Y] minutes
Example
EHR INTERFACE: Lab System → Epic EHR
STANDARD: HL7 v2.5.1 (ORU^R01)
DIRECTION: Unidirectional | TRANSPORT: MLLP (port 6661)
TRIGGER: Real-time on result finalization
DATA MAPPING:
| Source Field | Target Field | Transform | Required | Code Map |
|-----------------|------------------|------------------|----------|----------------|
| result.test_code| OBX-3 | Local → LOINC | Yes | Lab→LOINC table|
| result.value | OBX-5 | Unit conversion | Yes | — |
| result.ref_range| OBX-7 | Format: "L-H" | Yes | — |
| result.abnormal | OBX-8 | Map: A→A, H→H | Yes | Flag codes |
ERROR HANDLING:
Validation: Message structure, required fields, value range
Retry: 3 attempts, 5/15/60 min intervals
Alerting: >5 failures in 15 min → PagerDuty
TESTING:
Unit: 12 result types × 5 scenarios each (normal, abnormal, critical, empty, malformed)
Integration: 50 sample results end-to-end with Epic validation
Volume: 200 messages/min for 30 minutes
1---2name: ehr-integration-architect3description: Designs EHR integration architectures using HL7 FHIR, C-CDA, and X12 standards. Outputs interface specifications with data mapping, error handling, and interoperability compliance for health information exchange.4allowed-tools: Read, Write, WebSearch5effort: high6metadata:7 source: https://skillmd.com/skills/uitbreidenos/ehr-integration-architect8---910# EHR Integration Architect1112## When to activate13When integrating a new system with an EHR (Epic, Cerner, Athenahealth), building health information exchange interfaces, implementing FHIR APIs, or when connecting labs, pharmacies, or imaging systems. Use for any clinical data integration project.1415## When NOT to use16Skip for simple CSV imports, one-time data migrations (not ongoing interfaces), or when the integration already exists and is functioning within SLA.1718## Instructions19201. **Define the interface:**21 - Source system and target system22 - Direction: Unidirectional vs. bidirectional23 - Transport: HL7 v2.x, FHIR R4, X12, C-CDA, REST API24 - Trigger: Real-time, batch, or on-demand25262. **Data mapping:**27 - Source fields → target fields with transformation rules28 - Code system mapping (SNOMED → ICD-10, local codes → LOINC)29 - Required vs. optional fields30 - Default values for missing data31323. **FHIR resource mapping (if applicable):**33 - Patient, Encounter, Observation, MedicationRequest, DiagnosticReport34 - USCDI data class compliance35 - SMART on FHIR scopes for authorization36374. **Error handling:**38 - Message validation (ACK/NAK for HL7, HTTP status for FHIR)39 - Retry logic (exponential backoff, max retries)40 - Error queue and manual review workflow41 - Alerting for interface failures42435. **Testing strategy:**44 - Unit tests per message type45 - Integration tests with sample data46 - Volume/stress testing47 - Go-live validation checklist4849## Output Format5051```52EHR INTERFACE: [Source] → [Target]53STANDARD: [HL7 v2.x / FHIR R4 / X12 / C-CDA]54DIRECTION: [Uni/Bidirectional] | TRANSPORT: [MLLP/HTTPS/SFTP]55TRIGGER: [Real-time/Batch/On-demand]5657DATA MAPPING:58| Source Field | Target Field | Transform | Required | Code Map |59|-------------|-------------|-----------|----------|----------|6061FHIR RESOURCES (if applicable):62 [Resource type]: [Profile URL]63 Scopes: [SMART scopes]6465ERROR HANDLING:66 Validation: [Rules]67 Retry: [Strategy]68 Alerting: [Threshold + channel]6970TESTING:71 Unit: [X] message types × [Y] scenarios72 Integration: [End-to-end scenarios]73 Volume: [X] messages/min for [Y] minutes74```7576## Example7778```79EHR INTERFACE: Lab System → Epic EHR80STANDARD: HL7 v2.5.1 (ORU^R01)81DIRECTION: Unidirectional | TRANSPORT: MLLP (port 6661)82TRIGGER: Real-time on result finalization8384DATA MAPPING:85| Source Field | Target Field | Transform | Required | Code Map |86|-----------------|------------------|------------------|----------|----------------|87| result.test_code| OBX-3 | Local → LOINC | Yes | Lab→LOINC table|88| result.value | OBX-5 | Unit conversion | Yes | — |89| result.ref_range| OBX-7 | Format: "L-H" | Yes | — |90| result.abnormal | OBX-8 | Map: A→A, H→H | Yes | Flag codes |9192ERROR HANDLING:93 Validation: Message structure, required fields, value range94 Retry: 3 attempts, 5/15/60 min intervals95 Alerting: >5 failures in 15 min → PagerDuty9697TESTING:98 Unit: 12 result types × 5 scenarios each (normal, abnormal, critical, empty, malformed)99 Integration: 50 sample results end-to-end with Epic validation100 Volume: 200 messages/min for 30 minutes101```