Stream: implementers
Topic: Adding tags
Richard Kavanagh (Feb 22 2017 at 23:52):
I've not used tags so far so every chance I am doing something wrong. I am attempting to create a Patient and add a Tag to it. As far as I can see this is a two stage process.
First create patient
Used a POST to http://fhir3.healthintersections.com.au/open/Patient/ which was successful. Patient 337 created
Check it exists with GET http://fhir3.healthintersections.com.au/open/Patient/337 Patient returned
Now add the tag via the $meta-add operation
POST to http://fhir3.healthintersections.com.au/open/Patient/337/$meta-add with the following payload (from the spec)
<Parameters>
<parameter>
<name value="meta"/>
<valueMeta>
<tag>
<system value="http://example.org/codes/tags"/>
<code value="record-lost"/>
<display value="Patient File Lost"/>
</tag>
</valueMeta>
</parameter>
</Parameters>
This results in a 404 returning an OperationOutcome stating " <p>Resource Id "Patient:337" does not exist</p>"
What did I do wrong?
Richard Kavanagh (Feb 23 2017 at 00:16):
Seems to work on http://fhirtest.uhn.ca/baseDstu3 @Grahame Grieve does your server have an issue?
Lloyd McKenzie (Feb 23 2017 at 03:17):
You don't actually need to do it as two steps - you can specify your tags in the resource (under meta) in your initial POST if you know what they're supposed to be at the time of the Create. And yes, that looks like a problem with Grahame's server
Grahame Grieve (Feb 24 2017 at 19:09):
yes please submit an issue here:
Grahame Grieve (Feb 24 2017 at 19:09):
https://github.com/grahamegrieve/fhirserver
Brian Postlethwaite (Feb 26 2017 at 00:53):
Yes, doesn't need to be 2 steps. Benefit of doing it as 1 step (apart from only being 1 step) is that it will also flow through the subscription channels, where $meta-add/delete etc doesn't
Last updated: Apr 12 2022 at 19:14 UTC
