I'm not really sure that it even means what we need in this case El lun., 24 sept. 2018 19:35, Diego Boscá <[email protected]> escribió:
> I've never understood the usefulness of that attribute: Seems strange to > populate an attribute that will end up in data with a value that could > provoke misunderstandings > > El lun., 24 sept. 2018 19:23, Ian McNicoll <[email protected]> escribió: > >> Hi Diego, >> >> Does DV_DURATION not inherit magnitude_status as a separate attribute >> from the RM? >> >> >> https://www.openehr.org/releases/trunk/UML/#Architecture___18_1_83e026d_1433773264460_352968_7042 >> >> Not sure it would work in archetyping constraint but in data it >> would/should just be >> >> value: "P24H" >> magnitude_status: "<" >> >> Ian >> >> Dr Ian McNicoll >> mobile +44 (0)775 209 7859 >> office +44 (0)1536 414994 >> skype: ianmcnicoll >> email: [email protected] >> twitter: @ianmcnicoll >> >> >> Co-Chair, openEHR Foundation [email protected] >> Director, freshEHR Clinical Informatics Ltd. >> Director, HANDIHealth CIC >> Hon. Senior Research Associate, CHIME, UCL >> >> >> On Mon, 24 Sep 2018 at 17:08, Diego Boscá <[email protected]> wrote: >> >>> Yeah, it is supported in 1.4. However, I'm not sure that that Durations >>> are the way to go here, as all the duration is constraint as string, which >>> means string lists or regex in best case scenario, which IMO makes pretty >>> difficult to represent the "<" or ">". Personally I would go with an >>> alternative of dv_quantity, as a single one with range is impossible to be >>> created if they don't share the same units. When validating, only one of >>> the alternatives needs to be valid, thus complying with the "or" >>> >>> >>> >>> El lun., 24 sept. 2018 a las 17:39, Pieter Bos (<[email protected]>) >>> escribió: >>> >>>> Not sure if this is already in the RM version you use and not sure if >>>> ADL 1.4 supports this, but can this be a DV_INTERVAL of DV_DURATION? >>>> >>>> Regards, >>>> >>>> Pieter Bos >>>> >>>> Op 24 sep. 2018 14:42 schreef "Bakke, Silje Ljosland" < >>>> [email protected]>: >>>> >>>> Hi, >>>> >>>> >>>> >>>> I’ve got a use case where we need to represent a time duration (of a >>>> symptom), which can be for example <24H or >3M. Is it possible to represent >>>> this using the DV_DURATION data type, like you can do with DV_QUANTITY and >>>> magnitude_status? If not, what should we do? >>>> >>>> >>>> >>>> Kind regards, >>>> Silje Ljosland Bakke >>>> >>>> >>>> >>>> Information Architect, RN >>>> >>>> Coordinator, National Editorial Board for Archetypes >>>> Nasjonal IKT HF, Norway >>>> >>>> Tel. +47 40203298 >>>> >>>> Web: http://arketyper.no<http://arketyper.no/> / Twitter: >>>> @arketyper_no<https://twitter.com/arketyper_no> >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 654604676 <+34%20654604676> >>> www.veratech.es >>> >>> La información contenida en este mensaje y/o archivo(s) adjunto(s), >>> enviada desde VERATECH FOR HEALTH, SL, es confidencial/privilegiada y está >>> destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Le >>> recordamos que sus datos han sido incorporados en el sistema de tratamiento >>> de VERATECH FOR HEALTH, SL y que siempre y cuando se cumplan los requisitos >>> exigidos por la normativa, usted podrá ejercer sus derechos de acceso, >>> rectificación, limitación de tratamiento, supresión, portabilidad y >>> oposición/revocación, en los términos que establece la normativa vigente en >>> materia de protección de datos, dirigiendo su petición a Avda Puerto 237, >>> 1º, pta 1 - 46011 Valencia o bien a través de correo electrónico >>> [email protected] >>> >>> Si usted lee este mensaje y no es el destinatario señalado, el empleado >>> o el agente responsable de entregar el mensaje al destinatario, o ha >>> recibido esta comunicación por error, le informamos que está totalmente >>> prohibida, y puede ser ilegal, cualquier divulgación, distribución o >>> reproducción de esta comunicación, y le rogamos que nos lo notifique >>> inmediatamente y nos devuelva el mensaje original a la dirección arriba >>> mencionada. Gracias >>> _______________________________________________ >>> 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
