Workflow or API calls:
Request payloads that used to work for /POST Observation (create), now return:
{
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "error",
"code": "invalid",
"details": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/operation-outcome",
"code": "MSG_PARAM_INVALID",
"display": "Parameter 'Observation.valueQuantity.value' content is invalid"
}
],
"text": "The value for Observation.valueQuantity.value is not supported."
},
"diagnostics": "Observation.valueQuantity.value: must be a valid decimal",
"expression": [
"Observation.valueQuantity.value"
]
}
]
}
When changing the Observation.valueQuantity.value from a string to a number as the examples at https://docs.oracle.com/en/industries/health/millennium-platform-apis/mfrap/op-observation-post.html the response is another issue:
{
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "error",
"code": "invalid",
"details": {
"text": "Unprocessable entity"
}
}
]
}
This behaviour is occurring in client environment and also in the public sandbox.
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
Expected Result:
The Observation payload with an id attached to it and other generated field.
Actual Result:
Currently getting an OperationOutcome.
X-Request-Id / Cerner-Correlation-Id / opc-request-id: 33129ce3-2321-6ea7-6bac-1de23ab2299d +mFNT_vOEU
Date/time of the example: 12th of August 2025 - 20:32 BST