EMR Integration Guide

Overview

MediVoice supports bi-directional EMR integration. This means:

• Pull (EMR → MediVoice): Your EMR queries MediVoice to retrieve clinical notes, diagnoses (with ICD-10 codes), investigation orders, and medication orders.
• Push (MediVoice → EMR): MediVoice sends finalized reports and structured data directly into your EMR's patient charts.

Connection Methods

MediVoice supports four integration methods. Choose the one that matches your EMR's capabilities:

Method	Protocol	Best for	Effort
1. FHIR R4 Server	HL7 FHIR R4 REST API	Epic, Cerner, OpenMRS, any FHIR-compliant EMR	Low — your EMR just queries our API
2. FHIR R4 Client	HL7 FHIR R4 REST API	MediVoice reads from / writes to your EMR's FHIR endpoint	Low — we connect to your FHIR server
3. REST API Adapter	Custom REST/webhook	Proprietary EMRs with a REST API	Medium — build a small adapter
4. File Import/Export	PDF, JSON, CSV	EMRs with no API — manual or scheduled file exchange	Low — no real-time sync

Method 1: FHIR R4 Server (EMR reads from MediVoice)

MediVoice exposes a standards-compliant FHIR R4 REST API. Your EMR system (or a middleware) queries it to pull patient data.

Base URL

https://medivoice.cloud/fhir

Authentication

All requests (except /metadata) require a Bearer token:

Authorization: Bearer <your-integration-token>

The token is provisioned per-tenant. Contact your MediVoice administrator to generate one.

Available FHIR Resources

Resource	Endpoint	Search Parameters	What it returns
Patient	GET /fhir/Patient	identifier (MRN), name	Patient demographics from encounters
Encounter	GET /fhir/Encounter	patient	Clinical encounters (visit records)
Condition	GET /fhir/Condition	patient	Diagnoses with ICD-10/SNOMED codes
DocumentReference	GET /fhir/DocumentReference	patient	Finalized clinical reports (base64 JSON)
ServiceRequest	GET /fhir/ServiceRequest	patient	Investigation orders (labs, imaging)
MedicationRequest	GET /fhir/MedicationRequest	patient	Medication/management orders

Example: Retrieve a patient's diagnoses

curl -H "Authorization: Bearer YOUR_TOKEN" \
     "https://medivoice.cloud/fhir/Condition?patient=MRN-12345"

Response (FHIR R4 Bundle):

{
  "resourceType": "Bundle",
  "type": "searchset",
  "total": 2,
  "entry": [
    {
      "fullUrl": "https://medivoice.cloud/fhir/Condition/101",
      "resource": {
        "resourceType": "Condition",
        "id": "101",
        "clinicalStatus": {
          "coding": [{"system": "http://terminology.hl7.org/CodeSystem/condition-clinical", "code": "active"}]
        },
        "code": {
          "coding": [{"system": "http://hl7.org/fhir/sid/icd-10", "code": "E11.9", "display": "Type 2 Diabetes Mellitus"}],
          "text": "Type 2 Diabetes Mellitus"
        },
        "subject": {"reference": "Patient/MRN-12345"},
        "recordedDate": "2026-07-15T10:30:00+00:00"
      }
    }
  ]
}

Capability Statement

Check what MediVoice supports without authentication:

curl https://medivoice.cloud/fhir/metadata

Method 2: FHIR R4 Client (MediVoice reads from / writes to your EMR)

If your EMR exposes a FHIR R4 API (Epic, Cerner, OpenMRS), MediVoice can connect as a client to:

• Read: Import patient demographics, recent encounters, vitals, lab results
• Write: Push clinical reports as DocumentReference resources into the patient chart

Setup (Administrator)

1. Obtain your EMR's FHIR base URL (e.g., https://your-emr.com/fhir)
2. Register MediVoice as a SMART on FHIR app with your EMR vendor
3. Obtain OAuth 2.0 credentials (client ID + client secret)
4. Configure in MediVoice via API:

POST https://medivoice.cloud/api/ai/config
Content-Type: application/json
Authorization: Bearer <admin-session>

{
  "task": "emr",
  "provider_type": "fhir_r4",
  "base_url": "https://your-emr.com/fhir",
  "token": "YOUR_OAUTH_BEARER_TOKEN"
}

Test the connection

POST https://medivoice.cloud/api/emr/test

Method 3: REST API Adapter (Proprietary EMRs)

For EMRs with a custom REST API but no FHIR support, MediVoice provides an adapter framework:

1. Build a small adapter script on your EMR server that translates between MediVoice's FHIR resources and your EMR's native format
2. Point MediVoice's FHIR base URL to the adapter
3. The adapter translates: Patient ↔ your patient table, Condition ↔ your diagnoses, etc.

Contact support for the adapter specification.

Method 4: File Import/Export (No API)

For EMRs with no API at all, MediVoice can export reports as structured files:

• JSON: Full structured report (sections, diagnoses, orders) — for programmatic import
• PDF: Formatted clinical document — for manual upload or scanning
• CSV: Diagnosis + order lists — for spreadsheet import

Files can be delivered via:

• Manual download from the MediVoice app
• Scheduled email delivery
• SFTP upload to your EMR server

Connecting to Specific EMR Systems

Security

Patient Identity Matching

MediVoice uses a patient crosswalk table to link MediVoice patients to EMR patients:

Matching method	How it works
MRN (preferred)	Medical Record Number — exact match
Name + DOB	Fuzzy match if MRN unavailable
Manual	Physician selects the correct patient during the encounter

The crosswalk is stored per-tenant and remembered for future encounters.

Getting Started

To set up an EMR integration:

1. Identify your EMR's API capability — Does it support FHIR R4? (Ask your IT team or EMR vendor)
2. Contact MediVoice support — support@naghamyhealth.com — to provision an integration token
3. Choose a method from the table above
4. Configure the connection via the API or admin panel
5. Test with the /api/emr/test endpoint
6. Enable write-back (if pushing data to the EMR) — this is a deliberate admin action

← Back to MediVoice Privacy