FHIR Chat · TestScript.scope · TestScript Resource

Stream: TestScript Resource

Topic: TestScript.scope


view this post on Zulip Jose Costa Teixeira (Jan 22 2021 at 08:50):

From my side:
The most important seems to be adding the "a TestScript.scope" element, as per J#27007

view this post on Zulip Jose Costa Teixeira (Jan 22 2021 at 08:52):

we can refactor the whole metadata thing, but in any case I thinhk we do need an element clear ly dedicated to what is this supposed to test.

view this post on Zulip Richard Ettema (Jan 22 2021 at 14:40):

Jose, thank you. I've been trying to think of a good name for this element. 'scope' works for me.

view this post on Zulip Richard Ettema (Jan 25 2021 at 19:58):

@Jose Costa Teixeira, I have added comments to J#27007 with my version of a new "supports" (instead of "scope") repeating complex element that will replace the current "metadata" element. Please review.

view this post on Zulip Jose Costa Teixeira (Jan 25 2021 at 19:59):

I prefer "scope" because of "test scope".
"supports" is unclear to me. And I do not want to challenge metadata yet

view this post on Zulip Richard Ettema (Jan 25 2021 at 20:00):

OK. I'll update it to "scope".

view this post on Zulip Richard Ettema (Jan 25 2021 at 20:02):

Do the child elements and their definitions make sense?

view this post on Zulip Jose Costa Teixeira (Jan 25 2021 at 20:16):

yes, it looks good

view this post on Zulip Richard Ettema (Jan 25 2021 at 20:21):

The "level" and "phase" elements are coded values (enums) where I indicate an "other?" code value in case you can think of any other values that make sense. If you're ok, we can drop the "other?" value. We could then set the binding to example or extensible (my preference) to allow for additional code values if needed.

view this post on Zulip Peter Jordan (Jan 25 2021 at 20:42):

I'd suggest setting the the binding level to 'preferred' and changing the data type to coding. IMHO, the code data type only makes sense for required bindings with strictly controlled value sets where the codes are both human and machine readable.

view this post on Zulip Richard Ettema (Jan 25 2021 at 20:48):

Peter, thanks for that suggestion. I'll play around with my local FHIR R5 workspace and build this out for review.

view this post on Zulip Richard Ettema (Jan 26 2021 at 01:07):

Ok. Local FHIR build with these TestScript updates successful:
image.png

view this post on Zulip Richard Ettema (Jan 26 2021 at 01:09):

The next thing to define would be the search parameters.

view this post on Zulip Peter Jordan (Jan 26 2021 at 01:26):

At some stage, it would be prudent to consult the Vocabulary WG as we'll need a CodeSystem & ValueSet for level and phase. They'll also have a view on the binding strength.

view this post on Zulip Richard Ettema (Jan 26 2021 at 01:34):

As with most of the TestScript coded elements, I have created 'local' i.e., "Defined as part of FHIR" TestScript CodeSystem and ValueSet resources. I've attached them for review.
codesystem-testscript-scope-level-codes.xml codesystem-testscript-scope-phase-codes.xml valueset-testscript-scope-level-codes.xml valueset-testscript-scope-phase-codes.xml

view this post on Zulip Richard Ettema (Jan 26 2021 at 15:32):

I've now added new TestScript search parameters to my local build:
image.png


Last updated: Apr 12 2022 at 19:14 UTC