# Adding simplified (flat JSON) paths in exported Excel representation?

**Category:** [Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)
**Created:** 2022-01-28 16:17 UTC
**Views:** 720
**Replies:** 3
**URL:** https://discourse.openehr.org/t/adding-simplified-flat-json-paths-in-exported-excel-representation/2302

---

## Post #1 by @erik.sundvall

Hi!

Would it be possible to add another column in the Excel-files that are currently possible to export based on a template in archetype designer? It would simplify some integration work.

A simple stupid example of current format is attached for curious readers. 
[test2.xlsx|attachment](upload://8XVDwAMrVSCO023uiOHgbFYyMmg.xlsx) (6.3 KB)

So what I am asking for could for example be added as a new additional last column (K) and contain the kind of path format used in [simSDT](https://specifications.openehr.org/releases/ITS-REST/Release-1.0.2/simplified_data_template.html#_json_formats) format  -- the same that is also implicitly provided if concatenating ID-fields in the structure of the "web template" export format as described in: https://ehrbase.readthedocs.io/en/latest/02_getting_started/05_load_data/index.html#flat-format

---

## Post #2 by @ian.mcnicoll

I'd support this Erik. Indeed adding the concatenated wtPaths to the Web Templates alongside the aqlPaths would be seriously useful.

---

## Post #3 by @erik.sundvall

Also... 
...turning on line breaks in column F (Data type) by default helps readability, you then in the current format see texts like these:
```
CODED TEXT:
> Regular [The pattern is regular.]
> Irregular [The pattern is irregular.]
```
Another helpful addition for hackers/integrators would be to add the  "at"-codes in  column F (Data type) to get something like the "technical" view in CKM...
```
CODED TEXT:
> at0006::Regular [The pattern is regular.]
> at1028::Irregular [The pattern is irregular.]
```
...or something similar.

Or even **Better** for implementers/integrators, emit a YAML-parsable thing like this in column F:
```
CODED_TEXT:
  at0006: Regular   # The pattern is regular.
  at1028: Irregular # The pattern is irregular.
```

---

## Post #4 by @ian.mcnicoll

Even better use the compressed forms like
CODED TEXT:
 local::at0006 | Regular | [The pattern is regular.]
 local::at1028 | Irregular | [The pattern is irregular.]

Which is also close to the SNOMED CT way of documenting termcodes  and rubrics

---


**Canonical:** https://discourse.openehr.org/t/adding-simplified-flat-json-paths-in-exported-excel-representation/2302
**Original content:** https://discourse.openehr.org/t/adding-simplified-flat-json-paths-in-exported-excel-representation/2302