Sam Heard wrote: > ... What we have been doing is setting the regex to: > >> openEHR-EHR-CLASS_NAME\.REGEX_EXPRESSION
This is not quite right because REGEX_EXPRESSION might contain patterns for multiple concepts, as Adam mentioned. You would have to wrap it up in parentheses: openEHR-EHR-CLASS_NAME\.(REGEX_EXPRESSION) Then it should work. Adam Flinton wrote: > > ... thus it needs to be split by a "regex pre-processor" > & then each sub statement needs to have the > "openEHR-EHR-CLASS_NAME" > appended to it & then put through the regex engine. No need to do that, Adam, just wrap the regex within parentheses. So taking the example you gave, the correctly-wrapped regex would be: Include entries openEHR-EHR-CLUSTER\.(checklist_item-general-cvs1.v1|checklist_item-general-cvs2.v1|checklist_item-general-cvs3.v2|checklist_item-general-cvs4.v2draft|checklist_item-general.v1|checklist_item-general.v2|checklist_item-general.v3) The code to generate this is trivial in any programming language (assuming your programming language has the ability to concatenate strings, which I reckon is a safe bet). Unless you're programming in assembly language, it's probably one simple line of code. - Peter
