Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-33063

UCUM page should indicate curly-braces codes are discouraged

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • Terminology Infrastructure
    • Terminologies - Systems
    • Hide

      http://build.fhir.org/ucum.html#4.3.5.3

      Add the following text to this section (UCUM Expressions) 

      Curly braces {} in the code element are discouraged. Curly braces provide additional descriptive text in the code expression but do not contribute to the meaning of the code.  

       

      Show
      http://build.fhir.org/ucum.html#4.3.5.3 Add the following text to this section (UCUM Expressions)  Curly braces {} in the code element are discouraged. Curly braces provide additional descriptive text in the code expression but do not contribute to the meaning of the code.    
    • Rob Hausam/Reuben Daniels: 3-0-0
    • Clarification
    • Non-substantive
    • R5

    Description

      The UCUM page should add a section like this:

      Curly-braces codes

      UCUM supports adding curly-braces in the 'code' element to allow additional human-readable content.   E.g. 3 "{cartons}".  In FHIR, the Quantity.unit and Coding.display are typically available to convey a human-readable unit and therefore there is less need for using curly-braces in the Quantity.code element.  Because some systems may not recognize that codes containing distinct curly-brace content are in fact equivalent, it is recommended that use of curly-braced content be minimized and the human-readable representation be sent in those elements specifically for that purpose.

      Attachments

        Activity

          People

            marc.duteau Marc Duteau
            lloyd Lloyd McKenzie
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: