Recently a client committed COMPOSITIONS with empty content to the EHRServer, because in the OPT all the structure was associated to context.other_context.
After reviewing the specs, I found this invariant on the COMPOSITION spec:
Content_valid: content /= Void implies not content.is_empty
That means that content can actually be null/void, since on that case, the “implies” is true.
Also checked the COMPOSITION XSD, and the minOccurs for content is 0.
Does it make sense to have an empty COMPOSITION.content?
Does other implementers support that?
On which cases?
I have certainly built templates where there is no expected content, only additional other_contecxt and I can imagine situations where any/all data could be carried by Composition RM attributes e.g in feeder_audit, so I can’t see a good reason for enforcing content.