Jussara, Here is a copy of the paper we presented on INFOLAC 2014
https://www.slideshare.net/pablitox/generacin-automtica-de-interfaces-de-usuario-para-sistemas-de-informacin-clnicos-basados-en-una-metodologa-multinivel The presentation http://www.sueiidiss.org/images/archivos2015/temasinfolac/22.pdf That paper is referenced from my MEDINFO 2015 paper https://books.google.com.uy/books?id=OmZrCgAAQBAJ&pg=PA49&lpg=PA49&dq=Generaci%C3%B3n+autom%C3%A1tica+de+interfaces+de+usuario+para+sistemas+de+informaci%C3%B3n+cl%C3%ADnicos+basados+en+la+metodolog%C3%ADa+multinivel&source=bl&ots=GAd8sfgJuz&sig=UK5rAgO1xrSUEnrUPpWPxDdSJ-E&hl=en&sa=X&ved=0ahUKEwjh_vPPoLbZAhWimeAKHaexDkoQ6AEIMDAB#v=onepage&q=Generaci%C3%B3n%20autom%C3%A1tica%20de%20interfaces%20de%20usuario%20para%20sistemas%20de%20informaci%C3%B3n%20cl%C3%ADnicos%20basados%20en%20la%20metodolog%C3%ADa%20multinivel&f=false All are also here http://independent.academia.edu/pablopazos Since then, I have updated the UITemplate model to use OPTs instead of archetypes directly, added improvements and features that are not in the initial model from the paper. The new model still needs work, but we proven we can use it as an abstract, generic, declarative openEHR UI definition focused on data entry and form-oriented visualization. And that technology specific UI generators can use it to output other declarative form UI specifications, that dev tools / IDEs can take in order to render UIs. E.g. from an UITemplate instance in XML, different generators can generate XAML (.NET UI definitions), SwiXML (Java Swing UI definitions), XHTML/HTML5 (for web), and there are XML UI definitions also for Android and iOS that can be generated. Basically generators are XML mappers, and knowing the destination schema is really easy to create the maping rules between input UITemplates and X technology UI definition. A second level, of definition is also missing, about the rules for data input, like "if field X has a value, show field Y". I don't think we need to specify mandatory or cardinality constraints on the UITemplate since the OPT already has those and the UITemplate should just define UI stuff that is not on the referenced OPT. I hope to have an updated & translated spec for next week. Best, Pablo. On Tue, Feb 20, 2018 at 1:52 PM, Pablo Pazos <[email protected]> wrote: > Let me look for it, haveit on a backup disk somewhere :) > > On Tue, Feb 20, 2018 at 9:59 AM, Jussara Macedo Rötzsch <jussara.macedo@ > coreconsulting.com.br> wrote: > >> Could we have access to that Pablo? >> Regards >> Jussara Rotzsch >> >> Em dom, 18 de fev de 2018 às 15:58, Pablo Pazos <[email protected]> >> escreveu: >> >>> I have a pdf spec in Spanish, this was a university project to have >>> platform independent GUI definitions based on opts, while creating >>> technology specific GUI generators for data entry and display. I mentioned >>> this a while ago on the lists but catched not much attention. >>> >>> Need to do a little translation work :) >>> >>> >>> On Feb 18, 2018 7:51 AM, "Thomas Beale" <[email protected]> >>> wrote: >>> >>> >>> >>> On 17/02/2018 20:11, Pablo Pazos wrote: >>> >>>> I think SET<LOCATABLE> has a lot of applications, including result >>>> sets. Of course that should interior from LOCATABLE to be archetypable. >>>> >>>> I'm not sure on the types associated with the UI. I have a >>>> specification for UITenplates that includes some of that, I can share it :) >>>> >>>> >>> I think any existing UI/template specification / app modelling would be >>> useful to share - possibly on the wiki - let me know if you need a page >>> there. >>> >>> My aim would be to get closer to an IDE application building tool for >>> clinical people to at least build a POC application that works, something >>> like Balsamiq but with real data connections built in. Marand's EhrExplorer >>> does some of this, and it would also be useful to extract some of the >>> semantics of that tool into a standard specification to support this kind >>> of thing. >>> >>> - thomas >>> >>> >>> >>> _______________________________________________ >>> openEHR-technical mailing list >>> [email protected] >>> http://lists.openehr.org/mailman/listinfo/openehr-technical_ >>> lists.openehr.org >>> >>> >>> _______________________________________________ >>> openEHR-technical mailing list >>> [email protected] >>> http://lists.openehr.org/mailman/listinfo/openehr-technical_ >>> lists.openehr.org >> >> -- >> >> >> _______________________________________________ >> openEHR-technical mailing list >> [email protected] >> http://lists.openehr.org/mailman/listinfo/openehr-technical_ >> lists.openehr.org >> > > > > -- > Ing. Pablo Pazos Gutiérrez > [email protected] > +598 99 043 145 <099%20043%20145> > skype: cabolabs > <http://cabolabs.com/> > http://www.cabolabs.com > https://cloudehrserver.com > Subscribe to our newsletter <http://eepurl.com/b_w_tj> > -- Ing. Pablo Pazos Gutiérrez [email protected] +598 99 043 145 skype: cabolabs <http://cabolabs.com/> http://www.cabolabs.com https://cloudehrserver.com 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
