Hi all, I'm adding some extra checks on the EHRServer, and found cases where users were committing compositions with nodes that are not defined in the referenced OPT.
That made me think of the interpretation of non existing constraints. For instance, the extreme case of can empty COMPOSITION OPT (no constraints defined for the COMPOSITION.content), how that should be interpreted? 1. open: any structure is allowed on the COMPOSITON.content 2. closed: structures not defined in the OPT are not allowed On a normal case where the full OPT is defined, from COMPOSITION to ELEMENT.value, how that OPT is interpreted? open or closed? Are extra ENTRIES and other nodes allowed even no definition for them is on the OPT? (open interpretation), or only OPT defined nodes are allowed? (closed interpretation). I think this is key to understand implementation, and it is sad I didn't recognized this issue before, but here we are :) Best, Pablo. -- *Ing. Pablo Pazos Gutiérrez* pablo.pa...@cabolabs.com +598 99 043 145 skype: cabolabs Subscribe to our newsletter <http://eepurl.com/b_w_tj> <https://cabolabs.com/> http://www.cabolabs.com https://cloudehrserver.com
_______________________________________________ openEHR-clinical mailing list openEHR-clinical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
