Wound Care Interoperability: Connecting Your Systems

Wound Care Interoperability: Why Data Exchange Matters

Wound care does not happen in isolation. A single patient's care involves their primary care physician, the wound care clinician, the home health agency, the pharmacy, the lab, the DME supplier, and the payer. Every one of those parties needs information from the others. When that information flows electronically, care is coordinated. When it does not, someone is faxing, someone is re-entering data, and someone is making a clinical decision without the full picture.

Wound care interoperability is the ability of your systems to exchange clinical and operational data with the systems used by everyone else involved in the patient's care. This guide covers the standards, challenges, and practical approaches to making wound care data exchange work.

The Standards: HL7 and FHIR for Wound Care

Two data exchange standards dominate healthcare interoperability. Both matter for wound care, and they serve different purposes.

HL7 Version 2 (HL7v2)

HL7v2 is the workhorse of healthcare data exchange. It has been in use since the 1990s, and the vast majority of existing EHR interfaces use it. HL7v2 messages handle:

ADT (Admit/Discharge/Transfer) messages. When a patient is admitted to a facility, discharged, or transferred, an ADT message notifies connected systems. For wound care, this triggers care coordination events.
ORM/ORU messages. Order and result messages for lab work. When you order a wound culture and the lab returns sensitivity results, these messages carry that data.
SIU messages. Scheduling information. Appointment creation, modification, and cancellation notifications between scheduling systems.

HL7v2 works. It is also text-based, loosely structured, and requires significant custom mapping between any two systems. Every HL7v2 interface is essentially a bespoke integration project.

FHIR (Fast Healthcare Interoperability Resources)

FHIR is the modern standard, and it changes how wound care data can be exchanged. Instead of flat text messages, FHIR uses structured resources -- discrete, well-defined data objects with consistent formats.

FHIR resources relevant to wound care include:

Condition. Wound diagnosis, etiology, and clinical status.
Observation. Wound measurements, tissue assessments, and clinical findings.
Media. Wound photographs with associated metadata.
Procedure. Debridements, dressing applications, and treatments performed.
ServiceRequest. Referrals to wound care, orders for wound-related lab work or DME.
DiagnosticReport. Lab results including wound cultures and pathology.

The practical advantage of FHIR for wound care is that it can carry wound photographs, structured wound assessments, and treatment histories in a standardized format. HL7v2 was never designed to handle wound images or structured wound measurement data.

For EHR considerations when evaluating interoperability capabilities, see Wound Care EHR Selection Guide.

Common Wound Care Integration Challenges

Theory and practice diverge sharply in healthcare interoperability. Here is what wound care practices actually encounter.

Referral data exchange remains largely manual. When a physician refers a patient to wound care, the referral often arrives as a fax or a phone call. The wound care practice re-enters demographic data, insurance information, and the reason for referral. Even when both sides use EHRs with referral management capabilities, the systems frequently do not talk to each other.

Wound-specific data has no standard vocabulary. FHIR defines general observation and condition resources, but wound care lacks a universally adopted coding system for wound bed composition, periwound characteristics, and wound location specificity. Two systems can exchange "wound data" and still not agree on what "wound bed: 60% granulation, 30% slough, 10% eschar" means structurally.

Lab result integration varies by lab vendor. National lab companies (Quest, LabCorp) offer HL7v2 interfaces, but connecting them requires an interface engine and configuration work. Smaller regional labs may only offer results via their own portal. Wound cultures with sensitivity panels are critical for treatment decisions, and delayed results mean delayed treatment changes.

Photo exchange is the biggest gap. Wound photographs are the most important clinical data in wound care, and they are the hardest to exchange electronically. Most EHR-to-EHR interfaces do not support image transfer. FHIR Media resources can carry images, but adoption is limited. In practice, wound photos stay trapped in the system that captured them.

Practical Approaches to Wound Care Data Exchange

Full interoperability is a long-term goal. These approaches address data exchange needs today.

Direct Secure Messaging for referrals. Direct (the protocol, not the adjective) is an encrypted email-like system designed for healthcare data exchange. Many EHRs support sending and receiving Direct messages. Using Direct for wound care referrals eliminates fax and delivers structured data including patient demographics, insurance, and clinical summaries.

Interface engines for lab and ADT feeds. If your practice processes enough volume to justify it, an interface engine (Mirth Connect, Rhapsody, or similar) can receive HL7v2 feeds from labs and facilities, transform the data, and load it into your wound care system. This is a capital expense and an ongoing maintenance commitment, but it eliminates manual data entry for lab results and patient census data.

API-based integrations for newer systems. Modern wound care platforms and EHRs increasingly offer REST APIs and FHIR endpoints. When both systems support FHIR, integration becomes configuration rather than custom development. Ask vendors specifically about their FHIR R4 capabilities and what resources they expose.

PDF-based clinical summaries as a fallback. When electronic data exchange is not feasible, generating and sharing structured PDF summaries (wound photos, measurements, treatment history, and care plan) is better than faxing handwritten notes. Standardize your summary format so receiving providers get consistent, readable wound care reports.

For coordination with home health agencies specifically, see Wound Care Home Health Coordination.

What to Ask Your Vendors

When evaluating wound care technology for interoperability, these questions separate marketing claims from actual capability:

What HL7v2 message types do you support sending and receiving? Specifically ADT, ORM, ORU, and SIU.
Do you have a FHIR R4 API? If yes, which resources? Can you exchange wound-specific data (observations, media) via FHIR, or only demographics?
How do you handle inbound referral data? Can you receive electronic referrals, or does your intake process start with manual entry?
Can wound photographs be exported or shared electronically? In what format? With what metadata?
What interface engines have you integrated with? Ask for reference customers using the same labs and facilities you work with.

Key Takeaways

HL7v2 handles legacy data exchange; FHIR is the path forward for wound-specific data including photos, measurements, and structured assessments.
Wound photography exchange is the biggest interoperability gap in wound care today, with most photos trapped in the system that captured them.
Referral data exchange remains largely manual despite EHR capabilities on both sides, making electronic referral a high-impact improvement target.
Ask vendors specific interoperability questions about message types, FHIR resources, and reference implementations before purchasing.

Interoperability in wound care will improve as FHIR adoption grows and wound-specific data standards mature. In the meantime, prioritize the integrations that eliminate the most manual data entry and the most clinical information gaps in your daily operations.