Empty COMPOSITION.content is valid?

Hi all,

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?

Thanks!

this is indeed what the spec says. This is certainly the way to decide whether Void is allowed or not. - thomas

Imagine a visit to a GP, and nothing clinical comes out of it. Nothing worth mentioning, but still having had a composition and a consult to pay for.

You would be surprised to the amount of legacy data with no clinical content, just because original systems allowed it

In the archetype the amount of constraints must be minimal.

In the Template the amount of constraints must be optimal (maximal?)

Archetypes are generic patterns.
Templates are specific patterns.

Generic meaning to be used in all systems at all points in time.
Specific meaning to be used in a jurisdiction at a point in time.

Gerard Freriks
+31 620347088
gfrer@luna.nl

Kattensingel 20
2801 CA Gouda
the Netherlands

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.

Ian