The template designer only opens OET files, not OPTs, OPT is an exported file while the OET is the source. I guess you are trying to edit an OPT file and that is not the correct way of editing templates. That is why it gives you the validation errors. Those are different formats!
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| OPT 1.4 Specification | 26 | 1944 | 21 December 2024 | |
| How about creating an openEHR test base? | 50 | 94 | 15 May 2012 | |
| Is DV_STATE and it's profile constraint C_DV_STATE used anywhere in the specs? | 22 | 959 | 10 November 2021 | |
| Modeling generic concepts, considerations for querying | 17 | 73 | 10 October 2017 | |
| The good, the bad and the "Wat?" of current simplified FLAT/SimSDT openEHR exchange format | 45 | 1716 | 26 November 2025 | |
| template formal definition | 17 | 20 | 22 October 2014 | |
| Which AOM2 release are AWB/Nedap using for exporting OPT2 to JSON? | 32 | 1177 | 29 November 2021 | |
| Inconsistency in REST API Create EHR implementations -needs spec clarification? | 27 | 890 | 9 October 2024 | |
| Q on openEHR XML-schema versioning | 14 | 23 | 15 December 2008 | |
| Multi RM JSON schema validation and current schema issues | 20 | 795 | 12 November 2022 |