Sushi and Shorthand - separate or part of the same spec.

XMLWordPrintableJSON

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

      We propose to remove SUSHI from the IG and maintain that documentation outside of HL7. 

      The IG tries to make it clear that the FSH language is normative, but SUSHI is not. However, having implementation in the IG is confusing and inconsistent with the way other similar specifications are presented. SUSHI should not have a position of privilege over other implementations. Maintaining SUSHI separately allows it to freely evolve, outside the formal standards process.   

       This was discussed and supported by users on the FHIR Shorthand call 6/11/2020.

       

       

      Show
      We propose to remove SUSHI from the IG and maintain that documentation outside of HL7.  The IG tries to make it clear that the FSH language is normative, but SUSHI is not. However, having implementation in the IG is confusing and inconsistent with the way other similar specifications are presented. SUSHI should not have a position of privilege over other implementations. Maintaining SUSHI separately allows it to freely evolve, outside the formal standards process.     This was discussed and supported by users on the FHIR Shorthand call 6/11/2020.    
    • Kramer/Rhodes: 14-0-0
    • Correction
    • Compatible, substantive

      The suggests a tight integration between Sushi and the Shorthand specification. Unless Sushi becomes a part of the specification (I would not object), maybe we should rewrite the specification is to show the progress to generating an IG without mentioning Sushi and then state that Sushi implements this. The Sushi specifics would then be part of the Sushi documentation adn not ShortHand.

            Assignee:
            Unassigned
            Reporter:
            Bas van den Heuvel
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: