Make an HL7 CDA R2 document readable - as a clear HTML view, generated locally in the browser, with no upload.
Running locally on your device ...
Running locally on your device ...
0%
Your files never left your device
Continue with this file
No re-upload neededThese tools accept .HTML - your file is handed over directly.
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
HL7 CDA R2 (Clinical Document Architecture) is a widespread XML standard for clinical documents - from a discharge letter to a nursing report. The ClinicalDocument (namespace urn:hl7-org:v3) carries a header (title, date, document type, patient data) and a structured body of sections, each with a title and text. As a raw XML file it is hard for a person to read. This tool turns the core fields into a plain, clear HTML page that opens on any device.
Drop your CDA XML; the tool reads the header (title, date, document type, patient with name, gender, birth date and identifier(s) - even when several identifiers such as a case number and an insurance number sit side by side) and the sections of the structured body and renders them as HTML tables and sections. The section text is carried over as readable running text; when a section carries coded clinical entries (such as SNOMED CT or LOINC inside the entry element), those codes are shown alongside the running text. You can drop several files at once, each becomes its own HTML page. Every value read from the XML is inserted HTML-safe (no injected code).
Everything runs entirely locally in the browser (pure JavaScript, no server, no foreign library from a foreign CDN) - the document with its patient data never leaves your device. Honest framing: this is a readable view of the core fields, not a full CDA stylesheet renderer and not a clinical tool. Nested tables or lists inside the section text are simplified to running text; for the full, official rendering use your system viewer.
| Input formats | XML, CDA |
|---|---|
| Output format | HTML |
| Batch processing | Yes |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Makes an HL7 CDA R2 document (ClinicalDocument, namespace urn:hl7-org:v3) readable as HTML: header (title, effectiveTime as the date, document type from the code element, recordTarget/patient with name, gender, birth date and identifier(s) - several id elements such as a case number and an insurance number are all shown) and the sections of the structuredBody (title + section text carried over as running text, plus coded clinical entries from the entry element - such as SNOMED CT or LOINC codes - whenever a section carries any). It is a view of the core fields, not a full CDA stylesheet renderer, not a full entry-template parser and not a clinical tool: nested tables/lists in the narrative are simplified to text, embedded stylesheets and attachments are not evaluated. Every value is inserted HTML-safe. For the full, official rendering use your system viewer.
No. Reading the CDA XML and building the HTML view run entirely locally in the browser (pure JavaScript, no server); the document never leaves your device.
The header (title, date, document type, patient with name, gender, birth date, identifier(s)) and the structured-body sections with title, text and - where present - coded clinical entries (e.g. SNOMED CT, LOINC).
No. It is a view of the core fields; nested tables or lists in the section text are simplified to running text. For the official rendering use your system viewer.
Yes. Every value read from the XML is inserted HTML-safe (escaped), so no injected code is executed.
Yes. Drop several CDA files at once; each becomes its own HTML view.
Yes, whenever a section carries coded entries inside the entry element: the code, code system and display name are shown alongside the running text. It is a best-effort display of every code element found, not a full, template-aware CDA entry parser.