Profiling should document rules for documentation & mappings

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • FHIR Infrastructure
    • STU
    • Profiling
    • Hide

      Add note that when doing differential, you cannot remove definitions, usage notes, rationale or mappings. When creating a snapshot directly, you SHALL not remove definitions, but MAY remove usage notes, rationale, and mappings, though this is merely not telling the user about them, not actually making them not true

      Show
      Add note that when doing differential, you cannot remove definitions, usage notes, rationale or mappings. When creating a snapshot directly, you SHALL not remove definitions, but MAY remove usage notes, rationale, and mappings, though this is merely not telling the user about them, not actually making them not true
    • Ewout Kramer / Josh Mandel: 5-0-0
    • Clarification
    • Non-substantive
    • DSTU1 [deprecated]

      We say you can constrain definitions, usage notes, etc. However, we should make explicit the following:

      • you cannot remove definition
        - you can remove usage notes and rationale if they don't apply in your context
        - you can filter out mappings if they don't apply in your context

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: