Hi Ronald,
Thanks very much for this helpful review.
I'm still not sure how to interpret this. The v2.6 text seems to
address "what can go in a field". If there's no corresponding text for
"what can go in a component/subcomponent" (is there? I don't have
access to this spec) then I think this wou
[sorry for the slow reply - was offline for bit]
On Thu, Sep 13, 2007 at 11:29:09AM -0400, Bryan Tripp wrote:
> Hi Ronald,
>
> > I think there's a slight confusion regarding HL7 Null's: only a field
> > as a whole may be Null, not individual components. So, |""| says the
>
> Yes, I might be con
Hi Ronald,
> I think there's a slight confusion regarding HL7 Null's: only a field
> as a whole may be Null, not individual components. So, |""| says the
Yes, I might be confused about that. Can you give me a section reference?
Thanks,
Bryan
-
Hi Bryan,
On Wed, Sep 12, 2007 at 11:42:41AM -0400, Bryan Tripp wrote:
>
> Thanks for the explanations. I think I understand where you're coming
> from but I have a few more questions ...
>
> > 1. Checking for Null currently is hard, because you actually have
> >to check all parts in a c
Hi Ronald,
Thanks for the explanations. I think I understand where you're coming
from but I have a few more questions ...
> 1. Checking for Null currently is hard, because you actually have
>to check all parts in a composite type. E.g. for a field of type
>XPN you have to check that XPN.
Hi Bryan,
thanks for your reply.
On Mon, Sep 10, 2007 at 09:26:19AM -0400, Bryan Tripp wrote:
>
> I'm not sure I understand the motivation for handling them specially.
> Nulls (as opposed to empty fields) are to indicate that corresponding
> data should be deleted from the receiving applicati
Hi Ronald,
I'm not sure I understand the motivation for handling them specially.
Nulls (as opposed to empty fields) are to indicate that corresponding
data should be deleted from the receiving application. This is
supported -- if a field contains "\"\"" then the application should
delete data -- b
7 matches
Mail list logo
