Mediedge
Integration

Meet the chart
where it already lives.

Ennox supports two practical integration paths designed for a straightforward turn-up: use available EHR FHIR interfaces, or begin quickly with secure intake of digitally generated PDF charts.

Discuss integration Compare pathways
FHIREHR dataStructured resources
EnnoxEvidence engineNormalize • interpret • support
PDFDigital chartsDocument intake
Two integration pathways

Start with the connection that fits.

The right approach depends on EHR capabilities, chart format, technical readiness, security requirements, and the workflow being evaluated.

01 / FHIRStandards-based

EHR integration through FHIR

Where supported by the EHR and authorized by the customer, Ennox can use available FHIR interfaces to receive structured clinical and encounter information for the coding workflow.

  • Use the EHR's supported FHIR version, profiles, and authorization model
  • Map relevant encounter, condition, observation, diagnostic, medication, procedure, and document resources
  • Normalize source data into the Ennox evidence model
  • Route reviewable results into an agreed downstream workflow

Exact resources and interactions are determined from the EHR's implementation guide and capability statement.

02 / PDFDocument-based

Digitally generated PDF charts

For organizations that are not ready for an API connection, Ennox can begin with digitally generated, text-readable PDF charts delivered through an agreed secure workflow.

  • Receive consistent digital chart exports without requiring immediate EHR API work
  • Extract and organize diagnoses, tests, medications, procedures, and decision-making evidence
  • Preserve source references so recommendations remain reviewable
  • Return coding results through the pilot's agreed review and export process

Scanned or image-only documents require separate qualification and testing; text-native digital PDFs are preferred.

Simple by design

A practical path from first chart to live workflow.

Integration should not become a larger project than the coding problem it solves. Ennox starts with the lightest viable connection, validates it with your team, and expands only as the workflow requires.

Fast-start pathDigital PDF

Start with the chart export you already have.

A consistent, text-readable PDF workflow can reduce initial interface work and create a direct path to pilot evaluation.

  • Confirm a representative chart format
  • Agree on secure delivery and result return
  • Validate extraction and evidence references
  • Begin a controlled coding pilot
Connected pathFHIR

Use the standards-based interfaces already available.

When the EHR exposes the required FHIR data, the connection can focus on authorization, resource mapping, and workflow routing.

  • Review the EHR capability statement
  • Confirm access, scopes, and required resources
  • Validate the data mapping with sample encounters
  • Activate the agreed operational workflow
Controlled turn-up

Four steps. Clear owners. No unnecessary lift.

01

Discover

Choose FHIR or digital PDF and confirm the people, data, security, and workflow in scope.

02

Validate

Use representative examples to verify intake, evidence extraction, and expected outputs.

03

Pilot

Run a controlled evaluation with qualified coding reviewers and agreed success measures.

04

Turn up

Finalize operating procedures, monitoring, support ownership, and the approved production workflow.

Turn-up is environment-specific. A digital PDF pilot can often require less initial interface work, while FHIR readiness depends on the EHR's enabled capabilities, authorization process, and available data. Scope and timing are confirmed during discovery.

Integration workflow

A clear path in. A reviewable result out.

01

Connect or receive

Use authorized FHIR access or an agreed secure digital-PDF intake process.

02

Normalize

Organize source information into a consistent evidence model for processing.

03

Interpret

Identify chart evidence and prepare supported coding recommendations.

04

Review and route

Present evidence for professional review and deliver results through the agreed workflow.

Implementation discovery

Integration is specific to your environment.

A pilot begins by documenting the available interfaces, source data, chart format, authentication, transport, review workflow, output destination, and security responsibilities.

01EHR and interface readinessVendor, FHIR version, implementation guide, enabled resources, and access process
02Chart and data scopeEncounter types, source documents, expected fields, and PDF characteristics
03Workflow and outputsReview queue, export format, API response, or other agreed destination
04Security and operationsAuthorization, secure transport, access controls, monitoring, and support ownership
About FHIR

Built around an established exchange standard.

FHIR (Fast Healthcare Interoperability Resources) is an HL7 standard for exchanging healthcare information electronically. Each implementation can expose different versions, profiles, resources, and interactions, so every connection is qualified against the specific EHR environment.

Read the official HL7 FHIR overview ↗
Plan the connection

FHIR or digital PDF—we can start with your workflow.

Discuss integration Plan a pilot