Value rules are patterns, Exactly rules are fixed

XMLWordPrintableJSON

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

      Voter makes a good point that "fixed value rule" could be misleading because in a profile, it is implemented as a pattern. We propose to change this to the more generic "assignment rule" with interpretation of "required pattern rule" versus "exact value rule" in the context of profiles, and"fixed value rule" in the context of instances.

      Show
      Voter makes a good point that "fixed value rule" could be misleading because in a profile, it is implemented as a pattern. We propose to change this to the more generic "assignment rule" with interpretation of "required pattern rule" versus "exact value rule" in the context of profiles, and"fixed value rule" in the context of instances.
    • Moesel/Rhodes 11-0-1
    • Correction
    • Compatible, substantive

      Without the "exactly" option, it appears that "Fixed value rules" specify the "pattern" for an element, whereas with "exactly", the rule specifies the "fixed" value for an element. This is a bit confusing coming from the StructureDefinition side of things. Consider either renaming "Fixed value rules" to just "Value rules", or at least making clear what the resulting impact on the generated profile will be in the same terms used within the StructureDefinition resource

      Existing Wording:

      The exactly option indicates...

            Assignee:
            Unassigned
            Reporter:
            Bryn Rhodes
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: