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 need to change your workflow.
Regards 2016-07-12 7:09 GMT+02:00 pablo pazos <pazospa...@hotmail.com>: > I made a mistake, when I said "INSTRUCTION.instruction_details" was really > "ACTION.instruction_details". Sorry! :) > > -- > Kind regards, > Eng. Pablo Pazos Gutiérrez > http://cabolabs.com > > ________________________________ > From: pazospa...@hotmail.com > To: openehr-technical@lists.openehr.org; openehr-clini...@lists.openehr.org; > s...@lists.openehr.org > Subject: Shouldn't INSTRUCTION_DETAILS.wf_details be archetypable? > Date: Tue, 12 Jul 2016 02:06:24 -0300 > > > Looking at the model, INSTRUCTION_DETAILS.wf_details is an ITEM_STRUCTURE, > and that lead me to think that should be archetypable. > > Playing around with the archetype editor, it doesn't allow to archetype > anything inside INSTRUCTION.instruction_details. > > Is this a problem of the AE or that structure is not meant to be archetyped? > > If it is not meant to be archetyped, wouldn't that be an issue for querying? > > Thanks! > > -- > Kind regards, > Eng. Pablo Pazos Gutiérrez > http://cabolabs.com > > _______________________________________________ openEHR-clinical mailing > list openehr-clini...@lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical@lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org _______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
