Defining profiles and Keywords in General

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • Shorthand (FHIR)
    • 0.12.0 [deprecated]
    • FHIR Infrastructure
    • Language Reference
    • 3.4.3 and 3.4.1
    • Hide

      Several suggestions here:

      1) We will add explanation on the scope/uniqueness of IDs. Specifically, IDs must be unique within the scope of their type in the IG, but are recommended to be unique across all types in the IG.  For example, you definitely cannot have two StructureDefinitions with id “foo” in the same IG, but you could have a StructureDefinition with id “foo” and a SearchParameter with id “foo” in the same IG – but this is discouraged.

      2) We will check the completeness and accuracy of section 3.4.1 (keywords) to make sure there are no omissions.

      Show
      Several suggestions here: 1) We will add explanation on the scope/uniqueness of IDs. Specifically, IDs must be unique within the scope of their type in the IG, but are recommended to be unique across all types in the IG.  For example, you definitely cannot have two StructureDefinitions with id “foo” in the same IG, but you could have a StructureDefinition with id “foo” and a SearchParameter with id “foo” in the same IG – but this is discouraged. 2) We will check the completeness and accuracy of section 3.4.1 (keywords) to make sure there are no omissions.
    • Kramer/Rhodes: 14-0-0
    • Clarification
    • Non-substantive

      It isn't clear whether the ID value has to be/should be unique within the IG. Please add information to explain. All Keywords and reserved words/symbols should be described/defined. Please consider a glossary. Some, but not all are described in 3.4.1. And some are in 3.4.1 but not listed as a keyword (Mapping, source)

            Assignee:
            Unassigned
            Reporter:
            Carmela Couderc
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: