Stream: cds hooks/github
Topic: docs / Issue #81 Support of JSON and/or xml
Github Notifications (Sep 08 2017 at 16:20):
bvdh opened Issue #81
What formatting is supported in REST calls? The specification seems to suggest that JSON is supported. Is xml also supported?
I suggest to state that the CDS Service MUST support JSON, and MAY support xml. The EHR MUST support JSON as well as xml.
Also provide references to the JSON specification (rfc7159) and xml specifications.
Github Notifications (Sep 08 2017 at 20:36):
olbrich commented on Issue #81
I don't know that the specification really should care about what format is used for interchange, but pragmatically I would expect any such service would provide at least XML or JSON.
Github Notifications (Sep 09 2017 at 20:35):
CDS Hooks only defines JSON as the data format -- everyone MUST support JSON (so we have that question answered).
I personally do not want to define support for XML in CDS Hooks as I don't see much value in doing so. JSON is pervasive and has proven to be very popular and well supported by everyone. Also defining optional support for XML will further increase our complexity (or at the very least, surface area).
Is XML a must have for you @bvdh?
Github Notifications (Sep 09 2017 at 22:57):
grahamegrieve commented on Issue #81
you might say that the CDS <--> FHIR Server interface could make use of XML if the EHR capability statement allows for it, but introducing an XML format in the EHR <--> CDS interface seems like a lot of work for very little outcome
Github Notifications (Sep 11 2017 at 06:09):
My main concern is that the spec is a bit vague in specifying what is mandatory. If the only thing that is supported is JSON. That is ok for me. But please state it explicitly.
Github Notifications (Sep 12 2017 at 18:02):
brynrhodes labeled Issue #81
Github Notifications (Sep 12 2017 at 19:01):
Per discussion at the Sept WGM (Tue Q2), we will update the spec to explicitly state that JSON (and only JSON) MUST be supported by both the EHR and CDS Services.
Github Notifications (Nov 26 2017 at 15:03):
kpshek assigned Issue #81
Github Notifications (Nov 27 2017 at 18:57):
kpshek closed Issue #81
Last updated: Apr 12 2022 at 19:14 UTC
