Page Comparison

FHIR ‘conditional create’. Seref Arikan (Personal) consider using the REST approach established by FHIR (i.e. If-None-Exist: [search parameters] extension header); still need to work out our own semantics. How do we do search params ? Could these params be abused i.e. access control. Need to be limited - maybe - ‘match params' or 'creation criteria'.

Seref Arikan (Personal) : set the singleton template id list via a dedicated REST endpoint.

Matija Polajnar : treat this as a back-end validity question.

Ian McNicoll : template ids + Composition names?

Diego Bosca : modify existing OPT upload REST endpoint header params?

Bjørn Næss : rules need to be context specific, e.g. in certain episode, folder etc.

Ian McNicoll : maybe start with true persistent singletons?

Bjørn Næss : how to handle branching? Partial commits (multi-Composition) fail if one Composition breaks the rule.

Thomas Beale : consider these as ‘content policies’ for EHR system deployments.

DO we want a ‘singleton’ Composition category? Ian McNicoll create a new attribute to replace existing category with same possible values as category? Seref Arikan (Personal) - dangerous!

Erik Sundvall : ‘blacklist’ - can have a template id; plus a test AQL that must return 0 results? Seref Arikan (Personal) allow criteria (could be AQL, JS etc) to items in the blacklist.