How to do client assigned IDs with Transaction builder? #2099
Replies: 3 comments 3 replies
-
Update... this code generates something much closer (p is a new Patient Resource):
This creates:
The only diff here is my POST ends in /Bundle, whereas the example I was given doesn't. I get a Forbidden code back posting this. |
Beta Was this translation helpful? Give feedback.
-
Seems there might be a server side setting for Client ID mode |
Beta Was this translation helpful? Give feedback.
-
Another update ; the issue #2100 resolved how to accomplish this POST:
But it returned a 500 error in my case. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I can't figure the correct syntax with TransactionBuilder to do client assigned IDs.
The server is a Smile CDR, and the developer says i need to create a Transaction bundle containing a patient resource with my desired ID.
They gave me an example (this is creating a resource of type Organization, not Patient, but same idea). Note that the HTTP is a POST, but the inner resource has a method of PUT...
However, the request generated by my code does a PUT on a Patient, rather than a POST on a Bundle...
How do I get the code to do what they want? Do I ignore the transaction builder and instead create a manual bundle with an entry and POST that? Seems the transationbuilder should be helping me do that if I can just understand how!
Beta Was this translation helpful? Give feedback.
All reactions