FHIR Chat · Close up · fhir/infrastructure-wg

Stream: fhir/infrastructure-wg

Topic: Close up


view this post on Zulip Grahame Grieve (Aug 07 2018 at 12:34):

Do we want to try and find time for GF#14245?

view this post on Zulip Grahame Grieve (Aug 07 2018 at 12:38):

and we are remiss not to have discussed GF#13216 but this really feels like a face to face discussino

view this post on Zulip Brian Postlethwaite (Aug 07 2018 at 12:41):

I agree, face to face would be far better for this one, and I agree with your notes on it, especially the great example.

view this post on Zulip Grahame Grieve (Aug 07 2018 at 12:50):

GF#17538 - this looks like we should do it as a technical correction

view this post on Zulip Grahame Grieve (Aug 07 2018 at 12:51):

so does GF#17489 - definite technical correction we shoud apply now

view this post on Zulip Grahame Grieve (Aug 07 2018 at 12:56):

ok i've reviewed all the tasks. Just the open ones here or already scheduled for the call on Friday

view this post on Zulip Lloyd McKenzie (Aug 07 2018 at 14:07):

17489 can't be a technical correction as it's a substantive change that isn't a clear error. But we can vote on it quickly. 17538 has been auto-approved. What can we do with 13216 now such that it's not going to cause issues at ballot and such that any changes we make after Friday can be non-substantive?

view this post on Zulip Lloyd McKenzie (Aug 07 2018 at 14:09):

My recommendation is to:
- add a SHOULD NOT on adding parameters to a search result other than _count
- add a SHALL declare any added parameters into the SELF link

view this post on Zulip Lloyd McKenzie (Aug 07 2018 at 14:10):

Also add SHALL check the self link and guidance on the importance of using certain search parameters like Patient.active

view this post on Zulip Lloyd McKenzie (Aug 07 2018 at 14:10):

(including the issue of missing data)


Last updated: Apr 12 2022 at 19:14 UTC