Mirth FHIR Server
Deploy a production FHIR R4 server on Mirth Connect — HL7-to-FHIR translation, SMART on FHIR authorization, bulk export, and HIPAA-compliant cloud hosting.
Mirth FHIR Server Capabilities
From FHIR endpoint configuration to HL7 translation pipelines and HIPAA-compliant hosting — everything you need to run FHIR on Mirth Connect.
FHIR R4 Server Setup on Mirth Connect
Install and configure Mirth Connect as a production FHIR R4 server — HTTP Listener channels, FHIR-compliant REST endpoints, CapabilityStatement, and resource routing.
- ✓Mirth Connect HTTP Listener configuration for FHIR REST endpoints
- ✓FHIR R4 CapabilityStatement generation and hosting
- ✓Resource CRUD endpoint routing (GET, POST, PUT, DELETE)
- ✓FHIR search parameter implementation ($search, _include, _revinclude)
- ✓FHIR $validate operation for resource validation
- ✓FHIR $everything and $summary operation support
HL7 to FHIR Translation Pipeline
Mirth Connect channels that receive HL7 v2 messages from legacy systems and serve them as FHIR R4 resources in real time — bridging old and new without rip-and-replace.
- ✓Inbound MLLP/TCP HL7 v2 receiver channel configuration
- ✓JavaScript / Groovy transformer scripts for HL7 → FHIR mapping
- ✓Patient, Encounter, Observation, Condition, MedicationRequest resource generation
- ✓FHIR resource persistence to MySQL, PostgreSQL, or MongoDB
- ✓Real-time FHIR API serving from translated HL7 data
- ✓Bidirectional: FHIR writes back to HL7 for downstream legacy systems
SMART on FHIR Auth for Mirth Server
Implement SMART on FHIR authorization on top of your Mirth Connect FHIR server — OAuth 2.0, authorization server integration, token validation, and scope enforcement.
- ✓OAuth 2.0 authorization server integration (Keycloak, Okta, Azure AD)
- ✓Bearer token validation on all Mirth FHIR endpoints
- ✓SMART scope enforcement (patient/, user/, system/ contexts)
- ✓SMART launch context injection (patient, encounter, practitioner)
- ✓Refresh token handling and token revocation support
- ✓FHIR Capability Statement advertising SMART security extension
FHIR Bulk Data Export via Mirth
FHIR Bulk Data Access implementation on Mirth Connect — asynchronous Group/$export and Patient/$export endpoints with NDJSON output for analytics pipelines.
- ✓Asynchronous FHIR bulk export job management in Mirth
- ✓Group-level and patient-level export endpoint implementation
- ✓NDJSON file generation with resource type filtering
- ✓Bulk export status polling ($status) and file download links
- ✓Backend service (system-level SMART) authorization for bulk access
- ✓Output delivery to S3, Azure Blob, or SFTP destinations
HIPAA-Compliant Mirth FHIR Hosting
HIPAA-compliant cloud hosting for your Mirth Connect FHIR server — AWS, Azure, or GCP with TLS termination, WAF, audit logging, automated backups, and HA configuration.
- ✓HIPAA-compliant Mirth FHIR server hosting on AWS, Azure, or GCP
- ✓TLS 1.3 termination and Web Application Firewall (WAF) configuration
- ✓Multi-AZ high availability and automated failover
- ✓FHIR audit logging to SIEM (Splunk, Datadog, CloudWatch)
- ✓Automated encrypted backups with point-in-time recovery
- ✓Infrastructure-as-code (Terraform) for reproducible environments
Mirth FHIR Server Monitoring & Support
24/7 monitoring of your Mirth Connect FHIR server — channel health, FHIR endpoint response times, error rate alerting, and managed support SLAs.
- ✓24/7 automated monitoring of all Mirth FHIR channels and endpoints
- ✓FHIR API response time and error rate dashboards
- ✓Real-time alerting via PagerDuty, Slack, or email
- ✓Monthly FHIR server health reports and capacity planning
- ✓Emergency response within 2 hours for P1 FHIR server outages
- ✓Mirth Connect version upgrades and security patch management
Frequently Asked Questions
Is Mirth Connect a good choice for a FHIR server?
Mirth Connect excels as a FHIR translation and routing layer — ideal for organizations that already use it for HL7 v2 interfaces and need to expose FHIR APIs without replacing existing infrastructure. For purely FHIR-native use cases, we also work with HAPI FHIR and can advise on the right architecture.
Can Mirth Connect handle high FHIR API throughput?
Yes, with proper JVM tuning, connection pooling, and clustering. Mirth Connect can be scaled horizontally for high-throughput FHIR workloads. We configure multi-server Mirth clusters with load balancing for production environments requiring high availability.
What database does the Mirth FHIR server use to store resources?
We configure Mirth to persist FHIR resources to PostgreSQL, MySQL, or SQL Server — depending on your existing infrastructure. We also support MongoDB for document-oriented FHIR resource storage.
Can you migrate our existing HAPI FHIR server to Mirth Connect?
We can help you evaluate whether migration makes sense. In many cases, the better approach is to keep HAPI FHIR for resource persistence and use Mirth Connect in front of it for HL7 translation and routing — giving you the best of both.
Related Services & Reading
Ready to deploy your Mirth FHIR server?
Free architecture review — our Mirth Connect experts will design your FHIR server deployment and integration pipeline.