Workflow or API calls:
This is more of a question about patient combine from the FHIR R4 API perspective. I've read through the Combine Help documentation but I'm still not 100% clear on what happens from the FHIR R4 side of things.
I know what happens to the Patient record, as described at the top of the Patient GET R4 API page:
When the requested patient record is combined into another record, an inactive patient entry is returned with a link to the current patient entry. Entries for combined patients are only returned when retrieving the entries directly by ID. They are not returned when searching with other parameters.
My question is around other FHIR resources like RelatedPerson, Encounter, Immunization, etc. Are all of these resources updated to point to the current patient entry instead of the inactive patient entry?
For example, if patient A had an appointment A that was completed in the past and patient B has an upcoming appointment B, and then patient A & B are combined (with Patient B being the current patient), do both the old Appointment A and the future Appointment B both point to Patient B now?
Does the inactive patient have any residual FHIR R4 resources referencing it or is it essentially a data point with no references that can only be retrieved by ID?
Are there any other oddities around the inactive patient that should be called out as it relates to combine operations?
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?
If so, which client: N/A
Application's Client ID and App ID, if relevant: N/A
Expected Result:
Clear documentation around how resource references are updated with regards to patient combine operations
Actual Result:
Only documentation around how Patient resources are affected by patient combine operations
X-Request-Id / Cerner-Correlation-Id / opc-request-id: N/A
Date/time of the example: N/A