FHIR Chat · CodeableConcept · committers

Stream: committers

Topic: CodeableConcept

Grahame Grieve (Feb 20 2018 at 11:47):

@Eric Haas GF#14136 - do you have any suggetsions which bit to bring across?

Rob Hausam (Feb 20 2018 at 12:14):

I think a lot of it is Observation specific, dealing with code/value. I can work with Eric on what to bring over to CodeableConcept.

Grahame Grieve (Feb 20 2018 at 12:18):

that'd be great

Eric Haas (Feb 20 2018 at 16:24):

@Rob Hausam can discuss this today maybe on OO on FHIR call

Rob Hausam (Feb 20 2018 at 16:25):

sure

Grahame Grieve (Mar 14 2018 at 00:10):

@Eric Haas ping on this

Eric Haas (Mar 14 2018 at 00:43):

http://build.fhir.org/observation.html#10.1.4.4.1

Eric Haas (Mar 14 2018 at 00:44):

http://build.fhir.org/observation.html#10.1.4.4.2

Rob Hausam (Mar 14 2018 at 01:28):

I think both of those sections are pretty good. The question still is which bits (assuming that there are some) should be copied over to CodeableConcept.

Eric Haas (Mar 14 2018 at 01:44):

I think the entire sections.

Eric Haas (Mar 14 2018 at 01:44):

and then just reference them in Observation

Rob Hausam (Mar 14 2018 at 02:09):

Hmm. A lot of the existing text is specific to Observation and value[x] - as it should be. For the parts that also apply to CodeableConcept, I think they need to be more generic - if not, it seems that it won't really fit. So unless I'm not seeing it, I think that both are going to be needed.

Eric Haas (Mar 14 2018 at 02:10):

OK lemme generalize it

Eric Haas (Mar 14 2018 at 05:20):

@Rob Hausam here is the xhtml for the this:

<h4>Code Translations </h4>
<p>More than one set of codes for a coded concept using multiple value sets based on different code systems may be used for CodeableConcept elements. These concepts may be cross mapped using the <a href="conceptmap.html">ConceptMap</a> resource and/or given as translations directly iuse the <code>Codings</code> element in the CodeableConcept datatype as shown in the example below.</p>
<p>For example many qualitative laboratory test results values are typically represented with coded presence/absence concepts. Using the coded value for 'negative' with a standard SNOMED CT code translation, <code>valueCodeableConcept</code> would be:</p>
<pre class="json">

"valueCodeableConcept": {
    "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"
}

</pre>
<h4> Using Free Text in CodeableConcept:</h4>
<p>When the data element is a  <code>CodeableConcept</code> type, a plain text representation of the concept is permitted if there is no appropriate code and only free text is available (and not prohibited by the implementation). For example using text only, the <code>Observation.valueCodeableConcept</code> element would be:</p>
<pre class="json">

"valueCodeableConcept": {
    "text": "uncoded free text result"
}

        </pre>

Eric Haas (Mar 14 2018 at 05:21):

here is what it looks like....Capture.PNG

Eric Haas (Mar 14 2018 at 05:22):

I would apply it but I am not sure where to ...

Eric Haas (Mar 14 2018 at 05:22):

... and will keep the notes in observation too since I agree they are very specific

Rob Hausam (Mar 14 2018 at 07:49):

I think that looks good. I think probably I would add it as a separate "Code Translations and Free Text" (or similar title) section in "Using Codes in Resources" - probably near the end between "Binding Strengths" and "Other notes". And then you could make a reference to that section at the end of the CodeaableConcept discussion on the "Data Types" page. Those are my thoughts at the moment.

Grahame Grieve (Mar 14 2018 at 10:39):

ok

Eric Haas (Mar 14 2018 at 16:30):

who is applying this? I don't know where the source page for the datatypes is. (I did a search and came up empty)?

Rob Hausam (Mar 14 2018 at 17:55):

I wouldn;t mind doing it but I don't think I will have time before the 4:00 PM freeze.

Eric Haas (Mar 14 2018 at 17:57):

I can do it but where do I apply "And then you could make a reference to that section at the end of the CodeaableConcept discussion on the "Data Types" page." I can't find that source page.

Eric Haas (Mar 14 2018 at 19:28):

I got it. but am reversing Rob recommendation. referencing in Using codes and detailing in the data type notes. check it out after I apply ti

Rob Hausam (Mar 14 2018 at 19:34):

OK. Not sure why that's a better choice, but I'm sure it will work. I based what I said partly because the data type documentation tends to be leaner - and this is broader guidance that seemed to me to fit pretty well in Using Codes in Resources. But will check it out.

Eric Haas (Mar 14 2018 at 19:53):

I think the guidance should go in one place and preferrably with what it is talking about, besides it already has a couple of paragraphs devoted to these topics and this just fleshes out even more and makes it more tangible. any way take a look and can fix it later if you still think is better the other way.

Rob Hausam (Mar 14 2018 at 20:16):

It's probably fine, Eric - thanks

Last updated: Apr 12 2022 at 19:14 UTC