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

Refrain from repeating FHIR profiling specificaiton.

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Low Low
    • Shorthand (FHIR)
    • 0.12.0 [deprecated]
    • FHIR Infrastructure
    • Language Reference
    • 3.3.4
    • Hide

      The documentation will be clarified that this is not a new rule coming from FSH, but an example of a FSH rule consistent with FHIR. The documentation will be changed to refer to FHIR, rather than repeat too much of FHIR in the FSH specification.

      Show
      The documentation will be clarified that this is not a new rule coming from FSH, but an example of a FSH rule consistent with FHIR. The documentation will be changed to refer to FHIR, rather than repeat too much of FHIR in the FSH specification.
    • Kramer/Rhodes: 14-0-0
    • Clarification
    • Non-substantive

    Description

      In this, and also other places, shorthand seams to repeat restrictions and specification elements that come from FHIR profiling. I suggest that Shorthand only defines the shorthand related elements and does not repeat the FHIR specification. This will make it easier for Shorthand to be used and evolve idependently of the FHIR specification version. It will also prevent discrepancies occuring between the two specifcations.

      Existing Wording:

      The data type choices must always be more restrictive than the original data type. For example, if the parent data type is Quantity, it can be replaced in an only rule by SimpleQuantity, since SimpleQuantity is a profile on Quantity (hence more restrictive than Quantity itself).

      Attachments

        Activity

          People

            Unassigned Unassigned
            bvdh Bas van den Heuvel
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: