A User Defined HL7 OTD Does not Parse The OBR-13 Segment Properly (Doc ID 1607688.1)

Last updated on DECEMBER 16, 2013

Applies to:

Oracle Java CAPS Enterprise Service Bus - Version R6.3 and later
Information in this document applies to any platform.

Symptoms

A user defined HL7 OTD doesn't always parse the OBR-13 segment properly.  This OTD will sometimes incorrectly unmarshall the OBR segment. Starting around OBR-13 the fields will be shifted off by one.

An example of the data in OBR-13, that does not parse would be:

    |~^SCREENING MAMMOGRAM~^N~^Y~^N~^Y|

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms