Skill

domain-healthcare:ehr-integration

EHR system integration covering Epic, Cerner/Oracle Health, and Allscripts platforms, HL7v2 messaging, interface engines, CCD/C-CDA document exchange, and integration testing with vendor sandboxes.

Install

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

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBash

Preview

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

Supporting Assets

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

SKILL.md

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

157.6k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

157.6k

Hook Development

10 files

Guides implementation of event-driven hooks in Claude Code plugins using prompt-based validation and bash commands for PreToolUse, Stop, and session events.

plugin-dev

83.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

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