Seamless EMR
Integration
ReasonTele connects with your existing clinical systems through HL7v2, FHIR R4, native connectors, and secure fax — so consult notes flow directly into the patient chart.
Integration Architecture
A single integration layer connects ReasonTele to every EMR system in your organization.
Supported EMR Systems
Pre-built connectors for the most widely deployed EMR platforms, plus an open API for everything else.
Epic
Deep integration via Epic App Orchard and FHIR R4. Consult orders flow in, notes flow back. Support for MyChart patient notifications.
- App Orchard certified application
- FHIR R4 Patient, Encounter, and DocumentReference resources
- CDS Hooks for consult decision support
- MyChart patient-facing consult status updates
- Epic In Basket notifications to ordering provider
Oracle Health (Cerner)
HL7v2 ADT feed ingestion and CDS Hooks integration. Millennium interface engine compatible.
- Millennium interface engine bidirectional messaging
- HL7v2 ADT, ORM, and ORU message support
- CDS Hooks for real-time consult triggers
- PowerChart embedded view available
- Cerner Open platform API compatibility
MEDITECH
HL7v2 bidirectional interface. Support for MEDITECH Expanse and 6.x platforms.
- MEDITECH Expanse and 6.x platform support
- HL7v2 ADT and results messaging
- NPR and MAGIC report integration
- Bidirectional order and result workflows
- Custom report formatting per facility
Allscripts
HL7v2 and FHIR integration. TouchWorks and Professional EHR compatible.
- TouchWorks EHR integration
- Professional EHR compatibility
- HL7v2 ADT and clinical document exchange
- FHIR R4 API support for modern deployments
- Unity API connectivity for enterprise clients
ReasonEMR
Native integration — consult requests originate from the patient chart, notes flow back automatically. Zero configuration required.
- One-click consult request from the patient chart
- Auto-populated demographics, vitals, labs, and imaging
- Notes return to the encounter record instantly
- Shared authentication and role model
- Zero configuration — works out of the box
Custom / Other
Open API and HL7v2 interface engine support. Our integration team works with your IT staff to configure any EMR.
- RESTful API with comprehensive documentation
- HL7v2 interface engine adapter library
- Custom message mapping and transformation
- Dedicated integration engineer assigned to your project
- Sandbox environment for development and testing
Integration Methods
Four pathways for connecting ReasonTele to your clinical infrastructure.
HL7v2 ADT Feeds
Real-time patient demographics and admission data
HL7v2 ADT feeds provide automatic patient context when a consult is initiated. When a patient is admitted, transferred, or discharged, ReasonTele receives the ADT message and maintains an up-to-date patient roster for each facility.
Technical Specifications
- Supported message types: ADT^A01 (Admit), A02 (Transfer), A03 (Discharge), A04 (Register), A08 (Update)
- Transport: MLLP over TLS (secure TCP), or SFTP batch processing
- Character encoding: UTF-8 with HL7 escape sequences
- Acknowledgment: ACK/NAK with configurable retry logic
- Processing: Real-time (<1 second) or batch (configurable interval)
FHIR R4 APIs
RESTful APIs following HL7 FHIR R4 specification
Our FHIR R4 implementation supports modern interoperability standards for bidirectional clinical data exchange. Authentication follows the SMART on FHIR specification.
Technical Specifications
- Resources: Patient, Encounter, DiagnosticReport, DocumentReference, ServiceRequest, Practitioner
- Authentication: OAuth 2.0 / SMART on FHIR with scopes
- Supported interactions: read, search, create, update
- Subscriptions: webhook notifications for resource changes
- Conformance: US Core Implementation Guide profiles
Direct API
ReasonTele REST API for custom integrations
The ReasonTele REST API provides full programmatic access to the platform for custom integrations, white-label solutions, or automated workflows.
Technical Specifications
- Authentication: JWT bearer tokens with RSA-256 signing
- Rate limiting: 1,000 requests/minute per API key (configurable)
- Webhook events: consult.created, consult.accepted, consult.completed, note.delivered
- SDKs: TypeScript/JavaScript, Python, C#/.NET, Java
- API versioning: URL-based (v1, v2) with 12-month deprecation policy
Secure Fax
Automated fax delivery for facilities without electronic interfaces
For facilities that rely on paper-based workflows, ReasonTele provides fully automated secure fax delivery with custom formatting and delivery confirmation.
Technical Specifications
- HIPAA-compliant fax provider with BAA
- Custom note formatting per facility (header, logo, layout)
- Delivery confirmation with timestamp and page count
- Automatic retry on busy/no-answer (3 attempts over 15 minutes)
- Fax audit trail integrated into consult record
Implementation Timeline
Most integrations go live within four weeks.
Discovery & Configuration
- Kick-off call with your IT and clinical stakeholders
- EMR version and interface engine inventory
- Message mapping and data flow design
- VPN or secure connectivity setup
- Sandbox environment provisioning
Testing & Validation
- End-to-end message testing with sample data
- Patient matching and deduplication validation
- Note delivery format review with clinical team
- Error handling and retry logic verification
- Security and access control testing
Go-Live & Monitoring
- Production cutover with parallel monitoring
- Real-time dashboard setup for interface health
- On-call integration support for first 72 hours
- Post-go-live review and optimization
- Handoff to ongoing support team
Integration FAQ
What data formats do you support for consult note delivery?
Consult notes can be delivered as HL7v2 ORU messages (embedded PDF or plain text), FHIR DocumentReference resources (with attached PDF), direct API webhook payloads (JSON with embedded document), secure fax (formatted PDF), or downloadable PDF via the ReasonTele portal.
How is PHI secured during data transmission?
All data in transit is encrypted with TLS 1.3. HL7v2 messages are transmitted over MLLP/TLS (secure TCP) or SFTP. FHIR and REST API calls use HTTPS exclusively. VPN tunnels (IPSec or WireGuard) are available for facilities that require network-layer encryption.
What happens if the interface goes down?
ReasonTele includes automatic retry logic with exponential backoff for all interface types. Failed messages are queued in a persistent dead-letter queue and retried automatically when connectivity is restored. Secure fax is available as an immediate fallback.
Do you support bidirectional integration?
Yes. Inbound integrations bring patient demographics (ADT feeds), orders, and clinical context into ReasonTele. Outbound integrations deliver consult notes, status updates, and disposition recommendations back to your EMR.
How long does a typical integration take?
Most integrations are completed within 4 weeks. Simple configurations can be live in as little as 2 weeks. Complex integrations involving FHIR, CDS Hooks, or custom API workflows may take 6-8 weeks. ReasonEMR native integration requires zero configuration.
Let's Connect Your Systems
Our integration team will assess your current EMR environment and design a connectivity plan — typically completed in under four weeks.