Stream: cds hooks
Topic: lightweight-json-params
Grahame Grieve (Mar 23 2016 at 00:42):
josh you haven't commented on me proposal to use Parameters like that in json
Bryn Rhodes (Mar 23 2016 at 00:42):
Then each module only defines the parameters it needs above and beyond the common ones.
Grahame Grieve (Mar 23 2016 at 00:42):
Bryn - well, maybe it would be better to refine operation definition so shared definitions are possible
Bryn Rhodes (Mar 23 2016 at 00:42):
@Josh Mandel agreed, that would be fantastic.
Bryn Rhodes (Mar 23 2016 at 00:43):
@Grahame Grieve, yep, that would be good too, a sort of "parameter mixin".
Grahame Grieve (Mar 23 2016 at 00:43):
I abominate the word 'mixin', we'd have to come up with a better word
Bryn Rhodes (Mar 23 2016 at 00:43):
Yes, but you knew what I meant :)
Grahame Grieve (Mar 23 2016 at 00:43):
got to hit the road - back later
Josh Mandel (Mar 23 2016 at 00:44):
I think lightweight JSON params would be nice -- but we figured it made more sense for CDS Hooks to focus on using FHIR as-is if we value FHIR for this.
Josh Mandel (Mar 23 2016 at 00:44):
I'd like to work on getting that lightweight JSON thing standardized though
Josh Mandel (Mar 23 2016 at 00:44):
Even if we don't block on it it in CDS hooks.
Ewout Kramer (Apr 13 2016 at 08:18):
What's the beginning of this thread? What do the leightweight json params look like?
Josh Mandel (Apr 13 2016 at 13:02):
They look like:
{
a: "b"
}
Instead of
{
resourceType: "Parameters" ,
parameter: [{
name: "a",
valueString: "b"
}]
}
Last updated: Apr 12 2022 at 19:14 UTC
