-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error Populating Slices on Observation.component #122
Comments
I'm not sure if this is it, but this:
should probably be:
|
That doesn't fix it. This feels like a Publisher error to me. Aside from the discriminator type, I don't see anything wrong with this -- and I certainly don't see any cases of trying to slice |
What is the next step on this? It's pretty serious if we can't slice Observation.component. It is extremely common thing to do. If it were the IG Publisher, it wouldn't have gone unnoticed. |
Ideally we'd post a message to Zulip and ask if anyone has any idea what's going on. That said, it's harder without being able to point to IG source that they understand (not FSH). We should consider pushing up fsh-mcode IGs on a branch of the HL7 mCODE repo. While I understand your point about it going unnoticed, the publisher is changing all the time -- and sometimes with unintended consequences. If this is a bug that was introduced in last night's build, it might go unnoticed. Either way, I just don't see anything wrong with it, so I could use some extra eyes on it. |
We figured this out due to some good (tedious) debugging from @markkramerus. Here is a fuller picture of the FSH in question:
The culprits are the
when it should be:
It appears that this happens because |
In cases where the element id is a substring of another element id (but the same number of parts), it was possible for the element to be placed in the wrong location (after the element with the id its own id is a substring of). This fixes that. Fixes #122
In cases where the element id is a substring of another element id (but the same number of parts), it was possible for the element to be placed in the wrong location (after the element with the id its own id is a substring of). This fixes that. Fixes #122
Re-opening until it is released |
Fixed in 0.6.2 |
The CancerGeneticVariant profile needs to slice Observation.component. SUSHI seems to be OK with populating the slices in-line, but the IG Publisher crashes with this message:
The offending lines are currently commented out so we can build the IG, but look for these lines in CancerGenomics.fsh:
The text was updated successfully, but these errors were encountered: