Skill

domain-healthcare:ehr-integration

Guides EHR integrations with Epic, Cerner/Oracle Health, Allscripts via FHIR R4, HL7v2 messaging, interface engines like Mirth/Rhapsody, CCD/C-CDA exchange, and vendor sandbox testing.

api-development

backend

npx claudepluginhub rnavarych/alpha-engineer --plugin domain-healthcare

Popularity

Parent stars

Parent forks

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/domain-healthcare:ehr-integration

User invocable

Model invocable

Inline context

Default effort

Tool Access

This skill is limited to the following tools:

ReadGrepGlobBash

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

- Integrating with Epic, Cerner, or Allscripts via FHIR R4 or proprietary APIs

Supporting Files

references/epic-cerner-allscripts.mdreferences/hl7v2-messaging.mdreferences/interface-engines-document-exchange.md

SKILL.md

28 lines · ~498 tokens

Similar Skills

domain-healthcare:hl7-fhir

Guides HL7 FHIR R4 interoperability: resources CRUD/search, HAPI/Microsoft servers, SMART on FHIR auth, CDS Hooks, bulk export, US Core profiles.

3 files4 tools

domain-healthcare

fhir-software

Provides FHIR development guidance including package management, resource modeling, server implementation, and terminology handling for R4, R4B, R5.

fhir-developer-skills

abridge-reference-architecture

2.2k

Provides reference architecture for Abridge clinical AI integration with EHRs (Epic/Athena) via FHIR R4 APIs. Includes HIPAA-compliant data flows, project structure for multi-site health systems.

3 tools

abridge-pack

Stats

LanguageShell

Parent stars13

Parent forks1

MaintenanceGood

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

EHR Integration

When to use

Integrating with Epic, Cerner, or Allscripts via FHIR R4 or proprietary APIs

Processing HL7v2 ADT, ORM, ORU, or other message types from an EHR feed

Selecting or configuring an interface engine (Mirth, Rhapsody)

Implementing CCD or C-CDA document generation, parsing, or reconciliation

Setting up or debugging SMART on FHIR application registration

Testing integrations against vendor sandboxes

Core principles

FHIR R4 first, HL7v2 as legacy — all new integrations use FHIR; HL7v2 is maintenance mode for existing feeds

Interface engine as single point of control — route all EHR traffic through one engine; direct point-to-point integrations become unmanageable fast

ACK or it didn't happen — every HL7v2 message needs acknowledgment; assume delivery failure without it

Dead letter queue from day one — messages that fail processing will happen; design the failure path before the happy path

Test against real sandboxes, not mocks — vendor-specific quirks (Epic's ADT extensions, Cerner's FHIR pagination) only show up against actual endpoints

Reference Files

references/epic-cerner-allscripts.md — Epic FHIR R4, App Orchard, MyChart, Interconnect; Cerner Millennium, Code Console, CDS Hooks; Allscripts Open API and Unity API

references/hl7v2-messaging.md — ADT/ORM/ORU/MDM/SIU/DFT/RDE message types, segment structure, ACK pattern, field mapping best practices, dead letter queue design

references/interface-engines-document-exchange.md — Mirth Connect channel architecture, Rhapsody routing, interface engine best practices, CCD/C-CDA exchange, Direct messaging, integration testing tools

EHR Integration

When to use

Integrating with Epic, Cerner, or Allscripts via FHIR R4 or proprietary APIs
Processing HL7v2 ADT, ORM, ORU, or other message types from an EHR feed
Selecting or configuring an interface engine (Mirth, Rhapsody)
Implementing CCD or C-CDA document generation, parsing, or reconciliation
Setting up or debugging SMART on FHIR application registration
Testing integrations against vendor sandboxes

Core principles

FHIR R4 first, HL7v2 as legacy — all new integrations use FHIR; HL7v2 is maintenance mode for existing feeds
Interface engine as single point of control — route all EHR traffic through one engine; direct point-to-point integrations become unmanageable fast
ACK or it didn't happen — every HL7v2 message needs acknowledgment; assume delivery failure without it
Dead letter queue from day one — messages that fail processing will happen; design the failure path before the happy path
Test against real sandboxes, not mocks — vendor-specific quirks (Epic's ADT extensions, Cerner's FHIR pagination) only show up against actual endpoints

Reference Files

references/epic-cerner-allscripts.md — Epic FHIR R4, App Orchard, MyChart, Interconnect; Cerner Millennium, Code Console, CDS Hooks; Allscripts Open API and Unity API
references/hl7v2-messaging.md — ADT/ORM/ORU/MDM/SIU/DFT/RDE message types, segment structure, ACK pattern, field mapping best practices, dead letter queue design
references/interface-engines-document-exchange.md — Mirth Connect channel architecture, Rhapsody routing, interface engine best practices, CCD/C-CDA exchange, Direct messaging, integration testing tools

domain-healthcare:ehr-integration

Popularity

Invocation

Tool Access

Context Preview

Supporting Files

SKILL.md

Similar Skills

Help us improve

Help us improve

Find plugins for your project

domain-healthcare:ehr-integration

Popularity

Invocation

Tool Access

Context Preview

Supporting Files

SKILL.md

EHR Integration

When to use

Core principles

Reference Files

Similar Skills

Help us improve

EHR Integration

When to use

Core principles

Reference Files