Skip to content
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

support forming a URI from Coding values #129

Open
balhoff opened this issue Oct 7, 2021 · 2 comments
Open

support forming a URI from Coding values #129

balhoff opened this issue Oct 7, 2021 · 2 comments
Assignees
Labels
model Issues relating to the CRDC-H model

Comments

@balhoff
Copy link
Contributor

balhoff commented Oct 7, 2021

Currently an instance of Coding looks like this:

collection_site:                                            # type = BodySite
    site:                                                     # type = CodeableConcept
      coding:                                                 # type = Coding
        - code: C12468
          label: Lung
          system: http://ncithesaurus.nci.nih.gov
          tag:
            - harmonized
        - code: Lung
          label: Lung
          system: http://crdc.nci.nih.gov/gdc
          tag:
            - original

While the system value is a URI, this doesn't imply that it can be used as a URI namespace to be prepended to the code, if one wants to derive a URI for the coding value to use in RDF-based tools. In FHIR examples I've seen, this URI is not intended to be a namespace, just an identifier for a system. It would be nice if CRDC-H (or even as a feature of LinkML) we had a defined way to include a URI version of the coding value, or generate a URI from components in the coding instance. If we are going to use the CodeableConcept model, I don't think we need to precisely mirror FHIR. We could support better interoperability with the linked data world.

@gaurav gaurav added the model Issues relating to the CRDC-H model label Oct 10, 2021
@bfurner
Copy link
Contributor

bfurner commented Oct 18, 2021

I'm not sure I'm totally following the nuances here, so we should discuss at an upcoming meeting.

What we are looking to support in a Coding are 1) the code, 2) ideally a resolvable URL to an authoritative source for the code system, and 3) a version of the code system from which the code is drawn. In these examples, we're only showing the code and system, but certainly would want the flexibility to support versioning.

I take it you would like to see support for the 'code' represented as a CURIE (e.g. NCIT:C12468) as well as the simple code (e.g. C12468)?

@balhoff
Copy link
Contributor Author

balhoff commented Oct 18, 2021

I take it you would like to see support for the 'code' represented as a CURIE (e.g. NCIT:C12468) as well as the simple code (e.g. C12468)?

Yes, basically a predictable way to interoperate with semantic web tools, where an identifier is expected to be a URI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
model Issues relating to the CRDC-H model
Projects
None yet
Development

No branches or pull requests

3 participants