1. FHIR R4 APIs for Oracle Health Millennium Platform
  2. Tasks
  3. Appointment

Patch an appointment

patch

/Appointment/{ID}

Patches an existing appointment.

Note:

  • Only the body fields mentioned below are supported. Unsupported fields are ignored, or can result in errors.
  • Video Visit functionality requires additional licensing, configuration, and application support.
  • For Video Visit link patch operations, both Appointment.read and Appointment.write scopes are required.
  • This implementation follows the JSON PATCH specification.
  • Only operations on the paths listed below are supported.
  • For Video Visit link patch operation paths, contained index 0 represents the provider link and contained index 1 represents the patient link.

Errors

In addition to the common errors and operation outcomes, the following errors may be returned:

  • Updating an Appointment resource with the incorrect version returns a 409 (Conflict) response.
  • Updating an Appointment resource without sending the If-Match header returns a 412 (Precondition Failed) response.
  • Updating an Appointment resource that is currently being modified returns a 423 (Locked) response.
  • If the Appointment resource could not be updated because of an operation that is necessary for the update (for example, encounter association), a 424 (Failed Dependency) response is returned.
  • Patching a Video Visit Appointment with add operations that has previously been patched for Video Visit links returns a 409 (Conflict) response.
  • Mixing add and replace patch operations is not supported while patching a Video Visit Appointment and returns a 422 (Unprocessable Entity) response.
  • Patching a Video Visit Appointment with any missing required patch operations returns a 422 (Unprocessable Entity) response.
  • Patching an Appointment with a participant status other than accepted returns a 422 (Unprocessable Entity) response.

Authorization Types

This operation supports the following authorization types:

Patch Operations

Path Operation Value Type
/status replace code
  • Description: The status of the appointment
  • Example:
    • {
              "op": "replace",
              "path": "/status",
              "value": "cancelled"
            }
  • Note:
    • Only arrived, checked-in, cancelled, booked, and fulfilled are supported
    • This patch operation must be accompanied by the add Slot patch operation when updating status to booked
/slot add Reference (Slot)
  • Description: The slot that this appointment is filling
  • Example:
    • {
              "op": "add",
              "path": "/slot",
              "value": [
                {
                  "reference":"Slot/1986119705-4048128-15648907-60"
                }
              ]
            }
  • Note:
    • When present, this patch operation must be accompanied by the replace Status patch operation with a value of booked
    • Only one Slot reference may be provided in the value array
/slot replace Reference (Slot)
  • Description: The Slot that this appointment is filling
  • Example:
    • {
              "op": "replace",
              "path": "/slot",
              "value": [
                {
                  "reference":"Slot/1986119705-4048128-15648907-60"
                }
              ]
            }
  • Note:
    • Not dependent on any other patch Operation
    • Only one Slot reference may be provided in the value array
/reasonCode add List of CodeableConcept
  • Description: The clinical reason for why this appointment is being scheduled
  • Example:
    • {
              "op": "add",
              "path": "/reasonCode",
              "value": [
                {
                  "text": "I have a headache"
                }
              ]
            }
  • Note:
    • When present, this patch operation must be accompanied by the replace Status patch operation with a value of booked
    • Only one CodeableConcept may be provided in the value array
    • CodeableConcept.text is required and CodeableConcept.coding, if present, will be ignored
    • When the value array is empty, any existing reasonCode will be removed
/cancelationReason add CodeableConcept
  • Description: The coded reason for the appointment being cancelled
  • Example:
    • {
              "op": "add",
              "path": "/cancelationReason",
              "value": {
                "coding": [
                  {
                    "system": "https://terminology.hl7.org/CodeSystem-appointment-cancellation-reason.html",
                    "code": "oth-err"
                  }
                ]
              }
            }
  • Note:
    • When present, this patch operation must be accompanied by the replace Status patch operation with a value of cancelled
    • Only one coding may be provided in the value
    • The cancellation reason value.coding can be from either the standard or proprietary system
    • CodeableConcept.coding is required and CodeableConcept.text, if present, will be ignored
/contained/0/telecom/0/value add string
  • Description: The provider Video Visit link
  • Example:
    • {
              "op": "add",
              "path": "/contained/0/telecom/0/value",
              "value": "http://providerlink.vmr.net"
            }
  • Note:
    • This patch operation may only be used for Cerner Video Visit appointments
    • This patch operation must be accompanied by all other Video Visit link patch operations with an op of add
    • The URL length must be less than or equal to 255 characters
/contained/1/telecom/0/value add string
  • Description: The patient Video Visit link
  • Example:
    • {
              "op": "add",
              "path": "/contained/1/telecom/0/value",
              "value": "http://patientlink.vmr.net"
            }
  • Note:
    • This patch operation may only be used for Cerner Video Visit appointments
    • This patch operation must be accompanied by all other Video Visit link patch operations with an op of add
    • The URL length must be less than or equal to 255 characters
/contained/0/telecom/0/period/start add datetime
  • Description: The start datetime for the Video Visit
  • Example:
    • {
              "op": "add",
              "path": "/contained/0/telecom/0/period/start",
              "value": "2019-07-13T08:00:00.000Z"
            }
  • Note:
    • This patch operation may only be used for Cerner Video Visit appointments
    • The value for this patch operation will be applied to both the provider Video Visit link and the patient Video Visit link
    • This patch operation must be accompanied by all other Video Visit link patch operations with an op of add
/contained/0/telecom/0/period/end add datetime
  • Description: The end datetime for the Video Visit
  • Example:
    • {
              "op": "add",
              "path": "/contained/0/telecom/0/period/end",
              "value": "2019-07-13T08:30:00.000Z"
            }
  • Note:
    • This patch operation may only be used for Cerner Video Visit appointments
    • The value for this patch operation will be applied to both the provider Video Visit link and the patient Video Visit link
    • This patch operation must be accompanied by all other Video Visit link patch operations with an op of add
/contained/0/telecom/0/value replace string
  • Description: The provider Video Visit link
  • Example:
    • {
              "op": "replace",
              "path": "/contained/0/telecom/0/value",
              "value":  "http://providerlink.vmr.net"
            }
  • Note:
    • This patch operation may only be used for Cerner Video Visit appointments
    • This patch operation must be accompanied by all other Video Visit link patch operations with an op of replace
    • The URL length must be less than or equal to 255 characters
/contained/1/telecom/0/value replace string
  • Description: The patient Video Visit link
  • Example:
    • {
              "op": "replace",
              "path": "/contained/1/telecom/0/value",
              "value":  "http://patientlink.vmr.net"
            }
  • Note:
    • This patch operation may only be used for Cerner Video Visit appointments
    • This patch operation must be accompanied by all other Video Visit link patch operations with an op of replace
    • The URL length must be less than or equal to 255 characters
/contained/0/telecom/0/period/start replace datetime
  • Description: The start datetime for the Video Visit
  • Example:
    • {
              "op": "replace",
              "path": "/contained/0/telecom/0/period/start",
              "value":  "2019-07-13T08:30:00.000Z"
            }
  • Note:
    • This patch operation may only be used for Cerner Video Visit appointments
    • The value for this patch operation will be applied to both the provider Video Visit link and the patient Video Visit link
    • This patch operation must be accompanied by all other Video Visit link patch operations with an op of replace
/contained/0/telecom/0/period/end replace datetime
  • Description: The end datetime for the Video Visit
  • Example:
    • {
              "op": "replace",
              "path": "/contained/0/telecom/0/period/end",
              "value":  "2019-07-14T08:30:00.000Z"
            }
  • Note:
    • This patch operation may only be used for Cerner Video Visit appointments
    • The value for this patch operation will be applied to both the provider Video Visit link and the patient Video Visit link
    • This patch operation must be accompanied by all other Video Visit link patch operations with an op of replace
/patient-status replace code
  • Description: The participant status on Patient participant types
  • Example:
    • {
              "op": "replace",
              "path": "/patient-status",
              "value":  "accepted"
            }
  • Note:
    • This patch operation may be used only for appointments with a booked status
    • This patch operation may be used only for Patient participants with a tentative status
/extension replace Extension
  • Description: The comment to be associated with the action performed on the resource
  • Example:
    • {
              "op": "replace",
              "path": "/extension",
              "value": [
                {
                  "url": "https://fhir-ehr.cerner.com/r4/StructureDefinition/action-comment",
                  "valueString": "not required, cancelled"
                }
              ]
            }
  • Note:
    • When present, this patch operation must be accompanied by add cancellation reason and replace status patch operation when updating the status to cancelled
    • When present, this patch operation must be accompanied by replace slot when rescheduling the appointment.
    • Only one value may be provided in the value array
/comment replace string
  • Description: Additional text to aid in facilitating the appointment
  • Example:
    • {
              "op": "replace",
              "path": "/comment",
              "value": "Arrived"
            }
  • Note:
    • When present, this patch operation must be accompanied by the replace Slot patch operation
/extension add Extension
  • Description: The coded reason for the appointment being rescheduled
  • Example:
    • {
              "op": "add",
              "path": "/extension",
              "value": {
                "coding": [
                  {
                    "system": "https://terminology.hl7.org/CodeSystem-appointment-cancellation-reason.html",
                    "code": "oth-err"
                  }
                ]
              }
            }
  • Note:
    • When present, this patch operation must be accompanied by replace slot operation
    • Only one value may be provided in the value array

Request

Supported Media Types
Path Parameters
Header Parameters
Body ()
The body of the patch operation
Root Schema : AppointmentPatch
Type: array
Minimum Number of Items: 1
Show Source
Nested Schema : items
Type: object
Show Source
Back to Top

Response

Supported Media Types

Default Response

Example patch for an appointment to booked status.

Example Request: 
PATCH https://fhir-ehr-code.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/Appointment/4817517
Example Request Body: 
[
    {
      'op': 'add',
      'path': '/slot',
      'value': [
        {
          'reference': 'Slot/24477854-21304876-62852027-0'
        }
      ]
    },
    {
      'op': 'replace',
      'path': '/status',
      'value': 'booked'
    }
  ]
Example Response: 
  Cache-Control: no-cache
  Content-Length: 0
  Content-Type: text/html
  Date: Tue, 26 Mar 2019 15:42:29 GMT
  Etag: W/"10"
  Last-Modified: Tue, 26 Mar 2019 15:42:27 GMT
  Vary: Origin
  X-Request-Id: 11111111-1111-1111-1111-111111111111
  opc-request-id: /11111111111111111111111111111111/11111111111111111111111111111111
The ETag response header indicates the current If-Match version to use on a subsequent update.
Headers
  • For Update or Patch versioning controls. Related to If-Match. When a resource performs an operation that creates or updates a record, an Etag value is returned as a header. This same value should be included in request headers as an If-Match for any subsequent update to that record.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the X-Request-Id, if present.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the opc-Request-Id, if present.

x-patch-add-cancelationReason Response

Example patch for an appointment to add a cancelationReason.

Example Request: 
PATCH https://fhir-ehr-code.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/Appointment/4817517
Example Request Body: 
[
    {
      'op': 'replace',
      'path': '/status',
      'value': 'cancelled'
    },
    {
      'op': 'add',
      'path': '/cancelationReason',
      'value': {
        'coding': [
          {
            'system': 'https://terminology.hl7.org/CodeSystem-appointment-cancellation-reason.html',
            'code': 'oth-err'
          }
        ]
      }
    }
  ]
Example Response: 
  Cache-Control: no-cache
  Content-Length: 0
  Content-Type: text/html
  Date: Tue, 26 Mar 2019 15:42:29 GMT
  Etag: W/"1"
  Last-Modified: Tue, 26 Mar 2019 15:42:27 GMT
  Vary: Origin
  X-Request-Id: 11111111-1111-1111-1111-111111111111
  opc-request-id: /11111111111111111111111111111111/11111111111111111111111111111111
The ETag response header indicates the current If-Match version to use on a subsequent update.
Headers
  • For Update or Patch versioning controls. Related to If-Match. When a resource performs an operation that creates or updates a record, an Etag value is returned as a header. This same value should be included in request headers as an If-Match for any subsequent update to that record.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the X-Request-Id, if present.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the opc-Request-Id, if present.

x-patch-add-rescheduleReason Response

Example patch for an appointment to add a rescheduleReason.

Example Request: 
PATCH https://fhir-ehr-code.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/Appointment/4817517
Example Request Body: 
[
    {
      'op': 'replace',
      'path': '/slot',
      'value': [
        {
          'reference': 'Slot/2582093771-22784981-63303788-60'
        }
      ]
    },
    {
      "op": 'add',
      "path": '/extension',
      "value": [
        {
          "url": 'https://fhir-ehr.cerner.com/r4/StructureDefinition/reschedule-reason',
          "valueCodeableConcept": {
            "coding": [
              {
                "system": 'https://terminology.hl7.org/CodeSystem-appointment-cancellation-reason.html',
                "code": 'oth-err'
              }
            ]
          }
        }
      ]
    }
  ]
Example Response: 
  Cache-Control: no-cache
  Content-Length: 0
  Content-Type: text/html
  Date: Tue, 26 Mar 2019 15:42:29 GMT
  Etag: W/"1"
  Last-Modified: Tue, 26 Mar 2019 15:42:27 GMT
  Vary: Origin
  X-Request-Id: 11111111-1111-1111-1111-111111111111
  opc-request-id: /11111111111111111111111111111111/11111111111111111111111111111111
The ETag response header indicates the current If-Match version to use on a subsequent update.
Headers
  • For Update or Patch versioning controls. Related to If-Match. When a resource performs an operation that creates or updates a record, an Etag value is returned as a header. This same value should be included in request headers as an If-Match for any subsequent update to that record.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the X-Request-Id, if present.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the opc-Request-Id, if present.

x-patch-add-video-visit-links Response

Example patch for an appointment to add video visit links.

Example Request: 
PATCH https://fhir-ehr-code.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/Appointment/4627745
Example Request Body: 
[
    {
      'op': 'add',
      'path': '/contained/0/telecom/0/value',
      'value': 'http://providerlink.vmr.net'
    },
    {
      'op': 'add',
      'path': '/contained/1/telecom/0/value',
      'value': 'http://patientlink.vmr.net'
    },
    {
      'op': 'add',
      'path': '/contained/0/telecom/0/period/start',
      'value': '2019-07-13T08:00:00.000Z'
    },
    {
      'op': 'add',
      'path': '/contained/0/telecom/0/period/end',
      'value': '2019-07-13T08:10:00.000Z'
    }
  ]
Example Response: 
  Cache-Control: no-cache
  Content-Length: 0
  Content-Type: text/html
  Date: Tue, 26 Mar 2019 15:42:29 GMT
  Etag: W/"10-1"
  Last-Modified: Tue, 26 Mar 2019 15:42:27 GMT
  Vary: Origin
  X-Request-Id: 11111111-1111-1111-1111-111111111111
  opc-request-id: /11111111111111111111111111111111/11111111111111111111111111111111
The ETag response header indicates the current If-Match version to use on a subsequent update.
Headers

x-patch-replace-slot Response

Example patch for an appointment to replace the slot.

Example Request: 
PATCH https://fhir-ehr-code.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/Appointment/4817517
Example Request Body: 
[
    {
      'op': 'replace',
      'path': '/slot',
      'value': [
        {
          'reference': 'Slot/2582093771-22784981-63303788-60'
        }
      ]
    }
  ]
Example Response: 
  Cache-Control: no-cache
  Content-Length: 0
  Content-Type: text/html
  Date: Tue, 26 Mar 2019 15:42:29 GMT
  Etag: W/"1"
  Last-Modified: Tue, 26 Mar 2019 15:42:27 GMT
  Vary: Origin
  X-Request-Id: 11111111-1111-1111-1111-111111111111
  opc-request-id: /11111111111111111111111111111111/11111111111111111111111111111111
The ETag response header indicates the current If-Match version to use on a subsequent update.
Headers
  • For Update or Patch versioning controls. Related to If-Match. When a resource performs an operation that creates or updates a record, an Etag value is returned as a header. This same value should be included in request headers as an If-Match for any subsequent update to that record.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the X-Request-Id, if present.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the opc-Request-Id, if present.

x-patch-replace-video-visit-links Response

Example patch for an appointment to replace video visit links.

Example Request: 
PATCH https://fhir-ehr-code.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/Appointment/4627745
Example Request Body: 
[
    {
      'op': 'replace',
      'path': '/contained/0/telecom/0/value',
      'value': 'http://providerlink.vmr.net'
    },
    {
      'op': 'replace',
      'path': '/contained/1/telecom/0/value',
      'value': 'http://patientlink.vmr.net'
    },
    {
      'op': 'replace',
      'path': '/contained/0/telecom/0/period/start',
      'value': '2019-07-13T08:00:00.000Z'
    },
    {
      'op': 'replace',
      'path': '/contained/0/telecom/0/period/end',
      'value': '2019-07-13T08:10:00.000Z'
    }
  ]
Example Response: 
  Cache-Control: no-cache
  Content-Length: 0
  Content-Type: text/html
  Date: Tue, 26 Mar 2019 15:42:29 GMT
  Etag: W/"10-1"
  Last-Modified: Tue, 26 Mar 2019 15:42:27 GMT
  Vary: Origin
  X-Request-Id: 11111111-1111-1111-1111-111111111111
  opc-request-id: /11111111111111111111111111111111/11111111111111111111111111111111
The ETag response header indicates the current If-Match version to use on a subsequent update.
Headers

x-patch-update-action-comment-and-replace-status Response

Example patch for an appointment with an updated action comment and replace status.

Example Request: 
PATCH https://fhir-ehr-code.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/Appointment/4817517
Example Request Body: 
[
    {
      'op': 'replace',
      'path': '/extension',
      'value': [
        {
          'url': 'https://fhir-ehr.cerner.com/r4/StructureDefinition/action-comment',
          'valueString': 'not required cancelled'
        }
      ]
    },
    {
      'op': 'replace',
      'path': '/status',
      'value': 'cancelled'
    },
    {
      'op': 'add',
      'path': '/cancelationReason',
      'value': {
        'coding': [
          {
            'system': 'https://terminology.hl7.org/CodeSystem-appointment-cancellation-reason.html',
            'code': 'oth-err'
          }
        ]
      }
    }
  ]
Example Response: 
  Cache-Control: no-cache
  Content-Length: 0
  Content-Type: text/html
  Date: Fri, 11 Aug 2023 15:42:29 GMT
  Etag: W/"10"
  Last-Modified: Fri, 11 Aug 2023 15:42:29 GMT
  Vary: Origin
  X-Request-Id: 11111111-1111-1111-1111-111111111111
  opc-request-id: /11111111111111111111111111111111/11111111111111111111111111111111
The ETag response header indicates the current If-Match version to use on a subsequent update.
Headers
  • For Update or Patch versioning controls. Related to If-Match. When a resource performs an operation that creates or updates a record, an Etag value is returned as a header. This same value should be included in request headers as an If-Match for any subsequent update to that record.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the X-Request-Id, if present.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the opc-Request-Id, if present.

x-patch-update-action-comment-and-slot Response

Example patch for an appointment with an updated action comment and replaced slot.

Example Request: 
PATCH https://fhir-ehr-code.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/Appointment/4817517
Example Request Body: 
[
    {
      "op": 'replace',
      "path": '/slot',
      "value": [
        {
          "reference": 'Slot/2592955413-2581440805-96118899-0'
        }
      ]
    },
    {
      'op': 'replace',
      'path': '/extension',
      'value': [
        {
          'url': 'https://fhir-ehr.cerner.com/r4/StructureDefinition/action-comment',
          'valueString': 'Rescheduling Appointment'
        }
      ]
    }
  ]
Example Response: 
  Cache-Control: no-cache
  Content-Length: 0
  Content-Type: text/html
  Date: Fri, 11 Aug 2023 15:42:29 GMT
  Etag: W/"10"
  Last-Modified: Fri, 11 Aug 2023 15:42:29 GMT
  Vary: Origin
  X-Request-Id: 11111111-1111-1111-1111-111111111111
  opc-request-id: /11111111111111111111111111111111/11111111111111111111111111111111
The ETag response header indicates the current If-Match version to use on a subsequent update.
Headers
  • For Update or Patch versioning controls. Related to If-Match. When a resource performs an operation that creates or updates a record, an Etag value is returned as a header. This same value should be included in request headers as an If-Match for any subsequent update to that record.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the X-Request-Id, if present.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the opc-Request-Id, if present.

x-patch-update-participant-status Response

Example patch for an appointment with updated participant status.

Example Request: 
PATCH https://fhir-ehr-code.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/Appointment/4817517
Example Request Body: 
[
    {
      'op': 'replace',
      'path': '/patient-status',
      'value': 'accepted'
    }
  ]
Example Response: 
  Cache-Control: no-cache
  Content-Length: 0
  Content-Type: text/html
  Date: Tue, 26 Mar 2019 15:42:29 GMT
  Etag: W/"10"
  Last-Modified: Tue, 26 Mar 2019 15:42:27 GMT
  Vary: Origin
  X-Request-Id: 11111111-1111-1111-1111-111111111111
  opc-request-id: /11111111111111111111111111111111/11111111111111111111111111111111
The ETag response header indicates the current If-Match version to use on a subsequent update.
Headers
  • For Update or Patch versioning controls. Related to If-Match. When a resource performs an operation that creates or updates a record, an Etag value is returned as a header. This same value should be included in request headers as an If-Match for any subsequent update to that record.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the X-Request-Id, if present.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the opc-Request-Id, if present.

x-patch-update-reasonCode Response

Example patch for an appointment with updated reasonCode.

Example Request: 
PATCH https://fhir-ehr-code.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/Appointment/4817517
Example Request Body: 
[
    {
      'op': 'add',
      'path': '/slot',
      'value': [
        {
          'reference': 'Slot/24477854-21304876-62852027-0'
        }
      ]
    },
    {
      'op': 'replace',
      'path': '/status',
      'value': 'booked'
    },
    {
      'op': 'add',
      'path': '/reasonCode',
      'value': [
        {
          'text': 'I have a headache'
        }
      ]
    }
  ]
Example Response: 
  Cache-Control: no-cache
  Content-Length: 0
  Content-Type: text/html
  Date: Tue, 26 Mar 2019 15:42:29 GMT
  Etag: W/"1"
  Last-Modified: Tue, 26 Mar 2019 15:42:27 GMT
  Vary: Origin
  X-Request-Id: 11111111-1111-1111-1111-111111111111
  opc-request-id: /11111111111111111111111111111111/11111111111111111111111111111111
The ETag response header indicates the current If-Match version to use on a subsequent update.
Headers
  • For Update or Patch versioning controls. Related to If-Match. When a resource performs an operation that creates or updates a record, an Etag value is returned as a header. This same value should be included in request headers as an If-Match for any subsequent update to that record.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the X-Request-Id, if present.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the opc-Request-Id, if present.
Back to Top