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:
Failure to provide answers will impact our ability to respond in a timely and effective manner
Developer questions:
Good afternoon,
We are integration company, and we have customers using Cerner Millennium. We are currently developing an integration with our platform using the Cerner FHIR R4 APIs.
We would appreciate guidance on the recommended approach for implementing the following workflow, or insight into how other organizations typically solve this problem.
Our goal is to synchronize Encounter data for an entire tenant, including related Patient and Practitioner resources. According to the documentation below, it appears that we can use the `_lastUpdated` parameter to retrieve updated records:
https://docs.oracle.com/en/industries/health/millennium-platform-apis/mfrap/op-encounter-get.html
However, we need to run this synchronization very frequently (for example, once per minute).
The challenge we are encountering is that the `/Encounter` endpoint has a very limited set of search parameters, and it appears that one of the following parameters must be provided:
- patient
- _id
- identifier
- account
In standard FHIR implementations, it is often possible to query resources using `_lastUpdated` and use `_include` to retrieve related resources (for example `Patient` and `Practitioner`) in the same response. This allows us to create or update these related resources in our system if they do not yet exist.
At the product level, our requirement is to continuously fetch new or updated Encounter / Appointment records along with their associated Patient and Practitioner resources, and then perform create-or-update synchronization in our platform based on the last sync timestamp.
Our questions are:
- Did we correctly understand the limitations of the `/Encounter` endpoint in the Cerner FHIR API?
- What would be the recommended approach for implementing tenant-wide incremental synchronization of Encounters?
- Is there a recommended pattern for retrieving Encounter + Patient + Practitioner together, or should these resources be fetched separately?
Any guidance or best practices from your team or other Cerner integrators would be greatly appreciated.
Thank you.
Are you an Oracle Partner Network Member? Yes / No
If you answer Yes to the above, please answer the below as well:
Partner/Company Name:
Is your company enrolled in the Industry Healthcare Path? Yes / No
Does your company have the Oracle Health Millennium Platform (OHMP) Environment Access Technical Accelerator? Yes / No
Are you developing on behalf of an Oracle Health client?
If so, which client:
Application's Client ID and App ID, if relevant:
Expected Result:
Actual Result:
X-Request-Id / Cerner-Correlation-Id / opc-request-id:
Date/time of the example: