OHMPI Broadcast Messages Not To XML Standard (Doc ID 2273452.1)

Last updated on JUNE 22, 2017

Applies to:

Oracle Healthcare Master Person Index - Version 4.0.1.1 and later
Information in this document applies to any platform.

Symptoms

On : 4.0.1.1 version, Master Index Data Quality

ACTUAL BEHAVIOR
---------------
Customer reported that the date and date/time fields in the broadcast messages are not in the XML standard format. This means that they do not parse against the generated XSD.

The fields are implemented as attributes, and are produced in the format "xx/xx/yyyy hh:mm:ss". I believe the xx/xx portion of the date matches the date format specified in the object model (eg. either dd/mm/yyyy or mm/dd/yyyy). This is not the XML standard. The XML standard is "yyyy-mm-ddThh:mm:ss"

In addition, if a date or date/time field is null, it is being produced as datefield="". Again, this is not the XML standard. The correct format should be datefield=.

EXPECTED BEHAVIOR
-----------------------
Customer expects the date and date/time fields in the broadcast message should be in the XML standard format.

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