FHIR Chat · Fragment / Example expansions · terminology

Stream: terminology

Topic: Fragment / Example expansions


view this post on Zulip Grahame Grieve (Nov 17 2021 at 02:33):

@Michael Lawley what does OntoServer do if it gets a request for an expansion, and the underlying code system definition has content=fragment, or content=example ?

view this post on Zulip Grahame Grieve (Nov 17 2021 at 02:47):

or a validate-code?

view this post on Zulip Grahame Grieve (Nov 17 2021 at 02:47):

here's what I'm doing at present, or going to do:

view this post on Zulip Grahame Grieve (Nov 17 2021 at 02:50):

$validate-code:

  • if content < complete, always return true
  • if the code is not found in the incomplete code system, include cause = not found in the parameters
  • if the code is not found, or if the code system is an example, include the message The system {{system}} was found but did not contain enough information to properly validate the code (mode = {{mode}})

view this post on Zulip Grahame Grieve (Nov 17 2021 at 02:51):

$expand:

  • by default, return an error saying that one (or more) codesystem is incomplete
  • if the client passes a (as yet undefined) parameter saying it's ok with it, process the expansion as per normal, and mark the example and fragment code systems in the parameters

view this post on Zulip Grahame Grieve (Nov 17 2021 at 03:07):

also @Peter Jordan @Alexander Henket and @Carol Macumber, what do your servers do?

view this post on Zulip Grahame Grieve (Nov 17 2021 at 04:02):

I'm now using incomplete-ok=true for expansions. Case in point: https://terminology.hl7.org/ValueSet-service-category.html - that looks like a normal expansion, but see this:

Content: Example: A few representative concepts are included in the code system resource

from https://terminology.hl7.org/CodeSystem-service-category.html

view this post on Zulip Grahame Grieve (Nov 17 2021 at 04:02):

I want the expansion to be clear about this

view this post on Zulip Grahame Grieve (Nov 17 2021 at 04:18):

On this subject, I'm going to make a rule in all HL7 authored code systems: they SHALL have a content element. Let me know if anyone thinks that's a problem

view this post on Zulip Grahame Grieve (Nov 17 2021 at 04:23):

https://jira.hl7.org/browse/FHIR-34326

view this post on Zulip Michael Lawley (Nov 17 2021 at 05:40):

Ontoserver allows expansion / validation wrt content < complete. This is useful for, for example, UCUM.
We don't include any indicators in such an expansion that reference the potential incompleteness; I think we need to address this (item 2 of $expand above), but I would be reluctant to error by default (except maybe for example).
Another issue is how to handle multiple CodeSystem instances (same version) that have varying values of content < complete. For example two or more different fragments.

view this post on Zulip Peter Jordan (Nov 17 2021 at 05:53):

Grahame Grieve said:

On this subject, I'm going to make a rule in all HL7 authored code systems: they SHALL have a content element. Let me know if anyone thinks that's a problem

Not quite sure what this means as CodeSystem.content is a required element. Do you mean that content should be provided in the concept element (i.e. the CodeSystem.content code should never be 'not-present' for HL7 authored code systems)?

view this post on Zulip Richard Townley-O'Neill (Nov 17 2021 at 06:49):

@Peter Jordan is this in the correct stream?

view this post on Zulip Grahame Grieve (Nov 17 2021 at 07:58):

wow you're right. I forget to check, because it wasn't being an error. Obviously I'll have to go checking why I wasn't getting that as an error

view this post on Zulip Grahame Grieve (Nov 17 2021 at 07:59):

(and it wasn't really the right stream, for any confused readers)

view this post on Zulip Grahame Grieve (Nov 17 2021 at 08:00):

Ontoserver allows expansion / validation wrt content < complete. This is useful for, for example, UCUM.

But it's also dangerous.

view this post on Zulip Grahame Grieve (Nov 17 2021 at 08:01):

we can at least agree that we want to indicate the use of a fragment or an example code system in the expansion, yes?

view this post on Zulip Grahame Grieve (Nov 17 2021 at 08:11):

also, wrt UCUM, I do not think that UCUM is a fragment given how I support it

view this post on Zulip Michael Lawley (Nov 17 2021 at 23:16):

No, but the way we currently support it, it is a fragment.

view this post on Zulip Alexander Henket (Nov 22 2021 at 16:44):

We have two servers: ART-DECOR and NTS. The latter being Ontoserver based. ART-DECOR is not handling fragments at present but that is mainly because the nature of the internal codesystem format does not handle incompleteness or example status. This would change once we do. I'm keeping an eye on this thread.


Last updated: Apr 12 2022 at 19:14 UTC