FHIR Chat · Braille and ASL as languages · implementers

Stream: implementers

Topic: Braille and ASL as languages

Joanna Gaskill (Jun 05 2017 at 18:32):

Hi, I am not seeing braille or american sign languages as languages supported even by the expanded all languages codeset. is there an alternative way to represent that patients have special communication needs if it can't be represented in language?

Grahame Grieve (Jun 05 2017 at 19:01):

sgn-US for ASL

Grahame Grieve (Jun 05 2017 at 19:01):

braille... interesting problem

Robert McClure (Jun 05 2017 at 20:15):

Braille (Brai) is a "script" in the language tag world. That means it can be added after a language (+/- extlang). So for example, if you want to represent braille script for english, you'd use en-brai. If you want to represent US English braille it would be en-brai-us.

Grahame Grieve (Jun 07 2017 at 05:13):

actually, it's case sensitive. It should be

Grahame Grieve (Jun 07 2017 at 05:13):

en-Brai-US

Grahame Grieve (Jun 07 2017 at 05:14):

@Robert McClure should we update the common language binding to allow Brai? (at the moment we only allow lang/region e.g. en-US)

Grahame Grieve (Jun 07 2017 at 05:14):

actually, I think that's the US-core rule

Grahame Grieve (Jun 07 2017 at 05:15):

@Brett Marquard for your consideration

Brett Marquard (Jun 07 2017 at 12:22):

Thanks for note -- I believe the value set only was supposed to restrict the first part --text from value set: 'however only the language codes are required, all other elements are optional.' Am I missing where en-Brai-US is disallowed?

Grahame Grieve (Jun 07 2017 at 12:31):

check out valueset-simple-language which I created at .. your?... request :

    <compose>
        <include>
            <system value="urn:ietf:bcp:47"/>
            <filter>
                <property value="ext-lang"/>
                <op value="exists"/>
                <value value="false"/>
            </filter>
            <filter>
                <property value="script"/>
                <op value="exists"/>
                <value value="false"/>
            </filter>
            <filter>
                <property value="variant"/>
                <op value="exists"/>
                <value value="false"/>
            </filter>
            <filter>
                <property value="extension"/>
                <op value="exists"/>
                <value value="false"/>
            </filter>
            <filter>
                <property value="private-use"/>
                <op value="exists"/>
                <value value="false"/>
            </filter>
        </include>
    </compose>

Grahame Grieve (Jun 07 2017 at 12:31):

.. no script...

Joanna Gaskill (Jun 07 2017 at 18:19):

thanks I will use sgn-US and en-BRAI-US. Appreciate the input.

Last updated: Apr 12 2022 at 19:14 UTC