PerfuseGuides
Healthcare integration, explained in plain language
Each guide starts from nothing: what the thing is, why it exists, who it affects, and how to do it step by step, with pictures. No background in HL7 needed.
DICOM routing and de-identification: moving medical images safely
The DICOM services, imaging routing and de-identification explained, and how Perfuse routes and de-identifies studies in one pipeline.
Claims attachments and CMS-0053: signed C-CDAs in the X12 275
The X12 275, C-CDA attachments and HL7 DSDR signatures explained, and how Perfuse builds and verifies signed attachments.
Prior authorization metrics under CMS-0057-F: what payers must publish, and how
What the CMS-0057-F prior authorization metrics page must show, and how Perfuse produces it from a utilization management export.
Open-source healthcare integration engines compared: Mirth 4.5.2, OIE, BridgeLink and Perfuse
Mirth Connect 4.5.2, Open Integration Engine, BridgeLink and Perfuse side by side: origin, runtime, licence, channels and features.
Shadow mode: how to change a live interface without guessing
Run a new version of a channel on real traffic with nothing delivered, and see field by field what changes.
Feed contracts: catch upstream changes before they break an interface
Profile what a feed really contains, turn it into a contract, and be told the day a sender changes something.
eCR and ELR explained: automatic public health reporting from clinical data
How electronic case reporting and electronic lab reporting work, from trigger codes to Reportability Responses, and how Perfuse automates both.
TEFCA and UDAP explained: national health data exchange, in plain terms
How TEFCA, QHINs, Facilitated FHIR and UDAP work together for national exchange, and how Perfuse takes part.
SMART on FHIR explained: how apps get secure access to health data
SMART App Launch, Backend Services, scopes and PKCE explained, and Perfuse's built-in SMART authorization server.
X12 278 and FHIR PAS: two ways to request prior authorization, and how to bridge them
The X12 278 and Da Vinci PAS compared, why payers need both, and how Perfuse converts between them.
CMS-0057-F explained: the Interoperability and Prior Authorization rule, in plain terms
Who CMS-0057-F applies to, what it requires from 2026 and 2027, the FHIR standards behind it, and how Perfuse delivers the four payer APIs.
Da Vinci CRD, DTR and PAS explained: electronic prior authorization from order to decision
How the Da Vinci CRD, DTR and PAS guides work together for electronic prior authorization, and how Perfuse implements all three.
How to migrate Mirth Connect channels, step by step
Export, explain, translate, test and prove: a step-by-step migration from Mirth Connect, OIE or BridgeLink to Perfuse.
HL7 v2 to FHIR: a practical guide to converting real feeds
What HL7 v2 messages map to in FHIR, the details that make or break a conversion, and how Perfuse converts v2 to FHIR and US Core.
Mirth Connect 4.6 licence change: your options, and the fastest way forward
Mirth Connect now needs a paid licence from version 4.6. Your options, and how Perfuse, a free Apache-2.0 engine, runs your existing Mirth channels from a single download.