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

Using undefined terms

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • Shorthand (FHIR)
    • 0.12.0 [deprecated]
    • FHIR Infrastructure
    • Language Reference
    • 1.3.3
    • Hide

      The comment will be taken into account when this section (and the corresponding section in the normative specification) is reformatted into a table that lists each item and applicable keywords. 

       
      R = required (must), S = should (optional but recommended), M = optional (may), blank = disallowed
       

      Show
      The comment will be taken into account when this section (and the corresponding section in the normative specification) is reformatted into a table that lists each item and applicable keywords.    R = required (must), S = should (optional but recommended), M = optional (may), blank = disallowed  
    • Moesel/Rhodes 11-0-1
    • Clarification
    • Non-substantive

    Description

      The term "recommended" has not been introdiuced or defined. You are giving an example about "required" and "optional" keywords, yet all of a sudden you start talking about something that is "recommended". This is missleading.

      Existing Wording:

      For example, to define a profile, the keywords Profile and Parent are required, and Id, Title, and Description are recommended.

      Attachments

        Activity

          People

            Unassigned Unassigned
            ivan_zapreev Ivan Zapreev (Inactive)
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: