You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mint Thompson (They/Them/Theirs):theythem-teal: 9 hours ago
this is baffling. i'll take a look at it
Mark Kramer 9 hours ago
Thank you!
Nick Freiter (He/Him/His) 9 hours ago
But then if you run SUSHI on the version with SNOMED_CT, it runs without error right? I think it is using the SNOMED_CT CodeSystem, which is defined as part of the FHIR spec: https://www.hl7.org/fhir/codesystem-snomedct.json.html
Nick Freiter (He/Him/His) 9 hours ago
Notice the name, SNOMED_CT
Nick Freiter (He/Him/His) 9 hours ago
So it’s just preferring to use the name of a known resource over an alias
Mint Thompson (They/Them/Theirs):theythem-teal: 9 hours ago
oh, huh, you're right. the rule has SNOMED_CT, and it converts it to JSON in fsh online without an error
Nick Freiter (He/Him/His) 9 hours ago Yeah if you check the url on the SNOMED_CT resource, it is http://snomed.info/sct. So it makes sense we would resolve that url to the existing resource. It’s a weird special case that that resource is defined in FHIR, but I think GoFSH is behaving correctly here
Mark Kramer 9 hours ago
That is weird. I never would have guessed. Do you want me to close the bug report?
Nick Freiter (He/Him/His) 8 hours ago
Yeah unless we want to do something special for snomed, we can close it as not a bug
Mark Kramer 8 hours ago
I seem to be reporting many not-a-bugs. 🥸
GoFSH is generating this rule, although SNOMED_CT is undefined
* SNOMED_CT#442452003 "Life threatening severity (qualifier value)"
To see the example, use this URL in FSH Online, convert to JSON, then run GoFSH to convert back to FSH:
https://bit.ly/34rIMmU
I am planning to use this example at DevDays, so please give this priority.
The text was updated successfully, but these errors were encountered: