Place Orders

This topic provides the steps required to place an order for bulk document retrieval.

1. Prepare the order file using the required format specified below.

   Note:

   The order file limit is 500,000 rows.
2. Upload the order file to the request object store bucket.

Once these steps are completed, Oracle Health Clinical Data Exchange automatically detects an order file uploaded to your request bucket and processes the order.

Note:

Contact your Oracle support resource as needed to help with completing your bulk document retrieval setup.

Oracle Health Clinical Data Exchange requires you to submit order files in .CSV file format to facilitate the processing of bulk document retrieval requests. Any fields in the .CSV file that include a comma as part of the field value must be enclosed in double quotation marks (" "). The format for the order file is specified below.

Table 4-1 Order File Format

Field Name	Required	Data Type	Description
MemberId	Yes	Data type: Varchar (1, 256) Allowed characters: A-Z a-z 0-9 - _ #	The unique identifier for every patient record that the payer uses.
FirstName	Yes	Data type: Varchar (1, 256) Allowed characters: A-Z a-z 0-9 -	The patient's first name.
LastName	Yes	Data type: Varchar (1, 256) Allowed characters: A-Z a-z 0-9 - _ #	The patient's last name.
MiddleInitial	No	Data type: Varchar (1, 64) Allowed characters: A-Z a-z 0-9 - _ #	The patient's middle name or initial.
Sex	Yes	Data type: Predefined string (M)ale, (F)emale, (U)nkown Allowed characters: M m F f U u	Not applicable
DOB	Yes	Data type: Varchar Accepted formats: o mm/dd/yyyy Allowed characters: 0-9 /	The patient's date of birth. For example, 05/16/1980
Address1	No	Data type: Varchar (0, 256) Allowed characters: A-Z 0-9 a-z - . # $ @ space	Not applicable
Address2	No	Data type: Varchar (0, 256) Allowed characters: A-Z 0-9 a-z - . # $ @ space	Not applicable
City	No	Data type: Varchar (0, 64) Allowed characters: A-Z 0-9 a-z - . space	Not applicable
State	No	Data type: Varchar (0, 32) Allowed characters: A-Z 0-9 a-z -	Not applicable
Zip	Yes	Data type: Varchar (0, 12) Allowed characters: A-Z 0-9 a-z -	Not applicable
Homephone	No	Data type: Varchar (0, 16) Allowed characters: 0-9 - + ( )	Not applicable
MobilePhone	No	Data type: Varchar(0,16) Allowed characters: 0-9 - + ( )	Not applicable
Email	No	Data type: Varchar (0, 128) Allowed characters: A-Z 0-9 a-z - . # $ @	Not applicable
ServiceStartDate	Yes	Data Type: Varchar Timestamp with time zone Accepted formats: o yyyy-MM-dd'T'HH:mm:ssZ For example, 2024-01-01T00:00:00-0800	The service start date indicates the beginning of the encounter for which clinical documents are requested. Encounters that began before this date but remain active on or after this date are included, and encounters that are closed before the service start date are excluded. The service start date must be the same as or earlier than the service end date. If this condition is not met or the date is missing, an error is generated for the row.
ServiceEndDate	Yes	Data Type: Varchar Timestamp with time zone Accepted formats: o yyyy-MM-dd'T'HH:mm:ssZ For example, 2025-01-01T00:00:00-0800	The service end date indicates the conclusion of the encounter for which clinical documents are requested. Encounters that are active on or after the service start date but are not closed before the end date are included, and encounters that started after the service end date are excluded. The service end date must be the same as or later than the service start date. If this condition is not met or the date is missing, an error is generated for the row.
PurposeOfUse	Yes	Data type: Varchar (1, 64) Allowed characters: A-Z 0-9 a-z - . # $ @ space	This value describes the reason that the data is being requested. See the following examples: Risk & quality Payment operation
RowUUID	Yes	Data Type: Varchar(1, 150) Allowed characters: A-Z 0-9 az - #	This field includes a unique row identifier for a given row in an order.