# Excel sheet to generate FLAT .json composition paths - useful or not?

**URL:** <https://discourse.openehr.org/t/excel-sheet-to-generate-flat-json-composition-paths-useful-or-not/11960>\
**Category:** Tool Support\
**Created:** [17 April 2026 10:36 UTC](https://discourse.openehr.org/t/excel-sheet-to-generate-flat-json-composition-paths-useful-or-not/11960 "2026-04-17T10:36:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lars\_Fuhrmann](https://discourse.openehr.org/user_avatar/discourse.openehr.org/lars_fuhrmann/32/4485_2.png) [@Lars\_Fuhrmann](https://discourse.openehr.org/u/Lars_Fuhrmann)\
**Post date:** [17 April 2026 10:36 UTC](https://discourse.openehr.org/t/excel-sheet-to-generate-flat-json-composition-paths-useful-or-not/11960/1 "2026-04-17T10:36:33Z")

</div>

I wanted a quick way to get a list of flat .json format composition paths which I usually did by sending the template to an EHRbase instance and getting an example composition.

I wondered if there was a way to do this:

- Without a CDR,
- even without a coding environment
- in a format that could includes a little a bit more info on the template, and …
- ..can be easily displayed to collaborators who may not be used to looking at .json files.

**So.. let those who do not have Microsoft Excel installed cast the first stone!** 😬  
(they may be right to cast it, I’m just not one of them)

After a bit of back and forth with gemini it spit out a powerquery that seems to work without making too much of a mess. It is just 78 lines of code and it also gets the node type, at codes and cardinalities.

I just spend half an hour on this and fully expect it to break with some other data types or template features that i have not yet tried out!  
Before I spend even a minute more on it I just wanted to ask I’m the only one who thinks this may sometimes be useful?  
Otherwise I’ll probably leave it be!

example result:

 ![image](https://discourse.openehr.org/uploads/default/original/2X/0/0adc0bd569c450750b44cd31f6da93335f2ea458.png)

To use it you just need to enter the path to the web template .json in the source step. (Quelle = Source in German)

 ![image](https://discourse.openehr.org/uploads/default/original/2X/e/eb65bb95adb60e947796387a0da5539e08108fd9.png)

Can’t believe I just set up a [Github repo](https://github.com/larfuma/openEHR-flat-json-compositions-paths-via-excel/tree/main) for a silly little vibe-coded excel sheet!

---

<div class="post-metadata">

**Author:** ![Lars\_Fuhrmann](https://discourse.openehr.org/user_avatar/discourse.openehr.org/lars_fuhrmann/32/4485_2.png) [@Lars\_Fuhrmann](https://discourse.openehr.org/u/Lars_Fuhrmann)\
**Post date:** [17 April 2026 11:05 UTC](https://discourse.openehr.org/t/excel-sheet-to-generate-flat-json-composition-paths-useful-or-not/11960/2 "2026-04-17T11:05:30Z")

</div>

[Here](https://pastebin.com/PFfqd5wF) is a pastebin of the powerquery code,  
Again, this does not even cover all RM types, the point is just whether anyone would could imagine this becoming a useful little gimmick.