Define data validity rules for Versions with lifecycle_state = incomplete


Standardise the following change of behaviour for VERSIONs that have lifecycle_state set to incomplete :

  • When committing incomplete data, the validation should be relaxed, i.e. validation of [occurrences and] cardinality lower bounds is skipped, in other words, allow missing data.

  • All other validation (cardinality upper bounds and constraints on values) would be performed normally.

Additionally, when querying, data from incomplete versions would be completely ignored, unless accessed in a specific way. This requires a rule to be added to AQL.


see also


Matija Polajnar
June 15, 2020, 7:59 PM

I’m not sure, but you might be right to just include that into the AQL spec.

Bjørn Næss
September 21, 2020, 8:37 PM

Is it a requirement to have versioning also on incomplete or should we support overwrite of incomplete versions?

Ian McNicoll
September 21, 2020, 9:42 PM

I would allow versioning - that is one of the advantages of persisting the data within the EHR rather than externally like the Better /draft compositions.

Thomas Beale
September 26, 2020, 5:26 AM

I agree with - I would not change the versioning behaviour just because the authoring mode is draft. I would say that an external ‘crash-save-cache’ can still be offered by any product (even this editor here in Jira now remembers your uncommitted comments), but this is another level of functionality.

Matija Polajnar
October 2, 2020, 8:17 PM

I agree.



Adarsha Das

Raised By

Matija Polajnar


Affects versions