We have a client, Baystate Health, who is testing r4 upgrade on our Staging app. Their issuer is coming across in the launch as dstu2 instead of r4. Is there something that they need to configure on the Millenium side to send as R4 or does Oracle need to configure something on their behalf?
Workflow or API calls:
api/launch
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? 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? Yes
Are you developing on behalf of an Oracle Health client?
Contacting on behalf of an Oracle Health client using our app.
If so, which client:
Baystate Health
Application's Client ID and App ID, if relevant:
Application Name: Krames On FHIR - STAGING
ApplicationId: 6e1a789a-e4ff-4fde-801e-9e3aa87408b9
Apps ClientID: 2494e312-9f9b-41d5-8b3a-5092e98d75d6
Expected Result: r4 fhir version is sent in launch/iss value
Actual Result:
X-Request-Id / Cerner-Correlation-Id / opc-request-id:
opc-request-id: /AEC44E21F4604A5BBF09004E5F7B079D/5FBE102CA793454A9C91C9981A7F4C15
X-Request-ID: 6eda4a86-fbba-48e1-840a-6b4f3c99f330
Date/time of the example: Date: Thu, 04 Dec 2025 20:07:49 GMT