RE: Shouldn't INSTRUCTION_DETAILS.wf_details be archetypable?

2016-07-13 Thread pablo pazos
, Eng. Pablo Pazos Gutiérrez http://cabolabs.com From: heath.fran...@oceaninformatics.com To: openehr-technical@lists.openehr.org; openehr-clini...@lists.openehr.org; s...@lists.openehr.org Subject: RE: Shouldn't INSTRUCTION_DETAILS.wf_details be archetypable? Date: Wed, 13 Jul 2016 00:15:09 +

Re: Shouldn't INSTRUCTION_DETAILS.wf_details be archetypable?

2016-07-13 Thread Diego Boscá
Hello Pablo, For these kinds of use cases I'd really recommend you to try LinkEHR. You should be able to define anything valid in the openEHR schema. We went to the extent to add an 'export' option to ensure that the output ADL could be read by Archetype Editor and Template Designer, so you don't

RE: Shouldn't INSTRUCTION_DETAILS.wf_details be archetypable?

2016-07-12 Thread Heath Frankel
Hi Pablo, Since wf_details is ITEM_STRUCTURE, then yes it can be archetyped. Just because the AE doesn't support it does not change this fact. As is this case in many software projects, functionality in the AE was built on as needed basis so I would suggest that no one has needed it to date.