Streamline Developer Workflows with eFax® for Medplum
Embed secure cloud faxing directly into your programmable healthcare application using Medplum’s native, first-party infrastructure.
- Native FHIR Workflows: Build bidirectional send and receive logic seamlessly.
- Automated Routing: Eliminate complex telecom setups with developer-friendly API operations.
Native FHIR Interoperability
The Developer Problem – Technical DebtLegacy Programmable Faxing |
The Medplum eFax® Solution – Developer VelocityFirst-Party eFax® Connect Architecture |
|---|---|
| The Complexity: Building custom fax integrations from scratch requires managing brittle third-party APIs, raw image conversions, and non-compliant transmission channels. | Native Integration: Leverage a pre-built, first-party integration engineered to sync seamlessly with your existing Medplum clinical workflows with zero infrastructure to manage. |
| The Interoperability Gap: Traditional fax payloads sit outside your core data model, forcing engineering teams to write complex parsing scripts to associate documents with patient charts. | FHIR Communication Storage: Inbound and outbound faxes are automatically mapped and stored as native FHIR Communication resources for instant platform interoperability. |
| The Maintenance Burden: DevOps teams waste hours monitoring webhook failures, debugging connection timeouts, and managing insecure credential keys. | Automated Verification: Test connectivity and verify your eFax® API configurations on demand to ensure production readiness with minimal code. |
API Configuration and Capabilities
Safeguard your enterprise connection by injecting your eFax® Application ID, API Key, and default User ID straight into encrypted project secrets.
Deploy programmable endpoints to route faxes at the global system level, specific clinic location level, or individual practitioner level.
Trigger secure outbound transmissions directly from your core application logic using standard FHIR data payloads.
FHIR Operations Endpoint Registry
POST /fhir/R4/Communication/$receive-efax
- Use Case: Clinic-wide shared fax routing
- Identity Mapping: Pulls directly from your project secret eFax User ID
POST /fhir/R4/Organization/id/$receive-efax
- Use Case: Department or physical location specific fax routing
- Identity Mapping: Pulls directly from the eFax identifier assigned to the organization
POST /fhir/R4/Practitioner/id/$receive-efax
- Use Case: Private or individual practitioner specific fax routing
- Identity Mapping: Pulls directly from the eFax identifier assigned to the practitioner
Resource Configuration Payload Template
To enable seamless document routing, assign your eFax® user parameters directly to your Practitioner or Organization resources using the structured schema layout.
JSON
{
“resourceType”: “Practitioner”,
“identifier”: [
{
“system”: “https://efax.com”,
“value”: “<EFAX_USER_ID>”
}
],
“telecom”: [
{
“system”: “fax”,
“value”: “+15551234567”
}
]
}
Transitioning your app to the native eFax Corporate® plan requires minimal coordination.
Activate your eFax Corporate® account. Request the Medplum engineering team to activate the first-party eFax® integration toggle inside your administration console.
Populate your secure project dashboard with your official eFaxAppId, eFaxApiKey, and eFaxUserId parameters.
Execute the native connection diagnostics to instantly validate your security handshake before pushing to live production environment routes.
