[InterSystems-EnsHlth] Split HL7 message onto multiple transactions Part II

[M. Kurz]

Hi,

this question refers to another thread openend on June 23, 2009, which
is already closed:
http://groups.google.com/group/Ensemble-in-Healthcare/browse_thread/thread/d594ed64624bd9ec/9dc8e3c26cf643f9?hl=de&lnk=gst&q=multiple#9dc8e3c26cf643f9

I also need to split an ORM O01 message into multiple messages with 1
ordered service ORC-OBR each.

I find Yuriy's solution very elegant, and I would like to use it.
I would like it even better if I only had to misuse 1 MSH field and
was able
to count the number of OBR segments dynamically in the condition of
the rule,
like:
if HL7.{MSH:13} < HL7.{ORCgrp}.Count

Is there a way to phrase such a condition

--
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare Community" group.
To post to this group, send email to Ensemble-in...@googlegroups.com
To unsubscribe from this group, send email to Ensemble-in-Healt...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Ensemble-in-Healthcare?hl=en

[Ted Peck]

I hope this answers your question: we support a * character at almost every
level of potential repetition in an HL7 schema. It means what is the
repetition count at that location.
For the example you give, it would be:

If HL7.{MSH:13} < HL7.{ORCgrp(*)}

We recently noticed that this feature is not well documented and we are
planning to improve that.
Hope this helps,
Ted

PS. Also note that HL7.{*} will give you the total segment count, HL7.{1:*}
will give you the number of fields in MSH, and HL7.{3:3(*)} will give you
the number of array elements in PID:3 if segment 3 is a PID. In other words
the * syntax works on index property paths that are not schema-based as well
as schema-based property paths.

[M. Kurz]

Thanks, this is superb!!!

regards,

Michaela