Triggering behaviour

2012-08-14 Thread 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 at charmhealth.com.aumailto:paul.smith at 
charmhealth.com.au?subject=Email%20Paul%20Smith
[cid:image003.jpg at 01CD7A3D.A6492E60]

Suite 13, 65 MacGregor Terrace Bardon QLD
Telephone +61 (0) 7 3512 5300 | Fax +61 (0) 7 3512 5399
Helpdesk 1300 736 320 | support at charmhealth.com.aumailto:support at 
charmhealth.com.au?subject=Help%20Desk
Web www.charmhealth.com.auhttp://www.charmhealth.com.au/





DISCLAIMER: This e-mail, together with any attachments, is confidential and 
intended for the named
recipient(s) only. If you are not the intended recipient or have received this 
message in error, you are
asked to immediately notify the sender and delete this message and any copies 
of this message from
your computer system network and destroy any printed copies of this email. Any 
form of unauthorised
disclosure, modification, distribution, publication or use of this e-mail 
message is prohibited.


Scanned by the Netbox from 
(http://netboxblue.com/)

-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120814/cdd618cf/attachment-0001.html
-- next part --
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 180 bytes
Desc: image001.png
URL: 
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120814/cdd618cf/attachment-0002.png
-- next part --
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 168 bytes
Desc: image002.png
URL: 
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120814/cdd618cf/attachment-0003.png
-- next part --
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 2105 bytes
Desc: image003.jpg
URL: 
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120814/cdd618cf/attachment-0001.jpg


Triggering behaviour

2012-08-14 Thread Sam Heard
Hi Isaac

Just saw your post. The triggering rules could be based on the reference 
model alone but would be largely to do with access notification or the 
like - e.g. if the same user saves or reads more than 20 EHRs in an hour 
to stop the user access. All clinically oriented business rules need to 
be based on AQL and DO need to know what archetypes are involved - but 
not at the time of creating the system. These rules can be written when 
and as needed.

Cheers, Sam

On 14/08/2012 4:25 PM, Isaac Lamb wrote:

 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 at charmhealth.com.au 
 mailto:paul.smith at charmhealth.com.au?subject=Email%20Paul%20Smith

 Description: Description: Description: cid:image002.jpg at 01C8F3D1.27611F50

 Suite 13, 65 MacGregor Terrace Bardon QLD **

 *Telephone*+61 (0) 7 3512 5300 | *Fax* +61 (0) 7 3512 5399

 *Helpdesk*1300 736 320 | support at charmhealth.com.au 
 mailto:support at charmhealth.com.au?subject=Help%20Desk

 *Web*www.charmhealth.com.au http://www.charmhealth.com.au/**



   


 DISCLAIMER: This e-mail, together with any attachments, is 
 confidential and intended for the named
 recipient(s) only. If you are not the intended recipient or have 
 received this message in error, you are
 asked to immediately notify the sender and delete this message and any 
 copies of this message from
 your computer system network and destroy any printed copies of this 
 email. Any form of unauthorised
 disclosure, modification, distribution, publication or use of this 
 e-mail message is prohibited.



 Scanned by the Netbox from Netbox Blue http://netboxblue.com/


 ___
 openEHR-technical mailing list
 openEHR-technical at lists.openehr.org
 http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120814/c90a1392/attachment.html
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 168 bytes
Desc: not available
URL: 
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120814/c90a1392/attachment.png
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 2105 bytes
Desc: not available
URL: 
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120814/c90a1392/attachment.jpe