About "report": Maybe we just need a subclass of Folder that contains a "Locatable" (0..*) attribute. Shouldn't break things too much. Maybe going the FHIR way is also feasible: Create a new class with a Folder and a container of locatables that can be pointed by the Folder.
About questionnaire: This was written on the wiki some time ago: https://openehr.atlassian.net/wiki/display/healthmod/Questionnaires+and+openEHR Also, I asked a similar question on the 'questions' parts of the wiki: https://openehr.atlassian.net/wiki/questions/30900242/how-to-model-meta-archetypes Regards 2017-05-31 6:54 GMT+02:00 Pablo Pazos <[email protected]>: > Hi Thomas, > > Thinking about the hierarchy, at which level will be a Report be? Below > compo? Below entry? Structure? Representation? > > OT: many asked me this and didn't had a good answer. Do we have a pattern > to model questionnaires? Some require to define questions, and the answer > type in most cases is boolean, or coded text (multiple choice), and answers > might be 0..* (more than one answer for the same question is valid). > > Cheers, > Pablo. > > On Tue, May 30, 2017 at 11:55 PM, Thomas Beale <[email protected]> > wrote: > >> >> some of us have been looking at the idea that a 'report' should be a new >> content type in openEHR, that can include other content of different types, >> and in different ways. >> >> We have published a wiki page >> <https://openehr.atlassian.net/wiki/display/spec/Reports> with the >> initial notes on the idea, and a (possibly) novel approach to solving the >> quoting/inclusion problem, which is to serialise included content into the >> report. We think the report type (the name may need to be reconsidered) >> would apply to discharge summaries, general summaries, referrals, and >> possibly care plans. >> Comments and reactions welcome on the wiki page or here. >> >> thanks >> >> - thomas >> >> -- >> Thomas Beale >> Principal, Ars Semantica <http://www.arssemantica.com> >> Consultant, ABD Team, Intermountain Healthcare >> <https://intermountainhealthcare.org/> >> Management Board, Specifications Program Lead, openEHR Foundation >> <http://www.openehr.org> >> Chartered IT Professional Fellow, BCS, British Computer Society >> <http://www.bcs.org/category/6044> >> Health IT blog <http://wolandscat.net/> | Culture blog >> <http://wolandsothercat.net/> >> >> _______________________________________________ >> 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 > -- [image: VeraTech for Health SL] <https://htmlsig.com/t/000001C268PZ> [image: Twitter] <https://htmlsig.com/t/000001C47QQH> [image: LinkedIn] <https://htmlsig.com/t/000001C4DPJG> [image: Maps] <https://htmlsig.com/t/000001BZTWS7> Diego Boscá Tomás / Senior developer [email protected] [email protected] VeraTech for Health SL +34 961071863 <+34%20961%2007%2018%2063> / +34 627015023 <+34%20627%2001%2050%2023> www.veratech.es Su dirección de correo electrónico junto a sus datos personales forman parte de un fichero titularidad de VeraTech for Health SL (CIF B98309511) cuya finalidad es la de mantener el contacto con usted. Conforme a La Ley Orgánica 15/1999, usted puede ejercitar sus derechos de acceso, rectificación, cancelación y, en su caso oposición, enviando una solicitud por escrito a [email protected].
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
