Wound Care EMR Integration with Epic, Cerner, and Athena: What to Look For

Wound care software that doesn't talk to the host EMR becomes its own island. Here's what integration actually means with Epic, Cerner, and Athena — and how to evaluate it.

The three integration depths

1. PDF drop. The wound note is exported as a PDF and attached to the chart. Easiest to build, worst for downstream reporting. Codes don't flow, discrete fields don't populate, and quality reporting can't pull structured data.

2. HL7 ORU / MDM messaging. The classic interface. Structured results and documents move between systems over a point-to-point interface. Works reliably but requires interface engine work on both sides and is slow to change.

3. FHIR / SMART on FHIR. Modern, API-based, bidirectional. The wound app can read the problem list, allergies, and prior notes, then write back Observations, DocumentReferences, and Encounters. This is what enables a single record across settings.

What to ask each vendor

• Which Epic release does the integration support (e.g., May 2023, Nov 2024)? Certifications lag.
• Is the app in the Epic App Orchard / Showroom, Cerner Code, or Athena Marketplace?
• Do wound measurements post as discrete Observations, or only in the note narrative?
• Do ICD-10 and CPT codes generated by the scribe drop into the encounter for billing, or require re-entry?
• Can the AI-powered EMR stand alone for mobile visits where Epic isn't reachable, then sync back?

Why bidirectional matters for wound care

Wound patients cross settings — clinic, inpatient, home health, SNF. A read-only integration means clinicians re-enter history at every stop. A bidirectional FHIR link means the wound record is the record, no matter who opens the chart.

Red flags

• 'Integration coming Q3.' Assume Q3 of next year.
• Screenshots as the only proof. Ask for a live integration walkthrough on the host EMR you actually use.
• No mention of who owns the interface fees.