Thanks for all your replies! 馃槉

Attempt at summarising:

  *   DV_DURATION doesn鈥檛 support <>=~ at the moment, but there鈥檚 some SEC work 
underway to fix this.
  *   For now, using DV_QUANTITY with a property of time could do the trick.

Is this a good summary?

Regards,
Silje

From: openEHR-technical <[email protected]> On Behalf 
Of Diego Bosc谩
Sent: Tuesday, September 25, 2018 9:32 AM
To: For openEHR technical discussions <[email protected]>
Subject: Re: DV_DURATION and magnitude_status?

After rereading what Silje needed, I think the mentioned attribute would do the 
trick for her

However seems like we at SEC have work to do :)

El lun., 24 sept. 2018 a las 23:36, Pablo Pazos 
(<[email protected]<mailto:[email protected]>>) escribi贸:

On Mon, Sep 24, 2018 at 4:26 PM Thomas Beale 
<[email protected]<mailto:[email protected]>> wrote:


On 24/09/2018 16:19, Pablo Pazos wrote:
> I think there was a conversation about being able to constraint the
> magnitude of a DV_DURATION instead of the String expression. The issue
> was the magnitude is a function, not an attribute of DV_DURATION.

that is also my understanding...

I'm not sure if that was just a conversation or if we have a proposal from the 
SEC to make changes on that area, do you recall?


_______________________________________________
openEHR-technical mailing list
[email protected]<mailto:[email protected]>
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org


--
Ing. Pablo Pazos Guti茅rrez
[email protected]<mailto:[email protected]>
+598 99 043 145
skype: cabolabs
Subscribe to our newsletter<http://eepurl.com/b_w_tj>

[https://drive.google.com/uc?id=0B27lX-sxkymfM1pnTU44YXlFbHc&export=download]<https://cabolabs.com/>
http://www.cabolabs.com<http://www.cabolabs.com/>
https://cloudehrserver.com<https://cloudehrserver.com/>

_______________________________________________
openEHR-technical mailing list
[email protected]<mailto:[email protected]>
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org


--

[VeraTech for Health SL]<https://htmlsig.com/t/000001C268PZ>

[Twitter] <https://htmlsig.com/t/000001C47QQH>  [LinkedIn]  
<https://htmlsig.com/t/000001C4DPJG>  [Maps]  
<https://htmlsig.com/t/000001BZTWS7>
[https://s3.amazonaws.com/htmlsig-assets/spacer.gif]

Diego Bosc谩 Tom谩s / Senior developer
[email protected]<mailto:[email protected]>
[email protected]<mailto:[email protected]>

VeraTech for Health SL
+34 654604676<tel:+34%20654604676>
www.veratech.es<http://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]<mailto:[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

Reply via email to