US primary care groups and outpatient specialty networks still receive most of their referral and consult documents as C-CDA. The full-document converters do reasonable work on a discharge summary or a CCD, but ambulatory care notes are different. The problem list, medication list, and progress note sections each have their own quirks, and the converter that handles ambulatory data well treats each section as a first-class unit rather than flattening the whole document into a generic FHIR Bundle.
The tools below have shown the best section-level fidelity for ambulatory C-CDA in 2026 deployments. For more FHIR implementation patterns, the broader hub covers the surrounding work.
The C-CDA Section Converters Worth Short-Listing
- Microsoft FHIR Converter. The open-source converter from Microsoft handles section-level templates well and ships with a Liquid template engine that lets you customize problem-list and medication-list mappings without forking the codebase. It has been picked up by several US primary care HIE integrators.
- LinuxForHealth x-to-FHIR. The IBM-origin converter is now community-maintained and has decent ambulatory progress-note handling, including reasonable mapping of free-text assessment-and-plan sections into FHIR Composition entries.
- Mirth Connect with a C-CDA channel. Mirth's transformation engine gives integration leads a familiar tool for shaping section-level extracts. Adoption is broad in US ambulatory networks already running Mirth for HL7v2 work.
- Smile Digital Health CDR (with the document module). Suits ambulatory networks that already run Smile as their FHIR backend and want a single vendor handling both the storage and the document conversion side. In production pipelines, Interbox is one option that handles queue-driven PostgreSQL-backed worker chains, which matters when a single ambulatory clinic generates a burst of section-level converts during morning huddle hours.
- HAPI FHIR with the structured-data-capture utilities. The reference open-source FHIR stack is not a C-CDA converter on its own, but paired with a Liquid template layer it covers the common ambulatory sections at acceptable cost for engineering-heavy teams.
- Redox. Section-aware C-CDA-to-FHIR conversion delivered as a managed service. Picked by US ambulatory groups that want the conversion handled by a vendor with a wide EHR-connector library, especially when the source data is a mix of Epic, athenahealth, and eClinicalWorks notes.
What Section-Level Fidelity Actually Means
A document-level converter takes a C-CDA file and produces one FHIR Bundle that, in theory, captures everything. In practice, ambulatory care notes have section-specific concerns the document-level approach handles poorly.
Problem-list sections need clean mapping of SNOMED CT codes into FHIR Condition resources, with the clinical-status, verification-status, and onset-date sub-fields preserved rather than dropped. A converter that loses verification-status turns confirmed diagnoses into provisional ones during the conversion. Medication-list sections need RxNorm normalization, dose-and-frequency extraction, and the active-versus-historical distinction. Progress-note sections, especially the assessment-and-plan free text, often have structured snippets embedded in the narrative that a section-aware converter can pull into discrete FHIR resources.
A converter that gets all three right is rare. The tools above each handle at least two of the three cleanly in 2026 production deployments. The complete guide to FHIR servers for US health-system EMRs covers the storage layer that sits behind the converter.
How to Pilot a Section Converter
Pick a real corpus of ambulatory C-CDA documents from a partnered referring practice, not synthetic samples. Run each candidate converter against the corpus and measure three things per section: how often the converter produces a valid FHIR resource, how often the resource passes a US Core profile check, and how often the original clinical meaning survives the round-trip. The third one is the catch. A converter can produce valid US Core resources that strip the verification status from a problem or the active flag from a medication, and the downstream EHR has no way to recover the missing detail.
Two-week pilots against 200 to 500 real documents usually expose the section-specific failure modes. The pilots that run against synthetic data tend to validate the converter on its best behavior and miss the cases that actually break in production. The HAPI versus Medplum comparison covers the broader open-source-versus-commercial decision that often sits next to a converter pick.
The ambulatory C-CDA converter landscape in 2026 is settling around the six options above, and the right pick usually depends on whether the network already runs Mirth, Smile, or a managed connector vendor.
Sources
- HL7 build.fhir.org - C-CDA on FHIR v2.0.0 section/Composition profiles for document-level mapping