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

FHIR version declaration unclear

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Low Low
    • Shorthand (FHIR)
    • 1.0.0
    • FHIR Infrastructure
    • Normative
    • Language Reference
    • 3.2.3
    • Hide

      We will define better what a project is and what it contains (e.g., FSH items, a canonical URL, statement of IG dependencies, and FHIR version, at minimum). 

      We agree that the sentence "The FSH specification is not explicitly FHIR-version dependent, but implementations MAY support only a specific version or versions of FHIR." is confusing.

      What we really mean is that FSH is largely FHIR version-independent because it depends on normative FHIR features and does not depend on specific Resources, Profiles, or Extensions. However, the spec needs to reference specific data types in order to describe how FSH rules interact with them (what rules work on what data types, etc).  As long as the FSH spec refers to FHIR data types, there is no way to absolutely divorce FSH from specific FHIR versions.

      We will clarify this.

      Show
      We will define better what a project is and what it contains (e.g., FSH items, a canonical URL, statement of IG dependencies, and FHIR version, at minimum).  We agree that the sentence "The FSH specification is not explicitly FHIR-version dependent, but implementations MAY support only a specific version or versions of FHIR." is confusing. What we really mean is that FSH is largely FHIR version-independent because it depends on normative FHIR features and does not depend on specific Resources, Profiles, or Extensions. However, the spec needs to reference specific data types in order to describe how FSH rules interact with them (what rules work on what data types, etc).  As long as the FSH spec refers to FHIR data types, there is no way to absolutely divorce FSH from specific FHIR versions. We will clarify this.
    • Mark Kramer/Bas van den Heuvel : 13-0-0
    • Clarification
    • Non-substantive

    Description

      Each FSH project MUST declare the version of FHIR it depends upon. The form of this declaration is outside the scope of the FSH specification, and SHOULD be managed by implementations. The FSH specification is not explicitly FHIR-version dependent, but implementations MAY support only a specific version or versions of FHIR.

      From a spec language perspective this sentence is confusing.

      FSH project must declare the FHIR version it depends on- fine.
      The way it is done it outside the scope of this spec - understood.

      So why are we providing requirements on this. Remove the uppercase language from the other sentences. Alternatively, Sushi could add the concept of project in which object the version can be specified, see FHIR-33549

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: