CDA and XML comparison utility
CDA & Clinical XML Diff Tool
Compare two clinical XML documents structurally, match CDA sections and entries semantically, and review header, narrative, attribute, value, and internal reference changes without uploading the content.
Structured comparison
Compare two CDA or clinical XML documents
This tool compares parsed XML structure and applies practical CDA-aware matching. It is not a CDA, schema, template, terminology, or implementation-guide conformance validator.
Both documents stay in your browser and are not saved by this tool.
Separate paths with commas, semicolons, or new lines. Asterisks act as wildcards. Paths are matched against the structured result paths shown below.
CDA sections
Filter by section
Sections are matched by code, then template IDs, then title when semantic section matching is enabled.
Internal references
Reference changes
Changes to CDA narrative references and their local ID resolution state are shown separately.
| Status | Path | Original | Updated |
|---|
| Status | Scope | Path | Original | Updated |
|---|
Text report
Compare two documents to generate a report.
FAQ
CDA and XML comparison questions
Is this a line-by-line XML diff?
No. The tool parses both XML documents, compares elements, attributes, and direct text values, and uses CDA-aware semantic keys for sections and structured entries when possible.
How are reordered CDA sections handled?
With semantic section matching enabled, the tool prefers section code and code system, then template IDs, then title. Reordering the same sections should not create false removed and added section results.
How are structured entries matched?
The tool looks for statement identifiers first and coded statement keys second for common entry types such as observations, substance administrations, procedures, acts, organizers, encounters, and supplies. It falls back to order when stable unique keys are unavailable.
What do the default ignored options do?
They ignore the direct ClinicalDocument document ID and effectiveTime, plus author or authenticator time elements. Encounter effectiveTime and other IDs remain significant unless you explicitly ignore their paths.
Does this validate CDA conformance?
No. It performs structured comparison and practical CDA-aware matching only. It does not validate schemas, templates, terminology, or jurisdiction-specific implementation guides.
Can I paste real patient data?
No. Use synthetic or appropriately de-identified test data only.