Start with a C-CDA file.
Upload one XML document through the file picker or drag-and-drop area, with namespace selection.
Convert C-CDA XML into FHIR R4 bundles. Inspect readable output alongside JSON, export a PDF and follow conversion activity.
Browser-based evaluation. C-CDA XML. FHIR R4. Conversion audit reports.
Clinical summaries carry valuable context. Convert a representative document, inspect its resources and review any conversion issues before moving downstream.
Use a representative clinical summary to evaluate the path from document content to resources.
Let technical and clinical reviewers inspect the same converted bundle.
Use activity filters and error details to focus your investigation.
Evaluate the API alongside existing ingestion and validation steps.
A clear path from XML input to inspectable FHIR output.
Upload one XML document through the file picker or drag-and-drop area, with namespace selection.
Extract clinical content into resources such as Patient, Organization, Encounter and AllergyIntolerance.
Inspect converted resources in a readable view and formatted FHIR JSON.
Export the converted bundle for offline review and documentation.
Review upload dates, processing status, source identifiers and error details.
Filter activity by date, status or metadata to investigate conversion results.
Review a single document in the browser or use APIs for automated conversion.
Submit XML and retrieve FHIR JSON within your integration workflow.
Trial access includes API documentation. Review it for request formats and integration details.
Get Instant AccessRead the C-CDA-to-FHIR implementation guide. For the foundations, explore FHIR resources, APIs and validation.
Illustrative sample data and results. This preview does not process uploaded data.
Try C-CDA to FHIRUse synthetic or de-identified data only.
Explore the tool with representative test files before planning your production workflow.
Keep real patient data out of the trial environment.
Data transfers use encrypted connections.
The product does not retain uploaded source files.
Discuss your deployment and data-handling requirements with the Hgear team.
Integration engineers, clinical informaticists and platform developers can review the same output.
The converter accepts C-CDA XML, including CCDs, discharge summaries and referral summaries. Output uses FHIR R4.
The browser accepts one XML file at a time. Batch conversion is available through the API.
Review the error details, correct the source document and submit it again.
You can download a PDF of the readable bundle. The API returns FHIR bundles as JSON.
Use a test C-CDA file to explore conversion, review and export.
Try C-CDA to FHIRBuild on document conversion with transformation, validation and visualization across the Hgear platform.
Explore data transformation