Josh Mandel
Josh Mandel
I think it's a targeted fix that will eliminate confusion down the line. Also in favor of mixing this change: old clients that happen to include this extra `subject` property...
I think FHIRPath is a big help here. We'd need some way to define what resources(s) a FHIRPath expression runs against. A couple of possible models: ### "Basic Resource Set"...
I think it's a natural thing to include in the discovery endpoint. We might make it an array-valued field to support CDS Services that know how to handle >1 version...
That's interesting -- it'd be good to understand where it's breaking down in the sandbox, at least. HTTP doesn't specify a limit, but many clients and servers do have limits...
OK -- and is the error due to total query length, or something about the semantics of this particular query?
I wouldn't rely on valuesets, because most FHIR servers won't support allowing a client to create its own valuesets. (Sorry for the confusions -- that's why I put "right solution"...
Agreed we should clarify — and my preference would be to leave this open, at the CDS Hooks overall specification level, to say that Context values can be any valid...
Thanks @bdoolittle — this is real food for thought. One more question to add to the pile: what is the "meaning" of this kind of `data`? In other words, what...
Love the idea. Naming-wise, why not call it `condition-create` as you did in the PR text? If you prefer "problem" to "condition," that's fine, but I'm confused by "list" --...
(Similar to `appointment-book`.)