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

Constraint numbering doesn't follow convention

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Published (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive

      Description

      The constraint definitions `1`, `2`, `3`, and so on do not follow the normal convention of using a short 3-letter abbreviation for the resource. This should be corrected for consistency with the constraint naming convention.

        Attachments

          Activity

            People

            Assignee:
            bryn.rhodes Bryn Rhodes
            Reporter:
            bryn.rhodes Bryn Rhodes
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Vote Date: