During the SEC meeting today we decided that the SEC REST (sub)workgroup gets the task to clarify the specification regarding that client supplied UIDs should be used (not changed) by the recieving server including:
- what errors should be thrown if ID collisions etc. are detected
- if POST or PUT should be used for client supplied IDs (as discussed in e.g. [SPECITS-62] - openEHR JIRA )
We did not have time during the SEC to discuss if the reference in INSTRUCTION_DETAILS.instruction_id should/could point to a specific version of a COMPOSITION or not - but that would also need to be better described and exemplified in the specifications.
The approach with $selfComposition was not considered to be a prefered solution. Instead proper client-selected IDs was preferred since that would solve more other use cases at the same time than $selfComposition would.
Since there is no AQL sub-working group, the question regarding standardisation of AQL convenience functions such as current_state and instruction_aggregate_state will remain with the main SEC for some later point in time (it would be good to create a problem report and/or change request to track this issue if none already exists).