Result Bucket

To view completed files, access the result object store bucket.

Completed files (that is, C-CDA documents) are packaged as .ZIP files that contain the applicable patient data based on the order request. Each single row in the order file has a corresponding .ZIP file that contains all the C-CDA documents that were found. If no patient record is matched for a row in the order file, no .ZIP file is created for that row.

Note:

Once the order request is placed, the required processing time varies based on the complexity of the request. The results are delivered to the result bucket once the request is completed.

Completed files are named according to the following naming convention: [Member ID]_[ROW UUID]_Encounters.zip.

In the .ZIP file, C-CDA documents are named according to the following naming convention: [Binary ID]_[UUID].xml. In this naming convention, the binary ID is the identifier of the document used within Oracle Health systems, and the UUID is the global unique identifier that is generated by Oracle Health Clinical Data Exchange.

For each encounter, at least one structured C-CDA document is generated; unstructured (C62) document attachments are only generated if applicable.

The generated .ZIP files follow the structure indicated below.

<OrderFileName>/<MemberId>_<ROWUUID>_Encounters.zip
├── BinaryId1_UUID1.xml
├── BinaryId1_UUID2.xml
├── BinaryId2_UUID3.xml
├── BinaryId2_UUID4.xml
├── ....