Community Care Access Centre (CCAC)
Equipment and Supply Order
Format Specification
Organization:
Ontario Association of Community
Care Access Centres (OACCAC)
Division:
IS/IT
Version:
2.14
Version Date:
May 5, 2010
Prepared By:
Ion Moraru
Updated By:
Arthur Bydon
Ellen Hsu
Version:
Equipment and Supply Order Format Specification
2.14
Version Date: May 5, 2010
Revision Log
Version
No.
Version Date
Summary of Change
Changed by /
Input from
0.1
October 26, 2007
First draft
Guy Fortin
1.1
November 1, 2007
Changed valid value list for OrderAction
Nasreen Pirani
LineItemUnitCode changed from mandatory to
optional
ItemChargeAmount changed from mandatory to
optional (only valid for Finance types of orders)
1.2
December 4, 2007
Change VendorContractCode to ContractCode
Guy Fortin
Move VerbalOrder and ClientPickUp attributes
from EquipmentAndSupplyOrder element to
EquipmentAndSupplyItem element
Remove School element
Make RentalStartDate optional and add
comment that its : optional (preferred blank) if
"EndItem" OrderAction and Mandatory if
OrderAction is "Initial"
Make RentalEndDate optional and add
comment that its : optional (preferred blank) if
"Initial" OrderAction and Mandatory if
OrderAction is "EndItem"
Valid values for ItemStatus reduced to include
only: "Ordered", "Cancelled", "Removed"
Add a Date and Time description in Chapter 2
Add Appendix that lists all valid language codes
and reduced PreferredLanguage attribute to 3
bytes
Rename OrderAction to RequestType (so its
consistent with Referral RequestType)
2.0
Jan. 23, 2008
Combined DeliveryDate and DeliveryTime into
DeliveryDateTime in EquipmentAndSupplyOrder
element
Added ShippingAddress to
Date: May 7, 2010
2
Guy Fortin
Version:
Equipment and Supply Order Format Specification
Version
No.
Version Date
2.14
Version Date: May 5, 2010
Summary of Change
Changed by /
Input from
EquipmentAndSupplyOrder element
Moved ContractCode from
EquipmentAndSupplyOrder element to
EquipmentAndSupplyItem element
Moved GeopgraphicalArea from Client element
to EquipmentAndSupplyItem element
Removed ContactType and IsPrimary from
PhoneContact element
Change TelephoneNumber from an element to
a single Alpha / Num
Changed ItemDescription from Mandatory to
optional in EquipmentAndSupplyItem element
Add StatusChangeDate to
EquipmentAndSupplyItem element
2.1
Feb 7, 2008
Added OrganizationCode to
EquipmentAndSupplyOrder element
Deleted Vendor Element from
EquipmentAndSupplyOrder element
Added Requestor Element, moved CCACContact
element into it, changed fields within
CCACContact element, and added a new
ProviderContact element
Added VerbalOrderConfirmation, SentDateTime
and LastSentDateTIme to
EquipmentAndSupplyOrder element
Added Delivery element, with an IsClientPickup
attribute, to encapsulate all of the delivery
fields; deleted ClientPickupInstructions
Added ResidenceCode, Province and
AddtionalInfo fields to Address element and
made StreetNumber, StreetName. PostalCode,
and City mandatory
Deleted PreferredNamefrom
ClientDemographics
Add Contact element within PrimaryContacts
element to hold all of the Contact fields
Made ClientRelationship, Role, and LegalRole
Date: May 7, 2010
3
Guy Fortin
Version:
Equipment and Supply Order Format Specification
Version
No.
Version Date
Version Date: May 5, 2010
Summary of Change
mandatory in ClientContacts
Changed SpecialtyCode to SpecialtyDescription
in Physician element
Moved VerbalOrder and ClientPickup attributes
from line itme to top Element
Made ContractCode Mandatory, added
ContractDescription to line item
Added RentalPeriod element to contain all
rental period fields; added FollowUpDate to
RentalPeriod
2.2
Feb 7, 2008
Synch version number with XML file version
2.3
Feb 22, 2008
Made ReferalCaseloadTeam, ContactName
Optional in CcacContact and ProviderContact
Changed IsVeteran and IsSmoker from a field to
an attribute of the Client element (removed
SpecialStatus and clientCharacteristics)
Deleted ClientDemographics elements, and
promoted all fields to Client element
Made DateOfBirth, Gender, MaritalStatus, and
LivingArrangement Mandatory in Client
element
Added Comments to Address element
Made ContactAddress, ContactPhone, adn
RiscCode Optional
Made LineItemUnitCode, RentalStartDate
Mandatory
Added VendorAction element, move field
ActionRequired into it and added ActionDate
2.4
Feb 22, 2008
Added updated diagrams for condensed XML
2.5
March 3, 2008
Reflect feedback from CHRIS Team Review
-
Date: May 7, 2010
2.14
Renamed ProviderName to
OrganizationName in ProvidedContact
element
4
Changed by /
Input from
Version:
Equipment and Supply Order Format Specification
Version
No.
Version Date
Version Date: May 5, 2010
Summary of Change
-
Made LastSendDateTime optional
-
Added EnRentalPickupAddress
-
In Address element: deleted Comments;
Renamed FreeLine to AddressSummary;
-
Deleted RecordType and ItemOrderType
attributes, and GeographicalArea from
EquipementAndSupplyItem element
Deleted FollowUpDate from RetalPeriod
element
-
2.14
2.6
March 7, 2008
Renamed ClientReferralCode to
BillingReferenceNumber
2.7
May 27, 2008
Added RecordType attribute at the Line Item
level
Changed by /
Input from
Ion Moraru
Moved EndRentalPickUpAddress element from
the Order level to the line item level.
2.8
June 12, 2008
Renamed PurchaseOrderDate to
PurchaseOrderDateTime and
PurchaseOrderCancelDate to
PurchaseOrderCancelDateTime.
Added TransimissionDateTime.
Removed SendDateTime and
LastSendDateTime.
Moved CaseloadCaseManagerName and
ReferralCaseloadTeam into a new element –
CCACContact.
Turned the Requestor complex element into an
element choice (ProviderRequestor and
CCACRequestor).
Renamed the Delivery element to
DeliveryOrPickup and turned it into a choice
element for: Delivery, ClientPickUp and
EndRentalPickUp (removed the
EndRentalPickup address from the line item
level). It is assumed that many (one or more)
end rental items can be sent within the same
transmittal as long as the pickup address is the
same.
Date: May 7, 2010
5
Ion Moraru
Version:
Equipment and Supply Order Format Specification
Version
No.
Version Date
2.14
Version Date: May 5, 2010
Summary of Change
Changed by /
Input from
Removed Client Attributes: IsVeteran, IsSmoker
Removed Client Elements: ClientAdmitDate,
LivingArrangements, MaritalStatus, DateOfBirth
and PersonalContacts.
Removed LineItem elements: VendorAction,
EndRentalPickUpAddress, BillingMethod.
2.10
May 4, 2009
Reorganized the Order elements.
Ion Moraru
Added HealthCard element.
Removed ItemInstructions (Line Item level)
Added VendorInstructions (Line Item level)
Added EquipmentDischargeDisposition (Line
item level)
2.11
June 9, 2009
Added AdditionalInformation (Line Item level)
Nasreen Pirani
2.12
August 19, 2009
Change the RequestType, Address.Type and
PhoneLocation values to be in sync with CHRIS
values
Ion Moraru
2.13
December 9, 2009
Add Sender and Destination elements that
describe the participants in the message
exchange
Arthur Bydon
2.14
May 5, 2010
Add Extension to Client Phone and Medical
Contact
Ellen Hsu
Address:
- Change Type “Alternate” to “Other”;
- Remove Residence Code;
- Add room number and country
Date: May 7, 2010
6
Version:
Equipment and Supply Order Format Specification
2.14
Version Date: May 5, 2010
Table of Contents
1.
Equipment and Supply Order ................................................................................... 8
1.1
1.2
2.
Brief Description
High Level Structure of the EquipmentAndSupplyOrder
8
8
Equipment and Supply Order Elements.................................................................... 9
2.1
2.2
2.3
2.4
2.5
EquipmentAndSupplyOrder element detail
Order element detail
CCAC Contact element detail
Client element detail
2.4.1 Address element detail
EquipmentAndSupplyItem element detail
9
11
13
14
17
19
3.
Appendix A - ISO 639-2 Language Codes.............................................................. 21
4.
Appendix A - Distilled XML Schema ....................................................................... 35
4.1
Equipment And Supply Order
Date: May 7, 2010
35
7
Version:
Equipment and Supply Order Format Specification
2.14
Version Date: May 5, 2010
1. Equipment and Supply Order
1.1 Brief Description
Once the Service Plan for a Client has been determined, the CCAC will issue Equipment and
Medical Supply orders to the appropriate vendors to implement the plan.
This document specifies the information and associated format of the Equipment And Supply
Order that flows from the CCAC to the Vendor.
1.2 High Level Structure of the EquipmentAndSupplyOrder
The EquipmentAndSupplyOrder is an XML document with the following high level element
structure:
Figure 1 Equipment and Supply Order Structure
EquiomentAndSupplyOrder
(One only)
EquipmentAndSupplyItem
(One of Several)
Client
(One only)
Order
(One only )
CCACContact
(One only)
As the diagram above depicts, a EquipmentAndSupplyOrder element contains a single Client
element and one or more EquipmentAndSupplyItem elements. These are the primary elements
that make up the Equipment & Supply Order and below there is a section for each of them that
describes all of the information they contain.
Date: May 7, 2010
8
Version:
Equipment and Supply Order Format Specification
2.14
Version Date: May 5, 2010
2. Equipment and Supply Order Elements
The following tables detail the fields contained within the elements that make up a Equipment and Supply
Order as outlined in the structure diagram in the previous section.
A note about Date and Time specification:
All dates and times contained in the specification adhere to the W3C Universal Time Code (UTC)
standard and are formatted as follows:

date: yyyy-mm-dd (size 10 bytes); e.g. 2007-11-21

datetime: yyyy-mm-ddThh:mm[:ssTZD]; (size 16 bytes - if omitting ss and TZD - and 25 bytes
with ss and TZD); e.g. 2007-11-21T14:56:19-05:00 (for EST timezone)

time: hh:mm[:ssTZD] (size 5 - if omitting ss and TZD - and 14 bytes with ss and TZD); e.g.
14:56:19-05:00
Where "yyyy" represents the year, "mm" the month from 01 through 12, "dd" the day of the month,
"T" separates the date from the time, "hh" the hour from 00 through 24, "mm" the minutes, "ss" the
seconds and TZD represents the timezone which reflect the times difference relative to GMT, so it
can range from +12:00 to -13:00; both "ss" and TZD are optional; TZD is not yet supported by this
specification.
2.1 EquipmentAndSupplyOrder element detail
Name
Version (Attribute of
EquipmentAndSupplyOrder
element)
Field
Type
Length
(bytes)
Mandatory Description
Max 10
Alpha /
num
Yes
The version of the Schema that this
EquipmentAndSupplyOrder element
adheres to. E.g. "1.0". This is required
for the receiving provider to correctly
interpret the information being provided
by the CCAC
36
Alpha/
Num
(GUID)
Yes
The unique identifier of the message
that can be used for tracking
Sender (parent element)
-
-
Yes
A group of elements and attributes
identifying the sender of the document.
Destination (parent element)
-
-
Yes
A group of elements and attributes
identifying the recipient of the document
MessageTrackingId
Date: May 7, 2010
9
Version:
Equipment and Supply Order Format Specification
Organization (child element of
Sender or Destination)
2.14
Version Date: May 5, 2010
-
-
Yes
Identifies the organization sending or
receiving the document
Code (attribute of Organization)
50
Alpha/
Num
Yes
Specifies the unique code of the sender
or the recipient organization
Type (attribute of Organization)
150
Alpha/
Num
Yes
Specifies the type of the sender
organization. Valid content is:
“CCAC”
“Provider”
“Vendor”
Name (child of Organization)
250
Alpha
No
The name of the sender or the recipient
organization
OwnerOrganization (child of
Organization)
-
-
Yes
Specifies the owner organization of the
sender or the recipient
Code (attribute of
OwnerOrganization)
50
Alpha/
Num
Yes
Specifies the unique code of the sender
or the recipient owner organization
Type (attribute of
OwnerOrganization)
150
Alpha/
Num
No
Specifies the type of the sender or the
recipient owner organization. Valid
content is “CCAC”, “Provider” or
“Vendor”. If not provided the “CCAC”
type is assumed.
Name (child element of
OwnerOrganization)
250
Alpha
No
The name of the sender or the recipient
owner organization
CcacCode
2-4
Alpha
Yes
A unique number for the CCAC. Valid
values are:
"ES"
“SW"
"WW"
"HNHB"
"CW"
"MH"
"TC"
"CENT"
"CE"
"SE"
"CHAM"
"NSM"
"NE"
"NW"
Date: May 7, 2010
10
Version:
Equipment and Supply Order Format Specification
TransimissionDateTime
20
2.14
Version Date: May 5, 2010
DateTi
me
Yes
Date when the transmittal was sent
2.2 Order element detail
Order (element)
-
Element
Yes
The order header information
Max 15
Alpha /
num
Yes
The Purchase Order number provided
by the CCAC
PurchaseOrderDateTime
20
DateTime
Yes
Date when the Purchase Order was
created
PurchaseOrderCancelDateTime
20
DateTime
No
The date when the Purchase Order
was cancelled, if applicable
RequestType
25
Alpha /
num
Yes
Defines the type of action for the Order;
can be set to one of the following
values:
PurchaseOrderNumber
"E &
"E &
"E &
"E &
"E &
"E &
OrganizationCode
10
S
S
S
S
S
S
- Initial Order"
- Cancel Order"
- Resending PO"
- Cancel Line Item"
- End Rental"
- Finance Charge Update"
Num
Yes
A unique number assigned to Vendor
by local CCAC. Reference may be
“vendor” organization
Element
(Choice)
Yes
The party who is requesting this
equipment or supply. This may be
either a CCAC person or a Provider
RequestorType
Attribute
Yes
“CCAC” or “Provider”
ProviderRequestor
Element
No
The Provider requesting the items
Requestor (element)
Date: May 7, 2010
OrganizationName
25
Alpha /
num
Yes
The name of the Provider Organization
who is requesting the order
ContactName
25
Alpha /
num
No
The name of the person who is
requesting the order
11
Version:
Equipment and Supply Order Format Specification
ContactPhoneNumber
15
CCACRequestor
2.14
Version Date: May 5, 2010
Alpha /
Num
No
The telephone number for the contact
person.
Element
No
Indicates the CCAC is requesting the
items
ContactName
25
Alpha /
num
Yes
The name of the CCAC person who is
requesting the order
ContactPhoneNumber
15
Alpha /
Num
No
The telephone number.
1
Boolean
Yes
Indicates if this order has had a verbal
confirmation with the supplier
Element
(Choice)
Yes
This element wraps the entire Delivery
or Pickup information. This is a choice
of: Delivery content if the order is to be
delivered to a certain address, Client
Pickup content in case the order will be
picked up by the Client or
EndRentalPickup content in case of an
EndRental transmittal which will be
used by the Vendor for their pickup
process.
Element
Yes
Indicates the order will be delivered by
the vendor.
VerbalOderConfirmation
DeliveryOrPickUp (element)
Delivery
DeliveryDateTime
20
DateTime
Yes
Date and Time the equipment is to be
delivered.
DeliveryTimeInstructions
250
Alpha /
num
No
Additional delivery instructions
DeliveryPriority
25
Alpha /
num
Yes
DeliveryPriorityInstructions
250
Alpha /
num
No
Additional instructions associated with
the Delivery Priority
ShippingAddress (element)
-
Element
Yes
The shipping address (see Address
element below for details)
Date: May 7, 2010
12
The overall priority of this order. Can be
set to one of the following values:
"Normal"
"Same Day"
"Urgent"
Version:
Equipment and Supply Order Format Specification
ClientPickUp
2.14
Version Date: May 5, 2010
Element
Yes
Indicates the order will be picked up by
the client.
PickUpDateTime
25
DateTime
Yes
The date and time the client is
supposed to pick up the items.
PickUpInstructions
250
Alpha /
Num
No
Pick Up Instructions associated with
the Client
2.3 CCAC Contact element detail
Name
Field
Type
Length
(bytes)
CcacContact (element)
Mandatory Description
-
Element
Yes
The contact in the CCAC for this
order
CaseloadCaseManagerName
25
Alpha /
num
Yes
The Case Manager associated with
this Order
ReferalCaseloadTeam
25
Alpha /
num
Yes
The CCAC Team associated with
this Order
Date: May 7, 2010
13
Version:
Equipment and Supply Order Format Specification
2.14
Version Date: May 5, 2010
2.4 Client element detail
The Client element provides information about the person that is to receive the equipment or
medical supply.
Name
Field
Length
(bytes)
Type
Mandatory Description
ClientIdentifier
15
Alpha /
num
Yes
An identifier that uniquely identifies
this client to the CCAC
BillingReferenceNumber
12
Alpha /
num
Yes
A code that identifies the Client
Referral that is associated with this
order.
FirstName
25
Alpha
Yes
Client’s legal first name
SurName
25
Alpha
Yes
Client legal last name / surname
PreferredLanguage
3
Alpha
No
Language in which the client would
prefer to communicate for service
provision; see Appendix A for a list of
valid ISO 639-2 language codes
Gender
25
Alpha
Yes
One of :
"Male"
"Female"
"Undifferentiated"
"Unknown"
HealthCard (element)
-
element
No
Client's Health Card information (will
be blank until approved)
HCN
10
Numeric
Yes
Health Card Number
VC
2
Alpha
Yes
Version Code
ExpiryDate
-
DateTime
No
HC expiry date
Name
50
Alpha
No
Client name if different than Surname
-
element
Yes
The client's address (see Address
element below for details)
ClientAddress (element)
Date: May 7, 2010
14
Version:
Equipment and Supply Order Format Specification
ClientPhone (element)
-
Phone
PhoneLocation
20
2.14
Version Date: May 5, 2010
element
Yes
element
Yes
Alpha
Yes
Contains a list of client phone
numbers
One of
"Home”
“Work”
“Mobile”
“Other"
TelephoneNumber
15
Alpha /
Num
Yes
The telephone number.
Extension
10
Alpha /
Num
No
Extension for the telephone number
-
element
No
The list of medical contacts
(Physicians or Practitioner Nurses)
that are attending to the client.
MedicalContacts (element)
Physician (element)
element
TypeOfContact (attribute)
25
Alpha
No
The type of Physician; one of:
"Family"
"Attending"
"Referring"
"Specialist"
ContactFirstName
25
Alpha
Yes
Contacts first name
ContactSurName
25
Alpha
Yes
Contacts last name
ContactAddress
(subelement)
-
element
No
The contact's address (see Address
element below for details)
ContactPhone
-
element
No
The contact's phone number
TelephoneNumber
15
Alpha /
Num
Yes
The telephone number.
Extension
10
Alpha /
Num
No
Extension for the telephone number
Date: May 7, 2010
15
Version:
Equipment and Supply Order Format Specification
Specialities
(subelement)
SpecialtyDescription
ActiveClientRiskCodes
(element)
Version Date: May 5, 2010
-
element
No
A list of the Physician's specialties
(from a provincially maintained table of
specialties); Each Specialty contains
the following attributes...
50
Alpha /
num
No
A description of the specialty
-
element
No
The list of client active Risk Codes.
element
No
RiskCodeItem (collection
element)
RiskCode
10
Alpha /
num
Yes
AdditionalInformation
250
Alpha
No
Date: May 7, 2010
2.14
16
Risk code that identifies a risk of
importance related to the client (only
active codes are being sent)
Version:
Equipment and Supply Order Format Specification
2.4.1
2.14
Version Date: May 5, 2010
Address element detail
The Address element defines all of the fields available for specifying a physical address.
Name
Field
Length
(bytes)
Type
Mandatory
Description
AddressSummary
250
Alpha /
num
No
If the address cannot be specified for
any reason this allow manual entry of
address; may also contain a summary
of the address below.
Type
50
Alpha
Yes
The type of address that is being
specified; one of:
"Home"
"Mailing"
"Shipping"
"Other"
E&S Order Release 1.0 will use only
“Home”
BuildingName
50
Alpha
No
Used for organizational addresses
Name of LTC home / Retirement home
/ hospital in which the client resides
RoomNumber
6
Alpha /
num
No
The room number if applicable
SuiteNumber
6
Alpha /
num
No
The suite number if applicable
StreetNumber
6
Alpha /
num
Yes
The associated street number
StreetName
100
Alpha /
num
Yes
The name of the street the client
resides at
PostalCode
10
Alpha /
num
Yes
The associated postal code
City
50
Alpha /
num
Yes
The associated city
Date: May 7, 2010
17
Version:
Equipment and Supply Order Format Specification
2.14
Version Date: May 5, 2010
Province
25
Alpha /
num
No
Assumed to be Ontario if not present
Country
50
Alpha /
num
No
The associated country
Directions
250
Alpha /
num
No
The intent is to provide any necessary
information to assist the service
provider to drive to the client address.
This could include closest major
intersection to the address being
recorded or other driving instructions
AdditionalInfo
250
Alpha /
num
No
Additional information about the
location
Date: May 7, 2010
18
Version:
Equipment and Supply Order Format Specification
2.14
Version Date: May 5, 2010
2.5 EquipmentAndSupplyItem element detail
Name
Field
Length
(bytes)
Type
Mandatory Description
LineItemType (attribute of
EquipmentAndSupplyItem)
Max 10
Alpha
Yes
RecordType (attribute of
EquipmentAndSupplyItem)
Max 10
Alpha
Yes
PurchaseOrderLineNumber
Max 15
Alpha /
num
Yes
The code that identifies this Line
Number to the CCAC; provided by the
CCAC at time of order
ContractCode
Max 15
Num
Yes
Contract Number assigned to the
Vendor by the CCAC when the contract
was entered into
No
The description of the Contract
ContractName
Identifies this Line Item as either a
"Rental"
"Purchase"
“Finance Charge”
Identifies this Line Item as either an
"Equipment"
"Supply"
VendorItemCode
Max 15
Alpha /
num
Yes
The code that identifies the specific item
ordered
ItemClass
Max 15
Alpha /
num
Yes
Identifies this item as either a
"Normal"
"Exception"
LineItemUnitCode
Max 10
Alpha
Yes
FUTURE (always set to "unit"
initially)Code for the units in which the
item is to be delivered (e.g., EACH,
CASE, BOX, SET, DOZ, GROSS)
ItemDescription
Max 50
Alpha
Yes
A description of the item
element
No
DateTime
Yes
RentalPeriod
RentalStartDate
Date: May 7, 2010
10
19
Date rental is to start; optional (preferred
blank) if "EndItem" OrderAction and
Mandatory if OrderAction is "Initial"
Version:
Equipment and Supply Order Format Specification
RentalEndDate
ItemStatus
2.14
Version Date: May 5, 2010
10
DateTime
No
Date rental is to end; optional (preferred
blank) if "Initial" OrderAction and
Mandatory if OrderAction is "EndItem"
15
Alpha
Yes
Identifies this item as
"Ordered"
"Cancelled"
"Removed"
ItemStatusChangeDateTime
25
DateTime
Yes
The date the ItemStatus was last
changed. Optional on “Ordered”.
OrderedDateTime
25
DateTime
Yes
The date the item was ordered initially.
ItemQuantity
Max 10
Num
Yes
The number of items ordered. If the item
type is rental or finance-charge the
quantity will always be 1.
ItemChargeAmount
Max 20
Num
No
The amount the item costs; Sent only if
LineItemType is "Finance Charge"
VendorInstructions
512
Alpha
No
Future use (CHRIS 1.3)
-
element
No
Future use (CHRIS 1.3). Carries
additional information about End Rental
items.
DispositionCode
20
Alpha /
Num
Yes
Future use (CHRIS 1.3)
DispositionDescription
100
Alpha
Yes
Future use (CHRIS 1.3)
AdditionalInformation
300
Alpha /
Num
No
This is matching the Additional
Information in CHRIS (line items).
EquipmentDischargeDisposition
Date: May 7, 2010
20
Version:
Equipment and Supply Order Format Specification
Version Date: May 5, 2010
3. Appendix A - ISO 639-2 Language Codes
Afar
Code
ISO
639-2
AAR
Abkhazian
ABK
Achinese
ACE
Acoli
ACH
Adangme
ADA
Adyghe
ADY
Afrihili
AFH
Afrikaans
AFR
Afro-Asiatic (Other)
AFA
Ainu
AIN
Akan
AKA
Akkadian
AKK
Albanian
SQI
Aleut
ALE
Algonquian Languages
ALG
Altaic (Other)
TUT
Amharic
AMH
Angika
ANP
Apache Languages
APA
Arabic
ARA
Aramaic
ARC
Arapaho
ARP
Araucanian
ARN
Arawak
ARW
Argonese
ARG
Armenian
HYE
Aromanian
RUP
Artificial (Other)
ART
Assamese
ASM
Asturian
AST
Athapascan Languages
ATH
Value
Date: May 7, 2010
2.14
21
Version:
Equipment and Supply Order Format Specification
Version Date: May 5, 2010
Australian Languages
Code
ISO
639-2
AUS
Austronesian (Other)
MAP
Avaric
AVA
Avestan
AVE
Awadhi
AWA
Aymara
AYM
Azerbaijani
AZE
Balinese
BAN
Baltic (Other)
BAT
Baluchi
BAL
Bambara
BAM
Bamileke Languages
BAI
Banda
BAD
Bantu (Other)
BNT
Basa
BAS
Bashkir
BAK
Basque
EUS
Batak (Indonesia)
BTK
Beja
BEJ
Belarusian
BEL
Bemba
BEM
Bengali
BEN
Berber (Other)
BER
Bhojpuri
BHO
Bihari
BIH
Bikol
BIK
Bini
BIN
Bislama
BIS
Blin
BYN
Bokmål, Norwegian
NOB
Bosnian
BOS
Braj
BRA
Breton
BRE
Buginese
BUG
Bulgarian
BUL
Value
Date: May 7, 2010
2.14
22
Version:
Equipment and Supply Order Format Specification
Version Date: May 5, 2010
Buriat
Code
ISO
639-2
BUA
Burmese
MYA
Caddo
CAD
Cantonese
QYU
Carib
CAR
Catalan
CAT
Caucasian (Other)
CAU
Cebuano
CEB
Celtic (Other)
CEL
Central American Indian (Other)
CAI
Chagatai
CHG
Chamic Languages
CMC
Chamorro
CHA
Chechen
CHE
Cherokee
CHR
Cheyenne
CHY
Chibcha
CHB
Chichewa
NYA
Chinese
ZHO
Chinook Jargon
CHN
Chipewyan
CHP
Choctaw
CHO
Chuukese
CHK
Chuvash
CHV
Classical Nepal Bhasa
NWC
Coptic
COP
Cornish
COR
Corsican
COS
Cree
CRE
Creek
MUS
Creoles And Pidgins (Other)
CRP
Creoles And Pidgins, EnglishBased (Other)
Creoles And Pidgins, FrenchBased (Other)
CPE
Value
Date: May 7, 2010
2.14
23
CPF
Version:
Equipment and Supply Order Format Specification
Version Date: May 5, 2010
Value
Creoles And Pidgins,
Portuguese-Based (Other)
Crimean Tatar
Date: May 7, 2010
2.14
Code
ISO
639-2
CPP
CRH
Croatian
HRV
Cushitic (Other)
CUS
Czech
CES
Dakota
DAK
Danish
DAN
Dargwa
DAR
Dari
PRS
Dayak
DAY
Delaware
DEL
Dhivehi
DIV
Dinka
DIN
Dogri
DOI
Dogrib
DGR
Dravidian (Other)
DRA
Duala
DUA
Dutch
NLD
Dyula
DYU
Dzongkha
DZO
Eastern Frisian
FRS
Efik
EFI
Egyptian (Ancient)
EGY
Ekajuk
EKA
Elamite
ELX
English
ENG
Erzya
MYV
Esperanto
EPO
Estonian
EST
Ewe
EWE
Ewondo
EWO
Fang
FAN
Fanti
FAT
Faroese
FAO
24
Version:
Equipment and Supply Order Format Specification
Version Date: May 5, 2010
Fijian
Code
ISO
639-2
FIJ
Filipino; Pilipino
FIL
Finnish
FIN
Finno-Ugrian (Other)
FIU
Fon
FON
French
FRA
Friulian
FUR
Fulah
FUL
Ga
GAA
Gaelic
GLA
Gallegan
GLG
Ganda
LUG
Gayo
GAY
Gbaya
GBA
Geez
GEZ
Georgian
KAT
German
DEU
Germanic (Other)
GEM
Gikuyu
KIK
Gilbertese
GIL
Gondi
GON
Gorontalo
GOR
Gothic
GOT
Grebo
GRB
Greek
ELL
Guarani
GRN
Gujarati
GUJ
Gwich'in
GWI
Haida
HAI
Haitian Creole
HAT
Hausa
HAU
Hawaiian
HAW
Hebrew
HEB
Herero
HER
Hiligaynon
HIL
Value
Date: May 7, 2010
2.14
25
Version:
Equipment and Supply Order Format Specification
Version Date: May 5, 2010
Himachali
Code
ISO
639-2
HIM
Hindi
HIN
Hiri Motu
HMO
Hittite
HIT
Hmong
HMN
Hungarian
HUN
Hupa
HUP
Iban
IBA
Icelandic
ISL
Ido
IDO
Igbo
IBO
Ijo
IJO
Iloko
ILO
Inari Sami
SMN
Indic (Other)
INC
Indo-European (Other)
INE
Indonesian
IND
Ingush
INH
Interlingua (International
Auxiliary Lang. Assoc.)
Interlingue
INA
Inuktitut
IKU
Inupiaq
IPK
Iranian (Other)
IRA
Irish
GLE
Iroquoian Languages
IRO
Italian
ITA
Japanese
JPN
Javanese
JAV
Judeo-Arabic
JRB
Judeo-Persian
JPR
Kabardian
KBD
Kabyle
KAB
Kachin
KAC
Kalaallisut
KAL
Value
Date: May 7, 2010
2.14
26
ILE
Version:
Equipment and Supply Order Format Specification
Version Date: May 5, 2010
Kalmyk
Code
ISO
639-2
XAL
Kamba
KAM
Kannada
KAN
Kanuri
KAU
Karachay-Balkar
KRC
Kara-Kalpak
KAA
Karelian
KRL
Karen
KAR
Kashmiri
KAS
Kashubian
CSB
Kawi
KAW
Kazakh
KAZ
Khasi
KHA
Khmer
KHM
Khoisan (Other)
KHI
Khotanese
KHO
Kimbundu
KMB
Kinyarwanda
KIN
Kirghiz
KIR
Klingon
TLH
Komi
KOM
Kongo
KON
Konkani
KOK
Korean
KOR
Kosraean
KOS
Kpelle
KPE
Kru
KRO
Kumyk
KUM
Kurdish
KUR
Kurukh
KRU
Kutenai
KUT
Kwanyama
KUA
Ladino
LAD
Lahnda
LAH
Lamba
LAM
Value
Date: May 7, 2010
2.14
27
Version:
Equipment and Supply Order Format Specification
Version Date: May 5, 2010
Lao
Code
ISO
639-2
LAO
Latin
LAT
Latvian
LAV
Lezghian
LEZ
Limburgish
LIM
Lingala
LIN
Lithuanian
LIT
Lojban
JBO
Low German
NDS
Lower Sorbian
DSB
Lozi
LOZ
Luba-Katanga
LUB
Luba-Lulua
LUA
Luiseno
LUI
Lule Sami
SMJ
Lunda
LUN
Luo (Kenya And Tanzania)
LUO
Lushai
LUS
Luxembourgish
LTZ
Macedonian
MKD
Madurese
MAD
Magahi
MAG
Maithili
MAI
Makasar
MAK
Malagasy
MLG
Malay
MSA
Malayalam
MAL
Maltese
MLT
Manchu
MNC
Mandar
MDR
Mandarin
QCM
Mandingo
MAN
Manipuri
MNI
Manobo Languages
MNO
Manx
GLV
Value
Date: May 7, 2010
2.14
28
Version:
Equipment and Supply Order Format Specification
Version Date: May 5, 2010
Maori
Code
ISO
639-2
MRI
Marathi
MAR
Mari
CHM
Marshall
MAH
Marwari
MWR
Masai
MAS
Mayan Languages
MYN
Mende
MEN
Micmac
MIC
Minangkabau
MIN
Mirandese
MWL
Miscellaneous Languages
MIS
Mohawk
MOH
Moksha
MDF
Moldavian
MOL
Mongo
LOL
Mongolian
MON
Mon-Khmer (Other)
MKH
Mossi
MOS
Multiple Languages
MUL
Munda Languages
MUN
Nahuatl
NAH
Nauru
NAU
Navajo
NAV
Ndonga
NDO
Neapolitan
NAP
Nepal Bhasa
NEW
Nepali
NEP
Nias
NIA
Niger-Kordofanian (Other)
NIC
Nilo-Saharan (Other)
SSA
Niuean
NIU
N'Ko
NQO
No linguistic content
ZXX
Value
Date: May 7, 2010
2.14
29
Version:
Equipment and Supply Order Format Specification
Version Date: May 5, 2010
Nogai
Code
ISO
639-2
NOG
Norse, Old
NON
North American Indian (Other)
NAI
North Ndebele
NDE
Northern Frisian
FRR
Northern Sami
SME
Northern Sotho
NSO
Norwegian
NOR
Norwegian Nynorsk
NNO
Nubian Languages
NUB
Nyamwezi
NYM
Nyankole
NYN
Nyoro
NYO
Nzima
NZI
Occitan
OCI
Ojibwa
OJI
Old Church Slavonic
CHU
Oriya
ORI
Oromo
ORM
Osage
OSA
Ossetic
OSS
Otomian Languages
OTO
Pahlavi
PAL
Palauan
PAU
Pali
PLI
Pampanga
PAM
Pangasinan
PAG
Papiamento
PAP
Papuan (Other)
PAA
Persian
FAS
Philippine (Other)
PHI
Phoenician
PHN
Pohnpeian
PON
Polish
POL
Portuguese
POR
Value
Date: May 7, 2010
2.14
30
Version:
Equipment and Supply Order Format Specification
Version Date: May 5, 2010
Prakrit Languages
Code
ISO
639-2
PRA
Punjabi
PAN
Pushto
PUS
Quechua
QUE
Raeto-Romance
ROH
Rajasthani
RAJ
Rapanui
RAP
Rarotongan
RAR
Romance (Other)
ROA
Romanian
RON
Romany
ROM
Rundi
RUN
Russian
RUS
Salishan Languages
SAL
Samaritan Aramaic
SAM
Sami Languages
SMI
Samoan
SMO
Sandawe
SAD
Sango
SAG
Sanskrit
SAN
Santali
SAT
Sardinian
SRD
Sasak
SAS
Scots
SCO
Selkup
SEL
Semitic (Other)
SEM
Serbian
SRP
Serer
SRR
Shan
SHN
Shona
SNA
Sichuan Yi
III
Sicilian
SCN
Sidamo
SID
Sign Languages
SGN
Siksika
BLA
Value
Date: May 7, 2010
2.14
31
Version:
Equipment and Supply Order Format Specification
Version Date: May 5, 2010
Sindhi
Code
ISO
639-2
SND
Sinhalese
SIN
Sino-Tibetan (Other)
SIT
Siouan Languages
SIO
Skolt Sami
SMS
Slave (Athapascan)
DEN
Slavic (Other)
SLA
Slovak
SLK
Slovenian
SLV
Sogdian
SOG
Somali
SOM
Songhai
SON
Soninke
SNK
Sorbian Languages
WEN
South American Indian (Other)
SAI
South Ndebele
NBL
Southern Altai
ALT
Southern Sami
SMA
Southern Sotho
SOT
Spanish
SPA
Sranan Togo
SRN
Sukuma
SUK
Sumerian
SUX
Sundanese
SUN
Susu
SUS
Swahili
SWA
Swati
SSW
Swedish
SWE
Swiss German
GSW
Syriac
SYR
Tagalog
TGL
Tahitian
TAH
Tai (Other)
TAI
Tajik
TGK
Tamashek
TMH
Value
Date: May 7, 2010
2.14
32
Version:
Equipment and Supply Order Format Specification
Version Date: May 5, 2010
Tamil
Code
ISO
639-2
TAM
Tatar
TAT
Telugu
TEL
Tereno
TER
Tetum
TET
Thai
THA
Tibetan
BOD
Tigre
TIG
Tigrinya
TIR
Timne
TEM
Tiv
TIV
Tlingit
TLI
Tok Pisin
TPI
Tokelau
TKL
Tonga (Nyasa)
TOG
Tonga (Tonga Islands)
TON
Tsimshian
TSI
Tsonga
TSO
Tswana
TSN
Tumbuka
TUM
Tupi languages
TUP
Turkish
TUR
Turkmen
TUK
Tuvalu
TVL
Tuvinian
TYV
Twi
TWI
Udmurt
UDM
Ugaritic
UGA
Ukrainian
UKR
Umbundu
UMB
Undetermined
UND
Upper Sorbian
HSB
Urdu
URD
Uyghur
UIG
Uzbek
UZB
Value
Date: May 7, 2010
2.14
33
Version:
Equipment and Supply Order Format Specification
Version Date: May 5, 2010
Vai
Code
ISO
639-2
VAI
Venda
VEN
Vietnamese
VIE
Volapuk
VOL
Votic
VOT
Wakashan Languages
WAK
Walamo
WAL
Walloon
WLN
Waray
WAR
Washo
WAS
Welsh
CYM
Western Frisian
FRY
Wolof
WOL
Xhosa
XHO
Yakut
SAH
Yao
YAO
Yapese
YAP
Yiddish
YID
Yoruba
YOR
Yupik Languages
YPK
Zande
ZND
Zapotec
ZAP
Zazaki
ZZA
Zenaga
ZEN
Zhuang
ZHA
Zulu
ZUL
Zuni
ZUN
Value
Date: May 7, 2010
2.14
34
Version:
Equipment and Supply Order Format Specification
2.13
Version Date: Dec 9, 2009
4. Appendix A - Distilled XML Schema
4.1 Equipment And Supply Order
The following provides a distilled view of the XML document schema. The intent is to provide a concise view of the document layout. The full XML schema
specification is contained in file: EquipmentAndSupplyOrder.xsd
<xs:element name="EquipmentAndSupplyOrder">
<xs:complexType>
<xs:sequence>
<xs:element name="CcacCode" type="xs:string"/>
<xs:element name="TransmissionDateTime" type="xs:dateTime"/>
<xs:element name="Order">
<xs:complexType>
<xs:sequence>
<xs:element name="OrganizationCode" type="xs:string"/>
<xs:element name="PurchaseOrderNumber" type="xs:string"/>
<xs:element name="PurchaseOrderDateTime" type="xs:dateTime">
<xs:annotation>
<xs:documentation>Changed to date and time
Rename Date to DateTime</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="PurchaseOrderCancelDateTime" type="xs:dateTime" minOccurs="0">
<xs:annotation>
<xs:documentation>Changed to date and time
Rename Date to DateTime</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="RequestType" type="xs:string">
<xs:annotation>
<xs:documentation>Defines the type of action for the Order; can be set to one of the following values:
"InitialOrder", "CancelOrder", "ResendDuplicatePO", "CancelLineItem", "EndRental", "FinanceChargeUpdate"</xs:documentation>
Date: May 7, 2010
35
Version:
Equipment and Supply Order Format Specification
2.13
Version Date: Dec 9, 2009
</xs:annotation>
</xs:element>
<xs:element name="DeliveryOrPickup">
<xs:complexType>
<xs:sequence>
<xs:element name="Delivery" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="DeliveryDateTime" type="xs:dateTime"/>
<xs:element name="DeliveryTimeInstructions" type="xs:string"
minOccurs="0"/>
<xs:element name="DeliveryPriority" type="xs:string"/>
<xs:element name="DeliveryPriorityInstructions"
type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Delivery Priority instructions if it's
a delivery</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ShippingAddress">
<xs:annotation>
<xs:documentation>2.8 Removed
RoomNumber</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="AddressSummary"
type="xs:string" minOccurs="0"/>
<xs:element name="Type"
type="xs:string"/>
<xs:element name="BuildingName"
type="xs:string" minOccurs="0"/>
<xs:element name="SuiteNumber"
Date: May 7, 2010
36
Version:
Equipment and Supply Order Format Specification
2.13
Version Date: Dec 9, 2009
type="xs:string" minOccurs="0"/>
<xs:element name="StreetNumber"
type="xs:string"/>
<xs:element name="StreetName"
type="xs:string"/>
<xs:element name="PostalCode"
type="xs:string"/>
<xs:element name="City"
type="xs:string"/>
<xs:element name="Province"
type="xs:string" minOccurs="0"/>
<xs:element name="Directions"
type="xs:string" minOccurs="0"/>
<xs:element name="AdditionalInfo"
type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="ClientPickUp" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="PickUpDateTime" type="xs:dateTime"/>
<xs:element name="PickUpInstructions" type="xs:string"
minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="EndRentalPickUp" minOccurs="0">
<xs:annotation>
<xs:documentation>This is the pickup information for an EndRental
Date: May 7, 2010
37
Version:
Equipment and Supply Order Format Specification
2.13
Version Date: Dec 9, 2009
transaction</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="PickUpAddress">
<xs:annotation>
<xs:documentation>2.8 Removed
RoomNumber</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="AddressSummary"
type="xs:string" minOccurs="0"/>
<xs:element name="Type"
type="xs:string"/>
<xs:element name="BuildingName"
type="xs:string" minOccurs="0"/>
<xs:element name="SuiteNumber"
type="xs:string" minOccurs="0"/>
<xs:element name="StreetNumber"
type="xs:string"/>
<xs:element name="StreetName"
type="xs:string"/>
<xs:element name="PostalCode"
type="xs:string"/>
<xs:element name="City"
type="xs:string"/>
<xs:element name="Province"
type="xs:string" minOccurs="0"/>
<xs:element name="Directions"
type="xs:string" minOccurs="0"/>
<xs:element name="AdditionalInfo"
type="xs:string" minOccurs="0"/>
Date: May 7, 2010
38
Version:
Equipment and Supply Order Format Specification
2.13
Version Date: Dec 9, 2009
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="PickUpInstructions" type="xs:string"
minOccurs="0">
<xs:annotation>
<xs:documentation>This is matching the Item
comments in CHRIS at the End Rental Item level</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="VerbalOrderConfirmation" type="xs:boolean"/>
<xs:element name="Requestor">
<xs:complexType>
<xs:sequence>
<xs:element name="ProviderRequestor" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="OrganizationName" type="xs:string">
<xs:annotation>
<xs:documentation>2.5 Renamed to Org
E.g. "Commrehab"</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ContactName" type="xs:string"
minOccurs="0"/>
<xs:element name="ContactPhoneNumber" type="xs:string"
minOccurs="0"/>
Date: May 7, 2010
39
Version:
Equipment and Supply Order Format Specification
2.13
Version Date: Dec 9, 2009
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CCACRequestor" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="ContactName" type="xs:string"/>
<xs:element name="ContactPhoneNumber" type="xs:string"
minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="RequestorType" use="required">
<xs:annotation>
<xs:documentation>CCAC or Provider</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CCACContact">
<xs:complexType>
<xs:sequence>
<xs:element name="CaseloadCaseManagerName" type="xs:string"/>
<xs:element name="ReferralCaseloadTeam" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Client">
<xs:complexType>
Date: May 7, 2010
40
Version:
Equipment and Supply Order Format Specification
2.13
Version Date: Dec 9, 2009
<xs:sequence>
<xs:element name="ClientIdentifier" type="xs:string"/>
<xs:element name="BillingReferenceNumber" type="xs:string"/>
<xs:element name="FirstName" type="xs:string"/>
<xs:element name="SurName" type="xs:string"/>
<xs:element name="PreferredLanguage" type="xs:string" minOccurs="0"/>
<xs:element name="Gender" type="xs:string" minOccurs="0"/>
<xs:element name="ClientAddress">
<xs:annotation>
<xs:documentation>2.5 Deleted Comment</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="AddressSummary" type="xs:string" minOccurs="0"/>
<xs:element name="Type" type="xs:string">
<xs:annotation>
<xs:documentation>Home, Mailing, Other</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ResidenceCode" type="xs:string" minOccurs="0"/>
<xs:element name="BuildingName" type="xs:string" minOccurs="0"/>
<xs:element name="SuiteNumber" type="xs:string" minOccurs="0"/>
<xs:element name="StreetNumber" type="xs:string"/>
<xs:element name="StreetName" type="xs:string"/>
<xs:element name="PostalCode" type="xs:string"/>
<xs:element name="City" type="xs:string"/>
<xs:element name="Province" type="xs:string" minOccurs="0"/>
<xs:element name="Directions" type="xs:string" minOccurs="0"/>
<xs:element name="AdditionalInfo" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="ClientPhone">
Date: May 7, 2010
41
Version:
Equipment and Supply Order Format Specification
2.13
Version Date: Dec 9, 2009
<xs:annotation>
<xs:documentation>2.8 Changed the Phone number to collection</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="Phone" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="TelephoneNumber" type="xs:string"/>
<xs:element name="PhoneLocation" type="xs:string">
<xs:annotation>
<xs:documentation>Home, work, mobile,
other</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="MedicalContacts" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="MedicalContact" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="ContactFirstName" type="xs:string">
<xs:annotation>
<xs:documentation>renamed added
Contact</xs:documentation>
</xs:annotation>
</xs:element>
Date: May 7, 2010
42
Version:
Equipment and Supply Order Format Specification
2.13
Version Date: Dec 9, 2009
<xs:element name="ContactSurName" type="xs:string">
<xs:annotation>
<xs:documentation>renamed added
Contact</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ContactAddress" minOccurs="0">
<xs:annotation>
<xs:documentation>2.5 Deleted
Comments</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="AddressSummary"
type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>2.5
Renamed</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="BuildingName"
type="xs:string" minOccurs="0"/>
<xs:element name="SuiteNumber"
type="xs:string" minOccurs="0"/>
<xs:element name="StreetNumber"
type="xs:string"/>
<xs:element name="StreetName"
type="xs:string"/>
<xs:element name="PostalCode"
type="xs:string"/>
<xs:element name="City"
type="xs:string"/>
<xs:element name="Province"
Date: May 7, 2010
43
Version:
Equipment and Supply Order Format Specification
2.13
Version Date: Dec 9, 2009
type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>2.4
Optional</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Directions"
type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>2.5
Optional</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="ContactPhone" type="xs:string"
minOccurs="0"/>
<xs:element name="Specialties" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element
name="SpecialtyDescription" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="TypeOfContact">
<xs:annotation>
<xs:documentation> "Family" "Attending" "Referring"
"Specialist"
Added Jan 31</xs:documentation>
</xs:annotation>
Date: May 7, 2010
44
Version:
Equipment and Supply Order Format Specification
2.13
Version Date: Dec 9, 2009
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="ActiveRiskCodes" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="RiskCodeItem" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="RiskCode" type="xs:string"/>
<xs:element name="AditionalInformation" type="xs:string"
nillable="true" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="HealthCard" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="HCN" type="xs:string">
<xs:annotation>
<xs:documentation>Health Card Number</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="VC" type="xs:string">
<xs:annotation>
<xs:documentation>Version Code</xs:documentation>
</xs:annotation>
Date: May 7, 2010
45
Version:
Equipment and Supply Order Format Specification
2.13
Version Date: Dec 9, 2009
</xs:element>
<xs:element name="ExpiryDate" type="xs:dateTime" minOccurs="0"/>
<xs:element name="Name" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>optional if the same as client
name</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="EquipmentAndSupplyItem">
<xs:complexType>
<xs:sequence>
<xs:element name="LineItem" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="PurchaseOrderLineNumber" type="xs:string"/>
<xs:element name="ContractCode" type="xs:string"/>
<xs:element name="ContractName" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>2.8 Associated with migration
requiemrements</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="VendorItemCode" type="xs:string"/>
<xs:element name="ItemClass" type="xs:string">
<xs:annotation>
<xs:documentation>Normal or Exception (for non-contracted
item)</xs:documentation>
Date: May 7, 2010
46
Version:
Equipment and Supply Order Format Specification
2.13
Version Date: Dec 9, 2009
</xs:annotation>
</xs:element>
<xs:element name="LineItemUnitCode" type="xs:string" default="unit">
<xs:annotation>
<xs:documentation>always set to "unit"</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ItemDescription" type="xs:string"/>
<xs:element name="RentalPeriod" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="RentalStartDate" type="xs:date"/>
<xs:element name="RentalEndDate" type="xs:date"
minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="OrderedDateTime" type="xs:dateTime">
<xs:annotation>
<xs:documentation>2.8 New Element
Indicates when the item was ordered originally</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ItemQuantity" type="xs:decimal">
<xs:annotation>
<xs:documentation>2.8 Changed to decimal type</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ItemChargeAmount" type="xs:decimal" minOccurs="0">
<xs:annotation>
<xs:documentation>This will be populated for finance
charges</xs:documentation>
</xs:annotation>
Date: May 7, 2010
47
Version:
Equipment and Supply Order Format Specification
2.13
Version Date: Dec 9, 2009
</xs:element>
<xs:element name="VendorInstructions" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>required for CHRIS 1.3</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ItemStatus" type="xs:string">
<xs:annotation>
<xs:documentation>Ordered, Cancellled,
Removed</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ItemStatusChangeDateTime" type="xs:dateTime" minOccurs="0">
<xs:annotation>
<xs:documentation>2.8 Renamed
The date when the item status was last changed</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="EquipmentDischargeDisposition" minOccurs="0">
<xs:annotation>
<xs:documentation>required for CHRIS 1.3
only used for End Rentals</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="DispositionCode" type="xs:string"/>
<xs:element name="DispositionDescription" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="RecordType" type="xs:string" use="required">
<xs:annotation>
Date: May 7, 2010
48
Version:
Equipment and Supply Order Format Specification
2.13
Version Date: Dec 9, 2009
<xs:documentation>Equipment or Supply</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="LineItemType" type="xs:string" use="required">
<xs:annotation>
<xs:documentation>Rental, Purchase, Finance</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="Version" type="xs:decimal" use="required"/>
</xs:complexType>
</xs:element>
Date: May 7, 2010
49