New features: Endpoints for (i) Code systems, and (ii) codeable concept

[joeflack4]

New endpoint(s): Code systems

Example endpoints

1. An endpoint w/ all system URLs: /systems/

Shows all systems that the terminology service knows about. Can show information like system url, prefix, version.

2. /systems/<system>

Can get the same as (1), but only for the single system referenced. I suppose could accept URL or prefix.

Discussion

TCCM already has a model and endpoints for concept systems, so it would be best if that could be used.

Where/how to determine canonical URIs?

• NCIT: https://ncithesaurus.nci.nih.gov/
• CRDC Nodes: http://crdc.nci.nih.gov/NODE e.g. http://crdc.nci.nih.gov/gdc (Taken from Jim's example)

---

New endpoint(s): Codeable concept

(Related issue: https://github.com/cancerDHC/ccdh-terminology-service/issues/89)

Rather than, or in addition to, current enumeration endpoint(s), we can implement an endpoint that returns such data in the structure of FHIR codeable concept (see also: coding).

Example from FHIR docs:

    {
        "coding": [
            {
                "system": "http://snomed.info/sct",
                "code": "260385009",
                "display": "Negative"
            }, {
                "system": "https://acme.lab/resultcodes",
                "code": "NEG",
                "display": "Negative"
            }
        ],
        "text": "Negative for Chlamydia Trachomatis rRNA"
    }

[joeflack4]

Maybe I should have broken this into to separate issues., but I'll keep together for right now.

[joeflack4]

@turbomam @gaurav FYI