CDA R2 → FHIR R4 • Pure Python • Zero Dependencies

CDA to FHIR Converter.

Convert Clinical Document Architecture (CDA R2) documents to FHIR R4 bundles with comprehensive field mapping. Pure Python implementation — no Java runtime, no external libraries.

Pure Python, zero dependencies. Unlike solutions requiring Java runtimes or third-party services, the Redix CDA converter uses only standard library XML parsing. Easier deployment, faster startup, lower resource requirements. Does not require a separate AnyToAny Engine license.

CDA R2 C-CDA R1.1 C-CDA R2.1 FHIR R4 13 FHIR Resources Sub-second Processing Pure Python No Java

Supported Document Types

Full CDA R2 support for all major clinical document types

Core Clinical Documents

  • CCD — Continuity of Care Document (problems, medications, allergies, procedures)
  • Progress Notes — Clinical progress documentation and assessments
  • Discharge Summary — Hospital discharge records with diagnoses and treatment plans
  • History & Physical — Chief complaints and physical findings
  • Consultation Notes — Specialist consultation reports
  • Operative Notes — Surgical procedure documentation
  • Diagnostic Imaging Reports — Radiology and imaging results

Additional Document Types

  • Procedure Notes
  • Transfer Summary
  • Referral Notes
  • Care Plan Documents
  • Immunization Records
  • Lab Reports (embedded in CDA)
  • Pathology Reports
  • Problem List Documents
  • Medication List Documents

FHIR R4 Resource Extraction

13 FHIR resource types extracted from CDA documents

FHIR Resource Extracted From Coverage
Patient CDA Header (recordTarget)Demographics, identifiers, contact info 95%
Practitioner CDA Header (author, performer)Provider information 90%
Organization CDA Header (custodian, provider)Facilities, departments 90%
Encounter CDA Header (componentOf)Visit information 85%
Observation Results, Vital Signs, Social HistoryLabs, vitals, smoking status 90%
Condition Problem List, DiagnosesActive/resolved problems 90%
Medication Medications SectionCurrent medications 88%
MedicationRequest Medication OrdersPrescriptions, orders 85%
AllergyIntolerance Allergies SectionAllergies and adverse reactions 92%
Procedure Procedures SectionPast procedures 88%
Immunization Immunizations SectionVaccination history 90%
DocumentReference CDA Document MetadataDocument details 95%
Composition CDA Document StructureDocument composition 92%

Performance Benchmarks

Pure Python processing with standard library XML parsing

Document Type Typical Size Processing Time
Simple documentsBasic progress note, 2–4 sections 50–100 KB 100–200 ms
Standard CCDTypical continuity of care, 8–12 sections 100–300 KB 200–400 ms
Complex documentsDischarge summary, 12–16 sections 300–500 KB 400–600 ms
Large comprehensiveFull clinical summary, 15+ sections 500 KB – 1 MB+ 600–1000 ms

Test environment: RHEL 9, 2 CPU cores, 4 GB RAM. Pure Python processing with standard library XML parsing only.

Key Features

Zero Dependencies

  • Pure Python implementation
  • No Java runtime required
  • No external libraries
  • Standard library XML only
  • Easy deployment, fast startup

Multiple Interfaces

  • Web GUI with drag-and-drop
  • Command-line tools
  • REST API
  • Batch processing
  • Python library import

Quality Assurance

  • CDA R2 validation
  • FHIR R4 validation
  • Error reporting
  • Processing logs
  • Section mapping tracking

Architecture

Four integrated components in the transformation pipeline

1

CDA Parser

Extracts clinical data from CDA XML structure

2

Section Processor

Handles individual CDA sections (medications, problems, etc.)

3

FHIR Builder

Creates Patient, Encounter, Observation, and other resources

4

Bundle Generator

Assembles complete FHIR R4 transaction bundles

C-CDA Template Support

Consolidated CDA versions and standard clinical sections

Supported Versions

  • C-CDA R1.1
  • C-CDA R2.1
  • US Realm Header
  • HL7 CDA R2

Standard Sections

  • Problems Section
  • Medications Section
  • Allergies Section
  • Results Section
  • Procedures Section
  • Immunizations Section
  • Vital Signs Section
  • Social History Section

System Requirements

Python Version 3.9+ (pure Python, no other dependencies)
Minimum Hardware 2 CPU cores, 4 GB RAM, 10 GB storage
Recommended Hardware 4+ CPU cores, 8 GB+ RAM, SSD storage
Operating Systems Linux (RHEL 8/9, CentOS, Ubuntu 20.04+) or Windows (10/11, Server 2019/2022)
Deployment Options Standalone, Docker, Kubernetes, AWS, Azure, Google Cloud

What's Included

Software Components

  • CDA to FHIR transformation engine
  • Template-based section processors
  • Web GUI with admin dashboard
  • Command-line processing tools
  • Configuration files
  • FHIR resource validators

Documentation & Support

  • Getting Started Guide
  • Installation Guide (Linux & Windows)
  • CDA Section Mapping Documentation
  • FHIR Resource Mapping Specifications
  • Troubleshooting Guide
  • Sample CDA documents for testing

Service Packages

DIY Foundation

Complete source code, documentation, and sample files. Self-service implementation with comprehensive guides. Best for teams with Python expertise.

Professional Services

Foundation plus custom template mapping, testing, and deployment assistance. Best for standard implementations with custom CDA templates.

Enterprise Package

Complete turnkey solution with custom development, integration, training, and ongoing support. Best for complex environments with proprietary CDA extensions.

All nine conversion tools available here. Swagger API explorer here.