Hi!
I have no strong opinions regarding the naming, I just used FHIR’s name to point to the use-cases and design pattern.
What we have an immediate need for in the multi-vendor project is a vendor netrual possibility to express if/then conditionals like the ones you both have discussed above (e.g like Thomas’ “tobacco user Y/N”).
It looks like the ADL implies+exist rules or future expression language with assert+implies might do the job if I understand you correctly above.
One of the remaining questions:
Are there suitable (template?) authoring tools that can be used to explore the ADL rules approach?
If not, could we (for practical test purposes) make some annotations using present tools with the rule syntax in the annotation data somehow? The template(s) with annotations could then easily be automatically post-processed and convert the annotations into for example either:
- “proper” ADL rules and insert into the template or
- current vendor specific if/then rules in openEHR-based form engines (like Betters’s and Cambio’s)
Currently the national project is a “proof of concept”, so it can be used to test the general mechanisms and no essential harm is done if a future official openEHR syntax would change later.