Hi Dileep, You are mixing modeling/design with implementation/runtime. Archetypes can define terminology bindings at design time. Those should be resolved at runtime.
You can just create other files with AQLs, and another file that maps archetype paths to the AQL files. Your app will be able to load the archetype, load the AQL and execute AQL to resolve the term subset for each DV_CODED_TEXT in your archetype, and use that on a GUI. Of course files are just examples, implementation can be at a database level. Hope that helps :) On Wed, Jul 5, 2017 at 9:23 AM, Dileep V S <[email protected]> wrote: > HI, > > I am just wondering if it is possible to embed an AQL into the archetype > so that the data set for a DV_CODED_TEXT is formed out of existing > compositions. > > For example, a hospital registration form that asks for a person's > allergies. Instead of an empty field, it can be populated from existing > data through a query so that the front desk can just validate the data. Can > this be modeled into the archetype? Or should it be an implementation > detail? > > regards > Dileep V S > *Founder* > HealtheLife Ventures LLP > m: +91 9632888113 <+91%2096328%2088113> > a: 103, Innovation Centre, IIIT, Electronics City, Bangalore 560100 > w: healthelife.in e: [email protected] > > _______________________________________________ > openEHR-technical mailing list > [email protected] > http://lists.openehr.org/mailman/listinfo/openehr- > technical_lists.openehr.org > -- Ing. Pablo Pazos Gutiérrez Cel:(00598) 99 043 145 Skype: cabolabs <http://cabolabs.com/> http://www.cabolabs.com [email protected] Subscribe to our newsletter <http://eepurl.com/b_w_tj>
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
