Stream: implementers
Topic: Redirects
Grahame Grieve (Feb 12 2018 at 20:29):
GF#7936 asks about the use and meanings of redirects, particularly in the context of patient merge. It's an old issue that has never got enough interest to get traction. As things stand, we may take this up in Release 5. does anyone have strong feelings about this?
Mark Urian (Apr 22 2020 at 04:53):
Good day! This is my first time to integrate FHIR. May I ask if it allows and how to add multiple redirect URI on the cerner code console apps? because I can't add multiple redirect uri on the same app. Thanks!
Grahame Grieve (Apr 22 2020 at 05:15):
you are more likely to get an answer to this question on the cerner support forums
Michele Mottini (Apr 22 2020 at 13:19):
@Mark Urian the Cerner support Google group is cerner-fhir-developers@googlegroups.com. Last time I checked Cerner supported only a single redirect URL per client, if you need more you need multiple registrations
René Spronk (Apr 24 2020 at 13:53):
To get back to Grahame's original question: For distributed implementations you'd probably need to do redirects, as one can't guarantee referential integrity over multiple FHIR servers. In my FHIR training courses, I use a $merge operation (on Patient instances, as an example operation) with an IN parameter : "redirect" of type Boolean to give the client control over whether or not a redirect should be created.
Cooper Thompson (Apr 24 2020 at 14:21):
Just to chime in on the topic of redirects around patient merge, since Grahame's initial question in this topic back in 2018, PA has done a lot of work on defining merge behavior, including dealing with redirects. It isn't in the build yet, but the content we have is on Confluence. Note that while the page is titled "Merge Operation", it has a lot more info about merge behavior than just the operation itself.
Last updated: Apr 12 2022 at 19:14 UTC
