Middletong: /* Solution */

2010-04-28T09:21:18Z

Solution

← Older revision		Revision as of 11:21, 28 April 2010
Line 37:		Line 37:
	<ADDRESS_EMAIL>.		<ADDRESS_EMAIL>.

	Additional tags <ADDRESS_CUST_GROUP> , <ADDRESS_LOAD_RATE> and <ADDRESS_UNLOAD_RATE> have also been added under RIO NW-7V4EKL and will also need populating here.		Additional tags <ADDRESS_CUST_GROUP> , <ADDRESS_LOAD_RATE> and <ADDRESS_UNLOAD_RATE> have also been added under RIO NW-7V4EKL and will also need populating here.

	When the new xsd is applied to the HCRTST database and subsequently the HCRPRD database then all of the existing Healthcare ESI flows will need updating not just the new Baxter ones being added as MTS / CIM / MIC will not be able to distinguish between Healthcare data and Baxter data.		When the new xsd is applied to the HCRTST database and subsequently the HCRPRD database then all of the existing Healthcare ESI flows will need updating not just the new Baxter ones being added as MTS / CIM / MIC will not be able to distinguish between Healthcare data and Baxter data.

Middletong: New page: =268477 - NW-7V4GMB/ Changes for XML to MIC v2.0= Copyright OBS Logistics © 2010 The information contained herein is the property of OBS Logistics and is supplied without liability for ...

2010-04-28T09:21:07Z

New page

=268477 - NW-7V4GMB/ Changes for XML to MIC v2.0=

Copyright OBS Logistics © 2010

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

=FUNCTIONAL OVERVIEW=

==Client Requirement==
The Microlise Journey Schedule Import interface is already provided in XML using the OBS TripOrder XSD format. This order interface already provides the full address information including an ID, name, address lines, town, county, country and postcodes.
The XSD needs to be modified to allow the following additional data fields to be passed:

<ORDER_HEADER_ADDRESS><LOCATION_TYPE> - this will allow location types data to be included for example HOSPITAL, PRIVATE, WHOLESALE or BRANCH, SUPPLIER, RDC

<ORDER_HEADER_ADDRESS><ADDRESS_CONTACT_FORENAME> - this will allow a contact forename to be included.

<ORDER_HEADER_ADDRESS><ADDRESS_CONTACT_SURNAME> - this will allow a contact surname to be included.

<ORDER_HEADER_ADDRESS><ADDRESS_CONTACT_NUMBER> - this will allow a mobile telephone number to be included.

<ORDER_HEADER_ADDRESS><ADDRESS_EMAIL> - this will allow an email address for the contact name to be included.

==Solution==

Create a new version (2.4) of TripOrder.xsd containing the requested new tags below the existing <ORDER_HEADER_ADDRESS> tag :-

<ADDRESS_LOC_TYPE>

<ADDRESS_CONTACT_FORENAME>

<ADDRESS_CONTACT_SURNAME>

<ADDRESS_CONTACT_NUMBER> and

<ADDRESS_EMAIL>.

Additional tags <ADDRESS_CUST_GROUP> , <ADDRESS_LOAD_RATE> and <ADDRESS_UNLOAD_RATE> have also been added under RIO NW-7V4EKL and will also need populating here.

When the new xsd is applied to the HCRTST database and subsequently the HCRPRD database then all of the existing Healthcare ESI flows will need updating not just the new Baxter ones being added as MTS / CIM / MIC will not be able to distinguish between Healthcare data and Baxter data.

==Scope==
Not Applicable no Spec written

==Data==
Not Applicable no Spec written

=FUNCTIONAL DESCRIPTION=
Not Applicable no Spec written

=REFERENCES=

Not Applicable no Spec written

=DOCUMENT HISTORY=

Not Applicable no Spec written

=AUTHORISED BY=

{| Border="1"
| '''''Matt Crisford'''''
| Development Manager
|

|-
| '''''Peter Greer'''''
| TMSCC MTS Product Manager
|

|}

268477 - Revision history

Middletong: /* Solution */

Middletong: New page: =268477 - NW-7V4GMB/ Changes for XML to MIC v2.0= Copyright OBS Logistics © 2010 The information contained herein is the property of OBS Logistics and is supplied without liability for ...