Problem description
The original question from Matija Polajnar was: do we need an endpoint for committing persistent compositions, to ensure for example that one one instance is allowed of a particular Composition e.g. medications list.
Issues:
this kind of rule (e.g. can only have one Medications List persistent Compostion) will not be globally applicable - it will therefore apply to specific deployments;
Where are the rule(s) encoded?
Heath Frankel (Unlicensed) What about when the Composition is part of a multi-Composition Contribution?
problem of race condition of N clients trying to create a singleton Composition e.g. Meds list;
This example can be generalised to a) any kind of content and b) any multiplicity, e.g. this system allows <=10 Problem Lists.
Analysis
TODO
Solution ideas
Erik Sundvall endpoint ‘black list’ - special template ids? Should be a customer question