Stream: implementers
Topic: Subscription channel.payload
Anand Mohan Tumuluri (Jun 27 2016 at 23:20):
For subscription resource, channel.payload is a mandatory field( 1:1) and for non-payload subscriptions, the spec says to keep this field as blank. However this blank field does not make sense for JSON and even the reference implementation removes any such blank fields. So when to try to validate the existence of mandatory fields of a resource, it breaks. Can we have an alternate mechanism to indicate no-payload rather than blank?
Grahame Grieve (Jun 27 2016 at 23:47):
that's an oops. Can you make a task to fix that, and I suggest that you use n/a in the meantime
Anand Mohan Tumuluri (Jun 28 2016 at 00:05):
Thanks a lot @Grahame Grieve for your suggestion. I will use that for now. Regarding creation of a task, sorry but I am a complete newbie to HL7 standardization workflow (I have 16 years of experience with HL7v2 and DICOM, etc but never involved in standardization). Can you please send me a link or a doc that tells me how to add a task?
Grahame Grieve (Jun 28 2016 at 00:09):
bootom of every page, there's a link to htere:
Grahame Grieve (Jun 28 2016 at 00:09):
http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemAdd&tracker_id=677
Anand Mohan Tumuluri (Jun 28 2016 at 14:20):
http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10248
Grahame Grieve (Jun 28 2016 at 19:40):
thx
Last updated: Apr 12 2022 at 19:14 UTC
