![]() So it seems like sometimes we use conjunction and sometimes disjunction? Normally when a filter is applied eg "Size 12" + "green" we expect both qualities to be true at the same time and this is held true by the FHIR Spec that says " If multiple filters are specified, they SHALL all be true." (see ) However has two filters that pick up substances PLUS products and obviously they can't both be true at the same time. ML - call multiple times with single codes as a workaround. PJ - CodeableConcept (with multiple codings) will require multiple responses. ML - general principle that services should echo back the details they've been sent to process. Grahame Grieve: : Clarify the use of fragment (this is a discovered issue from the same session, relating to the first of the tasks above) Grahame Grieve: : $validate-code and $expand need a session parameter (as optimisation where ValueSet may need to be uploaded for a series of calls) Grahame Grieve: : $validate-code and $expand should have a parameter for related value sets and code systems Grahame Grieve: : $validate-code should return an operation outcome with the full details of issues found, including paths Grahame Grieve: : $validate-code should return system | version | code when display is returned ![]() G Grieve have created new HL7 Jira tickets: PJ suggests that we should populate the system-version here instead and that "version" would really be the version of the ValueSet itself which, given that it's being generated at runtime, could be the current timestamp. If the codeSystem on the server has a specified version then this version SHALL be provided as a parameter in the expansion (note that not all code systems have a version)." If the expansion will be persisted all of these parameters SHALL be included. The spec says " The server decides which parameters to include here, but at a minimum, the list SHOULD include all of the parameters that affect the $expand operation. Query is about what version gets used in the parameter field. Hmm, we agreed that valueSet was a thing that existed independently of it's implementation (Kuala Lumpur discussion) but that hasn't made it to the spec. SNOMED International follows published URI spec in this matter, see 2.6 URIs for Modelling Resources for pre-defined ValueSets. Implicit example: $expand?url= here we just return the url parameter that was specified in the GET request.
0 Comments
Leave a Reply. |