FHIR Sprint · From $13,500

FHIR R4 Adapter Sprint — Add FHIR to Your Existing Mirth Deployment

Add FHIR R4 capability to an existing Mirth Connect deployment in 6 weeks. REST connector setup, US Core profile mapping, OAuth 2.0 / SMART on FHIR security, ONC compliance checks. Fixed-price sprint starting at $13,500. Most teams have HL7 v2 channels working in production and want to add a FHIR layer for new use cases — payer-provider data exchange, mobile apps, ONC certification, modern API surfaces.

Free Discovery Call See All Pricing

Talk About: FHIR R4 Adapter Sprint

Tell us about your environment in 60 seconds. A solutions architect will reach out within 24 hours to confirm scope.

Why Teams Do This Sprint

Modern API surface

FHIR R4 is the standard for new healthcare APIs. Mobile apps, payer integrations, third-party developer ecosystems all expect FHIR.

ONC compliance

ONC's 21st Century Cures Act mandates FHIR R4 for certified health IT. Adding a FHIR adapter is the path to (g)(10) certification.

Bidirectional

Read AND write — receive FHIR resources from external systems, expose your data as FHIR, transform between HL7 v2 and FHIR R4.

US Core profile compliance

Out of the box, raw FHIR is too loose. US Core profiles are what payers, ONC, and partner platforms actually expect.

OAuth 2.0 / SMART on FHIR

FHIR APIs need real auth, not just basic credentials. We wire up SMART on FHIR with proper scopes and refresh tokens.

What We Deliver

Concrete deliverables. Code in your Git repo at the end.

Mirth Connect FHIR REST connector configured (server + client modes)

HL7 v2 → FHIR R4 transformer (ADT → Patient/Encounter, ORU → Observation, etc.)

FHIR R4 → HL7 v2 transformer for downstream legacy systems

US Core profile validation on input/output

OAuth 2.0 / SMART on FHIR authorization layer

Capability statement (`metadata` endpoint) advertising your FHIR API

FHIR resource search parameter handling (with paging + sorting)

Z-segment handling and custom extension mapping

Monitoring of FHIR endpoint latency, error rates, and OAuth token refresh

Documentation pack for partner developers consuming your FHIR API

Common Problems We Fix

If any of these match your situation, the sprint resolves them.

Mirth's REST connector returns 500 on FHIR POST

Root cause: Missing Content-Type=application/fhir+json or character encoding mismatch. Solution: explicit content negotiation and UTF-8 enforcement.

FHIR resources fail US Core validation

Root cause: Missing required extensions (us-core-race, us-core-ethnicity) or improperly bound code systems. Solution: pre-validate in transformer using the official US Core IGs.

OAuth 2.0 token refresh loop fails silently

Root cause: Token expiry not detected; expired token reused. Solution: explicit token-lifetime tracking with refresh window 5 minutes before expiry.

FHIR Bundle returns wrong total count or pagination

Root cause: Search parameter handling missing _count or _total parameter. Solution: implement proper Bundle.link chain (self/next/prev) and total-count semantics.

Productized Pricing

Pricing — All Numbers Public

Three productized sprint sizes, plus an optional managed-support continuation.

🎁

Free Assessment

30-minute call with a FHIR-specialist engineer. We review your existing Mirth deployment and target FHIR use cases — produce a written effort estimate.

Claim Free Assessment

FHIR R4 Adapter Sprint

From $13,500

6 weeks · single environment

Standard sprint. REST connector, HL7 v2 ↔ FHIR R4 transformers, US Core validation, OAuth 2.0 layer, monitoring, documentation.

Multi-Resource Enterprise Adapter

From $32,000

10 weeks · multiple resources

Adds CarePlan, MedicationRequest, DiagnosticReport, ServiceRequest, plus dev/staging/prod parity. Suited for ONC g10 submission.

Add Ongoing Support

From $6,800/mo

Silver Managed Support

After the sprint, continue with monthly Silver support — version-upgrade tracking, ONC re-certification cycles, OAuth token-rotation operations.

Continue with managed Silver Mirth Connect support after the sprint — from $6,800/month.

FHIR R4 Adapter Sprint — FAQ

Do we need to replace our HL7 v2 channels?

No. The FHIR R4 Adapter Sprint adds a FHIR layer alongside your existing HL7 v2 channels — it doesn't replace them. Most production deployments end up running both: HL7 v2 for legacy EHR/lab/radiology integrations and FHIR R4 for modern API surfaces. Mirth handles both natively in the same engine.

What's the difference between this and the eCW $export Sprint?

The FHIR R4 Adapter Sprint adds FHIR capability to your Mirth deployment so you can serve, consume, and transform FHIR resources. The eCW $export Sprint specifically implements bulk-data extraction from eClinicalWorks, with SMART Backend Auth. They're complementary — many teams do the FHIR Adapter Sprint first, then layer eCW $export on top.

Do you handle SMART on FHIR or just OAuth 2.0?

Both. OAuth 2.0 is the underlying authorization framework; SMART on FHIR is a healthcare-specific profile of OAuth that defines launch contexts, scopes (patient/Patient.read, system/*.read, etc.), and JWT bearer assertions. We implement the SMART profile by default since most healthcare partners expect it; raw OAuth 2.0 is also available where needed.

What about FHIR R5? Should we wait?

No. R5 is published but adoption is minimal — payers, ONC, and the major EHRs (Epic, Cerner, eCW) all standardize on R4. R5 will matter eventually but the current ecosystem is firmly R4. We can add R5 capability as a future sprint extension when it becomes relevant.