FHIR Chat · trouble slicing by value [genomics IG] · IG creation

Stream: IG creation

Topic: trouble slicing by value [genomics IG]


view this post on Zulip Patrick Werner (Jul 13 2018 at 15:59):

i tried to slice of a slice in the genomics IG without success. My attempt was to slice the Coding element inside the valueCodeableConcept by system.

view this post on Zulip Patrick Werner (Jul 13 2018 at 16:00):

Screen-Shot-2018-07-13-at-17.57.00.png

view this post on Zulip Patrick Werner (Jul 13 2018 at 16:00):

i end up with multiple:

StructureDefinition/obs-described-variant: StructureDefinition.differential.element[10].patternCodeableConcept.coding   error   Error null validating Coding

view this post on Zulip Patrick Werner (Jul 13 2018 at 16:02):

i pushed my try here:
https://github.com/HL7/genomics-reporting/tree/pwerner_canonica-variation-id

view this post on Zulip Patrick Werner (Jul 13 2018 at 16:03):

relevant excel file: observation-profile-spreadsheet.xml, sheet: obs-discrete-variant

view this post on Zulip Lloyd McKenzie (Jul 13 2018 at 18:51):

Those slices look correct and it's complaining about something that isn't even in your slices. element 10 sounds like it's earlier in the differential than your spreadsheet snapshot too. Are you sure the problem isn't from earlier?

view this post on Zulip Sarah Gaunt (Jul 30 2018 at 23:25):

@Patrick Werner Did you ever find a solution to this?

view this post on Zulip Sarah Gaunt (Jul 30 2018 at 23:29):

I am having a very similar problem - it's not related to slicing though - it's related to the pattern on the codeableConcept (which I see you have in your slice).

So this pattern used to work: pasted image

But it now gives that error message: pasted image

The only way I can get it to not error is to move the pattern down further in the tree (and I've tried every permutation possible - like adding the pattern to coding - this is the only one that doesn't error): pasted image

@Grahame Grieve @Lloyd McKenzie Is this the way we are supposed to be doing patterns now? Has something changed? I thought the pattern was supposed to be at the top level?

view this post on Zulip Lloyd McKenzie (Jul 31 2018 at 00:44):

Not clear on why you're enforcing the display value, but other than that, it looks right

view this post on Zulip Sarah Gaunt (Jul 31 2018 at 00:47):

Not going to enforce the display value - that was old. But it doesn't validate. The first pattern with the display. The only way I can get it to validate is to move the pattern down onto the system and code. Is it a bug then? Because all the places where there was a pattern at that level when this went to ballot in January are now erroring when run through the IG Publisher.

view this post on Zulip Sarah Gaunt (Jul 31 2018 at 00:50):

I don't have a problem with moving them down onto system and code btw - it's just that I thought the first option (pattern at the top of the codeableConcept tree) was the correct way. I'm worried that the way that I'm being forced to do it to get rid of the errors is wrong.

view this post on Zulip Lloyd McKenzie (Jul 31 2018 at 00:52):

Seems like a bug to me. Should be fine defining a pattern at the CodeableConcept level - we use it for slicing all the time.

view this post on Zulip Sarah Gaunt (Jul 31 2018 at 00:53):

Ok, will raise an issue.

view this post on Zulip Sarah Gaunt (Jul 31 2018 at 02:35):

Don't think the error has anything to do with the pattern, but to do with the LOINC terminology validation. When I run the IG publisher with -tx N/A the errors all disappear. And if I change the pattern to use a random SNOMED code (rather then LOINC), no error either.

view this post on Zulip Sarah Gaunt (Jul 31 2018 at 02:51):

And, I downloaded a new version of IG publisher and the issue has resolved itself. Guess I hadn't downloaded a new one for a while. My bad.


Last updated: Apr 12 2022 at 19:14 UTC