Skip to Main Content

Clinical APIs (EHR)

Announcement

For information related to the Oracle Partner Network (OPN) Industry Healthcare Track please visit our OPN Industry Healthcare Program page.

For specific questions related to Oracle Partner Network (OPN), please contact Partner Assistance.

Millennium FHIR and non-FHIR API Specifications and Supporting Documents can be found HERE on docs.oracle.com
Soarian FHIR API Specifications and Supporting Documents can be found HERE on docs.oracle.com.

Ability to attach content or include message history when replying/forwarding and limits/20241001/patientMessages/sentItems

Luis Ojeda3 days ago — edited 3 days ago

Workflow or API calls:

Reminder: If this is referring to a client domain or EHR activity—not the public sandbox—do not include API request data or live patient data.

Background Information:

Hi everyone,

I’m currently working with the Oracle Health Millennium API, particularly the endpoint:
POST /20241001/patientMessages/sentItems.

When sending a reply, I include the previousMessageId as documented, and the relationship between the messages is correctly established — the reply is properly linked to the original message.

However, I noticed that the content of the original message is not automatically included in the reply. The new message only contains the data provided in the content field, meaning the previous message text or conversation history is not forwarded or attached by default.

Similarly, when trying to simulate a “forward” action, there doesn’t seem to be a way to include or reference the original message’s body automatically. The API simply creates a new message without inheriting any previous content.

Heres the payload:

{
"messageSender": {
"id": "<personID>",
"type": "PERSON"
},
"recipients": [
{
"id": "<poolID>",
"type": "GROUPINBOX"
}
],
"encounter": "<encounterID>",
"patientId": "<personID>",
"subject": "Re: TESTING: NEW MSG",
"previousMessageId": "3257126987.9859041.-6.patient",
"content": "<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Strict//EN\" \"https://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\"><html xmlns=\"http://www.w3.org/1999/xhtml\"><body><a>Yes please I want to change my Email, because I don't have anymore the current one, thank you!</a></body></html>"
}

The API returns success and the new message is created correctly, but the previous content is not carried over.

So my questions are:

  1. Is this the expected behavior — that replies or forwards do not include the original message body automatically?
  2. Is the recommended approach to manually append the previous message’s content in the client before posting a reply or forward?
  3. Are there any built-in options or parameters to attach or embed prior message content when replying or forwarding?
  4. Is there a limit on the number of characters allowed for the entire message, including its content?

Thanks in advance for any clarification or best practices!

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

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

Expected Result:

Actual Result:

X-Request-Id:
2e143b67aa6fb2cf0a05a47b7dfb1817

/ Cerner-Correlation-Id:

/7D4D1A7645EDF3CE504FE7BAA6E771E7+4614

/ opc-request-id:
/7D4D1A7645EDF3CE504FE7BAA6E771E7/B4280BD9764B4FC54564B4F743214828

Date/time of the example:11/04/2025 1:28PM PT

Comments
Post Details
Added 3 days ago
0 comments
26 views