R4 APIs (Millennium)

Workflow or API calls:

We're attempting to create an Appointment via POST, using the documentation outlined here:

https://docs.oracle.com/en/industries/health/millennium-platform-apis/mfrap/op-appointment-post.html

We're sending the following POST body with a reasonCode text that is 256 characters long:

{
    "participant": [
        {
            "actor": {
                "reference": "Patient/13005571"
            },
            "status": "accepted"
        }
    ],
    "slot": [
        {
            "reference": "Slot/2559313301-21304876-66063102-495"
        }
    ],
    "status": "booked",
    "resourceType": "Appointment",
    "reasonCode": [
      {
        "text": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    ]
}

This request results in a 400 Bad Request.

If I modify the request to set the reasonCode text to 255 characters (one less), I can create the Appointment successfully:

{
    "participant": [
        {
            "actor": {
                "reference": "Patient/13005571"
            },
            "status": "accepted"
        }
    ],
    "slot": [
        {
            "reference": "Slot/24477838-21304876-66063720-150"
        }
    ],
    "status": "booked",
    "resourceType": "Appointment",
    "reasonCode": [
      {
        "text": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    ]
}

So, it seems like there's a limit on reasonCode text length that isn't outlined in the documentation. Can someone confirm this? Is there also a limit on Appointment.comment length?

Background Information:

Failure to provide answers will impact our ability to respond in a timely and effective manner
Developer questions:

Are you an OPN Member? Yes
Have you signed up to be in the Healthcare Developer Track? Yes
Are you a registered Code Program member? Yes
Does your App have a presence on the Oracle Healthcare App Marketplace? Yes

Are you developing on behalf of an Oracle Health client? No
If so, which client:

Application's Client ID and App ID, if relevant:

Expected Result:

201 Created response for Appointment with long reasonCode

Actual Result:

400 Bad Request

X-Request-Id: /82B1E546BE356977C28282534F32BE63+yOIR_6WRk
Date/time of the example: 20 March 2025 08:57 ET