# Triggering behaviour
**Category:** [Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)
**Created:** 2012-08-14 06:55 UTC
**Views:** 3
**Replies:** 1
**URL:** https://discourse.openehr.org/t/triggering-behaviour/14240
---
## Post #1 by @Isaac_Lamb
Hi All,
I have a question regarding triggering behaviour based on data captured via archetypes / templates.
In the openEHR Architecture Overview document, the following extract seems to indicate this has been considered in the openEHR specification.
“Clearly applications cannot always be totally generic (although many data capture and viewing applications are); decision support, administrative, scheduling and many other applications still require custom engineering. However, all such applications can now rely on an archetype- and template driven computing platform.”
When developing an openEHR system, how can decision support and the other actions mentioned above be implemented when there is no way to know which archetypes / templates will be used in the final system?
Kind Regards,
Isaac Lamb
Software Developer
**Email** [isaac.lamb@charmhealth.com.au](mailto:paul.smith@charmhealth.com.au?subject=Email%20Paul%20Smith)
Suite 13, 65 MacGregor Terrace Bardon QLD
**Telephone** +61 (0) 7 3512 5300 | **Fax** +61 (0) 7 3512 5399
**Helpdesk** 1300 736 320 | [support@charmhealth.com.au](mailto:support@charmhealth.com.au?subject=Help%20Desk)
**Web** [www.charmhealth.com.au](http://www.charmhealth.com.au/)
|
|