FHIR Chat · Missed voting on Jan 2018 ballot issue GF#14887 · terminology

Stream: terminology

Topic: Missed voting on Jan 2018 ballot issue GF#14887


view this post on Zulip Rob Hausam (Aug 04 2018 at 07:00):

In reviewing and updating our final resolutions for the ballot trackers I've discovered that we still have one open tracker from the Jan. 2018 Core ballot that we missed taking a vote on - GF#14887. I had intended for it to be included and voted on the Thursday (Aug. 2) call, but it didn't get in the list on Confluence and we missed looking at it. It was recently discussed on the July 16 FHIR Tracker Issues call and set to Persuasive with Mod with the current resolution text. Process-wise I'm not sure how we need/prefer to handle this one remaining open ballot tracker for the Vocab WG, as this proposes a substantive change and since the freeze is tomorrow we have no further opportunities to vote prior to that. Suggestions are welcome. @Grahame Grieve @Lloyd McKenzie @Ted Klein

view this post on Zulip Rob Hausam (Aug 04 2018 at 07:03):

Possibly the best way to handle it is to pre-apply it now and then vote on it on the Main Vocab call next Thursday?

view this post on Zulip Grahame Grieve (Aug 04 2018 at 09:00):

well, I don't know about unimplementable since I actually use it in the build

view this post on Zulip Lloyd McKenzie (Aug 04 2018 at 13:33):

This tracker item is from the January "for comment" ballot, so it's not something that technically has to be in the reconciliation package I post tomorrow. You could still disposition it (and apply the disposition) before the 10th.

view this post on Zulip Rob Hausam (Aug 04 2018 at 13:53):

I see that it's in library-fhir-model-definition-content.xml, but that's inside a reference to ExpansionProfile, which presumably needs to be removed? And it's in valueset-example-heirarchical.xml with a value of false. That's all that I see - is there anything else?

view this post on Zulip Rob Hausam (Aug 04 2018 at 13:56):

And I'm going to add a tracker to fix the spelling of hierarchical in valueset-example-heirarchical.xml and valueset-spreadsheet.xml.

view this post on Zulip Rob Hausam (Aug 04 2018 at 14:03):

Thanks, @Lloyd McKenzie - we'll do that, then.

view this post on Zulip Grahame Grieve (Aug 04 2018 at 14:15):

library-fhir-model-definition-content is fill of random junk comment. you can ignore that.

view this post on Zulip Grahame Grieve (Aug 04 2018 at 14:16):

it's in the java code - I expand the codes for the expansion in the html with it set to true, and expand the codes for schema etc with it set to false.

view this post on Zulip Grahame Grieve (Aug 04 2018 at 14:16):

I do not understand the disposition:

view this post on Zulip Grahame Grieve (Aug 04 2018 at 14:17):

'excludeNotForUI' $expand operation parameter is likely unimplementable

view this post on Zulip Grahame Grieve (Aug 04 2018 at 14:17):

why?

view this post on Zulip Grahame Grieve (Aug 04 2018 at 14:17):

the only hint of a reason is this:

view this post on Zulip Grahame Grieve (Aug 04 2018 at 14:17):

different code systems identify UI (or notForUI) codes with different kinds of properties

view this post on Zulip Grahame Grieve (Aug 04 2018 at 14:17):

which is exactly why we do define it

view this post on Zulip Rob Hausam (Aug 04 2018 at 18:05):

GF#17620 added to fix the spelling of "hierarchical".

view this post on Zulip Rob Hausam (Aug 04 2018 at 18:05):

I'll pre-apply it today.


Last updated: Apr 12 2022 at 19:14 UTC