openEHR Template Explorer

Paste a Web Template to browse its node tree, inspect occurrences and coded values, and list or export every FLAT path. Runs entirely in your browser.

How it works ↓

Input

Paste a Web Template JSON to explore its structure

Platform

Waiting for input

Web Template JSON

Template: -

0 nodes

0 archetypes

0 required

◎

Paste a Web Template JSON or OPT XML above, then click Explore

or load an example to get started

Click a node in the tree to see its details

FLAT Paths

Find the FLAT path for any field in your template

Writing a FLAT composition means knowing the exact path of every field, and those paths come from the template. The explorer reads a Web Template (the JSON rendering of an operational template that CDRs like EHRBase serve) and shows its structure as a tree. Click any node to see its FLAT path, RM type, occurrences, and coded values such as unit and code lists.

How to use it

Fetch your Web Template: in EHRBase, GET /rest/openehr/v1/definition/template/adl1.4/{template_id} with Accept: application/openehr.wt+json.
Paste it and click Explore, or load the example.
Expand the tree, select nodes for their details, and copy all FLAT paths or export them to CSV.

FAQ

Why a Web Template and not the OPT?

FLAT paths can't be reliably derived from OPT XML: CDRs apply their own naming and indexing rules. The Web Template is the authoritative source, so the explorer uses it (see ADR-0005).

What does the platform switch change?

The FLAT dialect: EHRBase 2.x omits :0 on single-occurrence nodes, while Better keeps more indices. Paths are shown the way your CDR expects them.

What do I do with the paths?

Use them to build FLAT compositions, by hand or with oehrpy's template builders, and check the result with the validator.

Is my template uploaded anywhere?

No. Parsing happens entirely in your browser.