Discussion:
OBX-2 and OBX-5 segments and "Data type error"
(too old to reply)
Eski
2009-02-19 11:32:36 UTC
Permalink
Hi colleagues!

I found from the web below discussion about HL7 accelerator and
BizTalk.

http://www.mombu.com/microsoft/biztalk-accelerator-hl7/t-ce-data-type-
in-obx5-causes-data-type-error-841448.html

I have exactly same problem than above link has discussed.

Well. When I handle some HL7 message (2.3.1) and OBX segment within BizTalk
and if there is OBX segment like below I got error "Data type error".
OBX|3|CE|ORGANISM|1|310784^SA||||||F|||20070531025 543+1000

As known OBX-2 tell datatypes for OBX-5. And OBX-5 is various field
(datatype is various for that). And as known HL7 accelerator 2.0 doesn't
support as default this feature (if I'm understood correctly). It seems that
I have to change native schema. And I think it's quite easy to change schema
to accept some known datatype. But I'd like that schema would be some kind
of dynamic that there would be whatever values which are support in HL7
(2.3.1).

And my question is that because there is no native support for OBX-5
handling so is everyone has made or changed this kind of schema that OBX-5
dynamically accept those datatypes which are supported within HL7? I'm very
happy if there examples exist already. Thank you, Eski
l***@gmail.com
2009-04-10 19:47:30 UTC
Permalink
Eski,

Did you ever find a solution? I have the same situation and am looking
for a solution.

The link you cited to www mombu.com doesn't work. However, I assume it
didn't have solution.

Regards,

bob L
Eski
2009-05-08 09:37:02 UTC
Permalink
Hi bob L!

I find one solution. But I think it's "quick and dirty". I was unable to
understand how change core schema to "dynamic" datatype so I changed "varies"
datatype to core schema to "CE". This was enough for me. But it have to
remember in future project that to core schemas has changed also. And maybe
it's not enought for future projects.
Marco
2009-07-16 08:24:01 UTC
Permalink
Hi everybody!
the "quick and dirty" solution will work until you will have to use a CE
data type for OBX.5.
But what if you have to use several OBX segments, each of them potentially
with a different data type?

Marco
Post by Eski
Hi bob L!
I find one solution. But I think it's "quick and dirty". I was unable to
understand how change core schema to "dynamic" datatype so I changed "varies"
datatype to core schema to "CE". This was enough for me. But it have to
remember in future project that to core schemas has changed also. And maybe
it's not enought for future projects.
Loading...