Re: ELEMENT.null_reason proposal

hnical [mailto:openehr-technical-boun...@lists.openehr.org] På vegne av David Moner Sendt: onsdag 25. januar 2017 14.24 Til: For openEHR technical discussions mailto:openehr-technical@lists.openehr.org>> Emne: Re: ELEMENT.null_reason proposal So, if I understand well, the idea is to add an attribute for

SV: ELEMENT.null_reason proposal

: ELEMENT.null_reason proposal So, if I understand well, the idea is to add an attribute for representing clinical reasons for a null flavor, maintaining the current null_flavor for technical reasons only. Is that right? 2017-01-25 13:34 GMT+01:00 Ian McNicoll mailto:i...@freshehr.com>>: Hi Diego, Th

Re: ELEMENT.null_reason proposal

So, if I understand well, the idea is to add an attribute for representing clinical reasons for a null flavor, maintaining the current null_flavor for technical reasons only. Is that right? 2017-01-25 13:34 GMT+01:00 Ian McNicoll : > Hi Diego, > > That's a pretty good suggestion, although in that

Re: ELEMENT.null_reason proposal

Diego, I think this is the same as * extending the current openEHR null_flavour code set, and making it hierarchical OR * allowing other local code-sets to be used in that slot. o if these codes were understood as proper local extensions of the openEHR code-set, i.e. any new cod

Re: ELEMENT.null_reason proposal

Hi Diego, That's a pretty good suggestion, although in that case we are really abandoning the idea of the current fixed base set of 'technical' null-flavours and allowing them to be replaced by local terms, while I was suggesting something more like the ISM_TRANSITION setup where archetype-specifi

Re: ELEMENT.null_reason proposal

If null_flavour is a DV_CODED_TEXT, what stops anyone to create an specialized archetype (directly from an rm class) that has the texts (+ codes) needed in a given country/use case? This probably should work even if set of null_flavour codes is fixed. I don't know if this would be enough, but in th

Re: ELEMENT.null_reason proposal

Hi Thomas, I agree that we should go ahead with this ASAP. However it might be worth a slight pause to think about the wider problem in handling 'clinical nulls'. To summarise, 'null flavours' have limited value in a great deal of clinical models because the standard set of null flavours, althoug

ELEMENT.null_reason proposal

Silje has just pinged me again on the question of whether we should have an ELEMENT.null-reason or similar attribute to accommodate specific reasons for null_flavour being set. There are 3 PRs on this as follows: * SPECPR-41 - Enable conten